[lnkForumImage]
TotalShareware - Download Free Software
Confronta i prezzi di migliaia di prodotti.
Asp Forum
 Home | Login | Register | Search 


 

Forums >

microsoft.public.dotnet.framework.interop

Regasm /u couldn't unregister .Net dll (.tlb

Hanna Yu

2/9/2007 5:52:00 PM

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
5 Answers

Patrick Steele

2/11/2007 1:44:00 PM

0

In article <471C5FAD-8902-4FBC-B5D4-CAAA07F19B69@microsoft.com>, =?Utf-
8?B?SGFubmEgWXU=?= <Hanna Yu@discussions.microsoft.com> says...
> 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.n...

Hanna Yu

2/12/2007 2:45:00 PM

0

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

"Patrick Steele" wrote:

> In article <471C5FAD-8902-4FBC-B5D4-CAAA07F19B69@microsoft.com>, =?Utf-
> 8?B?SGFubmEgWXU=?= <Hanna Yu@discussions.microsoft.com> says...
> > 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.n...
>

Hanna Yu

2/12/2007 4:23:00 PM

0



"Patrick Steele" wrote:

> In article <471C5FAD-8902-4FBC-B5D4-CAAA07F19B69@microsoft.com>, =?Utf-
> 8?B?SGFubmEgWXU=?= <Hanna Yu@discussions.microsoft.com> says...
> > 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.n...
>

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

2/12/2007 10:27:00 PM

0

In article <F32B3839-1F91-487B-86ED-0E5DDB9AE0E6@microsoft.com>,
HannaYu@discussions.microsoft.com says...
> 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/ms4...

--
Patrick Steele
http://weblogs.asp.n...

Hanna Yu

2/13/2007 3:11:00 PM

0

Thanks, I'll try that.

hanna Yu

"Patrick Steele" wrote:

> In article <F32B3839-1F91-487B-86ED-0E5DDB9AE0E6@microsoft.com>,
> HannaYu@discussions.microsoft.com says...
> > 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/ms4...
>
> --
> Patrick Steele
> http://weblogs.asp.n...
>