Go Win7 under Install configuration for SharePoint Server 2010

Transferred from: http://blog.sina.com.cn/s/blog_5d93d7aa010151lp.html

to develop a SharePoint 2010 application, developers must build a SharePoint 2010 development environment. One basic requirement for developing SharePoint 2010 applications is that almost all development work relies on SharePoint 2010 systems, in other words, in addition to Visual Studio 2010 in the development environment, You must also have SharePoint 2010 installed directly. Installing a visual Studio 2010 locally and then using a SharePoint 2010 system on a remote server is not supported.

It is also important to note that SharePoint 2010 Developer tools are built into only the versions of Visual Studio 2010 Professional, and that SharePoint 2010 project templates are only available in both C # and Visual Basic.NET.

2.1.1 Options for establishing a development environment

SharePoint 2010 must use the x64 schema, which in many cases poses some problems in creating the SharePoint 2010 development Environment. However, compared to the previous version, SharePoint 2010 can be installed into Windows Vista x64 S, in addition to the two server operating systems of Windows Server x64 and Windows Server R2 x64 P1 and Windows 7 x64 client operating systems. So developers can have a variety of options to build their own SharePoint 2010 development environment. Table 2-1 lists a few of the main ways that developers can choose.

method	description	Benefits	Disadvantage
Virtual machine running on the developer's local machine	Using virtual machine technology on the developer's local machine, installing Windows Server 2008/2008 R2 x64 in the virtual machine, SharePoint 2010, Visual Studio 2010, to build a complete development environment. All the development work is done in this virtual machine. If the developer's local machine's operating system is Windows Server 2008/2008 R2 x64, you can choose to use the Hyper-V features built into the operating system to create and use the virtual machine. If the developer's local machine's operating system is Vista SP1 x64 or Windows 7 x64, then you can choose to use other third-party virtual machine software, such as VMware Workstation or virtual Box. The	Development environment is more consistent with the actual running environment of SharePoint 2010. The development environment inside the virtual machine is very independent and will not be interfered with by additional extraneous software. The development team can create a standard development environment virtual machine and then share it with each developer. virtual machines are easy to back up. At the same time, common virtual machine software includes branching and rollback capabilities, which gives the development environment greater flexibility.	requires a high-performance development machine, especially a large amount of memory. If you want the virtual machine to run smoothly, the memory of the development machine should not be less than 8GB. The vast majority of virtual machine software requires that a 64-bit operating system be installed on the host virtual machine's development machine. (Some virtual machine software, such as VMware Workstation, supports running 64-bit virtual machines on a 32-bit host operating system.) The CPU of the development machine must support virtualization technology, EMT64, and execute Disable Bit.
Install SharePoint on your local machine	Developers can install SharePoint 2010 and Visual Studio directly on their local development machine 2010, then use the development machine directly as a development environment. If the developer's local machine's operating system is Windows Server 2008/2008 R2 x64, it is simpler to install SharePoint 2010 directly, which is basically no different from deploying a single-server SharePoint 2010. If the developer's local machine's operating system is Vista SP1 x64 or Windows 7 x64, then installing SharePoint 2010 directly requires a special operation that is not the same as a regular SharePoint 2010 deployment. If developers want to separate the development environment and the work environment (for sending and receiving mail, storing and listening to MP3, and so on), consider using multi-system boot to install the development environment in a separate system. You can even consider using the VHD boot factor when booting multiple systems. The	SharePoint 2010 environment runs faster than using virtual machine technology. The	development environment is difficult to back up and migrate. The operating system on the development machine, whether Windows 2008/2008 R2, or Vista or Windows 7, must be a 64-bit version. The development environment is susceptible to the many software installations that are installed in a daily environment. Maintaining a running SharePoint 2010 background service can also affect the performance of the development machine operating system even when it is not being developed.
Use a dedicated development server	The development team uses virtual machine technology on a dedicated server to create a separate SharePoint 2010 development environment for each developer. Developers can connect and use the development environment through Remote Desktop.	The benefits of having a virtual machine development environment. Because the development environment is not located on the developer's local machine, there is no need for the local machine to have too high performance. The maintenance and management of the development environment can be centralized on the server side.	The development team needs to have available server resources. Because the server needs to provide a separate development environment for each developer, this means that multiple virtual machines may need to be running on the server at the same time, which has a high performance requirement for the server. Because developers need to connect to the development environment on the server using Remote Desktop, the efficiency of the developer can be affected by the speed of the network connection between the local machine and the server.

