My machine has Windows 10 and Visual Studio 2015
I have downloaded a Stores Application Sample for "Windows 8.1" Solution and opened it, then tried to run it in simulator but it is showing the following error:
Severity Code Description Project File Line
Error Error : DEP1630 : Invalid "TargetOsVersion" property in the recipe file "C:\Users\**\Downloads\JavaCameraCaptureUI Sample (1)\JavaScript\bin\Debug\CameraCaptureUI.build.appxrecipe" CameraCaptureUI
The same has been running well with VS 2013.
What could be the Solution?
I had the same problem and after a few hours of reducing it discovered these two lines in the project (.jsproj) file:
<VisualStudioVersion>12.0</VisualStudioVersion>
<MinimumVisualStudioVersion>12.0</MinimumVisualStudioVersion>
I removed them from the file and everything started working great (open and edit it with Notepad, while VS being closed).
Related
Our previous development systems used Windows XP and Windows 7. Debugging C++ DLLs from Visual Studio worked great.
A recent move to Windows 10 has resulted in an annoying problem. We can debug once (using F5), but the 2nd time results in a linker error:
MyProg fatal error LNK1201: error writing to program database 'MyProg.pdb'
Trying to delete the .pdb manually in Explorer while Visual Studio is still open results in the error:
The action can't be completed because the file is open in devenv.exe
It doesn't matter whether you hit a breakpoint or not. Just start debugging once results in the problem. Re-starting Visual Studio resolves the issue (in the sense that you can debug once, but then you get the problem again).
If relevant:
x86 Visual Studio 2003.NET
targeting another x86 application
x64 Windows 10 Pro v1803
After hunting around for several hours some related, but unanswered, questions were found. Following suggestions in this MSDN article, along with some debugging of my own, this solution works:
Download FreePDB, a script written by MSDN user Toni76 (thanks Toni!)
Copy this script to a local folder (say C:\Apps\FreeDPB)
Download the latest version of SysInternals tool Handle (currently v4.21)
Copy handle.exe to C:\Apps\FreeDPB
NB! From the command line, run handle /? once. This is to agree the EULA. The script will not work if you skip this step!
Open Visual Studio, then Project > Properties > Build Events > Pre-Build Event
Set Command Line to C:\Apps\FreeDPB\freepdb $(ProjectName)
Set Description to Delete lock on PDB
...and now you don't need to restart Visual Studio to debug a 2nd time!
From comments, this works with multiple versions of Visual Studio on multiple versions of Windows.
Update
A more radical solution is described here which involves replacing a core Visual Studio DLL (NatDbgDE.dll). This solution only works for Visual Studio 2003 SP1, though.
In my case it was due to "Process Explorer" program, which was open alongside with my Visual Studio(I used it to check some properties of the exe I've created). After closing it problem solved.
I have a Windows 10 laptop and am running Visual Studio 2017 (15.3.3). When I try to debug my Angular 4 app hosted in an ASP.NET page I get an error stating Cannot debug some of the code in the process chrome.exe and that the WebKit code succeeded and Script code failed (0x80040154). See error details below:
Please help.
I ended up fixing it by uninstalling VS2017, deleting the C:\ProgramData\Microsoft\VisualStudio directory and then reinstalling VS2017. This is not a great solution but it was the only one I found that worked.
I used to use vs 2012 for some month without any problem, today when I want to open my c# project , I got this error message:
This program has known compatibility issues
Visual Studio 2012 Express for Windows Desktop is incompatible with this version of Windows.
when I click Run program I got this error:
'Microsoft.VisualStudio.Editor.Implementation.EditorPackage' package did not load correctly
When I continue with this error message, another error message shows: Visual Studio has stopped working. I need to get it work as soon as posible, any idea?
I had a similar problem, installing this patch solved it: KB2781514
I just got this error in VS2013 after installing a VS extension. I fixed it by closing all instances of Visual Studio, then removing %LOCALAPPDATA%\Microsoft\VisualStudio\12.0\ComponentModelCache
Happened to me today on VS 2012. The Update mentioned by Jarek didn't install (it complained I already have more stuff installed). Deleting the folder mentioned by squeaky didn't work.
Finally fixed after I installed VS 2012 Update 4 : http://www.microsoft.com/en-us/download/details.aspx?id=39305
I'm building a project in Visual Studio 2010 and the build fails because it cannot copy the assemblyname.dll file from obj to bin folder. The exact error message is:
Error 7
Unable to copy file "obj\Debug\AssemblyName.dll" to "bin\AssemblyName.dll". The requested operation cannot be performed on a file with a user-mapped section open.
I think this is because the previous file in bin-folder is not accessible. When I try to delete the file manually, I get an error "The action can't be completed because the file is open in another program". If I try to see what application locks the file with Unlocker, I don't get any results (No Locking handle found).
If I restart Visual Studio, the error goes away but happens again after a build or two. Goes without saying that this is seriously slowing me down. Any advice how to start solving this?
VIsual Studio 2012 on Windows 8. I was receiving the same error message on my project. Restarting Visual Studio or cleaning the obj folder manually did not help. Finally I closed all open files (Windows -> Close All Documents) and the problem went away.
This behavior was due to a newly installed Visual Studio extension called Visual Studio Achievements (http://visualstudiogallery.msdn.microsoft.com/bc7a433b-b594-48d4-bba2-a2f24774d02f)
I noticed that the .pdb file was locked by FxCop (using Unlocker) and I think that the Achievements -extension uses it. After disabling the extension I've no longer got the error mentioned above.
This bug has been fixed in recent versions of the extension (>1.7). It was released as a beta, btw...
This behavior of VS happen very often even on my computer (and on computers of my coworkers).
In my experience it happen more frequently when:
I have some form opened in design when i compile
I stop the execution od the application by pressing the "stop" button
in VS instead of exiting the application
So, closing the form in design before compile, and exiting the application instead of stopping it, somewhat mitigate the issue... but it still happen :-|
My computer is Win 7 x64 SP1 with VS 2010 SP1, 8Gb ram, and no swap file
Platform: Windows 8 Pro, Visual Studio 2012
I found that I receive this error when I am accessing the folder in Windows Explorer.
I was creating PDF documents with Visual Studio 2012. To review the sample document I would right click in Solution Explorer and use Open Folder in File Explorer.
On Windows 7 I would get a SYSTEM.IO error if the actual PDF document was open in Adobe Reader which is expected. With Windows 8 I found that I receive the above error if I have the folder open. I suspect there is a conflict with the Windows 8 preview.
If I close the folder and run the program it works fine.
Check if you open the dll in visual studio.
I open the dll in visual studio and this error happen!!
I create their basic Flash app with their Flash IDE for Visual Studio 2010
http://www.sapphiresteel.com/Products/amethyst-ide/article/amethyst-product-page
When launching the run button, it launch flash but with this error within Flash CS4:
The following JavaScript error(s) occurred:
At line 6 of file "FlashApplication1.jsfl":
Cannot find file file:///C:/temp/FlashApplication1/FlashApplication1/FlashApplication1.as.
Did someone tried and has this problem also and then a solution ?
This is discussed in a thread in the SapphireSteel Software forum: http://sapphiresteel.com/forum/index.php?topic=542.0