Switching between .net 1 and 2 ?
-
Hi! I use VS 2005, and C#. If framework 1 and framework 2 installed, in a project I use only .net 1 compatible thinks, but when I compile the executable, and transfer it to a machine witch haven't got .net 2, gon erro message. How can I adjust my project to require only .net 1? Thanks for help.
-
Hi! I use VS 2005, and C#. If framework 1 and framework 2 installed, in a project I use only .net 1 compatible thinks, but when I compile the executable, and transfer it to a machine witch haven't got .net 2, gon erro message. How can I adjust my project to require only .net 1? Thanks for help.
Unfortunately for you, VS 2005 targets .NET 2 only. In other words, you can't develop .NET 1 applications with it. What you could do is to create an installer for your application which installs the .NET Framework 2 Redistributable on the client.
the last thing I want to see is some pasty-faced geek with skin so pale that it's almost translucent trying to bump parts with a partner - John Simmons / outlaw programmer
Deja View - the feeling that you've seen this post before. -
Unfortunately for you, VS 2005 targets .NET 2 only. In other words, you can't develop .NET 1 applications with it. What you could do is to create an installer for your application which installs the .NET Framework 2 Redistributable on the client.
the last thing I want to see is some pasty-faced geek with skin so pale that it's almost translucent trying to bump parts with a partner - John Simmons / outlaw programmer
Deja View - the feeling that you've seen this post before.Really ? I thought that by changing some setting (I would guess inside AssemblyInfo.cs or maybe in a manifest file) one could tell .NET that the preferred version would be 2.0 but if that was not available .NET 1.1 (or 1.0) could be used instead. Of course as soon as some 2.0 specific feature would get accessed, it would throw when running on 1.x I dont know the details but would like to know more about it... Greetings,
Luc Pattyn
-
Really ? I thought that by changing some setting (I would guess inside AssemblyInfo.cs or maybe in a manifest file) one could tell .NET that the preferred version would be 2.0 but if that was not available .NET 1.1 (or 1.0) could be used instead. Of course as soon as some 2.0 specific feature would get accessed, it would throw when running on 1.x I dont know the details but would like to know more about it... Greetings,
Luc Pattyn
There is a way of doing it, but it means that you have to compile up outside of Visual Studio. VS2005 uses the .NET 2 compiler. Providing that you haven't used any of the .NET2 features such as partial classes etc..., then you can actually compile the application from the command line using the .NET 1.1 csc.exe compiler. It's not neat, but it does work.
the last thing I want to see is some pasty-faced geek with skin so pale that it's almost translucent trying to bump parts with a partner - John Simmons / outlaw programmer
Deja View - the feeling that you've seen this post before. -
There is a way of doing it, but it means that you have to compile up outside of Visual Studio. VS2005 uses the .NET 2 compiler. Providing that you haven't used any of the .NET2 features such as partial classes etc..., then you can actually compile the application from the command line using the .NET 1.1 csc.exe compiler. It's not neat, but it does work.
the last thing I want to see is some pasty-faced geek with skin so pale that it's almost translucent trying to bump parts with a partner - John Simmons / outlaw programmer
Deja View - the feeling that you've seen this post before.I hate to swear in a forum where most people use Visual Studio but here goes... How about SharpDevelop? It can target either .net 1.1, .net 2.0, Boo and Mono. It can also import projects from Visual Studio. It doesn't claim to be a replacement for VS but maybe it's worth a try.
Regards Wayne Phipps ____________ Time is the greatest teacher... unfortunately, it kills all of its students View my Blog
-
Unfortunately for you, VS 2005 targets .NET 2 only. In other words, you can't develop .NET 1 applications with it. What you could do is to create an installer for your application which installs the .NET Framework 2 Redistributable on the client.
the last thing I want to see is some pasty-faced geek with skin so pale that it's almost translucent trying to bump parts with a partner - John Simmons / outlaw programmer
Deja View - the feeling that you've seen this post before.