Comments on: rake-dotnet 0.1.9 http://blog.neverrunwithscissors.com/2009/07/07/rake-dotnet-0-1-9/ "Inspiration? Inspiration is the momentary cessation of stupidity" Wed, 25 Aug 2010 15:04:53 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Pete http://blog.neverrunwithscissors.com/2009/07/07/rake-dotnet-0-1-9/comment-page-1/#comment-223 Pete Sat, 12 Sep 2009 17:25:26 +0000 http://blog.neverrunwithscissors.com/?p=238#comment-223 That's right, msbuild will consider all the projects touched. rake has the same kind of incremental build as msbuild does with a solution file - only building those parts that have source files that are newer than the file-created of the output DLL. At present, rake-dotnet doesn't support taking the source-control revision from anywhere other than the directory that rake is being run from. This assumption works for me, because I've assumed that all code lives in the same repository. I think it ought to be possible to get rdn to take the revision from each project-directory instead, when generating the AssemblyInfo files - would that meet your need? If so, I'll open a github issue (or you could, if I've missed what you meant?). That’s right, msbuild will consider all the projects touched. rake has the same kind of incremental build as msbuild does with a solution file – only building those parts that have source files that are newer than the file-created of the output DLL.

At present, rake-dotnet doesn’t support taking the source-control revision from anywhere other than the directory that rake is being run from. This assumption works for me, because I’ve assumed that all code lives in the same repository. I think it ought to be possible to get rdn to take the revision from each project-directory instead, when generating the AssemblyInfo files – would that meet your need? If so, I’ll open a github issue (or you could, if I’ve missed what you meant?).

]]> By: Ronny Hanssen http://blog.neverrunwithscissors.com/2009/07/07/rake-dotnet-0-1-9/comment-page-1/#comment-217 Ronny Hanssen Wed, 09 Sep 2009 10:08:15 +0000 http://blog.neverrunwithscissors.com/?p=238#comment-217 Nice. I have a question though. I need to write incremental builds, where I only build and update the assemblyinfo-file for the actual projects being built. I need to have a clean version built, specifically for testing (is everything still working if we have to build everything from scratch), but I also need my application's different dll's to have independent versioning. Do you know how to get this done? I know that MSBuild can take a solution-file and then only build the projects that needs building, and in correct dependency-order. But, if I use your method and update all assemblyInfo-files surely MSBuild will consider all projects "touched", wouldn't it? Thanks, Ronny Nice.

I have a question though. I need to write incremental builds, where I only build and update the assemblyinfo-file for the actual projects being built.

I need to have a clean version built, specifically for testing (is everything still working if we have to build everything from scratch), but I also need my application’s different dll’s to have independent versioning. Do you know how to get this done?

I know that MSBuild can take a solution-file and then only build the projects that needs building, and in correct dependency-order. But, if I use your method and update all assemblyInfo-files surely MSBuild will consider all projects “touched”, wouldn’t it?

Thanks,
Ronny

]]>