Microsoft Visual Studio 10.0 Can not Load mso.dll for designer view - asp.net

I am doing an ASP project and I am having the following problem when trying to switch from code to designer view .A pop up appears and visual studio shuts down.
cannot load "c:\PROGRA~2\MICROS~2.0\Common7\packages\vwd\mso.dll
here are some solution from the Internet that I tried and did not work out
1. I reinstalled the software ( visual studio 10.0 )
2. Some suggest to user less privileged account, so I also tried that . Did not work .
3.I have Microsoft Office Installed and its working just fine
3. I read some vague thing about a certain patch ( but could not find it )
4. The mso.dll file is NOT missing or deleted .
Here is my installation folder for my visual studio 10.0
C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE
HELP ! ? !

I know this post from long ago but if someone still have an issue:
Update PATH environment variables with below proper path:
C:\Program Files\Microsoft Visual Studio 10.0\Common7\Packages
C:\Program Files\Microsoft Visual Studio 10.0\Common7\Packages\vwd.

To solve the problem, I tried many solutions available on the web. The one that really worked for me was:
First, I used the utility "Depency Walker". I opened the "C:\Program Files\Microsoft Visual Studio 10.0\Common7\Packages\vwd\mso.dll" file with this utility and it found missing Msvcr90.dll file dependency.
Then download the Microsoft Visual C ++ 2008 Service Pack 1 Redistributable Package MFC Security Update and run it.
The problem was solved.

Related

Migration error to Visual Studio 2017

I would like to migrate my ASP.NET Core project to Visual Studio 2017 Community Edition, but I'm getting an error.
E:\xxxxxx\projectName.xproj : error : The imported project
"C:\Program Files (x86)\Microsoft Visual
Studio\2017\Community\MSBuild\Microsoft\VisualStudio\v15.0\DotNet\Microsoft.DotNet.Props"
was not found. Also, tried to find "DotNet\Microsoft.DotNet.Props" in
the fallback search path(s) for $(VSToolsPath) - "C:\Program Files
(x86)\MSBuild\Microsoft\VisualStudio\v15.0" . These search paths are
defined in
"C:\Users\mskur\AppData\Local\Microsoft\VisualStudio\15.0_0cd52d80\devenv.exe.config".
Confirm that the path in the declaration is correct, and that
the file exists on disk in one of the search paths.
E:\xxxxxx\projectName.xproj
Do you need something else which can help you to investigate problem?
Thanks in advance.

"One or more error occurred" When right clicking form elements

When working with either a Custom or Standard Form in AX 7, right-clicking on the Design Node, Grid Container, Group Control etc. Visual Studio freezes for a couple of seconds then displays this error message: "One or more error occurred".
This is not isolated on my development VM, coworkers also experiencing the same issue.
Anyone ran into this problem?
I think I remember running into this and you can follow these steps to clear the cache.
Delete the contents from the following folders
C:\Users\<>\AppData\Local\Microsoft\Team Foundation
C:\Users\<>\AppData\Local\Microsoft\VisualStudio
C:\Users\<>\AppData\Local\Microsoft\VSCommon
Go to the Visual Studio IDE folder in command prompt and Run the following command “devenv /resetuserdata” from the Visual Studio IDE folder.
Typical location for 64 bit: C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE
Typical location for 32 bit: C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE
Per:
https://blogs.msdn.microsoft.com/willy-peter_schaub/2010/09/15/if-you-have-problems-with-tfs-or-visual-studio-flush-the-user-cache-or-not/

Installation of Qt 5.6.1 MSVC 2015 Update 3

