Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
A build framework for .Net projects
C# Perl Other
Branch: master

Merge pull request #16 from featurist/task_assembly_names

naming your tasks readme sentence that actually makes sense
latest commit 15bce6548f
@refractalize authored
Failed to load latest commit information.
Bounce.Console.Tests case-insensitivity for task names
Bounce.Console better exception handling
Bounce.Framework.IntegrationTests support for web sites
Bounce.Framework.Tests case-insensitivity for task names
Bounce.Framework case-insensitivity for task names
Bounce.TestHelpers moved all legacy code into LegacyBounce
Bounce parsing LogOptions from command line
Build case-insensitivity for task names
LegacyBounce.Framework.Tests moved all legacy code into LegacyBounce
LegacyBounce.Framework some major changes in logs, shell, nunit and msbuild
MultiStageTargets DependsOn now just ITasks, versions for Downloads target
References Better unit testing with SharpTestEx;
TestBounceAssembly case-insensitivity for task names
VeryLongRunningConsole target version 3.5 for build config Debug_3_5
docs commentary
.gitignore case-insensitivity for task names
Bounce.Framework.nuspec case-insensitivity for task names
Bounce.sln nunit path
Bounce.sln.DotSettings adding VS classes
LICENSE Edited LICENSE via GitHub
README.md naming your tasks readme sentence that actually makes sense
SolutionAssemblyInfo.cs refactoring MS build stuff, now exits with 1 with exceptions

README.md

Bounce

A task runner for .Net.

(theme track: Bounce, Rock, Skate, Roll - Vaughan Mason & Crew)

Install

Bounce can be found on NuGet, simply:

PM> Install-Package Bounce

Then, make sure that your bounce project's output directory is the Bounce folder, in the root of your solution. bounce.exe looks for this folder in the current and all parent directories. For example, go to your project settings, go to the Build tab, then enter ..\Bounce into the Output path box.

What is it good for?

Put simply, it's a way to create a project toolbox that can be operated from the command line, not unlike Rake.

Imagine you have this in your project:

using System;
using Bounce.Framework;

namespace MyProject.Bounce {
    public class Stuff {
        [Task]
        public void HelloWorld() {
            Console.WriteLine("hello, world!");
        }
    }
}

You could easily call it from the command line like this:

> bounce HelloWorld
hello, world!

Of course, you can pass arguments too:

using System;
using Bounce.Framework;

namespace MyProject.Bounce {
    public class Stuff {
        [Task]
        public void Hello(string name) {
            Console.WriteLine("hello, {0}!", name);
        }
    }
}

Then:

> bounce Hello /name Bob
hello, Bob!

And those arguments can even have useful defaults:

using System;
using Bounce.Framework;

namespace MyProject.Bounce {
    public class Stuff {
        [Task]
        public void Hello(string name = "all") {
            Console.WriteLine("hello, {0}!", name);
        }
    }
}

Then:

> bounce Hello
hello, all!

And, if you've forgotten what you can do, just run bounce and it will tell you:

> bounce
usage: bounce task [options]

tasks:

    MyProject.Bounce.Stuff.HelloWorld

    MyProject.Bounce.Stuff.Hello
        /name:string = all

Naming your tasks project

Ensure your project produces an assembly ending with ".Bounce.dll" or an executable ending with ".Bounce.exe" (both case-insensitive). Bounce only looks for tasks in these assemblies, so that it can start up really quickly.

Bounce has a bunch of utilities that make it easy to build VisualStudio projects, as well as deploy to IIS sites. More documentation to come.

Something went wrong with that request. Please try again.