Error: The error similar as below is displayed in the Error list in Visual Studio Express Error 1 Unable to copy file "obj\Release\ShellCustomAddIn.dll" to "..\..\..\bin\ShellCustomAddIn.dll". The process cannot access the file '..\..\..\bin\ShellCustomAddIn.dll' because it is being used by another process. ShellCustomAddInExpress Cause: at least one GN4 application is running while compiling, and it keeps DLLs locked, so compiler cannot replace them. Solution: exit all GN4 applications, and retry. |
Typically in that case there are plenty of various errors. A good attempt is to close Visual Studio Express and restart it. If the errors are gone, that was the solution. |
Typically in that case there are one or more errors. You can try the following: •Wait for the new daily, download and then retry. •Resync synced add-ins to a previous revision, and then retry. |
The error displayed may be similar to this: 'GnCLient' is not declared. It may be inaccessible due to its protection level. It probably means that the reference to the DLL that contains GNClient methods (in this example) is not present in the project. This may happen with the custom add-ins. See Adding a new reference to an add-in project for instructions how to add a reference. |
To solve this problem, see Edit and Continue: prepare debugging. |
This error may happen when you access Visual Studio Express through remote desktop, and the sessions ends unexpectedly, or when you clean Windows temporary files with some cleaning software. The specified folder may be missing. Note: the name of the folder can be any. To resolve the problem •Try to rebuild the solution. It helps in the case when the temporary files were removed by the cleaning software •Try to look if there are other folder in the same root path 'C:\Users\xxxxx\AppData\Local\Temp' - they're supposed to be numbered as well, e.g. 3, 4 or similar. If you find some, open it and then select all files you find there. Copy them to the clipboard, and then create the missing folder and paste the files there. Then, restart Visual Studio Express and try to rebuild the solution. |