apparantly the community msbuild tasks (http://msbuildtasks.tigris.org/) also have a task to generate assemblyinfo files so adding assemblyinfo files to our projects wouldn't be necessary.... so there would be no breaking changes and we can probably keep both solutions working side-to-side for now
i'll go ahead and try to get a clean msbuild script working On Mon, Feb 16, 2009 at 8:57 PM, Davy Brion <ral...@davybrion.com> wrote: > Hi guys, > > i'm trying to get everything up and running on the buildserver, and nant is > causing some problems with regards to easily being able to run tests for > various database configurations. > > Seeing as how the nant build scripts are way too complex (at least for my > taste), i propose we move to a simpler msbuild script. I have some > experience with msbuild, and while it's not perfect i do think it's simpler > than nant. > > Would there be any objections from any of you with regards to moving to > msbuild? > > There would be one breaking-change though... currently, none of our > projects have an AssemblyInfo.cs file because nant creates it (i'm told to > make sure that each AssemblyInfo.cs file contains the same versioning > information). I've never used that approach with msbuild, but there are > msbuild tasks available to keep the versioning information in synch across > projects. So if we do go ahead with this, we would have to add an > AssemblyInfo.cs file to each project again. > > Other than that, i think we can create a pretty simple script to build the > project, run the tests (for whatever database configuration you'd like) and > once that's working we can add automated binary and source packaging to the > mix as well. > > So, any objections? Or other suggestions? > > brs, > Davy >
