
Naive questions with creating a com+ component?
OK, these may be a very naive questions, but I am extremely new to
creating com+ (i.e., I have never done it). I have been hearing about com+
for a while now, and am currently creating a web site incorporating dll's
created from VB. This will be running on a Windows 2000 web server. Someone
suggested that my application would be a good candidate for com+. The
classes in VB do a number of things such as create a connection, via oledb,
to a sql server database, pull out user information, populate sections of a
web page, etc, all calling stored procedures. The connections are made,
information retrieved, and connection closed. Very data driven web site. The
dll's I have created are currently registered on my server as "IIS
In-Process Applications". Everything runs fine, I reference them in the asp
page as "server.createobject...". So, my questions are:
1. Does this sound like a good com+ scenario?
2. Did I "accidentally" turn these into com+ components?
3. How do I use the comsvcs.dll(com+ services type library) for code such as
"server.mappath", etc, or can I? I am programming on Winnt4.0 workstation. I
naively tried to copy the dll from the win2000 server onto my winnt
workstation and register it, and it wouldn't register.
4. I keep reading conflicting reports on the Class_Initialize functions. 1
says that this causes instability, and the other says that this is fixed
with sp1. So should I use Class_Initialize?
5. Another colleague told me that all I had to do was add a couple of lines
of code to declarations section of my VB class, and it would register as a
com+ component, is this true and what are those couple of lines of code?
I bought a book last night and starting reading from page 1, but I
thought I would try and get some other peoples judgment on this as well.
Thanks for helping to clarify my convoluted thoughts,
Jeff