|
Developing Workflows for the 2007 Microsoft Office System and Windows SharePoint Service “v3” Basic steps for workflow development
- Model workflow in VS
- Create and bind InfoPath forms
- Deploy to SharePoint Server
- Debug the running workflow
Examples use the Office “12” SharePoint Servers Beta 1 TR Starter kit – which adds a project type “SharePoint Sequential Workflow…”
Types of InfoPath forms in Workflows
- Association form
- when user adds workflow to a list
- for setting options on WF
- Initiation form
- for manual workflow start
- collects WF params
- Task completion form
- Modification form
To deploy your workflow to a SharePoint server:
- Generate metadatafiles
- Create the CAB (WSP) – box admin installs (via spadmin, IISreset)
- Install/activate the features
- Associate WF to the list/library
Now we get to see CODE! Sweet – my fast is happy now!
Linking InfoPath forms into a workflow – in InfoPath designer you can export source files. One of which is a .xsd file. Then run xsd.exe on that .xsd from within a VS command prompt. That generates a c# file (class) based on the form. Now reference the class from within your workflow project. Very slick
Customizing and Extending Microsoft Office SharePoint Server 2007 Search I see a pattern here. The presenter is busy clicking checkboxes and configuring web parts from within the tool parts. WTF? When did the definition of “Developer” include button clicking? This is frustrating. The description of this presentation has this phrase: “how to make use of the search engine and API from within your code”
So the presenter just said that he was showing us the GUI crap so that we have a frame of reference. Jeezus – I can click around a freakin’ UI myself. I equate this to a college professor reading from a book. I can do that on my own. Show me something that ain’t in the book. Show me cool stuff!!! ooooooo now we’re geeting into code. NOT… we are changing the XSLTs. Cool stuff for Ux dudes… but not for me.
Cool search thing #1 – I think we (at work) will be able to define an XSL for certain content types (think News) so that they show up differently in search results. Not sure how useful it is but it seems like there might be some value here.
Last hope for the day (it has Visual Studio in the title – must be cool, right?): SharePoint Technology Tools, Techniques, References and Resources for Visual Studio Developers Use FrontPage 2007 SharePoint Designer to:
- Write no-code workflows
- Modify CSS files
- Edit .aspx pages
- Add script to pages
- Customize look & feel of web parts
- Write XSLT to customize data rendering
Introducing Code Name “Visual Studio Extensions for SharePoint Services”
- Aims to address pain points around SP development
- Adds SP project type to VS
- Set of VS Project and Item templates
- Build. Deploy, debug support
- EWSS XSDs for XML intellisense
After installing Visual Studio Extensions for SharePoint Services there will be a a “SharePoint” node in the Visual Studio new project dialog where you can create a new:
- web part
- site definition
- list definition
- feature definition
- event handler
- workflow activity
SWEET! It gets better: When you it F5 it creates the CAB, deploys the web part, registers in SafeControls, adds to gallery, attaches to process. Wow. How hard was this in SharePoint 2003? This is a serious PITA! I think I have 4 or 5 docs I reference to get web part debugging working with the current version! Wow… this is awesome.
The bad news… won’t be ready until RTM. So much for helping beta and TAP customers!
Cool tips. Create a batch file like:
stsadm -o deleteweb -url http://localhost/test stsadm -o createweb -url http://localhost/test -lcid 1033 -sitetemplate HELPDESK#1 -title TestWeb start http://localhost/test
This would be good to setup/teardown a web for UnitTests.
|