Gør som tusindvis af andre bogelskere
Tilmeld dig nyhedsbrevet og få gode tilbud og inspiration til din næste læsning.
Ved tilmelding accepterer du vores persondatapolitik.Du kan altid afmelde dig igen.
I started working with the new Microsoft WinFX technology stack early in the beta and CTP (Community Technology Preview) stage. The foundations in WinFX (Windows Presentation, Windows Communication, and Windows Workflow) have now finally made their way into a shipping Microsoft product: .NET 3.0. I actually started to learn and use all three of these foundations at the same time in my day job. Talk about a massive learning curve. While I was impressed with the flexibility and capabilities of Windows Presentation Foundation and Windows Communication Foundation, I was somehow inexplicably drawn to Windows Workflow Foundation (WF). WF isn't just a new way to implement a user interface, or a new way to communicate between applications and services. WF represents a completely new way to develop applications. It is declarative, visual, and infinitely flexible. It promotes a model that cleanly separates what to do from when to do it. This separation allows you to change the workflow model (the when) without affecting the what. Business logic is implemented as a set of discrete, testable components that are assembled into workflows like building blocks. Workflow isn't a new concept. But when Microsoft spends years developing a workflow foun- tion and provides it to us without cost, it is an event worth noting. Other workflow frameworks exist, but WF will soon become the de facto standard workflow framework for Windows applications.
.NET represents a new and improved way of developing software for the Windows platform. Given the chance, youd probably rewrite all of your existing code in the newer managed code environment that .NET provides. But it is difficult or impossible to throw out all existing legacy code and start over when a new technology arrives. Instead, you need to find a way to move forward with new .NET development while reusing existing pieces of tested, working code. You need a way to interoperate with the existing code until you have a chance to finally rewrite all of it in .NET.The only recipe-style book on the subject, .NET 2.0 Interoperability Recipes: A Problem-Solution Approach guides Windows developers who are transitioning from native Windows code to .NET managed code..NET tools will allow you to interoperate with existing code. But finding the appropriate tool for the task at hand can sometimes be a frustrating experience. So this book will guide you past myriad infrequently used interop options to focus on those youll use most often.
Windows Workflow Foundation (WF) is a revolutionary part of the .NET 4 Framework that allows you to orchestrate human and system interactions as a series of workflows that can be easily mapped, analyzed, adjusted, and implemented.
Tilmeld dig nyhedsbrevet og få gode tilbud og inspiration til din næste læsning.
Ved tilmelding accepterer du vores persondatapolitik.