Branch rules/repositiry rules
I have a proposal to develop of the launch of triggers before operations Checking/Merge. These triggers will be realized by C# or other. If the trigger did with error, then operation Checking/Merge would not be executed.
The problem definition is the project files are added with specific settings during the collaborative software development into the control version, such as a remote debugging flag or inadvertently not all files are described in the project file for adding to version control. Therefore, the project on another desktop couldn’t be compiled or launched without additional corrections and rewriting of the project file. The solution is the definition of the rules for the branch of project or repository.
Perhaps it is advisable to keep these triggers on the server side. However, pass the triggers code to the client side before Checkin/Merge operation, because, the triggers size is much smaller than the data to be added to version control. Therefore, it will have the significant impact on to the performance of network traffic.
If you can read and check the Triggers Docu, maybe we can close this request.
It works well for me... :-O
I can't open https://www.plasticscm.com/documentation/triggers/plastic-scm-version-control-triggers-guide.shtml#Clientsidetriggers
Maybe It's broken link?
We already support before-checkin and after-checkin triggers, and they can happen both at client side and server side.
You can write them in any language you want, including C#.
So, not sure if we should discard your request.
Now, off-topic: the per-project settings issue you are facing is precisely why I always prefer to use NAnt or something similar to build releases, instead of relying on IDE settings. More often than not you end up with configuration issues due to these environments. NAnt scripts are the solution... Or something not touchable by hello-world-designed UIs :-)
It's real needed for the good development of high-loaded application!