6/29/2025 1:32:02 PM
|
| |
| slxdeveloper.com Community Forums |
|
| |
|
|
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
Forum to discuss the use of the SalesLogix Web Platform, Client and Customer Portals, and the Application Architect (For version 7.2 and higher only). View the code of conduct for posting guidelines.
|
|
|
|
Subversion and Application Architect
Posted: 25 Aug 10 8:35 AM
|
There is not much out there on integrating Subversion with App Architect. So right now I have taken Ryan Farley's articles describing source control integration using Git and replaced the words "Git" with Subversion, for the most part.
I think I have everything wired up properly but I am hoping I can get some confirmation on things here, as well as get a question answered 
We are just starting to introduce multiple developers. Here is the process I have outlined so far. We have a staging server (aka "DEV" server), a UAT server, and a production server. Assume everyone involved has the tools needed for local development (SLX Admin, AA, VS.NET).
1. Back up last known "good" project in App Architect from production into a zip file.
2. Create a new Project Workspace on DEV, and restore from the production zip file (do not create files).
3. Share this directory on the network.
4. Create a new empty repo in Subversion.
5. Add the code from the DEV workspace into the repo (this is now "version 1").
6. On developer machines, each developer creates a blank Project Workspace (do not create files).
7. Pull "version 1" files from the repo.
8. ?????
9. Profit!
This seems to work OK, but what I was hoping to implement was something more like using the directory from step 3 as a "master" repo where everyone would push and pull from. But from what I gather, this isn't really ideal? In other words, I think it would work better if two devs were working out of the one master repo and push changes back and forth. Instead, we have this repo that looks good but once all code is checked in we have to export the code back onto staging and update the staging project. Does that make sense?
Now on to my questions.
1. In Ryan Farley's article found here:
http://customerfx.com/pages/crmdeveloper/2009/11/12/excluding-saleslogix-model-files-from-source-control.aspx
There's a list of files to exclude. From what I am reading, should we completely exclude the deployment folder?
2. In the SLX training blog found here:
http://slxtraining.net/2009/09/using-saleslogix-web-in-a-multi-developer-environment/
Jason Huber ends his article with the following statement:
"Do not place source control on the output files (C:\inetpub\wwwroot\slxclient). This makes no sense. If you want a copy of these files then use a deployment snapshot instead. This was also covered in boot camp and in the various classes offered at Sage."
For some strange reason, although I have only specified the target folder as the protected repo, all my files in my local output target have source control applied to them as soon as I perform a local deployment. These files are not in the repo. I don't know whether I should leave these alone or remove source control from them.
Thanks in advance. |
|
|
|
Re: Subversion and Application Architect
Posted: 01 Sep 10 3:40 PM
|
OK - I sincerely hope someone else will chime in here.
So I've managed to get the repo going and I'm doing some trial and error with folders to ignore. In the spirit of Jason's statement, I have been looking for the reason why SLXClient is under source control protection.
Turns out that when the contents of Model\Portal\SlxClient\SupportFiles are source protected, then deployed, they remain under source control. When I ignored this folder in Subversion, the SC in the IIS output directory are also ignored.
This is fine, but the issue I have is how we are going to implement source control on SmartParts that are designated for release. If we use the Bundle Manager, will we be able to circumvent this issue? Right now, I've told everyone to simply ignore the folder but I have a feeling that's only half the story.
Thanks. |
|
|
|
Re: Subversion and Application Architect
Posted: 05 Oct 10 8:54 AM
|
Hi Elliot
We're using Git which frankly is pretty easy to set up and get working, especially with the Git Extensions for Saleslogix plugin provided by CustomerFX - full control from WITHIN Application Architect!
These are the only things we ignore within the working directory:
# Model files that are auto-generated
[Mm]odel[Ii]ndex.xml
# Standard deployment files
[Mm]odel/[Dd]eployment
I can't see any reason why subversion should be tying Model\Portal\SlxClient to the actual deployed website. You want the first to be source controlled, but not the second.
With regards to getting your changes to the central repo to appear in the staging workspace, you may want to consider some form of Continuous Integration. |
|
|
|
You can
subscribe to receive a daily forum digest in your
user profile. View the site code
of conduct for posting guidelines.
 Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
|
|
|
|
|
|
|
|