Logo 
Search:

Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Development question

  Asked By: Caitlin    Date: Jun 13    Category: Sharepoint    Views: 605

I'm in a process of moving our company's Intranet site to WSS 3.0
environment. I'm building this site from scratch so I need to create
Master Pages, Web Parts, Workflow etc., In order to do all these I
installed WSS 3.0 in a virtual machine. But I don't know where to
install Visual Studio 2005 (i.e., either in WSS installed Virtual
machine or in my local machine). If suppose I install VS2005 in VM
then I cannot allow "all" developers to work in that. So I need to
install VS2005 in developers machine in order to create master pages
etc., But to create these I need other WSS files from WSS installed
virtual machine. How can I get those from virtual machine to
developer's local machine? So if developers do some changes in their
machine, it should automatically copy in virtual machine's WSS files
and it should reflect in WSS sites.

Share: 

 

6 Answers Found

 
Answer #1    Answered By: Damon Garner     Answered On: Jun 13

I would install a complete environment (OS, SQL, WSS v3, Office clients
including SharePoint Designer, and VS 2005) in a virtual  machine and
have each of your developers work off that virtual machine  locally. Then
when they are ready to move their code to a shared development
environment, they can save their files out locally and provision them
into the shared environment using features (look at the <module> option
in the elements file).

Also, you will likely want to create your master pages  in SharePoint
Designer, not Visual Studio. The issues of customizing/unghosting files
is mitigated by using the above feature file provisioning technique
mentioned above.

 
Answer #2    Answered By: Hans Weiss     Answered On: Jun 13

okay this might work for development  environment. But how about QA
and production environment...? Do I need need to copy files manually
from one stage to another?

 
Answer #3    Answered By: Alison West     Answered On: Jun 13

Yes, you'll need to package your code files up into solutions (WSP
files) and deploy them into each environment.

 
Answer #4    Answered By: Freddy Heath     Answered On: Jun 13

You can use traditional deployment tools and scripts to automate the
movements of WSP files (just CABs really) from one environment to
another.

 
Answer #5    Answered By: Joanna Dixon     Answered On: Jun 13

I think
that Master Page development, like traditional ASPX development, belongs
in the hands of a .NET developer using Visual Studio. In my view,
SharePoint Designer is an Information Worker tool and can assist the
developer in some key developmental tasks, like 1) the creation of Data
Form Web Parts, 2) to generate a one off Workflow that can be handled by
the Wizard (hopefully we can eventually port the XOML to Vistual
Studio), 3) tasks that can only be done in SPD like setting Web Zone
Properties on an instance page or hiding a list from the All Site
Content page. But hard core development  tasks, like the creation of
Master Pages, should remain the domain of hard core developers using
Visual Studio.

 
Answer #6    Answered By: Justine Barrera     Answered On: Jun 13

I'm using Visual Studio to design master
page and it's easy to design in it that SPD.

 
Didn't find what you were looking for? Find more on Development question Or get search suggestion and latest updates.




Tagged: