How to mix different compiler versions in visualstudio :?

HI

our shared project was built on vs2003.earlier they used SQLDMO in the project. Now

we need to use SQLSMO instead, which should have .NETFRAMEWORK 2.0. But from my

Knowledge vs2003 works under .netframework1.1.

Now my question is how to mix the two. my thinking in my car i have alresdy

.NETFRAMEWORK 2.0 is installed such that this SMO prject (i hav written managed code) is compiled using framework 2.0 and after

Can this be mixed with VS2003, is it possible ??? (how to compile using the .NET framework, when I try to use msbuild.exe it shows the needs of the project should be open and converts to the latest error showing how to fix this)

(or)

I need to upgrade to VS2005 (last option only)

Help me plzzzzzzzzzzzz

-1


a source to share


3 answers


The first thing to do is run the project in VS2008 (or 2005 if you can't get 8) and see how it converts - a lot of things actually convert just fine, not many changes. This will set the pain level while moving forward. Compare this to the features in newer versions of the framework, and you should have a fairly simple solution.



Also keep in mind that if some components are pretty much a dead letter, .NET 2.0 can speak and reference 1.1 assemblies most of the time, so if some parts can't convert but don't change, you can just statically reference them ...

+1


a source


My advice is not to try to standardize on a later version of Visual Studio, you can easily migrate solution / project files.



0


a source


If you need to work with the .NET framework 2.0 your options are Visual Studio 2005 or VS2008. My preference would be VS2008 as you could target different .NET frameworks rather than the earlier Visual Studios tied to one version of the framework.

If you have a bunch of other projects that you depend on, you will either have to convert them or stay on .NET 1.1 and forget about SQLSMO. I don't think you can have both. If, on the other hand, there are several other projects that depend on you building 1.1 compatible asssemblies, then you are pretty much stuck with VS2003 and can forget about SQLSMO (again).

0


a source







All Articles