Hi Yakov,
To move a PowerServer code set from the PB IDE into source code control, you may just submit the PowerServer project file for source control in the same way as with the traditional c/s applications, and pay attention to the following factors that will work differently:
1. Web server profile configuration. Note that the Web server profiles are configured outside the application source code. So every member in your team shall configure the Web server profile by himself, and update the Web server profile information in the Client Deployment tab of the project settings ;
2. Database configuration. The database configuration is under source control, but if the database server specified is "localhost", other members cannot access. So, it is recommended that you use the actual IP address of the database server in the project settings.
3. Deployment version. If the team members all deploy to the same web server, and the deployment version is configured the same, only the app files with the highest deployment version will apply. To avoid conflicts, you may consider to recommend the team members to deploy to his local machine during the development, and arrange designated person to deploy to the shared web server.
I saw the discussion between you and Chris. Yes, it shall be unnecessary to version the C# solution unless you are making manual changes to it and have the changes versioned.
Best regards, Julie
Please excuse the newbe question But
Since these are 'generated' files, why would they need to be versioned? If not modified wouldn't they be regenerated on every deploy?
Yakov
Correct ... You asked how vs why. You might only want to place the C# solution into an SCM if you are making manual changes o the C# code or configuration files of the generated solution so that you can restore them after the next GEN is completed.
Regards ... Chris