[232] Status of #18763??

I don't mean to nag, but any idea when #18763 is going to fixed?

As I'm sure anyone who uses any kind of SCC within VS, this is the infamous 'cannot modify readonly document' exception that has been around for weeks (maybe even months).

The only way I can reliably test/use R# EAP is to basically check my entire soltuion so I don't get any exceptions. If I don't, I will get all sorts of exceptions. Fortunately, I am the only dev on my project so this isn't a major issue, but for others I'm sure this is an issue.

I only bring this up because I have been using 232 for two solid days and this is the only exception I have been getting. Great job in stabilizing the code base in the last couple of builds!

3 comments
Comment actions Permalink

Hello Mike,

some time ago we tested ReSharper with Vault SCC and all seemed to work correctly
- there were no any exceptions. We'll try to check other SCCs ASAP.


Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

I don't mean to nag, but any idea when #18763 is going to fixed?

As I'm sure anyone who uses any kind of SCC within VS, this is the
infamous 'cannot modify readonly document' exception that has been
around for weeks (maybe even months).

The only way I can reliably test/use R# EAP is to basically check my
entire soltuion so I don't get any exceptions. If I don't, I will get
all sorts of exceptions. Fortunately, I am the only dev on my project
so this isn't a major issue, but for others I'm sure this is an issue.

I only bring this up because I have been using 232 for two solid days
and this is the only exception I have been getting. Great job in
stabilizing the code base in the last couple of builds!



0
Comment actions Permalink

Hello Dmitry,

I use Vault for SCC. I am on their latest version.

My setup is a winforms application with 4 or 5 class libraries in the solution. The exceptions seemed to occur more when doing refactorings across multiple projects.

Here is a scenario I have observed:

Start VS with all files, projects and solution checked in. Do multi project refactor (e.g., rename) and have VS auto-check out files as needed. The exceptions will start to happen after the 3rd or 4th refactoring. If exception occurs and then I check out all of the files (in the same VS session), the exceptions will still occur. If I restart VS after all of the files have been checked out, no exceptions occur. It appears that R# is confused as to what is and isn't a read-only document.

I have noticed that once the first 'read-only' exception occurs, they seem to be much more prevelant.

Hope this helps with debugging.

Mike

0
Comment actions Permalink

Hello Mike,

thanks a lot for this information. We're investigating this problem now.


Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Hello Dmitry,

I use Vault for SCC. I am on their latest version.

My setup is a winforms application with 4 or 5 class libraries in the
solution. The exceptions seemed to occur more when doing refactorings
across multiple projects.

Here is a scenario I have observed:

Start VS with all files, projects and solution checked in. Do multi
project refactor (e.g., rename) and have VS auto-check out files as
needed. The exceptions will start to happen after the 3rd or 4th
refactoring. If exception occurs and then I check out all of the
files (in the same VS session), the exceptions will still occur. If I
restart VS after all of the files have been checked out, no exceptions
occur. It appears that R# is confused as to what is and isn't a
read-only document.

I have noticed that once the first 'read-only' exception occurs, they
seem to be much more prevelant.

Hope this helps with debugging.

Mike



0

Please sign in to leave a comment.