Hi Simon,

I know that there is a white paper that MSFT put out a while ago that
covers "best practices" for SP development.

I will try to find it for you.

 

Cheers,

Aaron

 

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Simon Cropp
Sent: Wednesday, 2 April 2008 10:40 AM
To: listserver@ozmoss.com
Subject: [OzMOSS] The perfect MOSS development environment?

 

All

I am curious to find out how people have set-up their development
environments for SharePoint.

ATM we have several developers. Each developer has their own virtual
machine (running locally) containing Win2003, SQLServer, MOSS, VS.Net
etc. 

Each developer is also in charge of the following

-ensuring they have the latest source of the project
-ensuring their virtual machine has the correct patches and service
packs
-ensuring that MOSS is setup and configure correctly
-ensuring they take snapshots of their VM if they are doing anything
that might break it

This is a large amount of overhead for every developer. I was wondering
how other people manage their environment.

Are there better was to do this using a server based virtual
environment? Perhaps each day a developer gets a new refreshed image
hosted on the server. When changes need to be made (window updates, MOSS
config etc) the base image is updated and the developers will get it on
the next day. If a developer breaks their image they can simply get a
new one.

Anyone know of Microsoft links that talk about this stuff?

Assume for this discussion that hardware is not an issue and both VMWare
and Microsoft are options. What do you see as the perfect dev
environment for MOSS?

Regards.

Simon

-------------------------------------------------------------------
OzMOSS.com - to unsubscribe from this list, send a message back to the
list with 'unsubscribe' as the subject.
Powered by mailenable.com 




------------------------------------------------------------------- OzMOSS.com 
- to unsubscribe from this list, send a message back to the list with 
'unsubscribe' as the subject.

Powered by mailenable.com

Reply via email to