 |
|||||||||
|
|||||||||
|
|
One of the problems with SharePoint development quite simply: you need SharePoint in order to develop. There is always the scenario where you take the DLLs from the SharePoint server, copy them to your XP machine and you tinker around until you get something manageable. I knew people that did this very thing, and they had extremely complex batch files that would deploy from their development machine, then they'd go to the SharePoint server, run iisreset, hit refresh, pray, and then wonder why they had so much trouble debugging.
First and foremost, you need Windows Server 2003 R2. If you can spare a physical box then that's an ideal situation just because of the sheer amount of crap you're going to install on this server, but I have used VMware and Virtual PC as well. If you're going the virtualization route, VMware seems to be the more robust solution and also seems to run much faster than VPC (and no, I don't work for VMware :)).
Second - install Microsoft SQL Server 2005 Developer Edition. You don't need to install Analysis Services or Reporting Services, but you might find yourself using Notification Services or the Service Broker at some point, so install Notification Services.
Thirdly, you need Microsoft Office SharePoint Server 2007. Don't bother installing WSS v3.0 without MOSS. As a developer, you want the full boat, and you'll need it for all the powerful enterprise features like Excel Services, the Business Data Catalog, etc. When you install this, do not install the standalone copy. You want to create a single-server farm and point your content and configuration databases at the SQL Server instance. The reason for this is that MOSS running on top of MSDE is quite possibly one of the most horribly performing application combinations I've ever seen, and your dev environment will screech to a grinding halt in Standalone mode.
Next, you need Visual Studio 2005 - at least Professional, but if you've got an MSDN subscription you might as well install the full boat. Also, if you're doing this for your company, you might want to consider installing the TFS client so you can check your SharePoint code in and out of Team Foundation Server. That's right - I actually said there was a good way of source-controlling SharePoint code - something that has been lacking in all previous versions of it.
So, to recap, setting up your development environment involves the following, in this order:
You will also want to find some migration path from your environment to a staging or testing environment, but the rest of those details are specific to your organization and your environment. If you create your SharePoint environment using the preceding steps and resign yourself to knowing the fact that you will be developing on Windows Server 2003 for all of your SharePoint work (unless you're doing Web Services, in which case any client environment will do) - then you should be off and running.
Now all you need is a good book to teach you everything you need to know about SharePoint programming :) *hint* *nudge* *wink*
Great tips. Have just placed an order for your book on Amazon UK. Can't
wait to get the book. Many thanks.
Why do you say "First and foremost you need, you need Windows Server 2003
R2." What is the benefit of R2 over SP1 to MOSS? Is there a real need?
R2 is a pre-requisite. You cannot install MOSS on a non-R2 version of
Windows Server 2003 because R2 is the version that enables .NET Framework
2.0 support for WSS v3, upon which MOSS is built.
How would you set up a development environment with multiple developers?
Obviously we need the ability to work independently (in the environment you
outlined above) but then combine our changes on a central server. Any ideas
on how to move content from several development servers into a single
SharePoint instance?
Can you run MOSS 2007 on SBS 2003 r2 premium w/ sql workgroup edition?
you can use something like TFS to centrally manage your code. If you are
using the WSS v3 extensions for Visual Studio, you'll notice that when you
deploy the solution to your local server, it creates a setup.bat file that
does the deployment.
I am not able to install sharepoint extension for VS 2005. I got the
"unexpect error and send report to Microsoft" message. Any Tips for that?
You Wrote:
R2 is a pre-requisite. You cannot install MOSS on a non-R2 version of
Windows Server 2003 because R2 is the version that enables .NET Framework
2.0 support for WSS v3, upon which MOSS is built.
I have MOSS 2007 installed on a Win2003 machine, not Win2003R2. I simply
installed .NET FW 2.0 before installing Sharepoint and it worked like a
charm.
I looked at the book description on Barnesandnobel.com. It looks like
programming focuses on C#. Is there a good resource for those of us that
are VB.net trained and want to do SharePoint development????
Thanks for the really good tips. Always good to hear this kind of things
from someone who has already been to this place I'm in.
Actually, R2 is NOT REQUIRED to run MOSS. As long as the .Net framework 2.0
and 3.0 are installed, you're ready to go. I have installed MOSS about 10
times to Windows Server 2003 SP1 just fine.
Well, R2 was a requirement during all of the beta phases, and I just never
read anything to the contrary since release.
What about licensing? I can't imagine that you need a server license for
each developer.
Well, if you are developing for SharePoint, then all of your developers
should be covered under their MSDN subscription license. Once you get into
production mode, then you need a server license, and then you need a CAL
(Client Access License) for each person using the system. If you've got a
Microsoft rep or licensing reseller, talk to them about the licensing plans
because Microsoft has different options for organizations of different
sizes.
Can I access user profile from an asp.net application? My application is
running on the same server as SharePoint Server 2007 and I am using object
model to access user profiles. It give me unauthorized access error. How
can I solve this? Please help.....
Try this on a laptop with a virtual machine, its taken me all day!
hopefully I can convince the IT manager to let me use the Dev Server when I
show him what we can do :)
Now you can install WSS 3.0 SP1 on Vista
Can we use MOSS2007 On windows XP. Is it necessary that we need
WindowsServer2003 installed in our system for developing share point
applications.Can anybody clarify me? Thanks in advance
