New Release 3.5 Configuration

Developer
Dec 8, 2010 at 4:05 AM

Before, the 3.5 specific output paths were hidden in the project file xml with no way to see them while working with the visual studio projects directory.  The need to specify specific build configurations (that is projects that should build and projects that should not build) based on the framework version has compelled me to take this a step further.  We now have Debug, Release, and Release 3.5.  Like Debug and Release, the last can be configured for AnyCPU or x86 platforms.  This should help us to cater to our 3.5 users, at least for a while longer.  Be warned... changing the build configuration to Release 3.5 does NOT change the target framework in and of itself.  It is just a dumping zone where we can specify which projects to turn on and off and specify an output path.  To build in 3.5 you must either use a macro to change the framework version:

http://www.codeproject.com/Articles/74805/Visual-Studio-2010-and-Target-Framework-Version.aspx

Or else take advantage of MSBuild or Nant.  On my computer, for instance, taking into account the new release mode, to build correctly for 3.5 x86 the command line would be:

"C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe" c:\dev\DotSpatial\DotSpatial.sln /t:rebuild /v:quiet /p:TargetFrameworkVersion=v3.5 /p:Configuration="Release 3.5" /p:Platform=x86

You can use a similar strategy, taking into account the specific layout on your computer for the path in order to build in 3.5, even though the existing projects are downloaded in 4.0.  Do not be surprized if a fresh commit to the source code repository does not build in 3.5.  This is actually the usual state, as edits update resource files in incompatible ways, so if you want to build 3.5 but don't want the headache of tweaking a bunch of resource files to say 2.0.0.0 instead of 4.0.0.0, you might want to just use the downloads section.

Ted