Visual Studio and .NET Framework Home
Opening a VB6 project initiates some Visual Studio 2010 configuration operation.
5/19/2009 1:14:31 PM
User(s) can reproduce this bug
I installed Visual Studio 2010 Beta 1 on a machine that already had Visual Studio 6. Every time I open a VB6 project, VS2010 attempts to perform some configuration operation. It can be stopped immediately by clicking the Cancel button, but if left to complete it takes 10-15 minutes. Even if you let it finish, it will do the same thing again next time you open a VB6 project.
Visual Studio 2010 Beta 1
Windows XP Professional
Operating System Language
Steps to Reproduce
double-clicked on a .vbp file in Explorer
the VB6 IDE opens and displayed the splash screen
the project stops loading and a message box pops up that says, "Please wait while Windows configures Microsoft Visual Studio 2010 Professional Beta 1 - ENU..."
progress bars creep along, reset, start moving again, etc. Sometimes it says, "Gathering required information...", other times it says, "Time remaining: N seconds (or minutes)..."
finally, after about 15 minutes of this, the message box goes away and the VB6 project finally loads
The loading of a VB6 project is interrupted by some unnecessary Visual Studio 2010 configuration process.
The VB6 project should just load as normal. It has nothing to do with Visual Studio 2010.
TAP Code (if applicable)
You can indicate your satisfaction with how Microsoft handled this issue by completing this quick
3 question survey
to post a comment.
Please enter a comment.
on 10/2/2010 at 8:24 PM
It is odd. I did that fix. Did not work. I looked in the directory, folder was not there. So I made a new folder, and started up Visual Basic 6.0 again. Guess what. It somehow deleted the folder! It was not there anymore!
on 7/10/2010 at 6:03 AM
But the problem still exists，though I create the very folder。Is there some connection with my Chinese version？
on 3/23/2010 at 9:50 PM
Running Windows 7 Ultimate 64 bit. Office 2010 RC installed. VS 2010 RC.
Using macros in Excel VBA and the same thing happens all the time.
FromGAC in either x86 or 64 bit Program Files does not fix it.
Any other ideas??????
on 3/4/2010 at 5:27 AM
@JJohnson165: Yes, creating that directory made the problem go away.
on 2/17/2010 at 10:38 AM
Look in your Application event log for an MsiInstaller warnings. One of them should say something like: The resource 'C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\FromGAC\' does not exist. If you create the FromGAC folder, the problem should go away...
Jan Willem B
on 2/10/2010 at 8:20 AM
The issue is still there after installing VS2010 RC
on 7/2/2009 at 4:57 PM
We were able to address the issue. Thanks again for reporting it.
on 6/2/2009 at 7:50 AM
Thanks for taking the time to submit this feedback. We are investigating this issue, and will post an update to this bug report when we make progress.
Visual Basic IDE Program Manager
on 5/27/2009 at 3:13 PM
It happens also with Excel 2007! It is very annoying!
on 5/21/2009 at 3:17 AM
Thank you for your feedback, We are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
to post a workaround.
Please enter a workaround.
on 3/4/2010 at 5:26 AM
@Adrian Halid: Yes, creating that directory made the problem go away.
on 3/2/2010 at 9:44 PM
We've seen similar issues fixed by determining which directory VS expects to be created and then creating it. We’ve fixed this in our RTMRel product and the Visual Studio tools for office team has put an additional test to check for project. To work around this issue try creating the following directory. Open an elevated command prompt and type the following command and then open project again. Let me know if this fixes the issue.
Md "%ProgramFiles(x86)%\Microsoft Visual Studio 10.0\common7\IDE\FromGAC"
on 5/21/2009 at 7:40 AM
Disabling all the Add-ins is not an option. I can't work without them. You can click the Cancel button on the on the message box as soon as it appears and loading of the VB6 project will continue as normal. So, this really isn't a showstopper, it's just really annoying.
on 5/20/2009 at 8:54 PM
Disable all add-ins except Source Code Control (if you are using it) to make this problem go away.
© 2014 Microsoft