Printable View
Why is visual studio locking my files even when application is not running?
The files are not under any source control or readonly either.
Before this it didn't allow me to edit the aspx.vb while debugging, though I can do that in other projects. So I think something is seriously bad in this project.
Any ideas?
Attachment 81155
Hey Pradeep,
I can't say that I have seen this behaviour in Visual Studio.
The only thing that springs to mind is that you are editing the project from a non trusted location, perhaps a network share somewhere. Is this the case?
Gary
No. It is on my local machine and in the same folder where I keep all my other projects.
I think something is corrupt in this project, or maybe some setting is doing this.
Hmm, strange. I am not aware of a setting that would do this, but that isn't to say that there isn't one.
Do you have a back up of the project that you could store to test it?
Gary
Some test,other than this i also can't think of something.
If you are using IIS then try to run it without it.
Also if you are creating the a new web project try to create it as a new website.
I am not mentioning win7 because from the design i see you are on XP.
Hey,
Not sure if this is related or not, but it turned up as the result of a quick google:
http://bphillips76.spaces.live.com/b...6166!365.entry
Gary
I ended up creating a new blank solution. Then adding new projects to it with same type and same name as my original ones. And then adding files from old projects to new one.
It is working now. So my problem is resolved. Though I still don't know why it happened or which file exactly was corrupt. Nor I'm sure whether the problem will come back again in this new project or not.
But for now it is resolved.
Very weird!!! :(
I just wanna add here that today i had a problem with the page not firing the load event.
No mater what i tried the load wouldn't fire.So i created a new web site , copy-pasted and magically it worked(?). This in Vs2008 latest service pack.
I'll mark this thread resolved since I'm no longer facing the problem with new solution.
I couldn't get the time to investigate into it due to project deadlines; though if find something I'll post it here.