p2p.wrox.com Forums

Need to download code?

View our list of code downloads.


  Return to Index  

asp_components thread: Object Permissions, COM & registering question


Message #1 by "Brad Urani" <bradurani@y...> on Tue, 10 Dec 2002 02:37:02
I figured out the answer to my Access Denied error, all I did to get it to 
work was create a new COM+ application and add my DLL to it using the 
Component Manager utility of Windows 2000. That brings me to my next 
question, If I change the source in VB, the only way I've found to test 
the changes is to unregister the DLL, then delete the COM+ application (If 
I don't do this, I can't get permissions from the file system to overwrite 
the old DLL) then I have to recompile the DLL, register it with the 
system, then create the COM+ app all over again just so I can test a 
change in the code! There has to be an easier way, is it possible to debug 
this stuff in VB without going through all this? if so how? I'm only using 
one computer here so network access stuff is not an issue. Thanks alot.
Message #2 by "Adrian Forbes" <adrian.forbes@n...> on Tue, 10 Dec 2002 09:25:25 -0000
Right-click on the Application in the MMC and select "Shut down".  This will
unload the DLL which allows you to replace it.  If it is VB6 and you look in
your Add-Ins you should find an "MTS" add-in that will refresh the
application with your new DLL as soon as you re-compile it (assuming
everything is on the same machine)

-----Original Message-----
From: Brad Urani [mailto:bradurani@y...]
Sent: Tuesday, December 10, 2002 2:37 AM
To: ASP components
Subject: [asp_components] Object Permissions, COM & registering question


I figured out the answer to my Access Denied error, all I did to get it to
work was create a new COM+ application and add my DLL to it using the
Component Manager utility of Windows 2000. That brings me to my next
question, If I change the source in VB, the only way I've found to test
the changes is to unregister the DLL, then delete the COM+ application (If
I don't do this, I can't get permissions from the file system to overwrite
the old DLL) then I have to recompile the DLL, register it with the
system, then create the COM+ app all over again just so I can test a
change in the code! There has to be an easier way, is it possible to debug
this stuff in VB without going through all this? if so how? I'm only using
one computer here so network access stuff is not an issue. Thanks alot.

%%email.unsub%%


Message #3 by "SEAK, Teng-Fong" <tfseak@f...> on Tue, 10 Dec 2002 19:34:57 +0100
	Unfortunately, this is not Java (nor .Net) in which links are
dynamically created at the moment of execution, so you have to go 
through
all those procedures.

	But I think Visual Studio could unregister and re-register after
compiling for you.  Maybe just a question of config ?  Otherwise, you 
could
make a simple batch file to do repetitive jobs.

HTH

> -----Message d'origine-----
> De : Brad Urani [mailto:bradurani@y...]
> Envoy=C3=A9 : mardi 10 d=C3=A9cembre 2002 03:37
> =C3=80 : ASP components
> Objet : [asp_components] Object Permissions, COM &
> registering question
>
>
> I figured out the answer to my Access Denied error, all I did
> to get it to
> work was create a new COM+ application and add my DLL to it using the 

> Component Manager utility of Windows 2000. That brings me to my next
> question, If I change the source in VB, the only way I've
> found to test
> the changes is to unregister the DLL, then delete the COM+
> application (If
> I don't do this, I can't get permissions from the file system
> to overwrite
> the old DLL) then I have to recompile the DLL, register it with the
> system, then create the COM+ app all over again just so I can test a
> change in the code! There has to be an easier way, is it
> possible to debug
> this stuff in VB without going through all this? if so how?
> I'm only using
> one computer here so network access stuff is not an issue.
> Thanks alot.
>

  Return to Index