So, I'm getting this not-so-rare error from what I have been able to search around for solutions:
Activation context generation failed for "C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\WDExpress.exe". Dependent Assembly debuggerproxy.dll,processorArchitecture="X86",type="win32",version="1.0.0.0" could not be found. Please use sxstrace.exe for detailed diagnosis.
I get this btw when I try to start up my VS 2013 Express Win Desktop version.
I went into Computer->Manage->Win Logs->Apps and see a file called debuggerproxy.dll is missing. Well, I downloaded the file and copied into this location:
C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\WDExpress
but it didn't help.
Does anyone know where this file should be copied to?
Thanks...
Related
Yesterday, I have finished working on my Android project (c# and Xamarin) on Visual Studio 2017, I closed it. Today, I re-opened the project in order to continue my work but the project is not loading, plus, I am getting an error in the output window saying:
There is a missing project subtype.
Subtype: '{EFBA0AD7-5A72-4C68-AF49-83D382785DCF}' is unsupported by this installation.
I have searched up and tried every solution online but nothing worked for me. I tried to delete .suo file, repairing vs.. I do not know what to do.. please help me to solve my problem.
Here's a screenshot of the error
UPDATE
I enabled Xamarin for Visual Studio, now the error in the output window is (and the project is still failing to load):
[I:]: Found Xamarin.Android 8.0.0.33
[I:sdk]: Runtime path: C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\Xamarin\Android
[I:sdk]: Framework path: C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\ReferenceAssemblies\Microsoft\Framework\MonoAndroid\v1.0
[I:sdk]: Key HKCU\SOFTWARE\Xamarin\VisualStudio\15.0_6c165955\Android\AndroidSdkDirectory found:
Path contains adb in \platform-tools (C:\Program Files (x86)\Android\android-sdk).
[I:sdk]: Key HKCU\SOFTWARE\Xamarin\VisualStudio\15.0_6c165955\Android\AndroidNdkDirectory found:
Path contains ndk-stack in \. (C:\ProgramData\Microsoft\AndroidNDK64\android-ndk-r13b).
[I:sdk]: Key HKCU\SOFTWARE\Xamarin\VisualStudio\15.0_6c165955\Android\JavaSdkDirectory found:
Path contains jarsigner.exe in \bin (C:\Program Files\Java\jdk1.8.0_131).
[I:]: Found Android SDK. API levels: 22, 23, 24, 25
Never worked with XAMARIN before but faced somewhat similar situations with other projects. Here's what you can do :
1. Create a new project
2. Right click on project > Add > Existing Item
3. Browse to the previous projects directory and add all the project files(i mean code files such as .cs)
**4. In winforms, if you add back a form's .cs file, it should automatically load the .designer.cs as well. **
After doing so, you can get back the entire project. There might be a few errors but they are easily fixable.
Hope this helps :)
I had a global.json with and sdk for dotnet core that wasn't installed.
Either install the targeted version or update your global.json to fit what you have installed.
I am trying to figure out why my simple .net console application is not compiling.
When I compile my app using Visual Studio 2015, which I have repaired already, I get the following error messages in my error list:
Severity Code Description Project File Line Suppression State
Error CS0006 Metadata file 'C:\Users\
\AppData\Local\Temp.sonarqube.static\csharp_1.11.0\SonarAnalyzer.zip\SonarAnalyzer.dll'
could not be found ConsoleApplication1 \ -201s\q_hme_09$\
\data\Visual Studio
2015\Projects\ConsoleApplication1\ConsoleApplication1\CSC 1 Active
Please note that I don't have any Sonar or SonarAnalyzer step in my compilation, nor anything like that is installed.
I really don't know on why it is searching for SonarAnalyzer.zip.
Any guesses?
After researching over the Internet and also repairing Visual Studio, I could not find the solution.
I search for the location where Visual Studio 2015 is installed.
The location is : C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE
I found one directory called .sonarqube. I deleted everything inside.
I can now recompile my project.
I cannot open Visual Studio Express and have the errors as shown in the attached images.
Please Solve my Problem...
Thank You.
Please Visit the following address for Images.
https://app.box.com/s/37srs5jf6bb0arw4nk5oqmowmk1pb99b
// The Error is generated by SideBySide Source.
Activation context generation failed for "C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\WDExpress.exe". Dependent Assembly debuggerproxy.dll,processorArchitecture="X86",type="win32",version="1.0.0.0" could not be found. Please use sxstrace.exe for detailed diagnosis.
// Above are the details of the error
You could try to open a developer command prompt in admin mode, then type wdexpress.exe /setup
I couldn't fix my issue, but I installed Visual Studio on a Virtual Machine and Worked Easily. I corrupted something because I didn't have enough space on my 'C' drive and tried to smlink or link a directory to 'D' drive and it failed. So, either do it in a Virtual Machine or Format the system.
When building our rather large solution (50 projects) in visual studio 2010 I get the following error. Once I get the error restarting the computer a couple (well once is enough sometimes) of times fixes it for a while and then it reoccurs.
The solution contains both WPF, WCF and database-projects.
Error message:
Could not find a part of the path 'C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO 10.0\COMMON7\IDE\PROPERTIES\DATABASE.SQLPERMISSIONS'. C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO 10.0\COMMON7\IDE\PROPERTIES\DATABASE.SQLPERMISSIONS
The DATABASE.SQLPERMISSIONS-file is located with the other property-files in the database-project where the error always occurs. The build action, copy to output directory and other file properties are set to the same as other, working database-projects.
I've tried
Deleting the databases from my local SQL-server
Redeploying
Clean/Rebuild/Build
Removing the database-project from the solution build definition
Restarting the SQL-server/IIS before rebuild
Deleting output-folders before rebuild
and a whole lot of other things, to no avail.
Does anybody have any suggestions to a semi-suicidal developer? Why would visual studio try to find the permissions-file in program files?
Deleting the project metadata (*.dbmdl) file should solve it.
I'm migrating a solution from visual studio 2005 to visual studio 2008. When I build the solution in 2005, I don't have any issues. However, after I use devenv.exe /Upgrade and then use msbuild on the solution, I get the following warnings:
CSC : warning CS1668: Invalid search path '\vc98\lib' specified in 'LIB environment variable' -- 'The system cannot find the path specified.'
CSC : warning CS1668: Invalid search path '\vc98\mfc\lib' specified in 'LIB environment variable' -- 'The system cannot find the path specified. '
CSC : warning CS1668: Invalid search path 'c:\program files\microsoft visual studio 9.0\vc\platformsdk\lib' specified in 'LIB environment variable' -- 'The system cannot find the path specified.'
I have checked http://social.msdn.microsoft.com/Forums/en-US/Vsexpressinstall/thread/3f875480-fee2-4bc3-b829-95e220b22a01 and it doesn't offer me any help because my LIB and INCLUDE environment variables are not set either in the user vars or the system vars. I've looked at Studio's Tools > Options > Projects and Solutions> VC++ Directories and there's nothing that references anything old:
Library Files:
$(VCInstallDir)lib
$(VCInstallDir)atlmfc\lib
$(VCInstallDir)atlmfc\lib\i386
$(WindowsSdkDir)\lib
$(FrameworkSDKDir)lib
$(VSInstallDir)
$(VSInstallDir)lib
Include files:
$(VCInstallDir)include
$(VCInstallDir)atlmfc\include
$(WindowsSdkDir)include
$(FrameworkSDKDir)include
I used diagnostic output so that I could see exactly what the LIB variable includes when being called:
lib = c:\Program Files\Microsoft Visual Studio 9.0\VC\ATLMFC\LIB;c:\Program Files\Microsoft Visual Studio 9.0\VC\LIB;C:\Program Files\Microsoft SDKs\Windows\v6.0A\lib;\vc98\lib;\vc98\mfc\lib;c:\program files\microsoft visual studio 9.0\vc\platformsdk\lib;c:\program files\microsoft visual studio 9.0\vc\lib;c:\program files\microsoft visual studio 9.0\vc\atlmfc\lib;
LIBPATH = c:\Windows\Microsoft.NET\Framework\v3.5;c:\Windows\Microsoft.NET\Framework\v2.0.50727;c:\Program Files\Microsoft Visual Studio 9.0\VC\ATLMFC\LIB;c:\Program Files\Microsoft Visual Studio 9.0\VC\LIB
So if that vc98 is NOT in my env vars, or my studio settings and vc98 isn't even installed (nor the redist), where is that path coming from? What process sets up the LIB env var like that?
Found on MSDN:
Yes this is a known issue that occurs
to some people. Look carefully in
your LIB path. Right after ATLMFC, V,
SDK -> \vc98\lib. Delete this entry
(and the one that follows). If the
LIB is a user variable then you'll
need to restart VS or perhaps log off
and back on. If it is a system
variable then you'll have to reboot.
Your error should then go away.
Here is the solution
http://msdn.microsoft.com/en-us/library/tcbs315h(v=vs.80).aspx
its refer to the LIB entry at Environment Variables
Seems like you have covered most things here, so the only thing I can think of is inherited property sheets.
They are specified in the vcproj XML (or you can check the Property Manager in the IDE):
<VisualStudioProject>
<Configurations>
<Configuration InheritedPropertySheets="stuff.vsprops">...
If you do have some inherited property sheets, go have a look in the file and see if you have any vc98 lib paths set explicitly?
I am wondering if this could be due to the change in using the compiler switches /MT and /MTd from /ML and /MLd which occured for VS2005 relating to C runtime libraries?
Refer to here and see if it helps:
http://msdn.microsoft.com/en-us/library/abx4dbyh.aspx
I'm having a very similar issue with C# projects in VS.NET2010. It appears only to affect those projects which import C++/CLI projects. The projects are still set to compile using the v9.0 toolset(C++, C++/CLI) and .NET 3.5 (C++/CLI, C#). Have you had any luck finding the source of the problem?
I worked around it by adding warning 1668 to the ignored warnings list in the properties of the affected projects. That's not ideal, but better than spam in my warnings list.