Table 2-1: List of optional methods for creating a SharePoint 2010 development environment

Tip For more information about the Boot of the VHD, refer to http://edge.technet.com/Media/Windows-7-Boot-from-VHD/.

The way you choose to build your development environment depends largely on the resources that your development team has. If you have a better hardware resource (such as a development machine with 8GB of memory), it is recommended to use Hyper-V or other third-party virtual machine technology to build a SharePoint 2010 development environment in a virtual machine. The benefit of a virtual machine is that it can create a standard, consistent development environment for the development team, and the development environment will not be interfered with by other assorted software. If the developer's local machine is not so "strong" and is accustomed to using Windows Vista x64 SP1 or Windows 7 x64 as its primary operating system, you can choose to install SharePoint 2010 directly into the operating system of your local machine.

Tip No matter how the development team ultimately chooses to build the development environment for the developer, the basic principle is that each developer should have a separate development environment and not be able to share a development environment with multiple developers (or even the entire development team). A shared development environment often leads to lower development efficiencies.

2.1.2 Installing SharePoint 2010 in the Windows 7 x64 operating system

Using virtual machine technology, or installing SharePoint 2010 directly on the Windows Server 2008/2008 R2 x64 operating system, and deploying a single-server SharePoint 2010 System is not a big difference, so it's not a separate story in this book. But because the new features of SharePoint 2010 are installed directly in SharePoint 2010 into the Windows 7 x64 operating system, and many developers are using this operating system on their local machines, we'll show you how in this section how to use Windows 7 Install SharePoint 2010 in the x64 operating system to build a development environment. We believe this is an economical and practical solution for developers.

The good news for developers who are preparing to install SharePoint 2010 on the Windows 7 operating system is that the development environment does not have to be joined to the domain. Regardless of whether your development machine has joined the domain, it doesn't matter.

Before you install, we recommend that you turn off Windows 7 built-in user Account Control (UAC). With Control Panel-system and security – Change user Account Control settings, open the interface shown in 2-1 and slide the slider to the bottom option.

tip Although SharePoint 2010 can also be installed in the Vista SP1 x64 operating system, it is limited in length, so this book only describes how to build a development environment using Windows 7 x64. If you are using Vista SP1 x64, refer to the relevant section in the SharePoint SDK: Http://msdn.microsoft.com/en-us/library/ee554869.aspx.

The SharePoint 2010 development environment We are going to install has the following features:

• We will install SQL Server R2 directly in the Windows 7 system as a SharePoint 2010 database.
• SharePoint 2010 will be installed in farm mode.

2.1.2.1 Installing the required patches and components

First, we need the various patches and components required to install SharePoint 2010 on the Windows 7 operating system. Below is a list of all the required patches and components and their, if there are multiple platform versions (x86, x64, IA64) displayed on the download page, make sure to download and install the x64 version:

• WCF hotfix: http://go.microsoft.com/fwlink/?linkid=166231

• ADO Data Services Update for. NET 3.5 SP1:http://www.microsoft.com/downloads/details.aspx?familyid= 79d7f6f8-d6e9-4b8c-8640-17f89452148e&displaylang=en
• Microsoft Sync Framework 1.0:http://go.microsoft.com/fwlink/?LinkID=141237
• SQL Server Native Client:http://go.microsoft.com/fwlink/?LinkId=123718
• Windows Identity Foundation:http://www.microsoft.com/downloads/details.aspx? Familyid=eb9c345f-e830-40b8-a5fe-ae7a864c4d76&displaylang=en
• Chart Controls:http://go.microsoft.com/fwlink/?LinkID=122517
• ADOMD. Net:http://download.microsoft.com/download/A/D/0/AD021EF1-9CBC-4D11-AB51-6A65019D4706/SQLSERVER2008_ASADOMD10.msi

In the command Prompt window that opens, enter the following command and run it. Note that the following instruction text is an entire line, not multiple instructions, and when you enter the instruction, make sure that there is no line break in the middle of the instruction text. It is recommended that you open Notepad first, then enter the instructions in Notepad first, and then paste it into the command prompt to run.

