Build.Net Release 0.6.2

  • Thread starter Thread starter Julian
  • Start date Start date
J

Julian

Build.Net is a build tool that parses and builds VS.NET project files.

Build.Net is run from the command line. It recursively searches a
directory for VS.NET project files to build. This directory to be
searched is passed in via the '-find' parameter. Any *.csproj OR
*.vbproj that is found is parsed into an object model and added to the
build list. Any *pattern* in the -findexclude parameter will NOT be
built. Build.Net will attempt to build any dependcies that does not
already exist in the output directory. The dependency is *hopefully*
in the build list. Your project files should all have the same output
directory (OutputPath).

http://serial.n6k.com/build.net/

Additional Features
-------------------
Visual Source Safe integration. Build.Net will perform a vss get from
the repository to the directory listed in the -find parameter by using
-vssget or -g command.

Email notification. Build.Net will send email to an address or
addresses separated by ';', when the build completes with Sucess or
Failure. Double quotes should be used with email addresses.

Logging. Build.Net logs the full build process. Format is
Build.Net-YYYYMMdd
 
Julian said:
Build.Net is a build tool that parses and builds VS.NET project files.

Build.Net is run from the command line. It recursively searches a
directory for VS.NET project files to build. This directory to be
searched is passed in via the '-find' parameter. Any *.csproj OR
*.vbproj that is found is parsed into an object model and added to the
build list. Any *pattern* in the -findexclude parameter will NOT be
built. Build.Net will attempt to build any dependcies that does not
already exist in the output directory. The dependency is *hopefully*
in the build list. Your project files should all have the same output
directory (OutputPath).
Click to expand...

csprog and vbproj? So why post this to the VC++ group if it doesn't
handle vcproj files?
 
Back
Top