I have encountered the following problem during a routine Qt 5 installation combined with Visual Studio 2015:
I did these steps:
Installed visual studio 2015 enterprise
Updated it to Update 3 (recent)
Installed X64 Debuggers And Tools-x64_en-us + 32bit
Installed Qt 5.6
I inspected the automatic detection of compiler, debuggers and the build environment comparing it to another machine, and all look OK.
Created new test projects using empty console application, Qt quick.
All fail during compilation step, with exactly 20 errors:
20 compile errors
I noted that the errors appears in code files of VC++ include path
for example in the code file xtr1common (first error in the picture).
I installed and used Qt with MSVC including MSVC Update 2 many times before but not with Update 3. What went wrong? How do I fix the problem?
Just go to windows updates and remove the visual studio update 3. This will return visual studio to original status including the C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\INCLUDE folder.
I hope there is a better answer than this because I needed the visual studio update 3 for other purposes than Qt. But what to do if the Qt 5.6.1 is not compatible with Visual Studio 2015 update 3. If someone have a better answer please hit me.

ASP.NET project templates missing after installing update 3 for Visual Studio 2013

After I installed the latest Visual Studio 2013 update, I cannot see any templates in the new project popup. Everything is disabled.
How can I get them back?
I found the answer from here.
All I had to do is to delete
Microsoft.VisualStudio.Web.WindowsAzure.Contracts.dll
and
Microsoft.VisualStudio.Web.WindowsAzure.Explorer.dll
in
C:\Program Files (x86)\Microsoft Visual Studio
12.0\Common7\IDE\PrivateAssemblies

Qt in Visual Studio 2012, "error C1083: Cannot open include file: 'stddef.h': No such file or directory"

I errors and a warning when I try to compile some openGL projects for Qt.
Many of them are:
error C1083: Cannot open include file: 'stddef.h': No such file or directory d:\documents\code\qt5pack\qt-everywhere-opensource-src-5.0.1\qtbase\src\corelib\global\qglobal.h 46 1 01-createcontext
Using Qt and OpenGL with Visual Studio or Creator is giving me a headache. I noticed that my $VCInstallDir is to VC10.. I don't know if that is anything important.
I had this exact problem and struggled with it for a few days. My situation was this:
Had VSE 2013 installed, Qt 5.3.1 (64 bit), and OpenCV 2.4.9 (64 bit). Was working fine, building projects in QtCreator + OpenCV using the VS 2013 compiler. Then I was trying to incorporate CUDA and found that the CUDA compiler was not compatible with VS 2013 so had to downgrade to 2012. That's when the problem started. Tried repairing, uninstalling, reinstalling...nothing seemed to work. I kept reading in posts that it probably had something to do with the Microsoft Platform SDK not being installed or installed correctly. So I went to this site to download a fresh copy and noticed that down the page there was a section that described how to uninstall it, including some manual steps.
http://msdn.microsoft.com/en-us/windows/desktop/bg162891.aspx
So, here's what I did to get everything working. Maybe all these steps were not required, but this is what I did.
1) uninstall VSE 2012 (I had already gotten rid of VSE 2013), and deleted the folders C:\Program Files (x86)\Microsoft Visual Studio 11.0 and C:\Program Files (x86)\Microsoft Visual Studio 10.0 which both had some residual stuff in them after the uninstall. NOTE: Remember that VS 2012 is really Visual Studio 11.0 and VS 2010 is Visual Studio 10.0.
2) uninstall all Microsoft .NET Framework SDKs (there were a few on my machine 4.5 and 4.51)
3) uninstall all Microsoft .NET Framework Multi-Targeting Packs, which apparently is part of the SDK. Again, there were several on my machine...I guess from different versions.
4) reinstall VSE 2012
5) reinstall the Microsoft SDK. For me this was the latest version 8.1 which works for Windows 7, 8, and 8.1.
6) made sure all my kits were right in QtCreator, which they were, and it all worked again.
Hope this helps someone.
Now I can get back to re-compiling OpenCV with all the NVidia/GPU options. :-)
VS2012 should actually point to VC11...
Have you checked your projects properties? Have you installed the Windows SDK?
I am very new to building, making and configuring projects and compiling from source. I don't know what exactly was wrong, but I think it might have had to do with the VS2010 express installation I did earlier this month. I "repaired" VS2012 using the uninstaller and now it seems to work.

Resources