Preferred version of VS?

[DavidWhite]

I am currently developing under XP using VS 2005 standard edition.

This version insists on putting some of the backup files, etc, under My Documents which due to company policy is on a network drive, which results in a 10 fold degradation of compile time performance when connected via VPN even when NO FILES are written to the network drive.

I applied to get an upgrade to 2008, but have been advised there is no upgrade path, so I need to get a new license for VS. What is the preferred version to get? We do not expect to migrate to Vista for at least 8-12 months, if at all.

Thanks,

David

[Jugoslav_Dujic]

Quoting - David White

I am currently developing under XP using VS 2005 standard edition.

This version insists on putting some of the backup files, etc, under My Documents which due to company policy is on a network drive, which results in a 10 fold degradation of compile time performance when connected via VPN even when NO FILES are written to the network drive.

I applied to get an upgrade to 2008, but have been advised there is no upgrade path, so I need to get a new license for VS. What is the preferred version to get? We do not expect to migrate to Vista for at least 8-12 months, if at all.

What happens if you edit registry keys under:
HKEY_CURRENT_USERSoftwareMicrosoftVisualStudio8.0 ?

I see some 5-6 references to /Visual Studio 2005, and the main one appears to be VisualStudioLocation. Try editing them to point to a local drive. (Make a backup of that key just in case, though changing them should not be harmful. Best, copy all the contents of your/Visual Studio 2005 to the target location first).

[DavidWhite]

Quoting - Jugoslav Dujic

What happens if you edit registry keys under:
HKEY_CURRENT_USERSoftwareMicrosoftVisualStudio8.0 ?

I see some 5-6 references to /Visual Studio 2005, and the main one appears to be VisualStudioLocation. Try editing them to point to a local drive. (Make a backup of that key just in case, though changing them should not be harmful. Best, copy all the contents of your/Visual Studio 2005 to the target location first).

You can change all of them to point to C: except MyDocumentsLocation. When all except this location are changed, MSVS appears to use these folders. However, the vssettings are still assumed to be under MyDocuments on the server. If te MyDocumentsLocation is changed by regedit, then MSVS fails to find the previous settings, and sets default values, and resets all of the values back to the original folders on the server.

[Jugoslav_Dujic]

Quoting - David White

You can change all of them to point to C: except MyDocumentsLocation. When all except this location are changed, MSVS appears to use these folders. However, the vssettings are still assumed to be under MyDocuments on the server. If te MyDocumentsLocation is changed by regedit, then MSVS fails to find the previous settings, and sets default values, and resets all of the values back to the original folders on the server.

I see. However, the registry location of settings file is also changeable in VS IDE under Tools/Options/Environment/Import and Export settings. You can move the .settings file elsewhere and point to that.

[DavidWhite]

Quoting - Jugoslav Dujic

I see. However, the registry location of settings file is also changeable in VS IDE under Tools/Options/Environment/Import and Export settings. You can move the .settings file elsewhere and point to that.

Jugoslav,

Not sure that this covers everything. VS has a registry setting MyDocumentsLocation, which I think still needs to point to the real MyDocuments. I changed everything today to point to C: and also used the Import Export as you suggest to point to C:. However, I can't test it on the VPN as I didn't bring my laptop home tonight. I'll try it tomorrow.

Thanks,

David

[Jugoslav_Dujic]

Quoting - David White

Jugoslav,

Not sure that this covers everything. VS has a registry setting MyDocumentsLocation, which I think still needs to point to the real MyDocuments. I changed everything today to point to C: and also used the Import Export as you suggest to point to C:. However, I can't test it on the VPN as I didn't bring my laptop home tonight. I'll try it tomorrow.

Thanks,

David

Ah, missed that one.

It seems that someone has had a similar issue like you before. I have to run now, but check for yourself:

http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=119764

as well as:

http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=119389

[DavidWhite]

Quoting - Jugoslav Dujic

Ah, missed that one.

It seems that someone has had a similar issue like you before. I have to run now, but check for yourself:

http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=119764

as well as:

http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=119389

Thanks, Jugoslav. I think this confirms that VS2005 is broken in respect to use of MyDocuments when not wanted by the user. Can anyone confirm that VS2008 has this bug fixed, so that VS2008 never accesses MyDocuments or any subfolders?

This issue is significant as is results in a 90% degradation of compile time performance when connected via VPN.

Thanks,


David