Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

visual studio express vs visual studio 2005

Status
Not open for further replies.

csphard

Programmer
Apr 5, 2002
194
US
I need to work on an asp.net application using framework 2.0. They are using visual studio 2005. However they may not supply me with that.
I can I use visual studio express 2010 to work on this application.
I am thinking it will as me if I would like to upgrade to 4.5.

I will just say no.

Is that correct?

Thanks in advance

Howard
 
I don't think you can use VS2010 with a VS2005 project without up-converting the project. It will then be impossible for those with VS2005 to edit the project.
I've tried this with one project and it doesn't open the project without converting it.

I would like to know, too, if there is a way to do this.

Tom
 
If the question is can you modify a 2.0 project in VS2010 without converting it, the answer is no, you can't
 
I just read the following.

While some rare users will need to continue using older versions of Visual Studio for various reasons, Visual Studio 2010 makes running side-by-side installations of Visual Studio 2005 and Visual Studio 2008 virtually unnecessary because Visual Studio 2010 can target the 2.0+ frameworks.


This makes me think that I can edit a asp.net application with vs2010. I will continue looking for information but is this correct?
 
SORRY type O

So can you modify it WITHOUT converting it?

Howard
 

You probably don't want to mix older versions of VS with newer. Once you open an older project, VS will want to convert it and save changes in the .proj file indicating the newer version used. VS will ask if you want to update the framework, but it will always try to up-convert the project, and in doing so, any references will be updated and saved as needed for the newer version to work properly. Older versions of VS will not be able to open the project as they will detect the project was last saved in a higher VS version.

If you absolutely had to, I would guess that you could save a copy of the .proj files and repackage it back. But you'd have to add any references and project chnages manually. Which may or may not work.




Mark

"You guys pair up in groups of three, then line up in a circle."
- Bill Peterson, a Florida State football coach
 
Thanks.. I really appreciate the help.

This started because I may have to update an asp.net application that is using 2.0 .net framework. I know the application was created using vs2005 on a pc using windows vista.
Problem is that I can not install vs2005 beta 2 on a pc using windows 7 enterprise. I keep getting set up failed.

I keep trying to trouble shoot this but was thinking I should just work with vs2010

The following component failed to install:
Microsoft .NET Framework 2.0 Beta 2

