cidico Posted February 24, 2012 Report Share Posted February 24, 2012 Hi! I was adding some Resource files to my project and I checked in the files. Then I needed to change some values. I added some new strings but the changes were not performed. One thing I noticed is that the "visual" file of the resource was checked out, but the generated code (that keeps all values of the Resource file) was not. Is it a bug or a normal feature of Visual Studio? Link to comment Share on other sites More sharing options...
manu Posted February 27, 2012 Report Share Posted February 27, 2012 Hi cidico, I'm a little bit lost... can you describe the issue with more details? Link to comment Share on other sites More sharing options...
cidico Posted February 27, 2012 Author Report Share Posted February 27, 2012 Sure! Do this test: Create a project in Visual studio; Add a Resource File; Checkin this file; Open the resource file (by double clicking on it); Add a value to the file; You'll see that the ResourceFile.Designer.cs is not checked out and your change made is not there. If I manually add an empty space to checkout the .Designer.cs file and I add a value to the Resource everything works. Got it? Link to comment Share on other sites More sharing options...
manu Posted February 27, 2012 Report Share Posted February 27, 2012 One question cidico, are you working on read-only mode? Are your controlled files in read-only or not? thanks. Link to comment Share on other sites More sharing options...
cidico Posted February 27, 2012 Author Report Share Posted February 27, 2012 Yes, I'm! Is this the problem? Link to comment Share on other sites More sharing options...
manu Posted February 27, 2012 Report Share Posted February 27, 2012 Yep, I think so. Try to co first the file, then add the value, tell me if it works. (just testing) Link to comment Share on other sites More sharing options...
cidico Posted February 27, 2012 Author Report Share Posted February 27, 2012 Hummmm... It worked! I guess that it is a problem of Visual Studio integration right? Not plastic itself. I know that your plugin uses the same integration that VSS or TFS, so it maybe a problem when using them too. My guess is that VS itself is not checking out the .Designer files. Link to comment Share on other sites More sharing options...
manu Posted February 27, 2012 Report Share Posted February 27, 2012 Well, more or less is what you are saying, the problem here is that the VS "save" hook is not telling us all the files that must be checked-out. We will try to think a way to bypass the VS limitation. You can work without the read-only attribute without problems, it's faster Link to comment Share on other sites More sharing options...
cidico Posted February 27, 2012 Author Report Share Posted February 27, 2012 Dumb question... If there's no problem with this, why do you have this option at all? Does It changes any work mode?! Is it just a feature to people who likes the "checkout -> modify -> checkin" worklow? Link to comment Share on other sites More sharing options...
manu Posted February 27, 2012 Report Share Posted February 27, 2012 Well, some people are more comfortable working with the read-only attribute, old times you know. But it's 100% safe working without it, and you save time every time you run an update since you don't have to set the read-only attribute. (you can run a "cm update . --noparallel --stats" on a empty workspace and check the time lost on it) Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.