This time it’s the Web Service Facade for Legacy Applications. Unlike many of the other patterns and practices, this is very lightweight – a scant 20 pages after you take out the coverage of the included sample application. However, a bigger issue that the lack of content is the definition of “legacy application”. This guide discusses three possible legacy apps – those that expose a COM interface, those that expose a DLL and those in a standalone EXE. However, when my customers talk about legacy apps, they’re usually referring to apps running on the mainframe. A more relevant guide in this vein would talk about using Host Integration Server to provide Web Service Facades for mainframe transaction programs.
Categories
Tags
ASP.NET (31)
Blogging (128)
C# (18)
Community (81)
dasBlog (12)
Database (13)
Debugger (23)
DLR (25)
Domain Specific Languages (15)
Dynamic Languages (12)
Entertainment (14)
ETech (15)
F# (51)
Family (33)
Functional Programming (18)
Games (18)
Hockey (34)
IronRuby (16)
Lanugages (43)
LINQ (24)
Microsoft (31)
Modelling (61)
Movies (23)
Music (20)
Parsing Expression Grammar (16)
PowerShell (41)
REST (18)
Ruby (23)
Service Broker (14)
Silverlight (20)
SOA (94)
Visual Studio (21)
Washington Capitals (43)
WCF (31)
Web 2.0 (67)
Web Services (12)
WF (21)
Windows Live (29)
Working at MSFT (23)
Xbox 360 (54)
XNA (15)
Series
Disclaimer
The information in this weblog is provided "AS IS" with no warranties,
and confers no rights. This weblog does not represent the thoughts,
intentions, plans or strategies of my employer. It is solely my opinion.
Inappropriate comments will be deleted at the authors discretion.