Error Log::
-------------------------------------
[09/25/13,13:53:05] Microsoft .NET Framework 2.0 Beta 2: [2] Error code 1603 for this component means "Fatal error during installation.
"
[09/25/13,13:53:05] Microsoft .NET Framework 2.0 Beta 2: [2] Setup Failed on component Microsoft .NET Framework 2.0 Beta 2
[09/25/13,13:53:11] setup.exe: [2] ISetupComponent::pre/Post/Install() failed in ISetupManager::InstallManagerHelper() with HRESULT -2147023293.
[09/25/13,13:53:11] setup.exe: [2] Component error string not specified in ISetupManager::AddToActionResultCollection()
[09/25/13,13:53:12] VS70pgui: [2] DepCheck indicates Microsoft .NET Framework 2.0 Beta 2 is not installed.
[09/25/13,13:53:12] VS70pgui: [2] Unknown component status forMSXML 6.0 Parser
[09/25/13,13:53:12] VS70pgui: [2] DepCheck indicates Microsoft Visual Studio 2005 Team Suite Edition Beta 2-English was not attempted to be installed.
[09/25/13,13:53:12] VS70pgui: [2] Unknown component status for.NET Compact Framework 1.0 SP3
[09/25/13,13:53:12] VS70pgui: [2] Unknown component status for.NET Compact Framework 2.0
[09/25/13,13:53:12] VS70pgui: [2] Unknown component status forMicrosoft Visual Studio Tools for Office System 2005 Runtime Beta 2
[09/25/13,13:53:12] VS70pgui: [2] Unknown component status forMicrosoft Visual J# Redistributable Package 2.0 Beta 2
[09/25/13,13:53:12] VS70pgui: [2] Unknown component status forSQL Server 2005 Mobile Edition
[09/25/13,13:53:12] VS70pgui: [2] Unknown component status forMicrosoft SQL Server 2005 Express Edition April CTP
[09/25/13,13:53:12] VS70pgui: [2] Unknown component status forMicrosoft Device Emulator version 1.0 Beta 2
[09/25/13,14:02:30] Microsoft .NET Framework 2.0 Beta 2: [2] Error code 1603 for this component means "Fatal error during installation.
"
[09/25/13,14:02:30] Microsoft .NET Framework 2.0 Beta 2: [2] Setup Failed on component Microsoft .NET Framework 2.0 Beta 2
[09/25/13,14:02:36] setup.exe: [2] ISetupComponent::pre/Post/Install() failed in ISetupManager::InstallManagerHelper() with HRESULT -2147023293.
[09/25/13,14:02:36] setup.exe: [2] Component error string not specified in ISetupManager::AddToActionResultCollection()
[09/25/13,14:02:37] VS70pgui: [2] DepCheck indicates Microsoft .NET Framework 2.0 Beta 2 is not installed.
[09/25/13,14:02:37] VS70pgui: [2] Unknown component status forMSXML 6.0 Parser
[09/25/13,14:02:37] VS70pgui: [2] DepCheck indicates Microsoft Visual Studio 2005 Team Suite Edition Beta 2-English was not attempted to be installed.
[09/25/13,14:02:37] VS70pgui: [2] Unknown component status for.NET Compact Framework 1.0 SP3
[09/25/13,14:02:37] VS70pgui: [2] Unknown component status for.NET Compact Framework 2.0
[09/25/13,14:02:37] VS70pgui: [2] Unknown component status forMicrosoft Visual Studio Tools for Office System 2005 Runtime Beta 2
[09/25/13,14:02:37] VS70pgui: [2] Unknown component status forMicrosoft Visual J# Redistributable Package 2.0 Beta 2
[09/25/13,14:02:37] VS70pgui: [2] Unknown component status forSQL Server 2005 Mobile Edition
[09/25/13,14:02:37] VS70pgui: [2] Unknown component status forMicrosoft SQL Server 2005 Express Edition April CTP
[09/25/13,14:02:37] VS70pgui: [2] Unknown component status forMicrosoft Device Emulator version 1.0 Beta 2
[09/26/13,07:52:28] Microsoft .NET Framework 2.0 Beta 2: [2] Error code 1603 for this component means "Fatal error during installation.
"
[09/26/13,07:52:28] Microsoft .NET Framework 2.0 Beta 2: [2] Setup Failed on component Microsoft .NET Framework 2.0 Beta 2
[09/26/13,07:52:33] setup.exe: [2] ISetupComponent::pre/Post/Install() failed in ISetupManager::InstallManagerHelper() with HRESULT -2147023293.
[09/26/13,07:52:33] setup.exe: [2] Component error string not specified in ISetupManager::AddToActionResultCollection()
[09/26/13,07:52:34] VS70pgui: [2] DepCheck indicates Microsoft .NET Framework 2.0 Beta 2 is not installed.
[09/26/13,07:52:34] VS70pgui: [2] Unknown component status forMSXML 6.0 Parser
[09/26/13,07:52:34] VS70pgui: [2] DepCheck indicates Microsoft Visual Studio 2005 Team Suite Edition Beta 2-English was not attempted to be installed.
[09/26/13,07:52:34] VS70pgui: [2] Unknown component status for.NET Compact Framework 1.0 SP3
[09/26/13,07:52:34] VS70pgui: [2] Unknown component status for.NET Compact Framework 2.0
[09/26/13,07:52:34] VS70pgui: [2] Unknown component status forMicrosoft Visual Studio Tools for Office System 2005 Runtime Beta 2
[09/26/13,07:52:34] VS70pgui: [2] Unknown component status forMicrosoft Visual J# Redistributable Package 2.0 Beta 2
[09/26/13,07:52:34] VS70pgui: [2] Unknown component status forSQL Server 2005 Mobile Edition
[09/26/13,07:52:34] VS70pgui: [2] Unknown component status forMicrosoft Device Emulator version 1.0 Beta 2
[09/26/13,10:08:40] Microsoft .NET Framework 2.0 Beta 2: [2] Error code 1603 for this component means "Fatal error during installation.
"
[09/26/13,10:08:40] Microsoft .NET Framework 2.0 Beta 2: [2] Setup Failed on component Microsoft .NET Framework 2.0 Beta 2
[09/26/13,10:08:46] setup.exe: [2] ISetupComponent::pre/Post/Install() failed in ISetupManager::InstallManagerHelper() with HRESULT -2147023293.
[09/26/13,10:08:46] setup.exe: [2] Component error string not specified in ISetupManager::AddToActionResultCollection()
[09/26/13,10:08:46] VS70pgui: [2] DepCheck indicates Microsoft .NET Framework 2.0 Beta 2 is not installed.
[09/26/13,10:08:46] VS70pgui: [2] Unknown component status forMSXML 6.0 Parser
[09/26/13,10:08:46] VS70pgui: [2] DepCheck indicates Microsoft Visual Studio 2005 Team Suite Edition Beta 2-English was not attempted to be installed.
[09/26/13,10:08:46] VS70pgui: [2] Unknown component status for.NET Compact Framework 1.0 SP3
[09/26/13,10:08:46] VS70pgui: [2] Unknown component status for.NET Compact Framework 2.0
[09/26/13,10:08:46] VS70pgui: [2] Unknown component status forMicrosoft Visual Studio Tools for Office System 2005 Runtime Beta 2
[09/26/13,10:08:46] VS70pgui: [2] Unknown component status forMicrosoft Visual J# Redistributable Package 2.0 Beta 2
[09/26/13,10:08:46] VS70pgui: [2] Unknown component status forSQL Server 2005 Mobile Edition
[09/26/13,10:08:46] VS70pgui: [2] Unknown component status forMicrosoft SQL Server 2005 Express Edition April CTP
[09/26/13,10:08:46] VS70pgui: [2] Unknown component status forMicrosoft Device Emulator version 1.0 Beta 2
[09/27/13,11:12:51] Microsoft .NET Framework 2.0 Beta 2: [2] Error code 1603 for this component means "Fatal error during installation.
"
[09/27/13,11:12:52] Microsoft .NET Framework 2.0 Beta 2: [2] Setup Failed on component Microsoft .NET Framework 2.0 Beta 2
[09/27/13,11:12:57] setup.exe: [2] ISetupComponent::pre/Post/Install() failed in ISetupManager::InstallManagerHelper() with HRESULT -2147023293.
[09/27/13,11:12:57] setup.exe: [2] Component error string not specified in ISetupManager::AddToActionResultCollection()
[09/27/13,11:12:58] VS70pgui: [2] DepCheck indicates Microsoft .NET Framework 2.0 Beta 2 is not installed.
[09/27/13,11:12:58] VS70pgui: [2] Unknown component status forMSXML 6.0 Parser
[09/27/13,11:12:58] VS70pgui: [2] DepCheck indicates Microsoft Visual Studio 2005 Team Suite Edition Beta 2-English was not attempted to be installed.
[09/27/13,11:12:58] VS70pgui: [2] Unknown component status for.NET Compact Framework 1.0 SP3
[09/27/13,11:12:58] VS70pgui: [2] Unknown component status for.NET Compact Framework 2.0
[09/27/13,11:12:58] VS70pgui: [2] Unknown component status forMicrosoft Visual Studio Tools for Office System 2005 Runtime Beta 2
[09/27/13,11:12:58] VS70pgui: [2] Unknown component status forMicrosoft Visual J# Redistributable Package 2.0 Beta 2
[09/27/13,11:12:58] VS70pgui: [2] Unknown component status forSQL Server 2005 Mobile Edition
[09/27/13,11:12:58] VS70pgui: [2] Unknown component status forMicrosoft SQL Server 2005 Express Edition April CTP
[09/27/13,11:12:58] VS70pgui: [2] Unknown component status forMicrosoft Device Emulator version 1.0 Beta 2
[09/27/13,11:24:19] Microsoft .NET Framework 2.0 Beta 2: [2] Error code 1603 for this component means "Fatal error during installation.
"
[09/27/13,11:24:20] Microsoft .NET Framework 2.0 Beta 2: [2] Setup Failed on component Microsoft .NET Framework 2.0 Beta 2
[09/27/13,11:24:25] setup.exe: [2] ISetupComponent::pre/Post/Install() failed in ISetupManager::InstallManagerHelper() with HRESULT -2147023293.
[09/27/13,11:24:25] setup.exe: [2] Component error string not specified in ISetupManager::AddToActionResultCollection()
[09/27/13,11:24:25] VS70pgui: [2] DepCheck indicates Microsoft .NET Framework 2.0 Beta 2 is not installed.
[09/27/13,11:24:25] VS70pgui: [2] Unknown component status forMSXML 6.0 Parser
[09/27/13,11:24:26] VS70pgui: [2] DepCheck indicates Microsoft Visual Studio 2005 Team Suite Edition Beta 2-English was not attempted to be installed.
[09/27/13,11:24:26] VS70pgui: [2] Unknown component status for.NET Compact Framework 1.0 SP3
[09/27/13,11:24:26] VS70pgui: [2] Unknown component status for.NET Compact Framework 2.0
[09/27/13,11:24:26] VS70pgui: [2] Unknown component status forMicrosoft Visual Studio Tools for Office System 2005 Runtime Beta 2
[09/27/13,11:24:26] VS70pgui: [2] Unknown component status forMicrosoft Visual J# Redistributable Package 2.0 Beta 2
[09/27/13,11:24:26] VS70pgui: [2] Unknown component status forSQL Server 2005 Mobile Edition
[09/27/13,11:24:26] VS70pgui: [2] Unknown component status forMicrosoft SQL Server 2005 Express Edition April CTP
[09/27/13,11:24:26] VS70pgui: [2] Unknown component status forMicrosoft Device Emulator version 1.0 Beta 2

 
VS2010 can target the 2.0 framework. However, if you work on the project in VS2010, it will up-convert and it can not be modified in VS2005. I haven't tried installing VS2005 on WIN7.
Why are you using VS2005 Beta 2 and not a final version of VS2005?

Here's a link that explains how to install VS2005 on WIN7. Note that it says you need to "install both Visual Studio 2005 Service Pack 1 and the Visual Studio 2005 Service Pack 1 Update for Windows Vista".
So, I'm guessing the beta won't work.

 
Make a copy of the project first (for safety in case anything goes wrong - that is, unless you have it under source code control).

Say your solution file is called xxx.sln. Copy this to xxxV10.sln. Copy all the xxx.csproj files to xxxV10.csproj

Edit xxxV10.sln in notepad. You will see a load of .csproj entries. Change them to V10.csproj. Save the file and you are now ready to convert.

Open xxxV10.sln in VS10. It will convert the V10.sln and ...V10.csproj files to VS10 format and leave the original .csproj files intact. Exit VS10 and save everything. Check the dates of all the csproj files. All the ones without VS10.csproj should not have been modified. If it has, you've missed it out when changing xxxV10.sln file.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top