RSS

All Project Updates

Discussions

Issue Tracker

Releases

Reviews

Source Code

Wiki & Documentation

RSS

v0.3 Alpha

Released:	Oct 22 2007
Updated:	Oct 22 2007 by deanward
Dev status:	-not yet defined by owner-
Rated:	No ratings yet for this release (Add your own rating)
Reviewed:	0 reviews
Downloaded:	4687 downloads
Wiki link:	[release:4574]

WFTools-v0.3.0.0.zip

source code, 220K, uploaded Oct 22 2007 - 2446 downloads

InstallationNotes.txt

documentation, 10K, uploaded Oct 22 2007 - 1289 downloads

ReleaseNotes.txt

documentation, 2K, uploaded Oct 22 2007 - 952 downloads

Microsoft Community License (Ms-CL)

The Microsoft Community License (Ms-CL) is a license that is best used for collaborative development projects. This type of license is commonly referred to as a reciprocal source code license and carries specific requirements if licensees choose to combine Ms-CL code with their own code. Nearly all current reciprocal licenses are based on the act of distribution to trigger their terms. The Ms-CL seeks to apply the reciprocal terms in a commercially reasonable fashion and to give developers clear guidance as to when the Ms-CL’s reciprocal provisions come into play.

Developers often have a range of architectural options at their disposal when crafting a particular product or solution. They frequently have the option to design a larger work as a series of separate files or components that communicate with each other at runtime on the end user’s computer, as opposed to one monolithic piece of code that is distributed to the end user as a single file. Although these architectural differences may not be obvious to the end user, they may have significant licensing implications for a developer, particularly if the developer uses Ms-CL code in creating a larger work. The Ms-CL (like the Mozilla Public License) works on a “file-by-file” basis. This means that if a developer uses Ms-CL code in a particular file then the entire file that contains the Ms-CL source code (including any other code in that file, no matter who wrote it), must be redistributed in source code form under the terms of the Ms-CL. On the other hand, for any files in larger works that do not contain Ms-CL code, the developer is free to license those files under the terms of their choice. This is true regardless of how these “non-Ms-CL” files interact with or communicate with the Ms-CL files at runtime. In other words, if the developer releases code under the Ms-CL and someone includes it in a file in their project (and then distributes their project to others), they must distribute under the Ms-CL anything that is in the specific file that contains the original developer’s work. While this file-by-file threshold might at first seem arbitrary, it has the benefit of being an easy to interpret, bright-line rule.

Thus, the intent of the reciprocal license is to use licensing as a mechanism to keep certain community-based code “in the community,” while allowing companies to commercialize and license (under terms of their choice) their “value add” code that interacts with the community-based code.

The copyright and patent grants in this license are both royalty free, meaning that licensees do not have to pay anything to the licensor to make use of the source code. The Licensee is required to keep any notices in the code for copyright, patent, trademarks, or other forms of attribution.

Microsoft has created a limited version, the Microsoft Limited Community License (Ms-LCL), of this license to be used for restricting usage to the Windows platform only. The platform restriction is a measure that may be chosen for a particular source code release in order to enable positive interaction with Windows-based developers.

Microsoft cannot provide legal advice on the use or implications of this license. We recommend that developers obtain appropriate legal advice before deciding how to license their source code.

New Features

Generic Tracking Service
- ADO implementation with support for MS SQL Server, Oracle (MS/ODP.NET) and MySql
Generic Persistence Service
- Support for MySql - requires at least MySql/Connector.NET 5.1.3 and MySql 5.1
ADO Batching Service
- Allows connection sharing amongst services with identical connection strings and forcing the use of local transactions in resource managers that do not support promotable single phase enlistment (PSPE) such as Oracle, MySql and SQL Server 2000.

Breaking Changes

Generic Persistence Service
- refactored - different class / interface names - configuration files may need changing
- Oracle implementation - WORKFLOWPKG is now called WORKFLOWPERSISTENCE_PKG

Known Limitations

This release does not support querying the tracking database. This will be provided
as a point release in the near future.

The tracking service provides no support for partitioning and is unlikely to be
implemented (shouldn't partitioning be performed by the DBA at a database level,
not by a developer in software - opinions welcome!).

Releases

Released | Planned

	v0.3 Alpha Oct 22 2007
	0.2.2 Alpha Jul 15 2007
	0.2.1 - Alpha Jun 7 2007
	0.2 Alpha May 30 2007
	0.1 Alpha Apr 22 2007

v0.3.1 Alpha

Planning

Reviews for this release

No reviews yet for this release.

Workflow Foundation Tools

Recommended Download

Other Available Downloads

Release Notes

New Features

Breaking Changes

Known Limitations

Releases

Rate this release

Delete v0.3 Alpha