- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
In VS2005, the MyDocumentsLocation registry key appears that it must point to the real MyDocuments folder, which for me is on a network server, resulting in a 90% reduction in compile speed when connected via VPN, as VS appears to access this folder during the Build process (even if it does no do anything in the folder).
If the MyDocumentsLocation key gets changed even to point to where the vssettings file have been exported (in my case C:\Dev and the Visual Studio2005 subfolders, on opening VS2005, it fails to find the file in MyDocuments, so resets all the registry keys which were pointing to C:\Dev back to point to the network folder.
There have been hints on this forum earlier that this behaviour has been fixed in VS2008. Can anyone confirm that beforeI spend money to upgrade to VS2008? I need to have all VS files on my local machine while still connected to the network via VPN. By corporate policy MyDocuments must be on the network machine.
Thanks,
David
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Can I have VS2005 and VS2008 coexisting on the same machine?
Thanks,
David
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Steve,
I now have VS2008 Protrial version installed. How do I get IVF integrated with VS2008? Do I need to do another install of IVF or is there a shorter way? I still have IVF integrated with VS2005 also.
Thanks,
David
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
"Modify". You should then be able to choose integration into VS2008 to add.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
"Modify". You should then be able to choose integration into VS2008 to add.
Thanks Steve. Have run the modify option and installed the Fortran Integration, however, VS2008 does not recognise Fortran. Can't see any diagnostics from the integration run, it appeared to run successfully. Any ideas what to check? Any possibilty that the Trial version of VS2008 does not permit IVF integration?
Thanks,
David
P.S., have passed onto Premier Support as issue 547462.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Steve,
Thanks, that fixed the installation issues.
I can now confirm that when connected to the VPN, compile times for VS2008 and VS2005 are similar (pos. up to 20% longer for 2008). However, the issue of accessing My Documents on a network drive still exists, and as reported in a separate thread, appears to be connected to ifort and fortcom. I'll pass these comments onto Premier Support.
Thanks,
David
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page