Discussion:
Regasm /u couldn't unregister .Net dll (.tlb)
(too old to reply)
Hanna Yu
2007-02-09 17:52:01 UTC
Permalink
I created a .Net component, and used "regasm" to get the compoennt
registered. I used an ASP page to call this component, and it worked ok.
Later I needed to make change to this component, so I unregistered the dll
by using "regasm /u" without getting any error. But it seemed like the
ungister function didn't work right away, because I coulldn't recompile the
dll project and I can still call this component from the ASP page after I
used the unregister function. Some times it took 20 minutes, but now it took
hours to get the component unregistered completely.

Please any help! Thank!

Hanna
Patrick Steele
2007-02-11 13:44:16 UTC
Permalink
Post by Hanna Yu
I created a .Net component, and used "regasm" to get the compoennt
registered. I used an ASP page to call this component, and it worked ok.
Later I needed to make change to this component, so I unregistered the dll
by using "regasm /u" without getting any error. But it seemed like the
ungister function didn't work right away, because I coulldn't recompile the
dll project and I can still call this component from the ASP page after I
used the unregister function. Some times it took 20 minutes, but now it took
hours to get the component unregistered completely.
The ASP process still had a hold of the DLL file. when you need to
replace a COM DLL used by an ASP page, you had to start/stop ASP to
release the hold on the DLL (stop asp, copy DLL over, re-start ASP).

One of the great things with ASP.NET is it's shadow-copy of assembly
DLL's means this practice of stopping/re-starting is a thing of the
past.
--
Patrick Steele
http://weblogs.asp.net/psteele
Hanna Yu
2007-02-12 14:45:01 UTC
Permalink
Thank you for your reply. I tried stop and restart IIS, but no luck. We are
using virtual machine. I don't know if any thing to do with the virtual
machine.

Hanna Yu
Post by Patrick Steele
Post by Hanna Yu
I created a .Net component, and used "regasm" to get the compoennt
registered. I used an ASP page to call this component, and it worked ok.
Later I needed to make change to this component, so I unregistered the dll
by using "regasm /u" without getting any error. But it seemed like the
ungister function didn't work right away, because I coulldn't recompile the
dll project and I can still call this component from the ASP page after I
used the unregister function. Some times it took 20 minutes, but now it took
hours to get the component unregistered completely.
The ASP process still had a hold of the DLL file. when you need to
replace a COM DLL used by an ASP page, you had to start/stop ASP to
release the hold on the DLL (stop asp, copy DLL over, re-start ASP).
One of the great things with ASP.NET is it's shadow-copy of assembly
DLL's means this practice of stopping/re-starting is a thing of the
past.
--
Patrick Steele
http://weblogs.asp.net/psteele
Hanna Yu
2007-02-12 16:23:00 UTC
Permalink
Post by Patrick Steele
Post by Hanna Yu
I created a .Net component, and used "regasm" to get the compoennt
registered. I used an ASP page to call this component, and it worked ok.
Later I needed to make change to this component, so I unregistered the dll
by using "regasm /u" without getting any error. But it seemed like the
ungister function didn't work right away, because I coulldn't recompile the
dll project and I can still call this component from the ASP page after I
used the unregister function. Some times it took 20 minutes, but now it took
hours to get the component unregistered completely.
The ASP process still had a hold of the DLL file. when you need to
replace a COM DLL used by an ASP page, you had to start/stop ASP to
release the hold on the DLL (stop asp, copy DLL over, re-start ASP).
One of the great things with ASP.NET is it's shadow-copy of assembly
DLL's means this practice of stopping/re-starting is a thing of the
past.
--
Patrick Steele
http://weblogs.asp.net/psteele
Please ignore my previous message. Last time I didn't restart the IIS, I
just restarted my web site which is one of the websites on the same web
server. Just now, I tried restart the IIS, and it works. Thank you for your
reply. By the way, what is the shadow-copy of assembly DLL, how to use that.
I'm kind new to .NET

Thanks again,

Hanna Yu
Patrick Steele
2007-02-12 22:27:23 UTC
Permalink
Post by Hanna Yu
Please ignore my previous message. Last time I didn't restart the IIS, I
just restarted my web site which is one of the websites on the same web
server. Just now, I tried restart the IIS, and it works. Thank you for your
reply. By the way, what is the shadow-copy of assembly DLL, how to use that.
I'm kind new to .NET
http://msdn2.microsoft.com/en-us/library/ms404279.aspx
--
Patrick Steele
http://weblogs.asp.net/psteele
Hanna Yu
2007-02-13 15:11:01 UTC
Permalink
Thanks, I'll try that.

hanna Yu
Post by Patrick Steele
Post by Hanna Yu
Please ignore my previous message. Last time I didn't restart the IIS, I
just restarted my web site which is one of the websites on the same web
server. Just now, I tried restart the IIS, and it works. Thank you for your
reply. By the way, what is the shadow-copy of assembly DLL, how to use that.
I'm kind new to .NET
http://msdn2.microsoft.com/en-us/library/ms404279.aspx
--
Patrick Steele
http://weblogs.asp.net/psteele
Loading...