Hi Paul

The couple of SharePoint MVPs I've had the opportunity todiscuss this with
have been in consenus that when developing solutions for SharePoint it is
their recommendation that developers, particularly in a team environment
each utilise their own dedicated MOSS development environment. Given the
realities of most organisations it is not possible for a developer to
maintain both a day-to-day general use PC/laptop as well as a dedicated MOSS
development server for each project they are involved in. The solution to
this is the use of virtualisation technology to enable the developer to run
and maintain one or more virtual servers that contain the required
development environment. Assuming the PC/laptop is adequately resourced this
virtualised development environment can be hosted on the one PC/laptop per
developer.  The recommended install within the virtualised server is, as you
would expect, whatever your current production MOSS environment is
running. When a developer's solution has problems, local debugging on the
virutal server is the most efficient way to address the problem and
alleviates the problem where when a break point is hit the MOSS instance
stops until execution is continued.

To create a robust server development environment within the virtualised
server, each of the developers should also have the following installed:

   - Server installation of Microsoft Visual Studio 2008 (we have Developer
   Edition)
   - Microsoft Visual Studio 2008 including Microsoft Visual Studio Tools
   for the Microsoft Office system (3.0)
   - Microsoft Visual Studio Extensions for Windows SharePoint Services
   (1.2)
   - Microsoft SQL Server 2005 instance (assuming your production env is
   running the same)

When each developer has his/her own instance of SQL Server 2005 and Office
SharePoint Server 2007 or Windows SharePoint Services 3.0, this
configuration helps prevent conflicts during development, mitigates
performance issues during debugging, and ensures that the solution works in
multiple environments

Here is an MSDN article that touches on this topic..
http://msdn.microsoft.com/en-us/library/bb428899.aspx

Regards,

Kirk.
2008/7/29 Paul Noone <[EMAIL PROTECTED]>

>  Hi all,
>
>
>
> I have yet another potentially embarrassing question.
>
>
>
> I've recently installed VS2008 on my local XP machine as a precursor to
> getting my hands dirty with some custom workflow activities and looking at
> what the VSeWSS 1.2 tools can do. And, well, ahem…it appears that remote
> connection to a MOSS server are not sufficient for the task.
>
>
>
> Short of wiping my current box, installing Windows Server 2003, MOSS2007
> and WSS3, I'd prefer to explore other possible solutions.
>
>
>
> What are other people doing for local dev? And if the resounding response
> is a VM, would someone mind outlining the requirements for one?
>
>
>
> And one more silly question (while I'm on a roll), can you wrap up SPD
> developed workflows with the SSG and: a) redevelop them in VS, b) deploy
> them to other sites and collections?
>
>
>
> As ever, all replies are gratefully received.
>
>
>
> Kind regards,
>
> Paul Noone
> Online Developer, ICT
>
>
>
> ------------------------------
>
> ____________________________________________________________________________
> This e-mail is intended for the use of the addressed recipient(s) only and
> may contain confidential and privileged information. If you have received
> this message in error, please delete the message and any attachments and
> copies immediately; and notify the sender by return e-mail.
>
> Any views expressed in this message or any attachments are those of the
> individual sender and do not necessarily represent the corporate opinion of
> the Catholic Education Office (CEO), Sydney.
>
> The CEO Privacy Policy is located at http://www.ceo.syd.catholic.edu.au
> ____________________________________________________________________________
>
>
> -------------------------------------------------------------------
> 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