Almost every time I try to rebuild a C++ project in Visual Studio 2010 after having recently launched the build target from Visual Studio, I get this error.
LINK : fatal error LNK1104: cannot open file 'D:\Programming\Projects\SpecsLauncher\Release\SpecsLauncher.exe'
I have used ProcExp from Sysinternals to check and see which application still has the file open, but it comes up with the System process as still having it open.
It does not appear anywhere in the Windows Task Manager, and closing and re-opening Visual Studio makes no difference.
I can't even delete the build target from Windows Explorer.
I do not experience this issue with anything other than executables built and run from Visual Studio.
I thought it might be my anti-virus (Symantec Endpoint Protection), so I tried temporarily disabling it, but it made no difference.
The only thing I can do is wait about 4 minutes and then try again.
Related
The project I'm working on in Visual Studio Code builds fine when you use the Live Code from The Unreal Editor but if you try to build from Visual Studio you get this in the terminal...
'C:\Program' is not recognized as an internal or external command,
operable program or batch file.
I'm assuming it is choking on the space in C:\Program Files (however that is a standard space in that Windows created directory so I can't change it without breaking links for countless other files in that directory). As well when you build from Unreal it doesn't choke on that space - so I'm wondering if anyone knows how to "ignore" the spaces. And since Visual Studio 2019 has no issues building that project - it must have some setting that is also ignoring the spaces. Thanks in advance.
(it doesn't seem to fail - it just seems to soft lock? the "thinking spinner" just keeps spinning and it never seems to complete the build task).
I brought the same project into Visual Studio 2019 and it builds fine, however I can't get Unreal's Live Code to link with 2019 so I'm just trying to get this working in Visual Studio Code since Live Code works great with it.
While installing Microsoft Visual Studio Code, I received this message:
"Setup was unable to automatically close all applications. It is recommended that you close all applications using files that need to be updated by Setup before continuing."
How do I solve it?
Thanks
You can try the following steps:
try to start setup as an administration
make sure you have closed the explorer, especially if you have opened anything related to C: drive.
If it still shows any problem, try to restart the system as some process is running in the background that holding onto some file that needs to modified by vscode setup.
try to disable Antivirus (last attempt).
try to install System installer of vscode instead of User setup (if you have downloaded user setup)
I have a project using the SpeechClient.dll from NuGet. The program runs fine on the development machine. So I have a Windows Setup Project that creates the installer. I run the installer and all the files show up including the SpeechClient.dll, but as soon as the program makes the first call to the Speechclient.dll, I get a
file not found
exception. This is the output from the event viewer.
Does anyone have any troubleshooting ideas? Thanks.
Seems now that I have installed visual studio on the machine that it is working. I wonder what visual studio installs? I was also trying to use Fusion Log Viewer to see what the problem was.
I had this problem as well. Installing the Visual Studio C++ Redistributable 2017 x64 cleared it up.
I cant see emulators and I also cant see Apache ripple in the debugging bar, all I see is start. even when I click start it shows error.
Check out this link:
Known Issues - Visual Studio 2015
In some cases, when you uninstall VS2013 or a previous version (RC) of VS2015, a library gets corrupted that causes the debug dropdown not to show all the target options. To resolve this issue:
Close all Visual Studio instances.
Browse "C:\Users\\AppData\Local\Microsoft\Phone Tools" folder
Rename the CoreCon folder to something else.
Launch Visual Studio again.
I've noticed that, despite always closing it before I quit, despite opening other files as well, Visual Studio Code will always re-open a particular file when I launch the app. This is still the case after upgrading to the latest version - 0.7.0 at the time of writing.
Is there a setting I'm missing, or something that needs to be cleared out / blown away?
I'm running on Windows Server 2012 R2.
This issue has been fixed for the next release and only shows up when you work in file mode and not folder mode (that is when you are not actually opening a full folder inside VS Code).
To workaround this, use the -n option when you run VS Code. -n will force to open VS Code empty without any file or folder opened.