CJ

The circle of life – ** .Net – Training – MOSS **

  • Past Post

  • Vistor Locations

MOSS Development Environment

Posted by Clayton James on May 16, 2007

I am in the process of setting up a clients MOSS development environment and reasearching various ways things can be achieved. I did some browsing a couple of weeks ago and didn’t find much content. But then on Monday I came across an article written by Microsoft (realeased April 2007) explaining the how to configure MOSS for Team-base development.

This article discusses two different forms of development that demand different development environments, namely assembly and artifact:

  • Assembly: Similar to traditional application development using Visual Studio to develop webparts, site/list definitions, etc…
  • Artifact: This relates to the look and feel of the site (master pages, css) and relates more to content.

What I found interesting was that the assembly development environment is based on the traditional form.
–> development –> progress to testing –> progress to production

But the artifact development environment is actually considered a production environment as MOSS has an inbuilt workflow approval process for content modfications.
–> production authoring environment –> production environment

I think this is just the article I was looking for 🙂

Advertisements

4 Responses to “MOSS Development Environment”

  1. Matt said

    have a look at http://blogs.msdn.com/sharepoint/archive/2007/04/10/debugger-feature-for-sharepoint.aspx
    It has a great debuggin tool!

  2. Rahul said

    As per our policy we need to have development environment where all changes must be tested before they can be put into production. Hence the changes to artifacts are implemented in dev environment and once proved can be migrated to Production.

    What is the best way to migrate the changes from dev to production without having to do it manually (its prone to error) and basic purpose of our policy is thrown out of the window.

    Please suggest

    Thanks
    Rahul

  3. CJ said

    Hi Rahul

    The way to migrate application development through dev–>stage–>prod is to use a new deployment process called Solutions (.wsp files). This allows developers to package up their development changes into a single .wsp file which is a .cab file underneath.

    Once the .wsp file has been created it is then added to Central Admin using stsadm, then from Central Admin it can be deployed to all of the WFE servers in the farm.

    This also allows developers to version their solutions packages using a source control product.

    Here is an article about solutions
    http://blogs.msdn.com/cjohnson/archive/2006/09/11/749105.aspx

    Another with sample code
    http://msdn.microsoft.com/msdnmag/issues/07/08/OfficeSpace/default.aspx

  4. Pjnwlind said

    ooOzIT comment4 ,

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

 
%d bloggers like this: