• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 210
  • Last Modified:

Moving from COM/NT server to Win2k/COM+ strategy?

Hello - I'm accustomed to writing COM objects in VB, compiling them and then to install them in my IIS app on NT server, I'd run netstop iisadmin, and then regsvr32 and then start the web-services again using netstart..

now, the environment at work is changing to Win2k server, and my team must develop on a shared server - that is, other teams are using the same server for their web applications.  I asked, "well, how then can I stop services everytime I want to publish a new DLL if other apps are running on it?" I was told "you can't, you should use COM+ now, you won't have to stop web-services to re-register your DLL."

Ok.. so - I need the basics, quick reference points to make this transition quickly.. What do I need to know to make COM+ objects rather than COM objects and what is the registration process like?

1 Solution
PMH4514Author Commented:
PAQ'd and points refunded.

Community Support Moderator @Experts Exchange

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now