DotSpatial .NET 3.5 AutoBuild - Incorrect target framework

Developer
Nov 24, 2010 at 5:37 AM

I'm trying to use the DotSpatial auto-build from http://river.sdsc.edu:88/ with HydroDesktop.

I'm using the build DotSpatial AnyCPU Targeted at 3.5.

The target framework of this build is incorrect. It seems to be currently set to 4.0 rather than 3.5, or possibly the auto-build is using files from a wrong path. The DotSpatial libraries from the "3.5" autobuild work correctly with a .NET framework 4.0 application, but they don't work with a .NET framework 3.5 application.

Developer
Nov 24, 2010 at 2:58 PM

Yes, I was afraid of this.  The SDSC needs to update the path that it points to for the 3.5 autobuilds.  I think it is better for the long term stability if we don't build 3.5 and 4.0 into the same output folders, so I have added new output paths in the project files of each project conditional to 3.5 builds.  It works great, but I think their build script copies files out of the original output directory, and so they get the 4.0 content. The up-side of the new system is they won't have to copy the output to a new path.  The downside is that their current script is getting the wrong files.

 

Ted

Developer
Nov 24, 2010 at 6:13 PM
http://river.sdsc.edu:88/admin/editRunType.html?id=buildType:bt28

No, it's targeted at:
/property:TargetFrameworkVersion=v3.5
and I've used the IL Disasembler to look at a few of the DLL's and
confirmed that one set was .net 2.0 (+), and the other was .net 4.

They are separate projects, so these are being built in different
directories (I believe).

These use the exact same solution that is provided. So if the .net 3.5
needs to look in a different directory for .net 3.5 dll's then it
needs to be built into the solution file. Some minor hand coding may
be required.



On Wed, Nov 24, 2010 at 7:58 AM, [email removed] wrote:
> From: shade1974
>
> Yes, I was afraid of this.  The SDSC needs to update the path that it points
> to for the 3.5 autobuilds.  I think it is better for the long term stability
> if we don't build 3.5 and 4.0 into the same output folders, so I have added
> new output paths in the project files of each project conditional to 3.5
> builds.  It works great, but I think their build script copies files out of
> the original output directory, and so they get the 4.0 content. The up-side
> of the new system is they won't have to copy the output to a new path.  The
> downside is that their current script is getting the wrong files.
>
http://river.sdsc.edu:88/admin/editRunType.html?id=buildType:bt28>
>
> Ted
>
> Read the full discussion online.
>
> To add a post to this discussion, reply to this email
> ([email removed]@discussions.codeplex.com)
>
> To start a new discussion for this project, email
> [email removed]@discussions.codeplex.com
>
> You are receiving this email because you subscribed to this discussion on
> CodePlex. You can unsubscribe or change your settings on codePlex.com.
>
> Please note: Images and attachments will be removed from emails. Any posts
> to this discussion will also be available online at codeplex.com