Visual Studio 2012 Fatal error 0x80131c39 - visual-studio

I am going bloody insane, I have installed a different type of Windows 8 (pro) at work, and now VS12 gives me this error. At home I have home edition W8 and everything works fine. I found ONLY ONE PERSON encountering this error EVER in Google, and he solved this by switching to .Net 3.5. But I am running an XNA 4.0 game (with a hack to make it work on VS12) and I don't have this option. Has anyone else EVER encountered something like this?

Related

Why does the VB6 IDE refuse to load valid add-ins?

I've recently installed VB6+SP6 on a new Windows 10 PC and it seems to work fine in itself.
But as I'm trying to get IDE add-ins working I'm running into this type of error:
This particular example is from the Microsoft add-in at this link: https://support.microsoft.com/en-us/help/837910/mouse-wheel-events-do-not-work-in-the-visual-basic-6-0-ide
but others are all doing the same thing.
I've never seen this before - what is the cause?
Thanks
EDIT: MZTools 8 and VBAdvance have WORKED even though others have not; those both had their own installer which apparently does something right.

Windows 8.1 Apps not Compiling

Recently, I needed to refresh my Windows 8.1 PC, and now that I have finally finished getting all of my programs reinstalled and everything is back to normal, I am ready to finish work on my Windows 8.1 app, but I am having an issue with compiling my apps. Every time I try to compile, I get the following error.
Now normally when I need to refresh my developer licesnse, Visual Studio tells me, but this time I didn't get any prompt at all, and that is the error that I got when trying to compile. How can I fix this? I am installing updates for Visual STudio at the moment, and I am hoping that doing so will somehow magically fix the problem, but I am also aware that it probably won't.
EDIT: Now that I have updated, the message has been shortened to "Can't resolve Windows.metadata."
For some reason, even though the Windows 8.1 SDK is supposed to be installed with Visual Studio Ultimate 2013, it wasn't for me. I was able to find the Windows 8.1 SDK by Googling it, and it came up as the top result. I installed it, and suddenly all of my errors went away and Visual Studio started recognizing them as legitimate Windows 8.1 app code.

.net framework 4 on windows server 2008

Ive got an issue, wich I just can not figure out how to fix. Ive got a pc with windows server 2008 and .net frameork 4.5 installed on it. Ive tried to run there appliction, that is running on .net framework 4.5, but it shows me an error .net framework 4 requied. Ive uninstalled NF4.5 and installed NF4 and.... the error is still there. Ive tried to compile a different application targetting .nf4(just a default informs project in VS) and it shows me the same error hen running on this PC. Searching gave me no results on this issue... Maybe somebody could help me?
Thank You very much for your attention and sorry for my bad english.
I found the solution some time ago, but had no time to answer it here. As I found out it as windows server 2008 RC, not release version and .net framework 4 or 4.5 coul be installed on it, but it will never pass the check if it is installed. So? it is a bug, but only in RC version, that is not supported by microsoft quite a long time.

ZeroC Ice demo failing

Note: I tried to post on their forum but was apparently not allowed so I went here.
I'm trying to get ZeroC Ice demos to work but I'm running into a problem.
I get this while trying both the C# and C++ demos.
Compiling works fine but when starting the server and client, nothing happens.
I have narrowed the cause down to the function ice_isA() which is called inside checkedCast().
When this function is called nothing happens, ie. nothing is returned and no error is raised, the debugging stops and the program does nothing.
What may be the cause of this?
This function is the first function called from the Ice library so it may as well have nothing to do with that specific function but instead something with my setup.
I run this on Windows 8 Dev Preview (essentially the same as Win 7 x64) with Visual Studio 2010 professional. The included Visual Studio 11 is uninstalled as it caused other problems.
Seems like it was just that it didn't work well with Windows 8. A switch back to Windows 7 solved everything.

ASP.NET MVC 3 RC VS10-KB2385361-x86 error (freezing)

I think I'm cursed in some way... I had errors while installing MVC 3 beta. and now the same thing with MVC 3 RC. I've read about this problem here : http://haacked.com/archive/2010/11/09/asp-net-mvc-3-release-candidate.aspx. But after uninstalling all the mvc-beta-nuget-asppages stuff I have the same thing hanging - this VS10-KB2385361-x86 error.
I'm on Win7 x64, and using VS 2010 x64. What might be the solution to all this? (I don't want to reinstall the whole VS because of it).
OK. I've managed to install it (after 2 days trying).
Here is what I've done:
Uninstalled ASP.NET MVC 3 run-time components,ASP.NET Web Pages run-time components. (doesn't work after this);
Reinstalled VS 2010 ( still freezes);
Launched VS (just did some work, nothing special, just writing code), then I tried installing MVC 3 RC again (it got frozen), after a while I launched installer again having the firs one opened (it prompted some message saying another installation is running), and some real magic happened because first installer suddenly started working and installed whole thing.
Don't know how it works, but everything is running well (so far).
I found this problem yesterday, but i resolve it today, ohye
1、unzip AspNetMVC3Setup.exe to a folder
2、In the AspNetMVC3Setup folder, you can install aspnetwebpages.msi and aspnetmvc3.msi and other install
I am a chinese ,so I english is not good, I found other people has the same prblem, hope you can tell them
This is due to it needing the visual studio cdrom. If you installed from MSDN mount the iso and it should work. Just tested this and it worked.
I had the same problem on Windows 7 32-bit on the first attempt, but it worked on the second try with no changes to the system. If you see this issue it's worth retrying at least one more time before trying other things.

Resources