[Update 2008-12-05: Justin Devine posted a fantastic article to build on this posting that contains many screen shots, additional comments and a section on writing and debugging your first SharePoint program in your new environment. So give this a read-through, but as you walk the steps I recommend starting from Justin's posting where you'll also see the visual cues and where necessary, links back to here.]
There are two choices: You can build a SharePoint server that contains all your developer tools too. Or you can build your SharePoint server in a virtual machine (VM or VPC), and keep all your developer tools local. Then you can treat your virtual machine just like a physical server, and surf or demo it just as you would a production environment. This way you avoid all the inconsistencies that come with running browser session on locked-down web servers, don’t fill your server’s GAC with quite as much junk, and really get the client experience. You can use this post as a starting point to build either.
This post describes the tools you will use. There are always others, so go ahead and tell me about yours in the comments section. I’ve left off CSS and XML editors because frankly the best aren’t free. Even though a few items listed here are commercial products (e.g. Visual Studio), all have evaluation versions that last long enough for you to learn the ropes and prepare for that first big SharePoint interview.
The biggest controllable factors on the speed of your SharePoint development environment are RAM and hard drive speed. If you do a lot of development, you will also want a lot of storage space to hold all those virtual machines.
The configuration described here is intended for a good laptop, which today is limited to 4Gb RAM. If you have 4Gb, give the virtual machine 2Gb. If you have 3Gb, give the virtual machine either 1.5Gb or 2Gb. If you have 2Gb or less, buy more RAM or host your virtual server elsewhere. Seriously.
If you need Exchange Server for any reason (1 to 2Gb recommended), you’ve grown out of laptop labs and should build this on a Virtual Server (or VMWare) host if you want some hair left over when you’re done. To build medium or large farms in a virtual environment, Virtual Server running on a 64-bit Windows 2003 Server R2 machine will remove your memory limitations. A 64-bit Vista machine provides the same expandability with Virtual PC or VMWare.
There are several factors to hard drive speed: keeping your VM on a different drive than your OS, drive transfer rates, and drive speed. Put another way: you want a big fast external drive. You can get a pretty big drive for around $200CAD now (I like my Seagate), and an enclosure with Firewire or eSATA (external SATA) is about $50CAD. If you don’t have Firewire or eSATA on your laptop you’ll need an adapter for that as well (also $50). Why not USB 2.0? Firewire is 33% to 70% faster than USB depending on the operation. eSATA is about five times faster than USB 2.0. While many enclosures also have a USB port, the difference is well worth it. PCMCIA (CardBus) runs at 132Mbytes per sec so an adapter for any of these will treat you fine. Note that newer laptops may have an ExpressCard slot instead of a PCMCIA slot.
Transfer Rate (Mbits per second)
1500 to 2400
The assumption is that you know what you like, know what you want to do, and will download and install accordingly. That said, maybe you really do want to develop with Notepad so here goes.
On your development machine you need the .Net Framework version 3.0 and a development interface (IDE), whether it’s Visual Studio, SharePoint Designer, or a plaintext editor like Notepad. If you don’t have a physical server available, you will use either Virtual PC or VMWare to host SharePoint. Beyond these, everything is optional.
On your server, you need Windows Server, IIS, the .Net Framework version 3.0, and either WSS, MOSS Standard, or MOSS Enterprise.
Building the Client
.Net Framework 2.0. This is optional, but if you do any development beyond SharePoint you likely have clients on v2.0.
.Net Framework 3.5
WPF, WCF, and essential to SharePoint: Workflow. Note that MOSS 2007 works great with .NET 3.5, is supported by Microsoft, and there is no reason not to deploy it for all your servers.
[Update 2008-11-04] Do not install .NET 3.5 SP1 if you require Records Center, and until the cause is identified there is a risk that other features are also affected. .NET 3.5 itself remains okay, this issue is only reported with SP1.
Microsoft Office SharePoint Server 2007 SDK [Read it online]
The MOSS SDK includes the Enterprise Content Management (ECM) Starter
Kit, a BDC definition editor, an Excel UDF sample, great workflow
samples, and lots more.
Windows SharePoint Services (WSS) 3.0 Software Development Kit (SDK) [Read it online]Red Gate .NET Reflector (was Lutz Roeder's Reflector)
The MOSS SDK contains this so you don't need both. If you only do WSS development, then you only need the WSS SDK.
One of the best .NET tools ever, and the way you'll browse object models and cut the class-assembly strings you'll need to paste into your manifests and web.config. “Reflector is a class browser, explorer, analyzer and documentation viewer for .NET. Reflector allows you to view, navigate, search, decompile and analyze .NET assemblies in C#, Visual Basic and IL.”
SharePoint Manager 2007
The best SharePoint management tool there is. Browse the complete object model, deactivate features, and even update object properties. You do need to be careful with this one, but wow it's powerful.
Office System Professional Plus Edition
Grab your disc, MSDN, or get the evaluation version. The Professional Plus edition includes Word, Excel, Outlook and PowerPoint plus: Access, Publisher and InfoPath. There is also an Enterprise edition which also includes OneNote and Groove.
SharePoint Designer (SPD)
Grab your disc, MSDN, or get the evaluation version.
Visual Studio 2005 or 2008Visual Studio 2005 Extensions for .NET Framework 3.0 (Workflow Foundation)
Grab your disc, MSDN, or get the evaluation version. I prefer either VS Professional or VSTS Developer Edition.
Not required with VS 2008 where these features are baked-in. Design Windows Workflow Foundation solutions for SharePoint and other .NET applications.
Visual Studio 2005 Tools for the 2007 Microsoft Office System (VSTO)
VSTO is used to build: Office System (Word, Excel, etc.) Add-ins and Ribbon elements, Outlook forms, and InfoPath templates.
Other Visual Studio Extensions. Optional extensions are available unrelated to SharePoint, though you should know they exist if you do other .NET development. Virtual PC 2007
This is where you will build all those beautiful webs! VMWare is a popular alternative.
SQL Server Express Edition
You may want SQL Express if you develop more than SharePoint and need a local data store. If not, it is built into the SharePoint standalone install so you do not need to download or install it locally.
Fiddler HTTP Debugger
Optional and strongly recommended. Inspect and manipulate HTTP traffic between your browser and the server, great for debugging forms and web services, determining whether Kerberos tokens are being generated, and more.
Internet Explorer Developer Toolbar
IE Developer Toolbar is optional, but recommended. Inspect HTML source,
style usage, IFRAME content, image locations, and more.
PowerShell (formerly Monad). [SharePoint Provider] [Script Repository]
is optional, but recommended. Write scripts to automate administration
and configuration tasks. Colin Byrne has posts to get you started: PowerShell and SharePoint, Build Me A Portal, and Upload a Directory in 4 Lines.
BDC Metadata Manager
Generate BDC XML from SQL data sources. The commercial version also builds definitions for web services. An alternative is baked into the MOSS SDK, but BDC Metaman will continue to be the gold standard.
Visual Studio 2005 Extensions for Windows SharePoint Services 3.0 (VSeWSS)
Not recommended. VSeWSS contains nothing to help you deploy features on anything but the machine running VS,
does not support x64, and is required to open projects that it creates.
So if you create a project today on a 32-bit machine, you will be
unable to open it in a year when you're building on 64-bit. This is
bad. The one good feature included is the SharePoint Solution Generator
(SPSolGen) which converts lists and sites “Saved as Template” into list
and site definitions. [Learn more here] [Registry hack to install VSeWSS to a machine that is not the server]
Required to create a private LAN between the client and server
Microsoft Loopback Adapter
a. Click Start, Control Panel, and open the Add Hardware wizard.
b. Click Next. Wait a moment while the wizard scans for hardware.
c. Select: Yes, I have already connected the hardware, click Next.
d. Scroll to the bottom of the list and select Add a new hardware device. Click Next.
e. Select: Install the hardware that I manually select from a list (Advanced). Click Next.
f. Select: Network adapters. Select: Microsoft. Select: Microsoft Loopback Adapter.
g. Click Next. Click Next again. Wait a moment. Click Finish.
Configure the Loopback Adapter
h. Click Start, Control Panel, and open the Network Connections utility.
i. Right-click the Microsoft Loopback Adapter connection and select Properties.
j. Double-click Internet Protocol (TCP/IP).
k. Now configure an address for this adapter.
Select: Use the following address
IP Address: 10.50.50.1
Subnet mask: 255.255.255.0
You can ignore DNS. Click OK. Click OK again.
Building the Server: Articles
Bob Fox explains step-by-step how to install Windows 2003 to Virtual PC and VMWare (up to the point where you install the OS).
Bob Fox explains good habits on re-using your base image for several implementations, and why you might need to add servers to the farm (e.g. for Exchange).
How to Create a MOSS 2007 VPC Image. This step-by-step series with screenshots by Tony Zink is as complete as complete can be and starts with configuration of IIS. Note that he puts SPD and Office on the server, while the goal of this post is to keep your server clean of client apps.
Microsoft Guidance on Standalone and Farm configurations.
Kevin Hoffman explains how to build a Standalone SharePoint server. He installs Visual Studio to the server, you can skip that step and run it locally on your development machine.
Jonathan Bradshaw explains how to build a Small Farm configuration with SQL and AD on a separate machine. His “OfficeDev” machine looks the most like our local development machine. One day someone will write an article with configuration steps, until then this is a good start.
Building the Server: Step-by-Step
Step 1: Install the Operating System
Windows 2003 Server R2. Grab your disc, MSDN, or get the evaluation version. Bring the machine up-to-date with Windows Update. Note that this process can last several hours.
Step 2: Configure Networking
R. Aaron Zupancic describes how to configure an IP address and host file entry so you can surf your virtual SharePoint sites from your development machine.
Simon Guest describes how to get all the machines in a virtual farm to talk to each other. In this configuration, while your virtual machines will see each other, your local machine will not be able to surf or debug the virtual machines.
Note that if you can join your virtual machine to your company’s domain and create domain accounts there (but different accounts than you will use for testing or production), it will simplify configuration and debugging, and you won’t need to make this or any machine in your development farm an Active Directory domain controller (DC). The drawback is that you need to be connected to the domain to get any work done.
Step 3: Install the .NET Framework
.Net Framework 3.0
WPF, WCF, and essential to SharePoint: Workflow.
Once activated and configured, Shut Down and back up your base server image. In the next steps you’ll prepare this machine for a specific purpose.
Step 4: Install Active Directory and DNS.
If this is going to be a Standalone configuration, you need a domain controller (DC). The Configure Your Server Wizard (Start, Administrative Tools) is a great way to assign roles to a server. Start with Domain Controller (Active Directory) and DNS.
If this is going to be a Small Farm, copy your base server image from the last step, and start building a second machine to host Active Directory and SQL Server. Note that after you install SharePoint you will not be able to make the machine a domain controller (unless you’re prepared for a world of hurt).
Step 5: Install Internet Information Server (IIS)
Once again, the Configure Your Server Wizard (Start, Administrative Tools) is an easy way to add the Application Server role to your VM.
Once IIS is installed, you will need to Allow ASP.NET 2.0.* in the Web Server Extensions section of the IIS Manager. If this option is not available, you may need to run the ASP.NET 2.0 setup and Repair your installation, which also sets the Allow flag.
Step 6: Install SQL Server
SQL Server Developer Edition [Google]
This is optional. If you don’t install it, Express Edition will be installed when you install SharePoint. However, Developer Edition includes the excellent SQL Server Management Studio, so if you have MSDN you may prefer it. For a production environment you will need to license SQL Server Standard or Enterprise Edition.
Step 7: Install SharePoint (WSS or MOSS)
Windows SharePoint Services (WSS) 3.0
WSS is a free extension to Windows Server. If your installation didn’t include WSS as an option, you can download now. If installing MOSS, then you do not need to separately install WSS. Also remember that you can upgrade a server, but you cannot downgrade from MOSS back to WSS. If you’re evaluating SharePoint you may want to start with WSS.
If you installed SQL Server Developer Edition, choose Advanced Installation to select your database.
Install the WSS Service Pack.
Microsoft Office SharePoint Server (MOSS) 2007
Grab your disc or MSDN, or get the evaluation version. Standard and Enterprise editions exist, so again keep in mind that you can upgrade but not downgrade. Enterprise includes Forms Server and the BDC.
Install the Office SharePoint Server Service Pack. [SP1]
Shut down and back up your virtual machine image(s).
Step 8: Configure SharePoint
Create a domain group for SharePoint Administrators, assign rights to it rather than any single account. The exception will be configuring SQL Server, where rights buried inside groups aren't always resolved and you need to assign permissions per-account.
Create an account to use as your SharePoint Service account (e.g. SPService). Configure this to be your Application Pool identity (you'll need to search what rights are required until I complete this section).
Create a content crawler account (you'll need to search what rights are required until I complete this section).
Create a developer account with the same name as the account you use on your development machine (and it better not be Administrator). Add your developer account to the Administrators group (Global Administrators if this is a DC, local Administrators if not) and Debugger Users group.
Create a typical end-user account for testing. Make it a member of Domain Users.
Step 9: Configure the server for Development
If you must develop on the server, install Visual Studio now. On one side, developing locally is simpler than developing remotely. On the other side, it’s so handy to keep all your code in one place and you won’t ever wonder where the most recent version of x is residing. If you really can’t get the hang of remote debugging, you can always install VS later.
Open up File Explorer on the server and Add to Favorites your frequently-used paths including the 12 hive and the default web root.
C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\
Backup the 12 hive into a zip file marked as read-only, and named “[Drive]:\Backups\12Hive-Out-of-Box-DoNotUpdate.zip”. You get the idea. When you accidentally edit a default ONET.XML file with WordPad and kill your site you will be glad you did.
And finally, make a text file on your desktop with Joubin’s SharePoint paths.
Step 10: Configure remote debugging.
Once SharePoint is installed, share the folder with SharePoint’s assemblies (*.DLL). You may also want to copy the assemblies to your development machine:
C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\ISAPI
Share the server’s web root and enable Read/Write.
Install the Visual Studio 2005 Debugging Components to the server. You want Full Remote Debugging, not Native Remote Debugging.
Follow Ross Dargan’s instructions on configuring remote debugging. You’ve just completed his step 1 and if you created your developer account as specified then you’ve also done 2 and 3.
Take a look at Andrew Noon’s document on Remote Debugging SharePoint Web Parts. He has additional steps for enabling error messages in web.config and screen shots that show what debugging looks like in action.
Read: Setup Remote Debugging
Read: Debugging SharePoint Web Parts
Thanks to the MOSS MVPs for suggesting ways to improve this post.
Thomas Lloyd was one of the first people to build minimal servers, and he’s always got great new gadgets like eSATA drives.
2007-03-02 Rearranged and added sections in a major overhaul of this post.
2008-02-27 Added a section for optional utilities, added references to VS 2008 and the service packs, added SharePoint manager 2007, rewrote parts of the introduction.
2008-11-04 Updated links to Reflector and others, added caveat for .NET 3.5 SP1, and minor text corrections.
The Business Data Catalog (BDC) is one of the best features of MOSS 2007 (no, it's not in WSS 3.0). What excites me is the prospect of not only reading from, but writing back to data sources defined in the BDC. It's recently come up a few times and I've found that many people believe that updating source data is simply not possible, so I second-guessed myself and went back for a closer look to clarify the reality.
The goal is to create, update, and delete data in addition to retrieving collections, single items and enumerators. There are two ways to do it, and both aren’t quite ends in themselves though only a little extra work is required for deletes.
The first method is to treat the BDC source simply as a data reader, and to build your create/update/delete logic in an assembly. The BDC object model provides the means to retrieve collections, list items and enumerators, and you do the rest. You get the Web Parts to display data, but you still need to roll your own forms inside web parts to create and update.
The other way is with Actions. Think of an action as simply a Link which appears beside each BDC item. In constructing the link, you can inject parameters from the selected BDC row. So the easiest here is Delete, though even that requires building a page that invokes the Delete method and then redirects back to the calling page (assuming the reload will show the revised list). Create and Update still require a form to edit content, and you could launch such a form from an Action. Again the BDC isn’t the end in itself. Additional benefit is that Actions are displayed in BDC Web Parts. They’re great for things like +1, -1, Map this location, Go buy this book, or Go see this product’s web page.
A third way that I don't consider "SharePoint" though it is "Office" is to create an Action which opens an InfoPath form to edit a BDC object. It’s the recommended solution. It requires InfoPath. It does work. Coming from a web background, I want SharePoint to be my web platform so requiring any application besides a browser seems klunky to me.
Before today, I thought there way another way but it turns out it doesn’t have all the pieces to work. You specify a data source's methods in the BDC’s configuration. The standard types are Finder, SpecificFinder, and IDEnumerator, and additional methods can be defined with the GenericInvoker type. I thought you could plug parameters into a GenericInvoker to run ops on a specific item, but its parameters aren't row-specific. So, it’s fine for invoking simple methods on the source, launching processes, and perhaps to lookup lists of available choices for a particular field, but doesn’t mean much for creating or updating new records.
So yes, you can specify methods that update a data source from a BDC configuration file, but they don’t automatically give you consistent ways for a user to create or update records. The easiest way to make forms to update items in BDC data sources is with InfoPath. Back to the Studio.
And then there's LOBi, for "Line-of-business Integration." This is the successor to the Information Bridge Framework (IBF). My understanding was that LOBi builds on the BDC, and then a product like Duet builds on LOBi for a specific data source. In Duet's case that source is SAP. The LOBi document linked above seems to dispute this and positions LOBi as a read-write alternative to the BDC. So maybe it was originally explained to me by someone in sales or marketing, for whom "builds on" means "it costs more and does more" rather than "y uses x as its underlying technology." Either way, LOBi would seem to solve the issue, if only there were a download, documentation, sample code, and a web part or two to refer to. Alas, back to custom code or InfoPath. And Studio.
Until next time,