7/4/2025 2:32:44 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.
|
|
|
|
Optimal Setup for Multiple Developers for 7.5 Web
Posted: 08 Sep 09 2:39 PM
|
I attended the Developing for SLX Web v7.5 course back in June. Unfortunately, we did not have a Dev environment at all until recently and I am not sure we are ready to go yet at this point. Here's the question: Assuming we are going to have multiple developers working on the same database, architecturally speaking what would be the ideal workstation setup for these developers? Assume we want the ability to develop not only in Application Architect but also Visual Studio and all other available tools. We are probably not going to be able to have IIS installed on both of the Development workstations due to security issues.(Unless there was some overwhelming reason to do so that would justify a security exception.)
I was adept at SLX Client Server development but this web thing is very new to me and at the moment somewhat overwhelming.
Thanks in advance for your expertise.
Jeff Parker
|
|
|
|
Re: Optimal Setup for Multiple Developers for 7.5 Web
Posted: 08 Sep 09 6:42 PM
|
You don't need IIS installed on each developer's machine, but you will need App Architect. Also, if they are doing .Net development, it will include its own Web Server (although only for debugging purposes).
There are many issues with Developers working on the same database. For starters, if you want their work to be shared, you need to keep the VFS on the Server, otherwise you may need to constantly be merging the VFS.
Also, you may want to setup distinct deployment targets for each developer so that they don't overwrite other user's test Sites while reviewing their code.
Also, are you going to be applying Source Control? If so, will it be against the VFS? Or will it be against the site as developed?
I have been involved in projects where All changes were done on VS.Net, in that case, it was quite simple to handle since we were just dealing with the Uncompiled code generated after a Build and it was stored on VSS and shared as any other ASP.Net project.
On the other hand, I have also been part of projects on which the VFS was under Source control, each developer had their own machine and their own VFS. Off course, on this project most changes were done via the App Architect, so it made more sense to do it this way.
|
|
|
|
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!
|
|
|
|
|
|
|
|