3. METODOLOGÍA
3.5 Fabricación del recubrimiento Carbon Black
The first thing we need to do is get our environment established. Anyone familiar with Share- Point 2003 development won’t find this very different. There are just a few new things to take care of. For the rest of you, this is all new so I’ll cover things in enough detail to get you going without padding out the book with mindless step-by-step directions to install everything. I’ve taught classes to fifth graders on how to install their operating systems. They need step-by-step directions. I’ll assume most of you are not fifth graders (no offense to fifth graders…).
■Note
This chapter is going to cover setting up a development environment—D-E-V-E-L-O-P-M-E-N-T— not a production environment. There are many, MANY, additional steps you will need to take to set up a production environment. Some of the shortcuts and configuration options I recommend here would make a network admin shudder and a security analyst crawl up in a fetal position and whimper. Please, please, please do not rely on this chapter for your production setup. Every production setup is different so you need to work out the details on your own. At most, look at these instructions as a starting point.First let’s take a look at the pieces we need. Table 2-1 covers the software requirements for our little excursion into Workflow.
Table 2-1. Software Prerequisites for Developing Workflows in Office 2007
Component Version Notes
Windows SharePoint Services 2007 Core component, which will be installed
for you if you install MOSS. If you’re installing MOSS, you don’t need to install this.
Microsoft Office SharePoint Server (MOSS)
2007 SharePoint Server, including Forms
Services. If you’re installing this, you don’t need to install WSS separately.
Windows Server 2003, with Service
Pack 1 or better
.NET Framework 2.0 Provides the primary .NET runtime
and development components. You will be prompted to install this by the 3.0 Framework if it is not already installed.
.NET Framework 3.0 Provides core WF components.
Visual Studio 2005 Development environment.
Workflow Extensions for Visual Studio 2005
Workflow extensions for Visual Studio. Contains the Workflow Designer elements and supporting libraries (like IntelliSense).
Office client applications 2007 For the examples in the book, you’ll
need the SharePoint Designer, Word, Excel, and InfoPath.
Office System XML Code Snippets
2007 Not technically required, but we’ll be
making use of one of the snippets in Chapter 7.
WSS and MOSS SDKs Reference material. Part of the MOSS
SDK is some material that used to be called the Enterprise Content Manage- ment Starter Kit. It contains excellent samples, white papers, and information on development in SharePoint 2007, including Workflow. Again, not technically required but we’ll use them heavily and the value they provide is huge.
■Note
A list of current prerequisites, including links to download them (where available), is available atwww.kcdholdings.com.
One thing that you’ll notice as being conspicuously missing from this list is a database. While you could install a full version of SQL Server (SharePoint requires SQL 2005 or SQL 2000 SP3a or better), we’re going to let the SharePoint installer install SQL Server 2005 Express Edition for us. This isn’t a production environment, and our usage will be limited to a single user (you) and low volume. Naturally, I would never recommend SQL Express for a production environment but for our purposes it will work out nicely.
■Caution
When you install Visual Studio you will be given the option of installing SQL Express. Don’t. Let SharePoint install the database.The software requirements in Table 2-1 are a little daunting. Am I telling you that you need to install all of this on your development machine just to get started? Well, the answer is really “It depends.” If all you want to work with are the out-of-the-box features and you don’t want to do any custom coding, you won’t need Visual Studio or the Workflow Extensions. If you’re not going to be using Forms Services and some of the other MOSS features, you won’t need that component. Otherwise, you pretty much need everything.
I can hear your reaction already:
YOU: Dave, that’s an awful lot to install on my machine just to play around with a new technology. I have real work I have to do. I can’t risk my machine being taken out of commission.
ME: Yep, it’s a problem, all right.
YOU: So what’s a poor workflow developer to do?
ME: Virtualize…
Seriously, I strongly recommend that you look into one of the virtual machine products available on the market for your development efforts—both for Workflow in Office 2007 and just general development. See the sidebar “Virtual Reality” for more information. Little if anything in this book will presume that you are working in a virtual environment as opposed to a “real” one; nonetheless, I strongly recommend it as the benefits are tremendous and the downside is pretty minimal.
Looking back at Table 2-1 you’ll see that I am freely mixing client and server elements. As this is a development environment, we are going to be installing everything on a single machine. It just makes things easier. Again, this would not be the case for a production environment, or even your test/QA environment. But for development, it works just fine.