Please review the following information before installing Microsoft® Windows® Workflow Foundation Beta 2.2.
The information in this document supports a preliminary release of a software product that may be changed substantially prior to final commercial release. This document, including without limitation any samples referenced in this document, is provided for your informational purposes only.
Microsoft makes no warranties, either express or implied, in this document. Information in this document, including URL and other Internet Web site references, is subject to change without notice. The entire risk of the use or the results from the use of this document remains with the user. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
© 2006 Microsoft Corporation. All rights reserved.
Microsoft, MS-DOS, Windows, Windows NT, Windows Server, Windows Vista, Visual C#, and Visual Studio are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
The names of actual companies and products mentioned herein may be the trademarks of their respective owners.
Software requirements
Supported operating systems:
-
Windows® XP, Service Pack 2 (SP2)
-
Windows® XP Professional x64 Edition
-
Windows Server™ 2003 Standard Edition, Service Pack 1 (SP1)
-
Windows Server™ 2003 Enterprise Edition, Service Pack 1 (SP1)
-
Windows Server™ 2003 Web Edition, Service Pack 1 (SP1)
-
Windows Server™ 2003 Standard x64 Edition
-
Windows Server™ 2003 Enterprise x64 Edition
-
Windows Server™ 2003 Datacenter x64 Edition
-
Windows Server™ 2003 R2 Standard Edition
-
Windows Server™ 2003 R2 Enterprise Edition
-
Windows Server™ 2003 R2 Datacenter Edition
-
Windows Server™ 2003 R2 Standard x64 Edition
-
Windows Server™ 2003 R2 Enterprise x64 Edition
-
Windows Server™ 2003 R2 Datacenter x64 Edition
-
Windows Server™ 2003 Enterprise IA64 Edition
-
Windows Server™ 2003 Datacenter IA64 Edition
-
Windows Vista™, February Community Technology Preview (CTP)
Other software requirements:
-
.NET Framework 2.0
Optional:
-
Microsoft® SQL Server 2000 Service Pack 4 (SP4) (required for using the included durable services)
-
Microsoft® SQL Server 2005, All Editions (required for using the included durable services)
Minimum hardware requirements
Processor: 800 Mhz Pentium III
RAM: 256MB
Hard Disk Space: 900mb on system drive, 4.1 GB Installation drive
Video: 800 x 600, 256 colors
Release Notes
Cannot publish activity libraries as Web services
You cannot publish an activity library project as a Web service, even though the context menu item is enabled. You can only publish workflows as web services.
Web hosting on Windows Vista requires update to web.config
A workflow cannot be published as a Web service on Windows Vista without modification. The web.config file must be modified to look like the following:
<system.webServer>
<modules>
<add name="WorkflowHost" type="System.Workflow.Runtime.Hosting.WorkflowWebHostingModule, System.Workflow.Runtime, Version=3.0.00000.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" preCondition="runtimeVersionv2.0" />
</modules>
<directoryBrowse enabled="true" />
</system.webServer> | |
Using the same GUID with CreateWorkflow will return the same workflow instance
All WorkflowInstance objects that were created with the same GUID used in the CreateWorkflow method will reference the same underlying object.
Rules will be associated with a different class if your workflow class is the second class in the code file
If you have a namespace with multiple classes and your workflow class is the second class listed, then during compilation, rules will be associated with the first class in your namespace. To avoid this problem, make sure the workflow class is the first class in your namespace.
ArgumentException is thrown by ManualWorkflowSchedulerService when interacting with DelayActivity and SqlWorkflowPersistenceService
ManualWorkflowSchedulerService throws an ArgumentException when a new DelayActivity activity executes if SqlWorkflowPersistenceService loaded a workflow with the SqlPersistenceWorkflowInstanceDescription.NextTimerExpiration property set.