CodingGorilla Posted November 21, 2011 Report Share Posted November 21, 2011 Why is it that when I add new files in visual studio, when I have Plastic set as the source control provider, are the new files automatically added to the repository? I always have to manually select them when I do a check-in. Am I missing something? Link to comment Share on other sites More sharing options...
psantosl Posted November 21, 2011 Report Share Posted November 21, 2011 Hi! Sorry for the delay. I'll be coming back with the answer tomorrow (believe it or not I do not use the plugin myself). But AFAIK they're not added to the repo, just marked to be added. Remember "add" is not the same in 4.0 than 3.0 (4.0 handles "adds" locally). Does it ring a bell? Link to comment Share on other sites More sharing options...
CodingGorilla Posted November 21, 2011 Author Report Share Posted November 21, 2011 Sorry, I'm a Plastic newbie, so the only frame of reference that I have is from working with SVN and related plug-ins. I would expect that when I add a new file in visual studio, and then do a check-in operation that the new file is already "checked" in the check-in UI to be added. Instead, it shows up as "private / Uncontrolled" and I need to put a check mark next to the files in the Check-in UI to make it a "Controlled" file. Is that more clear? Link to comment Share on other sites More sharing options...
CodingGorilla Posted November 22, 2011 Author Report Share Posted November 22, 2011 Here's an example: This image shows a new file in the "Solution Explorer", the source control status leads me to believe it has been "Added" to source control: http://screencast.com/t/ZddvY8Gx But when I do a "Check in" I see the following UI: http://screencast.com/t/2idQomsH The files are labeled as "Added and private" and I need to check the checkboxes in order to have them committed to the repository (as I would expect them to be since I added them to the visual studio solution). P.S. Sorry about the links, but I can't embed images I guess? Link to comment Share on other sites More sharing options...
psantosl Posted November 22, 2011 Report Share Posted November 22, 2011 Hi, Yes, what you ask is true. We do not mark the "added" by default on the GUI, because then some privates could find their way in without being really part of the controlled stuff. From VStudio we could change the behavior. But, instead of checking "all" the check boxes, can't you just check the container?? I mean, adding files is not as usual as modifying existing ones, so reviewing what really needs to be added shouldn't be an issue, is it? Link to comment Share on other sites More sharing options...
CodingGorilla Posted November 22, 2011 Author Report Share Posted November 22, 2011 Yea, it's not a big problem, as you mentioned I can check the container (except when there are files that I actually don't want added, then I have to ignore those). It just wasn't the behavior I expected, so I wanted to make sure I wasn't just missing something. Like i said, I'm new to Plastic SCM, I was just expecting SVN behavior... Link to comment Share on other sites More sharing options...
psantosl Posted November 22, 2011 Report Share Posted November 22, 2011 Hi! Ok, but your opinion is really valuable! So, where are these privates or ignored coming from? Aren't they on the vs project? Thanks, pablo Link to comment Share on other sites More sharing options...
CodingGorilla Posted November 22, 2011 Author Report Share Posted November 22, 2011 Yes, they are added using the regular-old visual studio methods. So for example, if I right click the project and hit New Item -> Class, the new file "Class1.cs" will be added to the project, the source control status shows the little yellow + next to the file. This leads me to think (again, based on how SVN and other plug-ins typically function) that Plastic is already going to add this to the repository (ie. It's status is now controlled, not private). However, as I demonstrated with the screen shots, it's still considered by Plastic to be 'private'. IMHO, the visual studio plugin should automatically set the status to 'Controlled' when a file is added via visual studio. Link to comment Share on other sites More sharing options...
danipen Posted November 22, 2011 Report Share Posted November 22, 2011 Hi CodingGorilla, The requested feature is planned to be implemented. It will be released in the next Plastic SCM release. Thanks for your feedback. Link to comment Share on other sites More sharing options...
danipen Posted December 2, 2011 Report Share Posted December 2, 2011 Hi CodingGorilla, We have implemented your requested feature and it will be integrated in our next public release. Thanks for your help. Link to comment Share on other sites More sharing options...
immitev Posted April 24, 2012 Report Share Posted April 24, 2012 Hi, We are using PlasticSCM 4.0 (a build from March) with VS.NET 2010 and the behaviour with new files showing up as private (i.e. not controlled) seems to persist... Is it supposed to be fixed in 4.0 or should we expect it in version 4.1? Link to comment Share on other sites More sharing options...
manu Posted April 25, 2012 Report Share Posted April 25, 2012 Hi immitev, with Dani's latest changes in the plugin when you have private elements they are shown with a yellow cross and when you try to commit they are checked by default to be added into Plastic SCM. That works for you? Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.