Click here to Skip to main content
15,886,110 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
Greetings,

I want to ask about something which happened as a first time with me and it considered very .

I don`t know how this following weird thing happened but I really need your advise:

When I try to open any Visual Studio 2003 project, it always run automatically in Visual Studio 2005 and a wizard to upgrade the code is shown. So in order to open any Visual Studio 2003 project,I should select "Open With" from the "RightClick Menu" and then choose Visual Studio 2003 to open my project. or I simply run VS2003 program first then load my project.

I think it is a configuration issue or Visual Studio settings that needs to be configured well in order to change the default program of VS 2003 projects.

Please advise on the above inconvenience behavior...

Thanks in advance..
Posted

http://msdn.microsoft.com/en-us/library/ms246609(v=vs.80).aspx[^]
This link will answer your WHY.

It is not visual studio setting, but a file association with .sln/.vbproj/.csproj files.
 
Share this answer
 
Comments
dgthecodeproject 19-Sep-11 2:54am    
Thank you my friend Prerak Patel...

I just went to the Tools > Options > General in my Visual Studio 2005 and I clicked on the "Restore File Associations" button and a messagebox saying "All default file Associations has been restored" is shown, but nothing changed regarding my above problem...Is there any way or any additional actions I can try to solve it.
dgthecodeproject 19-Sep-11 9:27am    
Sorry buddy for the above comment to your solution, but when I restarted the system it worked just very fine.....

Thank you...
Prerak Patel 19-Sep-11 23:21pm    
You are welcome. :)
This is expected behavior.

No, this is not a configuration issue. This is how your system registry is set up. As a Windows developer, you're supposed to know such things. See http://msdn.microsoft.com/en-us/library/windows/desktop/cc144148%28v=vs.85%29.aspx[^].

It happened just because you installed VS 2003 first and VS 2005 later. You can easily change the file type back to VS 2003 (consult the article I referenced above), but I don't advise to do so.

Also, why do you think there is anything wrong with opening all your projects with VS 2005. I think .NET v.2.0 (targeted by VS 2005) is the first decent version of .NET; and it still has its values these days, but everything prior to this version does not worth any support. Moreover, v.2.0 can be installed on any system which can have prior versions of .NET Framework, so you have absolutely nothing to loose.

Also, you can migrate to any later version of Visual Studio and still support v.2.0 as all later versions of Visual Studio support multi-targeting and a project can be targeted to any .NET Framework version starting from 2.0 (but not earlier versions; they really go out of support).

—SA
 
Share this answer
 
Comments
dgthecodeproject 19-Sep-11 2:46am    
Thanks Mr. SAKryukov..

I think I should supposed to know such things....

As for the old .Net version, I think it worth since my client is still using more than 20 custom applications developed using Vb.Net 2003..

Thanks for your reply....

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900