I'm working with Visual Basic 6.0 SP6. Many months ago I could make it run on Windows 10. My problem now is that every time I start Visual Basic, it takes too much time to open. I see the splash window:
but it takes more or less five minutes to open.
After five minutes or more, I have Visual Basic open but with the following error message:
Method '~' of object '~' failed
Any idea what's going on?
the solution for my problem is under:
VB6 IDE Slowness and 'VBKeySave5' in the Registry
I have deleted everything under vbkeysave5 and now vb6 opens very fast.
Related
Since a few days I am experiencing some weird issues with both SSMS and VS 2019:
SSMS cannot open for editing any table (right click on table name) or design: the application hangs and becomes unresponsive.
VS 2019 has become very very slow, opening windows takes a few second, compiling time for the same project has growth from 10 seconds to up to 1 minute (different projects tested)
No special errors in the Windows 10 Event Log, no other info.
Now I don't have many other details, I tried uninstalling and installing completely SSMS but didn't work.
Any help would be appreciated.
I had the same problem for weeks and finally cleared out temp files and it now works.
(C:\Users\User Account\AppData\Local\Temp)
I downloaded and installed Visual Studio 2013 Profession Trial on my Windows 7 64-bit computer ( RAM is 6 GB). But, when I start it for the first time, it says 'We're getting things ready. Thanks for your patience' and its been on for about an hour.
Is this normal with VS 2013?
EDIT 1:
I left my computer running the whole night, and by morning it had re-booted. After the re-boot, VS 2013 seems to be starting quickly. So, its hard to say why Visual Studio 2013 was taking hours to start up the first time.
If the loading is taking a long time, Alt+Tab to find a login page hidden underneath the "We're getting things ready" window. Enter your Microsoft account credentials.
This answer was originally posted by Alex K in a comment.
I had already gone past the credentials screen.
I left mine running for a while but eventually killed the process and restarted VS.
It started instantly.
I had no sign-on screen hiding behind the "We're Getting Things Ready". I ended the task in Windows Task Manager. Then I started Visual Studio again (no need to reboot). This time I noticed the option to "Sign In later". I selected this and it started up in just a couple of minutes. I then signed in after it started up. All seems to be working fine now.
I too experienced this odd first time start up 'hang' on a fresh install to a new PC. For what it's worth, my experience mirrored bassbytesbikes. I finally just killed and restarted it. No discernible ill effect... so far.
I came across this problem installing Visual Studio Premium 2013 in a VirtualBox VM. Specifically, I'd enter my login credentials and then it would hang on the 'Preparing for first time use' screen. If I killed VS and then restarted it, it'd bring up the main window but then hang before it displayed the startup page.
The solution for me was to enable 3D graphics acceleration in the VM settings. This seems to be because IE relies on 3D graphics and VS uses IE to display the start page (among other things).
As an answer, I got the same issue while creating, openning projects at visual studio 2012. Then I searched a lot about it and I learned that they fixed that problem with Visual Studio 2013 with Update 5. I got the vs2013 with update 5 and everything works well now.
For my situation the firewall was blocking the connection to Microsoft's server
I have a Visual Studio 2010 solution for an MFC application that used to run just fine on my Windows 7 machine. Today when I tried to run it, although it still compiles successfully, it gives me the following error on launch:
OLE initialization failed. Make sure that the OLE libraries are the
correct version.
Then the application closes. After some debugging, I found that the error occurs inside AfxOleInit as a result of the call to OleInitialize (return value RPC_E_CHANGED_MODE).
This application was actually provided to us by one of our vendors - so I did not write the code, and I personally have very little experience with MFC. What has me stumped is that the source code has not changed since the last time I ran it on this same machine (which was months ago). The only thing I can think of is that I have installed Visual Studio 2012 (alongside 2010) on this PC since the last time I successfully ran this application - could this have indirectly messed up references or DLL versions?
After spending some time Google searching for a solution and coming up with nothing, I am turning to you for any tips or suggestions you may have. Thanks in advance for your time and assistance.
I'm working on a solution in Visual Studio (v10.0.30319.1) which contains 8 C# projects (WPF Application and Class Libraries). I've been working on this solution for several months, but yesterday I started having problems with Visual Studio hanging for some time when starting and stopping my app in the debug environment.
I first notice it when I stop the application and VS hangs for around 5 seconds. I then press F5 to start again and it takes 5-10 seconds to start. Then I stop the application and it takes about 10 seconds to stop. The problem subsequently worsens until I reboot the computer (I'm not sure if restarting VS is sufficient - I will test and update the question when it happens again).
Once the computer has been restarted, I cannot replicate the problem, but I know it will creep up on me again today.
While the problem is happening, one of the cores is at 100% usage. Memory usage for devenv.exe is normal at a bit over 200MB, and not increasing.
The computer is quite powerful and everything else is working correctly so I'm sure it's not a resource issue.
Did you update VS2010 with Service Pack 1?
Microsoft Visual Studio 2010 Service Pack 1 Download
Be warned, although the page says it's only an 800 KB download, what is actually downloaded is a downloader that downloads over 800 MB of patches. (That's a lot of "downloads" :P)
Delete your solution user option files i.e. {SolutionName}.suo and {SolutionName}.docstates.suo
It worked for me, before doing that I tried #Casey solution but it didn't work.
so first try deleting files, if it do not work then update VS2010 and then delete files again.
MY VS2010 crashes dozens of times a day. Compare that to 2008 and 2005 which were rock solid.
Is 2010 known to be susceptible to crashing? Or could it be my environment? I'm using x64 as a dev box for the first time. The only plugin I has so far is Ankh.
It crashes when doing different things. One I've noticed so far that always happens is if I press the key sequence alt-f-s-up (or any cursor key) it will crash every time.
The older versions of AnkSVN had a bug that caused constant crashing in VS2010 (1x per hour or more). Upgrade to 2.1.8420 or later.
It never crashes on my laptop. But still I find it slower than VS2008. Maybe because of the new powerful features.
VS2010 is solid for me on x64.
Is that key sequence tied to Ankh? If so that might be the cause. Does this sequence also crash VS if you use it in a new project?
No crashes here, been running VS2010 on Win7x64 for quite awhile. Are you using version control? Try removing that plugin you mentioned, at least for a while, to see if the crash rate changes.
I had around 5 crashes last few days on Win7 Pro x64. And it happend without any concrete reason...
I found intresting page http://www.jetbrains.net/devnet/thread/288025.
This problem can appear with Resharper 5 and TODO statement in your code.
Mine freezes the whole system on debugging from time to time. It may freeze when I start debugging for a program or after some time the debugging has been started.
Here is what I found:
http://blogs.msdn.com/b/debugger/archive/2010/01/06/visual-studio-2010-beta2-hang-while-debugging.aspx
I have disabled the IntelliTrace, but today got another hang.