2024年1月21日发(作者：)

. This is optional, but if you do any development beyond SharePoint you likely have clients on , WCF, and essential to SharePoint: WorkflowThe IE Developer Toolbar is optional, but recommended. Inspect HTML source, style usage, IFRAME content, image locations, and r is optional, but recommended. Inspect and manipulate HTTP traffic between your browser and the tor is optional, and one of the best .NET tools ever. “Reflector is a class browser, explorer, analyzer and documentation viewer . Reflector allows you to view, navigate, search, decompile and analyze .NET assemblies in C#, Visual Basic and IL.”(formerly Monad). [] []PowerShell is optional, but recommended. Write scripts to automate administration and configuration tasks. Colin Byrne has posts to getyou started: , , and .Office System Professional Plus Edition

Grab your disc, , or . The Professional Plus edition includes Word, Excel, Outlook and PowerPoint plus: Access, Publisher and is also an Enterprise edition which also includes OneNote and oint Designer (SPD)Grab your disc, , or .Visual Studio 2005Grab your disc, , or .Build Web Parts, Field Controls, List Definitions, Site Definitions, and Content Types. Also includes the SharePoint Solution Generator(SPSolGen) which converts lists and sites “Saved as Template” into list and site definitions. []Design Windows Workflow Foundation solutions for SharePoint and other .NET is used to build: Office System (Word, Excel, etc.) Add-ins and Ribbon elements, Outlook forms, and InfoPath templates.. Optional extensions are available unrelated to SharePoint, though you should know they exist if you do other .NET development.

Generate BDC XML from SQL data sources. The commercial version also builds definitions for web services. [][]The download also includes the Enterprise Content Management Starter is where you will build all those beautiful webs! is a popular may want SQL Express if you develop more than SharePoint and need a local data store. If not, it is built into the SharePointstandalone install so you do not need to download or install it locally.

Click Start, Control Panel, and open the Add Hardware wizard.

Click Next. Wait a moment while the wizard scans for : Yes, I have already connected the hardware, click Next.

Scroll to the bottom of the list and select Add a new hardware device. Click Next.

Select: Install the hardware that I manually select from a list (Advanced). Click : Network adapters. Select: Microsoft. Select: Microsoft Loopback Next. Click Next again. Wait a moment. Click Finish.

Click Start, Control Panel, and open the Network Connections -click the Microsoft Loopback Adapter connection and select Properties.

Double-click Internet Protocol (TCP/IP).Now configure an address for this adapter.

Select: Use the following addressIP Address: 10.50.50.1Subnet mask: 255.255.255.0Default gateway:

You can ignore DNS. Click OK. Click OK again.

Building the Server: Articles(up to the point where you install the OS)., and why you might need to add servers to the farm (e.g. for Exchange).. 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 heputs SPD and Office on the server, while the goal of this post is to keep your server clean of client oft Guidance on and .. He installs Visual Studio to the server, you can skip that step and run it locally on your development SQL and AD on a separate machine. His “OfficeDev” machine looks the most like our local development machine. One day someonewill write an article with configuration steps, until then this is a good ng the Server: Step-by-StepStep 1: Install the Operating SystemWindows 2003 Server R2. Grab your disc, , or .

Step 2: Configure Networkingso you can surf your virtual SharePoint sites from your development machine.. In this configuration, while your virtual machines will see each other, your local machine will not be able to surf or debug the that if you can join your virtual machine to your company’s domain and create domain accounts there (but different accounts than youwill use for testing or production), it will simplify configuration and debugging, and you won’t need to make this or any machine in yourdevelopment farm an Active Directory domain controller (DC). The drawback is that you need to be connected to the domain to get anywork done.

Step 3: Install the .NET FrameworkWPF, 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 specificpurpose.

Step 4: Install Active Directory and 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 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 ActiveDirectory and SQL Server. Note that after you install SharePoint you will not be able to make the machine a domain controller (unlessyou’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 IIS is installed, you will need to Allow 2.0.* in the Web Server Extensions section of the IIS Manager. If this option is notavailable, you may need to run the 2.0 setup and Repair your installation, which also sets the Allow flag.

Step 6: Install SQL ServerSQL Server Developer Edition []This is optional. If you don’t install it, Express Edition will be installed when you install SharePoint. However, Developer Edition includesthe excellent SQL Server Management Studio, so if you have MSDN you may prefer it. For a production environment you will need tolicense SQL Server Standard or Enterprise Edition.

Step 7: Install SharePoint (WSS or MOSS)WSS is a free extension to Windows Server. If your installation didn’t include WSS as an option, you can download now. If installingMOSS, then you do not need to separately install WSS. Also remember that you can upgrade a server, but you cannot downgrade fromMOSS back to WSS. If you’re evaluating SharePoint you may want to start with you installed SQL Server Developer Edition, choose Advanced Installation to select your oft Office SharePoint Server (MOSS) 2007Grab your disc or , or . Standard and Enterprise editions exist, so again keep in mind that you can upgrade but not downgrade. Enterpriseincludes Forms Server and the down and back up your virtual machine image(s).Step 8: Configure SharePointCreate a domain group for SharePoint Administrators, assign rights to it rather than any single account. The exception will be configuringSQL 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'llneed 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 (). Add your developer account tothe Administrators group (Global Administrators if this is a DC, local Administrators if not) and Debugger Users a typical end-user account for testing. Make it a member of Domain Users.

Step 9: Configure the server for DevelopmentIf you must develop on the server, install Visual Studio now. On one side, developing locally is simpler than developing remotely. On theother 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 youreally can’t get the hang of remote debugging, you can always install VS 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 FilesCommon FilesMicrosoft Sharedweb server extensions12C:inetpubwwwrootBackup the 12 hive into a zip file marked as read-only, and named “[Drive]:”. You get theidea. When you accidentally edit a default file with WordPad and kill your site you will be glad you finally, make a text file on your desktop with .

Step 10: Configure remote SharePoint is installed, share the folder with SharePoint’s assemblies (*.DLL). You may also want to copy the assemblies to yourdevelopment machine:C:Program FilesCommon FilesMicrosoft Sharedweb server extensions12ISAPIShare the server’s web root and enable Read/Write.

C:inetpubwwwrootInstall the Visual Studio 2005 Debugging Components to the server. You want Full Remote Debugging, not Native Remote . You’ve just completed his step 1 and if you created your developer account as specified then you’ve also done 2 and a look at Andrew Noon’s document on . He has additional steps for enabling error messages in and screen shots thatshow what debugging looks like in :Read:

AcknowledgementsThanks to the MOSS MVPs for suggesting ways to improve this Lloyd was one of the first people to build minimal servers, and he’s always got great new gadgets like eSATA drives.