VS 2010 Compiling Mixed Frameworks.
-
I have a solution with 10+ projects. Most of the projects are 100% .net 2.0. However one of the projects references a .Net 3.0 DLL. The solution compiles fine in VS2008, but will not compile with VS2010, because of the mixed frameworks. We may be able to upgrade to .Net 3.5, but that will be later on. Has anyone else found a solution to this issue? Currently the solution is in VS2005.
GSC
-
I have a solution with 10+ projects. Most of the projects are 100% .net 2.0. However one of the projects references a .Net 3.0 DLL. The solution compiles fine in VS2008, but will not compile with VS2010, because of the mixed frameworks. We may be able to upgrade to .Net 3.5, but that will be later on. Has anyone else found a solution to this issue? Currently the solution is in VS2005.
GSC
gscheek wrote:
will not compile
and what does that mean? :doh:
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]
Prolific encyclopedia fixture proof-reader browser patron addict?
We all depend on the beast below.
-
gscheek wrote:
will not compile
and what does that mean? :doh:
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]
Prolific encyclopedia fixture proof-reader browser patron addict?
We all depend on the beast below.
-
When trying to compile the solution, it contains 1000+ errors. VS2008 compiles fine with no errors.
GSC
really? that is horrible. I haven't been playing with VS2010 myself but that is not the behavior I expect, nor what I gathered from reading lots of posts in the Visual Studio forum and Lounge. Do you have .NET 2.0 installed? (yes the Framework itself, not VS2008). :)
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]
Prolific encyclopedia fixture proof-reader browser patron addict?
We all depend on the beast below.
-
When trying to compile the solution, it contains 1000+ errors. VS2008 compiles fine with no errors.
GSC
I've converted many projects from VS2008 to VS2010 and have not had any issues. Are they warnings or errors? What some of the errors you are experiencing?
I know the language. I've read a book. - _Madmatt
-
I have a solution with 10+ projects. Most of the projects are 100% .net 2.0. However one of the projects references a .Net 3.0 DLL. The solution compiles fine in VS2008, but will not compile with VS2010, because of the mixed frameworks. We may be able to upgrade to .Net 3.5, but that will be later on. Has anyone else found a solution to this issue? Currently the solution is in VS2005.
GSC
-
gscheek wrote:
but will not compile with VS2010, because of the mixed frameworks
That really should not be the case. When you opened the solution in 2010, did the conversion happen correctly?
When converting from 2005 - VS2008, it worked fine. But when converting the 2005 solution to VS2010, there was a warning for each project. The warning message was that the project is targeting 2.0 framework, but contained references to 3.0 .net dll's. If VS2008 didn't have an issue with this, why would VS2010. Also, I have VS2005, VS2008, and VS2010 installed on the same machine. Exact warning message from VS2010, it done this for several of the projects in the solution file. Your project is targeting .NET Framework 2.0 or 3.0. If your project uses assemblies requiring a newer .NET Framework, your project will fail to build. You can change the .NET Framework version by clicking Properties on the project menu and then selecting a new version in the '.NET Framework' dropdown box. (In Visual Basic, this is located on the Compile tab by clicking the 'Advanced Compiler Options...' button.)
GSC
modified on Thursday, April 29, 2010 10:08 AM
-
When converting from 2005 - VS2008, it worked fine. But when converting the 2005 solution to VS2010, there was a warning for each project. The warning message was that the project is targeting 2.0 framework, but contained references to 3.0 .net dll's. If VS2008 didn't have an issue with this, why would VS2010. Also, I have VS2005, VS2008, and VS2010 installed on the same machine. Exact warning message from VS2010, it done this for several of the projects in the solution file. Your project is targeting .NET Framework 2.0 or 3.0. If your project uses assemblies requiring a newer .NET Framework, your project will fail to build. You can change the .NET Framework version by clicking Properties on the project menu and then selecting a new version in the '.NET Framework' dropdown box. (In Visual Basic, this is located on the Compile tab by clicking the 'Advanced Compiler Options...' button.)
GSC
modified on Thursday, April 29, 2010 10:08 AM
gscheek wrote:
Your project is targeting .NET Framework 2.0 or 3.0. If your project uses assemblies requiring a newer .NET Framework, your project will fail to build. You can change the .NET Framework version by clicking Properties on the project menu and then selecting a new version in the '.NET Framework' dropdown box. (In Visual Basic, this is located on the Compile tab by clicking the 'Advanced Compiler Options...' button.)
Did you try this?
-
gscheek wrote:
Your project is targeting .NET Framework 2.0 or 3.0. If your project uses assemblies requiring a newer .NET Framework, your project will fail to build. You can change the .NET Framework version by clicking Properties on the project menu and then selecting a new version in the '.NET Framework' dropdown box. (In Visual Basic, this is located on the Compile tab by clicking the 'Advanced Compiler Options...' button.)
Did you try this?
yes, I was trying avoid doing this though, since in VS 2008 it worked when I targeted the 2.0 framework. After I changed all the projects to 3.5 framework, many of the errors disappeared, but now other ones have come up. So I'm trying to get those fixed.
GSC