10-13-06 12:25 PM
Hi Courtney,
Below are some update of your question and our Commerce team¡¯s comments on
how to build such kind of independent dev environment. The Development
Environment docs has also been included into the product docs to introduce
the process of building independent or shared dev environment:
http://msdn.microsoft.com/library/e...0eb4-6110-4cb1-
a89f-c86fac60d7f8.asp?frame=true
The best practices are:
¡¤ Each developer has CS and SQL installed locally.
¡¤ Each developer maintains their own MSCS_ADMIN with their
solution (this is a subject of major debate but I have found that it works
every time)
¡¤ Each developer can opt to either a) point their resources
locally and maintain local copies of the profiles and catalog or b) point
to a central integration server
¡¤ DO NOT use the add web server command in CS if you share an
MSCS_ADMIN DB! This will make CS think it is operating in a web farm and
developers will bounce from machine when they try to access/debug the site.
As a workaround, you can set the non-secure host name and secure host name
to localhost.
¡¤ Use the QueryStringBuilder for URL¡¯s in your code to make the
code ¡°portable¡± from environment to environment
¡¤ Download the IIS resource kit and use the SelfSSL for testing
https
To set up the minimum environment:
Needed -
¡¤ 1 or more dev workstations with W2k3 CS, SQL and VS.NET
¡¤ 1 Server with CS, VS.NET and SQL (integration)
To set up the first workstation
1. On 1 workstation, create the CS site, application resources and
VS.NET project
2. (optional but highly recommended) Check in the project/connect to
TFS or source safe
3. Modify AzMan for web services
4. PUP the site
5. UnPUP/deploy to a separate integration environment to the same
directory and web site as the developer machine (this eliminates problems
with paths, relative references, etc)
On the other dev workstations:
1. UNPUP the site using custom
2. Point all of the DB connection strings LOCALLY (important)
3. When complete, you can re-point the resources to the integration
environment to share the CSAuth, catalog, profiles, marketing, and
campaigns resources
4. Do not share transaction, transactionConfig, or MSCS_ADMIN, keep
these pointed locally
5. In VS.NET, open the project file and pull down the latest source
from TFS. VSS
Day to day development:
¡¤ If a developer is working on catalog or profile schema, have
them point locally and when complete, push the changes to the central
catalog. If the other developers want to work offline, they will have to
import it.
¡¤ When you build/integrate the project, pull the source or deploy
to an integration environment and smoke test there. (This helps to
eliminate the ¡°works on my machine¡± phenomena J)
¡¤ Use the domain accounts for services, app pools, DB¡¯s etc,
preferably with the same permissions that will exist in production (i.e. no
administrator/local service running the app pools and no SA/DBO access to
DB). This helps to eliminate deployment issues later on.
¡¤ Use a central azman and central web service applications on
integration. If developers need to work offline, they can copy/modify the
Azman and modify their own resource connection strings.
In this case, every developer should have their own instance of Commerce
Server and SQL on their machine.
I hope the info helps. Please let me know if you have further question or
concern.
Sincerely,
WenJun Zhang
Microsoft Online Community Support
========================================
==========
Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscript...ault.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at:
http://msdn.microsoft.com/subscript...t/default.aspx.
========================================
==========
This posting is provided "AS IS" with no warranties, and confers no rights.
 Attachment:
This has been downloaded 0 time(s).
[ Post a follow-up to this message ]
| 
