Stop tieing VS to the .NET framework, its just a damn IDE, why cant I chose what version to target? Why must I have to chose the entire damn IDE? I now look elsewhere for an IDE that I CAN CHOOSE.

Jack,

That's excellent feedback. And now you can use the LadyBug site to provide it. As far as I understand it, Visual Studio is not tied to the .NET framework and you are free to use an IDE of your choice. I frequently edit small C# programs in Vim.

Strange, VS2002 is targeting 1.0 framework and VS2003 is targeting 1.1 on here, so you are saying I can install VS2002 and target 1.1 framework? Great!

No APPLY button on Options dialog sucks :D niggly I know but its always annoying to have to click OK then reopen the dialog for changes to take effect. I do hate uncoordinated or unthoughtout UIs

So hmm by youre explination, then I can target 2.0 framework with VS2002 IDE!! NICE! Oh wait, I do think you are very wrong though. This is what I dont like about the current VS IDE, I MUST upgrade it to target 2.0 framework etc, so yes i think it is very closely bound to the framework version.

I think what would be best is an ide much like most java ide's. you point the ide at the "framework" version you are compiling against and it works with that version.

I think now that whidbey is not responsible for building assemblies there is a greater opportunity for this to happen.

I ran into a similiar problem and found that I really would like a feature like this. i want to work in the whidbey version of vs.net. This would allow me to use the new vstf along with the refactoring, but i cant because vs.net wants to upgrade all my projects to its specific version of the framework. Now that I think about it, J# actually provided a feature similiar. You could include the 1.1.8 or 1.2 jar file in your project and intellisense for the 1.2 features.

Jack, I see what you are saying. The new version of VS requires the 2.0 version of the .NET framework and does not work with 1.1. I will ask on the internal list if there is a workaround for this.

The solution that I am using to this problem right now is to use VS 2005 for editing the project, and then to build on the command line (using nmake) for 1.1.