February 26th, 2004, 12:13 PM
|
|
Registered User
|
|
Join Date: Feb 2004
Posts: 1
Time spent in forums: < 1 sec
Reputation Power: 0
|
|
COM+ Deployment Command Pattern
Hello,
I hope this long explanation is palatable enough for someone to help with! I’m a development manager for client focused financial service provider with approximately 2,000 users. Most of the organisation’s service requirements are met by industrial strength / mainframe applications, but service gaps still exist and thus extensive stand-alone VB and VBA solutions exist. Very little of the work-products created by the stand-alones do more than host a 'button and a place to push it', more specifically, the user is not required to provide more that three or four standard arguments (e.g. Date, Client Name and Report Name) for the process to run. I believe I can design a Command Design Pattern (or Abstract Object Factory?) to solve this hosted on a COM+ server and a user deployed .NET windows form (let’s call it a ‘Process Viewer Form with an 'Execute Button'). The process viewers initialise themselves by merely taking a trip to the database (which would names of the classes installed on the COM+ server by name), expose the classes installed on the COM+ Server and upon user request, call the execute method of the class (all other intelligence would live in the object or the database).
Can anyone steer me to a .NET deployment of a strategy like this?
P.S. to shorten the request I have simplified where I thought the details might be self-evident, sorry in advance if I have over-simplified the details (also we need to stay away from http server for this, we’re in a WebSphere holy-war right now) : - (
|
Dev Articles Community Forums Sponsor:
Del.icio.us
Digg
Google
Spurl
Blink
Furl
Simpy
Y! MyWeb
Linear Mode
