InnerWorkings Blogs

Pleasanton, CA - December 15, 2006 - A Vista-compatible version of the InnerWorkings Developer Interface will be released on December 19, 2006. Developer Interface 3.5 enables developers running the new Vista operating system to use InnerWorkings’ practice-based learning environment.

Developers in your organization who have already changed their operating system to Vista, or are planning to migrate in the near future, will need to upgrade to Developer Interface 3.5 to continue accessing our client application. From December 19, developers can download and install the new version from this location: http://resource.innerworkings.com/developer_interface.

Note: The release of Developer Interface 3.6 in Q1 2007 will include further enhancements to support Vista and all developers will be prompted to automatically update their InnerWorkings client software at that time.

Developers using Vista’s User Access Control (UAC) security feature will notice some differences in the way they interact with the Vista-ready version of the Developer Interface:

• To install or uninstall the Developer Interface, UAC users will be prompted to elevate their user rights to administrator level
• To install or uninstall Drills and Developer Programs, UAC users will need administrative rights
• For UAC users, the Developer Interface will never attempt to close a Visual Studio instance

Developers who are not using the UAC feature will have the same user experience with Vista as they have in Windows XP or Windows 2000 today.

Because Visual Studio 2002 and 2003 are not supported in Vista, Drills based on these versions will not display to users running Vista. InnerWorkings’ entire catalog of Visual Studio 2005 Drills will display as usual to Vista users.

We hope that you’ll find these updates useful and continue to give us your valued feedback on the future direction of our products. If you have questions on this update, please contact us at customer.support@innerworkings.com.

Add this post to:             

As the drumbeat for Windows Vista and the .NET Framework 3.0 grows louder, Independent Software Vendors (ISVs) like InnerWorkings are getting to grips with these important new releases from Microsoft. Like every company focused on the needs of .NET developers, InnerWorkings has jumped headlong into the .NET Framework 3.0 in all it’s various Release Candidate and Beta variations - I still get cold sweats just thinking about those version changes now. This month we’re announcing the availability of three new Drills on Windows Workflow Foundation, which have just been published to our online catalog:

• Programming Sequential Workflows examines basic techniques
  for developing and running sequential workflows, which include building
  and consuming custom activities, using compensation handlers, using the
  ReplicatorActivity, dynamic updating, and policy.
• Programming State Machine Workflows explores basic techniques for developing and running state machine
  workflows, such as building and consuming Local Services for
  communication between the workflow and host, using workflow queue data to
  determine the available actions for a particular state, and using role-based
  authorization.
• Developing Custom Activities covers the development of
  custom workflow activities like creating a simple custom activity,
  and attaching to it a custom designer and toolbox item class. Other topics
  include enhancing custom activities with validation and compensation logic, and
  grouping child activities into a composite sequential activity.

I’ve always wondered how developers keep the tangle of business rules and endless branches of a typical business process straight in their heads. Trying to translate a “basic” workflow into an application that manages annual vacation schedules (for example) might seem simple enough at first glance, but then you start to realize that it must include definitions of all the key roles in that business process, determine approval criteria, synchronize group schedules, and talk to the HR system that allocates annual leave. Phew! Try finishing that workflow before your morning coffee break…

Then along comes the Windows Workflow Foundation (WF) as part of the .NET Framework 3.0 to make this whole process more manageable for developers working in Visual Studio 2005. It’s billed as a means of creating workflow-enabled applications across a variety of complex human and software interactions. MSDN bravely attempts to define WF as a way to create “workflow within line of business applications, user
interface page-flow, document-centric workflow, human workflow, composite
SOA workflow, business rule-driven workflow, and
workflow for systems management”. Thanks for that snappy definition, folks! Not to be too opportunistic here, but isn’t it good to know that companies like InnerWorkings are around to help you navigate this tangled web of creating workflow-enabled applications?

If you’re keen to get started with WF right away, please note that you need to have the Microsoft .NET Framework 3.0 and the Visual Studio 2005 Extensions for .NET
Framework 3.0 (Windows Workflow Foundation) installed on your computer. In fact, maybe you should grab a coffee first…

Add this post to: