Hi,
I like to keep design documentation in my VS projects. I set up a folder called Design in the project, and then store MS Word and Visio documents in it that contain the design documentation. Very convenient. It's great having them in Vault, because I can keep a complete history of versions without having to remember to re-name the document every time I edit it, and I don't have to worry about distributing the changes - they're always with the source.
My problem is that once I get a document (say a word document) into the Vault repository, when I subsequently load the project in VS, the non-VS files are copied into the workspace as "read only". This makes it impossible to modify any of these documents.
I can go into Windows Explorer and edit the properties of the files and re-set the documents to Read/Write, before I do any edits, but this is not convenient, and is error prone.
Why are these documents coming from the Repository as "read only"? Is there a setting I can set so that they are copied into the working directory in an editable state?
Thanks.
BBM
Non VS files are read from the repository as "read only
Moderator: SourceGear
What version of Visual Studio are you using?
If you check out the files, are they writable?
Generally in Visual Studio, files are read-only unless they have been checked out. VS 2005 has an option to allow checked-in items to be edited, but Vault doesn't yet support this.
If you check out the files, are they writable?
Generally in Visual Studio, files are read-only unless they have been checked out. VS 2005 has an option to allow checked-in items to be edited, but Vault doesn't yet support this.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
I'm using VS 2005 and Word 2003.
After my initial post, Vault started treating me better. I am able to check-out my design files, edit them, and check them back in. It started to work after I went in and changed the file properties directly to turn off the "read only" flag.
The only irritation at this point is that I can double-click on the document in the Solution Explorer and get it up in an editable state without checking it out. If you go ahead and modify it, it becomes impossible to update in the repository since it was never checked out. This is a minor inconvenience if you know how it's going to work.
I actually think that this post may be related to my other post about forcing off a user. I have noticed that when one of the non-VS documents is checked out, and if another user tries to edit the document, that it comes up in "read only" mode. I think it's possible that my "perpetual" user had the document checked out when I first tried to edit it, and it came up in read-only mode.
I'm going to continue to play with this, and I'll let you know if I find anything curious. For now I'd say it's OK.
BBM
After my initial post, Vault started treating me better. I am able to check-out my design files, edit them, and check them back in. It started to work after I went in and changed the file properties directly to turn off the "read only" flag.
The only irritation at this point is that I can double-click on the document in the Solution Explorer and get it up in an editable state without checking it out. If you go ahead and modify it, it becomes impossible to update in the repository since it was never checked out. This is a minor inconvenience if you know how it's going to work.
I actually think that this post may be related to my other post about forcing off a user. I have noticed that when one of the non-VS documents is checked out, and if another user tries to edit the document, that it comes up in "read only" mode. I think it's possible that my "perpetual" user had the document checked out when I first tried to edit it, and it came up in read-only mode.
I'm going to continue to play with this, and I'll let you know if I find anything curious. For now I'd say it's OK.
BBM