My application uses several files that contain constants, error code,
etc that are located in a directory call /bin. At times when I am
testing the application in "debug" mode, the files cannot be opened and
I receive an error. I have also seen occurances where for some reason
VS.NET suffered a fatal error and shut down. When teying to open the
files in /bin again after a reboot, I am unable to.
I have come up with 3 work-arounds so far:
1) move the files in the bin folder somewhere else, then move them back.
This sometimes works.
2) mark the folder and all contents as "read-only" then uncheck
read-only and apply to all. This works most of the time.
3) recycle the asp-wp (ASP Worker Process) thread. This normally works.
If this doesn't, then I try step 2 instead.
First off, has anybody else seen this behavior before?
What can I do to prevent this kind of behavior? From what I understand
VS.NET is "locking" the files in the bin folder for it's own use by
setting them read-only and reading from them as needed. The problem is
with setting these files back to writeable when the process is done.
Thank you.
--
Regards,
Top Hat
Please no email replies - reply in newsgroup <<<
MCP, MCSE, CSA