Due to some power failure my system got shutdown and now when I am opening the project all the abc.xaml.cs files are getting opened in notepad
I have tried to find auto recovery backup at Documents\Visual Studio 2013\Backup Files\project but here is nothing.
Please help me to get out of this problem.
Sounds like the association between the file type and Visual Studio has been lost. Try the steps # Reassociate files types for visual studio 2012
Related
I am getting this error for various DLL's which are outputs of projects in my solution.
Things I have tried:
Restarting PC multiple times
Closing visual studio
Turning off all visual studio extensions
Deleting the files manually in the explorer. I get the error "The action can't be completed because the file is open in another program"
Using ProcessExplorer to find processes that are using the DLL's. It does not find any processes
I have tried using ResourceMonitor and WhoLockMe as well, to no avail
I have killed the explorer.exe process and that didn't work either
From command line I ran 'git reset --hard HEAD' to revert to the last commit (which was a stable build)
Any other ideas how I might be able to unlock these files?
Update: Turns out that some of the DLL's in every solution that I opened with Visual Studio yesterday are permanently locked
I do not have Visual Studio Achievments installed and I have disabled all extensions. Closing open documents did not help.
Somehow the issue solved itself after I did the following:
Clone the project into a different folder
Build and run the cloned project with Visual Studio
A few hours of programming later I tried to delete the files and they were no longer locked
I'm facing a problem where I can't open .cs files in Visual Studio 2013 after one day.
It started on Monday: I opened an existing solution and tried to open the Program.cs file but instead was met with the following error message (rough translation):
No exports were found that meet the constraint:
ContractName
Microsoft.VisualStudio.Utilities.IContentTypeRegistryService
RequiredTypeIdentity
Microsoft.VisualStudio.Utilities.IContentTypeRegistryService
I tried opening .cs files in different solutions and always got the same message. The only exception being: Any Visual Studio instance that was opened before the Visual Studio instance in which the exception first occured was/is not affected by this.
I managed to get it working by choosing to repair the Visual Studio installation and rebooting but that only worked until the next day.
I tried searching for that message but got nothing so far.
Delete or rename this folder:
C:\users\\AppData\Local\Microsoft\VisualStudio\12.0\ComponentModelCache\
I had this issue and seems the file was open - but I could see what pane or anything. So I had to right click on a file and close all documents - then I could open the file again.
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.
I have the project solution bin in below location for dll, pdb . my build is getting failed due to below error.
C:\Users\myusername\Documents\Visual Studio 2010\Projects\mysolution\bin\debug\CommonServices.pdb
C:\Users\myusername\Documents\Visual Studio 2010\Projects\mysolution\bin\debug\CommonServices.dll
Error
The command "C:\Users\myusername\Documents\Visual Studio 2010\Projects\mysolution\bin\debug\CommonServices.dll" exited with code 3.
I tried by cleaning the solution and build / Rebuild. Either way, it is not given result.
Please help.
maybe you have some errors on PropertyGroup.
Read this:
http://social.msdn.microsoft.com/Forums/vstudio/en-US/589ffae3-59ca-4d0a-a7b1-9f1120db3792/msb3073-the-command-exited-with-code-3
A couple of things to consider and try - in the title, it says VS 2008 error, but the path points to 2010, are you sure it is pointing to the right reference for 2008?
If it is, try closing Visual Studio, deleting the pdb file. This will eliminate any pdb issues with building, as the pdb file will be recreated.
Then also delete the .suo file, this will also be recreated. This is to eliminate any build issues that may be caused by Visual studio version conflict.
Another thing to check is if there is any build events in your project that may be triggering this error, go into project properties and remove/edit any build commands.
I get the following error in Visual Studio 2005 when doing a build:
Error 9 Cannot register assembly
"E:\CSharp\project\Some.Assembly.dll"
- access denied. Access is denied. (Exception from HRESULT: 0x80070005
(E_ACCESSDENIED)) project
It happens only intermittantly and does go away if I restart the IDE, however this is incredibly annoying and I would like to put a stop to it happening permanently, if I can. I've checked the assembly itself, and it is not set to read only, so I've no idea why Visul Studio is getting a lock on it. I am working in Debug mode.
I've had a look around google, but can't seem to find anything other than "restart VS". Does anyone have any suggestions as to how I can resolve this annoying problem?
It sounds like you have a DLL that gets locked every now and then, preventing VS from overwriting/locking it. Have you tried using tools like Process Explorer (http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx), or Unlocker (http://www.emptyloop.com/unlocker/) to see what is locking the DLL? Unlocker in particular has saved me many a time.
As noted in the comments below (Thanks Jeff), you can also kill an individual lock from within Process Explorer.
This may be caused by Visual Studio requiring administrator rights on Windows 7 or higher. To check, see whether the registry key mentioned below is set. If not, copy into a .reg and merge. Be sure to check that your Visual Studio 2005 installation path in the .reg file is correct!
Windows Registry Editor Version 5.00
; Run Visual Studio 2005 with administrator rights
; This is required to run / debug the program directly from the IDE
[HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers]
"C:\\Program Files (x86)\\Microsoft Visual Studio 8\\Common7\\IDE\\devenv.exe"="~ RUNASADMIN"