the last access/last write time on file cannot be set. access to the path is denied I try to set the bin folder for unchecked as a read-only file and folder but no luck
It sees there are some problems with your Visual Studio. You can try to reinstall or update the Visual studio.
There is a same issue in the visual studio community which is resolved by downloading the higher version of VS.
You can check it:https://developercommunity.visualstudio.com/t/the-last-accesslast-write-time-on-file-xxx-cannot/520031
Related
Every time I do a git pull from remote to update my branch, Visual Studio 2017 shows "the type or namespace could not be found" error in many files as I open them. Interestingly I don't see the problem in Visual Studio 2015 for the same projects/repo. The software builds fine in both versions of Visual Studio so it is a false error. Doing a Clean or Rebuild doesn't fix the problem. I end up re-cloning the repo from remote and then Visual Studio 2017 is happy. Any one knows how to fix this annoying problem?
The problem is the package-restore. If it fails, you get the issue.
You can try to unload and reload the projects, but I also still haven't found a way to avoid it.
Unloading and reloading the project did not work work me.
Instead, I delete the hidden .suo file inside the project directory and everything started working again. The path is:
(project name) \ .vs \ (project name) \ v15 \ .suo
In my case I had csproj.user file that I've removed and then reloaded the project.
This issue occurred in VS 2019 while participating in a C# Essential Training course. My solution is:
Save the entire project
Close project
Open project
I'm working with WiX installer and trying to open my Installer files .wxs for editing and i'm getting a this error.
No EditorOptionDefinition export found for the given option
name:TextViewHost/LineNumberMargin Parameter name:optionId
Follow the steps:
1.Close Visual Studio
2.Open the folder: %LocalAppData%\Microsoft\VisualStudio\12.0\
3.Rename the ComponentModelCache folder
4.Restart Visual Studio. Visual studio will recreate the folder and all will be well with the world (or at least VS).
I was facing the exact issue where I was not able to open any files(code) .
The easiest way in which we can resolve issue is to download the visual studio web essentials .(http://vswebessentials.com/download)
Once you download you will be able to open your files and no error will be thrown.
thanks,
Abhimanyu
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.
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 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"