Frans has posted a solution to his earlier rant about VS.NET 2003. Forgot the problem already? Let me recap:
- VS.NET 2002 targets .NET 1.0 by default
- VS.NET 2003 targets .NET 1.1 by default
- If you want to use .NET 1.1, you have to use VS.NET 2003
- If you want to use .NET 1.0, you have to use VS.NET 2002
Now numbers 3 and 4 aren’t really true, but they may as well be to Mort, who will never figure this out. Here is a summary of the solution:
- When you create a new project or open an “old” project in VS.NET 2003, the project will be setup to use the .NET 1.1 runtime. So all of the References will be to .NET 1.1 DLLs.
- To get the project back to .NET 1.0 again, remove all of the References to the 1.1 DLLs and add in references to the 1.0 DLLs.
- Restart VS.NET to make sure all the old references are really unloaded.
- Make sure you use .NET 1.0 compliant code ONLY! The intellisense will mislead you sometimes into using .NET 1.1 calls.
Now, I haven’t actually done this myself. I’m still using the side-by-side install method. If someone out there can confirm 100% that this works, please let me know.
This solution has been mentioned before on many blogs, but the real issue I have is this: Why is it this hard? Why isn’t there a project property or a tool that allows us to use 1.0 or 1.1 easily from VS.NET 2003?