ttsonev Posted April 3, 2012 Report Share Posted April 3, 2012 Hello, We use PlasticSCM 4.0 build 22 We have problem with some solutions - they are binded (Change SourceControl says binded to all projects and the solution, we have tried to unbind and bind again and it doesn't fixed the issue), and check in on single file or project works as expected. However check-in on the solution shows New Workspace form and if you choose the folder it gives error that workspace is already availabe on this page. Update to Latest on the solution does nothing. We have solution folders in the project (I read that plasticscm integration has problems with them), but our solution is very big, and we cannot get rid of them. Also some solutions works fine, although they have solution folders, and other solution without solution folders has the problem. Greetings, Tsonko Tsonev - Validata. Link to comment Share on other sites More sharing options...
manu Posted April 3, 2012 Report Share Posted April 3, 2012 Hi Tsonko, can you confirm that all your projects are part of the same Plastic SCM workspace? If they are not under a common path that it's a Plastic SCM workspace you-ll get the create workspace window. Link to comment Share on other sites More sharing options...
ttsonev Posted April 3, 2012 Author Report Share Posted April 3, 2012 Hi, All of the projects are in the workspace. We have references to assemblies outside of the workspace, but this shouldn't affect it? Greetings. Link to comment Share on other sites More sharing options...
manu Posted April 4, 2012 Report Share Posted April 4, 2012 It should not be a problem. The issue raises when you have projects, solution files or files under a project that are stored outside of the Plastic workspace. Can you please check the 3 options? Link to comment Share on other sites More sharing options...
ttsonev Posted April 4, 2012 Author Report Share Posted April 4, 2012 Hi again, I'll check now. Meanwhile I have two more fast questions. First is how do I call forced update using the console cm command? And the second is - View History as 2D revision tree crashes the PlasticSCM client - is this a known issue in build 22 ? Link to comment Share on other sites More sharing options...
manu Posted April 4, 2012 Report Share Posted April 4, 2012 The old update force option is gone, forget about it. The option was "--forced". Wow!! I didn't know it was causing a GUI crash, it should be working!!! Can you please enable the Plastic GUI log and send it to us? The log config file is called "plastic.log.conf" you can download it and learn how to use it here: http://www.plasticscm.com/infocenter/technical-articles/kb-enabling-logging-for-plastic-scm-part-i.aspx Link to comment Share on other sites More sharing options...
ttsonev Posted April 4, 2012 Author Report Share Posted April 4, 2012 Why is it gone? I need to make script for build automation, which should extract the latest workspace and then build the solution, but as some dll's are under source control and even if i add them as Hidden change list, the update doesn't update them and some other files, but Forced Update does the trick, I need to execute it from the script. About the crash - I'll enable the log later, but for now I can send you this error: --------------------------- Error --------------------------- Unable to cast COM object of type 'System.__ComObject' to interface type 'Microsoft.VisualStudio.OLE.Interop.IServiceProvider'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{6D5140C1-7436-11CE-8034-00AA006009FA}' failed due to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)). --------------------------- OK --------------------------- I receive this if I execute View History as 2D tree from Visual Studio, If I execute it from the stand-alone client it just crashes after message Calculating branch explorer layout. Link to comment Share on other sites More sharing options...
manu Posted April 4, 2012 Report Share Posted April 4, 2012 We have fixed a issue with a similar behavior, I'll confirm it with the log. You can send it to me later, no problem. Regarding the --forced, it's really hard find a case where it's really needed. Why don't you can use a regular update operation? The --forced is basically as if you remove all the files and directories inside your workspace and then "cm update ." Link to comment Share on other sites More sharing options...
ttsonev Posted April 4, 2012 Author Report Share Posted April 4, 2012 We have a file in some projects added "As Link" (http://msdn.microsof...2(v=vs.80).aspx) But the added file is in the workspace, may that cause the problem ? Link to comment Share on other sites More sharing options...
ttsonev Posted April 4, 2012 Author Report Share Posted April 4, 2012 Here is the log up to the crash point. plastic20120404-18.log.txt Link to comment Share on other sites More sharing options...
ttsonev Posted April 5, 2012 Author Report Share Posted April 5, 2012 I found the bugger, there was a file added outside of the workspace, but when you have thousands of files it's hard to find it, maybe if Plastic listed the files outside of the Workspace it would be nice feature. What about the View History as 2D revision tree problem ? Link to comment Share on other sites More sharing options...
manu Posted April 9, 2012 Report Share Posted April 9, 2012 Hi ttsonev, yes, if you have a really big project it's difficult to find the guilty one. I think we can add more log info into the code, so the next time we will be able to find the one out of the wks. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.