START/W pkgmgr/iu:iis-webserverrole;iis-webserver;iis-commonhttpfeatures;iis-staticcontent;iis-defaultdocument ; iis-directorybrowsing;iis-httperrors;iis-applicationdevelopment;iis-aspnet;iis-netfxextensibility;i Is-isapiextensions;iis-isapifilter;iis-healthanddiagnostics;iis-httplogging;iis-logginglibraries;i Is-requestmonitor;iis-httptracing;iis-customlogging;iis-managementscriptingtools;iis-security;i Is-basicauthentication;iis-windowsauthentication;iis-digestauthentication;iis-requestfiltering;iis-performance ; iis-httpcompressionstatic;iis-httpcompressiondynamic;iis-webservermanagementtools;iis-managementconsole;i is-iis6managementcompatibility;iis-metabase;iis-wmicompatibility; Was-windowsactivationservice; Was-processmodel; Was-netfxenvironment; Was-configurationapi; Wcf-http-activation; Wcf-nonhttp-activation

Wait a moment, after this line of command is finished. Open Control Panel – Programs – Turn Windows features on or off, and in the window that opens, confirm that Windows features are enabled. If there are missing features, you can manually enable them in this window.

2.1.2.2 Installing SQL Server R2

Next, install SQL Server R2 in the Windows 7 operating system. Installing SQL Server R2 in Windows 7 is nothing special, basically the same as in the Windows Server 2008/2008 R2 operating system. Figure 2-5 to figure 2-9 shows the author in their own development environment to install the SQL Server R2 settings, the picture "Kaneboy-pc\kaneboy" is the author environment in the development of the machine administrator account, where "kaneboy-pc" is the machine name.

After the installation is complete, if everything goes well, in Windows 7 Task Manager, you should see the process for SQL Server related services.

Tip If you choose to install SQL Server 2008 instead of SQL Server R2, after you install SQL Server 2008, you will need to continue to install the following two SQL Server 2008 update packages separately:

• SQL Server SP1
• SQL Server SP1 CU2 (Cumulative update package 2,:http://support.microsoft.com/kb/970315) or a later version of CU

2.1.2.3 Installing SharePoint 2010

In order to install SharePoint 2010 into your system, it is recommended that you copy the installation files for SharePoint 2010 to the Windows 7 disk file system first. If your SharePoint 2010 installation media is a CD or ISO file, simply copy the files contained in the CD or ISO directly into Windows 7. If the installation media is an. exe executable file, you can run the Setup program by adding the "/extract" parameter (for example: "Sharepointserver2010.exe/extract") to the Setup program at the command prompt. You can extract the installer to the specified disk folder.

Open the "Prerequisiteinstallerfiles\filterpack" folder, double-click and run "Filterpack.msi". This is the only additional required component built into the SharePoint 2010 installation file that contains the various IFilter that the SharePoint 2010 search engine will use.

Open the "config. xml" file in the "Files\setupfarm" folder and add a new one to the "<Configuration>" node:

<setting id= "Allowwindowsclientinstall" value= "True"/>

Open a command prompt as an administrator (shown in 2-2), set the current folder to the directory where the SharePoint 2010 installation files are placed, and then execute the "Setup.exe/config files\setupfarm\config.xml" directive. Start the SharePoint 2010 Setup program, as shown in 2-13.

In the Installation Type selection screen shown in 2-14, select the server farm type. In the server Type selection screen shown in 2-15, select the "full" type.

Wait patiently for the SharePoint 2010 installation to complete, do not select the "Run SharePoint Product Configuration Wizard Now" check box when the prompt appears as shown, click the Close button directly

Open a Command Prompt window as an administrator, set the current directory to the Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\bin directory, and then in the Command Prompt window, enter Psconfig.exe–cmd Configdb–create–server < development machine name >-database Sharepoint_config–user < Development machine Administrator account >- Password < development machine Administrator account password >-admincontentdatabase sharepoint_admin_content-passphrase < Specify a password > "directive to encrypt the SharePoint farm traffic and run it to create the configuration database for the SharePoint 2010 system. Figure 2-17 shows the output after running this command. Although the message "local accounts should only be used in standalone mode" is output during execution, this does not prevent the configuration database from being successfully created.

Go Win7 under Install configuration for SharePoint Server 2010