|
|
Browse by Tags
All Tags » Financial and B... » MVP (RSS)
-
This is it, the big 150! The first New and Notable was on May 19, 2003 , (my first post was March 29, 2002 ) and I paid homage to the master, "I have always admired Mike's ability to look at the world out there and put it all into one great post, The Daily Grind . While I can't pretend to have Mike's writing ability, I would like to start moving to something similar instead of multiple seperate posts." I wish I had the discipline of Mike because if I posted daily I would be well towards 1000 instead of 150-) but hey I'm pretty proud of my record. I love this community and in the last 25 years this community (and Microsoft) have been real good to me and my family. I hope that what I have been picking here has been of good use to the community to keep you informed on key .NET activities as well as the architectural and design side. Thus, I go forth and pick: Entity Framework, ADO.NET 3, Orcas, MVP Summit One of the best writers in the community today is certainly Jeremy Miller . His latest post, MVP Summit Recapped: Linq for Entities, MonoRail, and Shameless Name Dropping , is a fine example of why. In one post, he is able to write quite elequently on complex subjects like the subtle design flaws in Entity Framework 3 and why WF 4 will rock your world. He is able to take a technology, stick to his design principles and stand his ground, educating and helping all involved achieve something better than was there before. He certainly wasn't the only one of us doing that but his post really captures the core design principles of no infrastructure code in business logic classes. Infrastructure is Infrastructure, business logic is business logic. We want the same thing: No marker interfaces, no codegen, no partial classes. Just plain "PO" and support for the Unit of Work pattern. David Laribee also talks on this area and makes clear that its a vision thing that doesn't really compare to NHibernate which is just OR/M; it's a full Read More...
|
-
I have been working with the Office Live Services Beta for some months now. They just went live with my site over the weekend (although I still have to work on the domain name transfer) and it looks pretty good! I have a new Header and Home Page design. I have added my How-To STS/Window Authentication with ADAM/AD, Roles in AzMan with WCF to the refurbished WCF page . I added a new Domain Driven Design page under Software Engineering . My Presentations, as always are here . Hey, what else am I going to do while I am waiting for my flight? I would like and appreciate any and all feedback as comments here. What's good? What's bad? Knowing my blog and its subjects, what would you like to see? Technorati Tags: .NET , Windows Communication Foundation , WCF , Software Architecture , INETA , MVP , .NET Framework 3 , Microsoft Share this post: Email it! | bookmark it! | digg it! | reddit! | kick it! Read More...
|
-
In the last two posts 101 and 102 , I went pretty deep in some areas. I want to step back and do some more tutorial stuff. So the first question out of the gate is what is Workflow itself and where might you use it? In a nutshell, a Workflow describes and automates a Business Process. It can be described as a "reactive" program which tends to contain some traits: Workflow declared as a set of Activities Coordinates people and software Has real-world control flow Runs reliably and durably Tolerates dynamic change A Workflow is typically designed by a Process Designer using Business Process Analysis, Modeling, and Definition tools. That Process Definition is fed into a Workflow Management System. The WMS will have Users, Applications and Administrators/Supervisors. The WMS will present that Process Definition visually in some form and launch applications. From looking at workflows, we see that some challenges are present. Unlike non-reactive programs, workflows tend to be long-running and stateful. It may take 20 days for an order to be shipped for instance. There usually needs to be some controls to allow a person to override or skip a step in the workflow. Finally, we must be able to see into the workflow and see what state its in and visualizing control flow. Workflow is used in many scenarios like: Business Process Management (BPM) Document Lifecycle Management (Sharepoint, K2) BizTalk Orchestration Sales Management Line of Business Apps Many others... Enter Windows Workflow (WF). Unlike K2 and Sharepoint, WF is not a Workflow Management system or product. It is instead, a general purpose framework for building workflow into your own applications. It ships as part of the .NET Framework 3.0, and ships with both Vista and Longhorn Server. It is installable on Windows XP SP2 and Win2K3. Since WF is baked into Vista and later systems, and is a general framework, it is a single workflow execution engine for all Windows platforms. Indeed, products like K2, Sharepoint, Read More...
|
-
As fellow CodeBetter Blogger Richard notes, in his very gracious post , I will be giving two talks on WCF for INETA this coming Monday in Oklahoma City. The deck is being refined once again with my latest Indigo learnings especially as we deploy in Financial Banks. I also hope to have new demos, perhaps integrating with WF! Technorati Tags: .NET , Windows Communication Foundation , Apache Axis , Financial and Banking , WCF , WF , Windows Workflow , , Software Architecture , Microsoft Share this post: Email it! | bookmark it! | digg it! | reddit! | kick it! Read More...
|
-
I don't really know what to call this post. I'm not as good as Palermo in doing 101 posts and I like to talk about the context so anyhow. Plus I'm not just a pretty link-blogger so away we go :). Way back in October, I talked about Re-Hosting the Windows Workflow Designer in our application . So the version that went out of our baseline Concentration product went without any workflow. I have been playing the Agile Architect the last few months scouting out the WF territory to see if we could accomplish our workflow architectural needs with WF. The short answer is Yes. If I had to summarize my months with WF is that WF is very powerful and capable. But a lot of that power comes from the fact that WF is such a general framework capable of being used in many different scenarios on Windows platform. There is no doubt that Microsoft providing such a powerful and flexible framework for developing workflows is so much better than having to develop our own framework, visual workflow designer, and runtime environment. But, as they say, with great power comes great responsibility. Because it is so general, you may have to do a lot of work to develop your domain-specific model and you will have to learn a lot about WF. You will still have to know about Workflow Architectures and deadlocks and all sorts of stuff. There are some in Redmond that seem to promote the view that you can just "drop" WF into your app and presto. One of the feedback items that us Architect MVPs gave the WF team last summit was this was dangerous. People have to be given guidance here. We have to leverage the decades of work that people like Eric Newcomer have already put into this field. People are using to transition UI pages for God's sake. In my original view of things, I thought I would re-host the WF Designer in our CAB Smart Client application giving Collateral Analysts a whole new power to design workflows. I thought, "wow, I can have analysts just drop Margin Calc and Collateral Demand activities Read More...
|
|
|
|