How to manage .net versions for a complete solution

Question

4.33/5 (3 votes)

See more:

Hi,
I use VS2010 and have several c# "libraries" (source code) which are written for several .net frameworks. All of this libraries are under version control with subversion. Today I add this libraries to a project solution, select the right .net framework for each library and add a define “dotNetVersion3_5” for example. If I commit this libraries to subversion, and checked them out at another project whis is only for .net 2.0 I have to make all these changes again by hand.
Is there any chance to:
a) Define a .net version for a project solution
b) Define a “define” for a project solution
In VS2010 ?
Thx Peter

Posted 13-Feb-11 1:03am

holschbach

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Wendelius · Answer 1 · 2011-02-13T01:41:00

Hi,

Don't know if this is a feasible solution for you but I once resolved a similar problem using following ideas:
- libraries are included as references, not as source code projects
- each library had different compile outputs (using different projects), for example one for each target framework. All the binaries went to different bin folders
- all the references for the actual project were pointing to a single directory, for example C:\CurrentLibraries
- had a small CMD file which copied the desired library versions from their original output folders to C:\CurrentLibraries

This way I could easily change the actual dll's in the C:\CurrentLibraries folder to whatever versions I needed without making modifications to the references nor to the library projects. When a library source code was changed all the necessary projects were built using again a separate cmd file so each library project didn't need to be compiled separately.

This was years ago so don't know if the tools currently provide more elegant ways to do this but this was the best solution at that time.

Regards,

mika