Dear readers,

this may be a rather stupid question since i'm not very experienced with the .Net framework.

I installed Version 1.0, 1.1 and 2.0 of the framework on my machine, and am working with Visual Studio 2005. I compiled the sources of an application with VS that was written for .Net 1.0 and it works fine on my machine under .Net 2.0.

The application has to run on another machine with only .Net Version 1.0, but it does not work. Most probably I made changes to the source not compatible with .Net 1.0.

My Question is, if there is a way to *force* VS to compile the application for Version 1.0 or any other way for me to recognize, if my binaries are 1.0 compatible.

Thank's for your help,

SM

Hi there,

Not with VS 2005. It can't produce 1.0 or 1.1 compatible assemblies.

You need VS 2002 (or 2003 if you want to compile for 1.1) or the SDK to compile at the command line.

Multi-targeting is introduced in VS 2008, but only targets 2.0, 3.0 and 3.5, not 1.x.

Cheers,

Imar
---------------------------------------
Imar Spaanjaars
http://Imar.Spaanjaars.Com
Everyone is unique, except for me.
Author of ASP.NET 2.0 Instant Results and Beginning Dreamweaver MX / MX 2004
Want to be my colleague? Then check out this post.

Hi Imar,

that's bad news...

Thank you!

Each framework comes with the compilers. You don't need to have the SDK just to compile an app. Look for the files csc.exe and vbc.exe in the framework directories. Here are example paths:

D:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\csc.e xe
D:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\jsc.e xe
D:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\vbc.e xe
D:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\vjc.e xe
D:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\csc. exe
D:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\jsc. exe
D:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\vbc. exe
D:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\vjc. exe
D:\WINDOWS\Microsoft.NET\Framework\v3.5\csc.exe
D:\WINDOWS\Microsoft.NET\Framework\v3.5\vbc.exe

One option you might have is to use a tool like NAnt to build your app. You can specify which framework to target and there are tools with it that can work with solution files and such. There's a learning curve, so you might be better off just finding VS2003 somewhere and building it with that.

-Peter

Yep, Peter is correct; you don't need the SDK.

Is upgrading the .NET Framework on the target machine an option?

Imar
---------------------------------------
Imar Spaanjaars
http://Imar.Spaanjaars.Com
Everyone is unique, except for me.
Author of ASP.NET 2.0 Instant Results and Beginning Dreamweaver MX / MX 2004
Want to be my colleague? Then check out this post.