«

I have a "homegrown" dll that I am using in IIS (VBScript). I need to
replace it on a production server, but I don't want to stop/restart server
in order to replace the dll.

Possible?


TIA,

Larry Woods

Larry Woods wrote:

> I have a "homegrown" dll that I am using in IIS (VBScript). I need to
> replace it on a production server, but I don't want to stop/restart server
> in order to replace the dll.
>
> Possible?
>
>
> TIA,
>
> Larry Woods
>
>
No.

> but I don't want to stop/restart server in order to replace the dll.
>
> Possible?

Nope, the DLL will remain in memory as long as the IIS services remain
running.

--
http://www.aspfaq.com/
(Reverse address to reply.)

Larry Woods wrote:
> I have a "homegrown" dll that I am using in IIS (VBScript). I need to
> replace it on a production server, but I don't want to stop/restart
> server in order to replace the dll.
>
> Possible?
>
>
> TIA,
>
> Larry Woods
Usually no, it is not possible.

If you configure your application to run in isolated mode (High security),
you will sometimes be able to unload the application in order to unregister,
replace and register a dll. But this does not always work.

Bob Barrows
--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.

Right. I have found that "unloading" the application does allow me to
replace the dll, but when I click the "unload"
button I get the "all applications in the application pool will be stopped"
(paraphrased). What is the definition of the "application pool". IOW, will
this stop OTHER applications running on the server?

TIA,

Larry Woods

"Bob Barrows [MVP]" <> wrote in message
news:%...
> Larry Woods wrote:
> > I have a "homegrown" dll that I am using in IIS (VBScript). I need to
> > replace it on a production server, but I don't want to stop/restart
> > server in order to replace the dll.
> >
> > Possible?
> >
> >
> > TIA,
> >
> > Larry Woods
> Usually no, it is not possible.
>
> If you configure your application to run in isolated mode (High security),
> you will sometimes be able to unload the application in order to
unregister,
> replace and register a dll. But this does not always work.
>
> Bob Barrows
> --
> Microsoft MVP -- ASP/ASP.NET
> Please reply to the newsgroup. The email account listed in my From
> header is my spam trap, so I don't check it very often. You will get a
> quicker response by posting to the newsgroup.
>
>

I'm not sure: I've never seen that message. You may want to ask on the iis
group if nobody here answers.

Bob Barrows
Larry Woods wrote:
> Right. I have found that "unloading" the application does allow me to
> replace the dll, but when I click the "unload"
> button I get the "all applications in the application pool will be
> stopped" (paraphrased). What is the definition of the "application
> pool". IOW, will this stop OTHER applications running on the server?
>
> TIA,
>
> Larry Woods
>
> "Bob Barrows [MVP]" <> wrote in message
> news:%...
>> Larry Woods wrote:
>>> I have a "homegrown" dll that I am using in IIS (VBScript). I need
>>> to replace it on a production server, but I don't want to
>>> stop/restart server in order to replace the dll.
>>>
>>> Possible?
>>>
>>>
>>> TIA,
>>>
>>> Larry Woods
>> Usually no, it is not possible.
>>
>> If you configure your application to run in isolated mode (High
>> security), you will sometimes be able to unload the application in
>> order to unregister, replace and register a dll. But this does not
>> always work.
>>
>> Bob Barrows
>> --
>> Microsoft MVP -- ASP/ASP.NET
>> Please reply to the newsgroup. The email account listed in my From
>> header is my spam trap, so I don't check it very often. You will get
>> a quicker response by posting to the newsgroup.

--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.

> "all applications in the application pool will be stopped" (paraphrased).

You might have better luck if, instead of paraphrasing, you actually tell us
the actual message you actually received. Then, we could search for the
error message and do a bit of research. With a paraphrase, we have no idea
what to look for.

--
http://www.aspfaq.com/
(Reverse address to reply.)

Larry Woods wrote:
> Right. I have found that "unloading" the application does allow me to
> replace the dll, but when I click the "unload"
> button I get the "all applications in the application pool will be
> stopped" (paraphrased). What is the definition of the "application
> pool". IOW, will this stop OTHER applications running on the server?

So you're using Server 2003, right? In that case, you ought to be able to
cycle the application pool. With any luck, this application has been set up
with its own application pool, so cycling it does not require interruption
of the rest of your web apps.

-- Windows Server 2003 only --
• Open IIS Manager
• Navigate to your web application
• View its properties to determine the application pool it is running under
• Expand Application Pools
• Right-click on appropriate one and select [Recycle]



--
Dave Anderson

Unsolicited commercial email will be read at a cost of $500 per message. Use
of this email address implies consent to these terms. Please do not contact
me directly or ask me to contact you directly for assistance. If your
question is worth asking, it's worth posting.

I wrote:
> Larry Woods wrote:
>> Right. I have found that "unloading" the application does allow me
>> to replace the dll, but when I click the "unload"
>> button I get the "all applications in the application pool will be
>> stopped" (paraphrased). What is the definition of the "application
>> pool". IOW, will this stop OTHER applications running on the server?
>
> So you're using Server 2003, right? In that case, you ought to be
> able to cycle the application pool...

Ugh. I hate when people don't answer the question at hand. The answer is a
big "it depends". The good news is that you can usually make it a "no" even
as you isolate it for future use. If the app is in a shared application pool
(which it will be by default), you can simply create an application pool and
reassign that pool to the application you want to cycle.

So...in principle, you should be able to change that DLL without
interrupting the other apps. In principle, anyway.



--
Dave Anderson

Unsolicited commercial email will be read at a cost of $500 per message. Use
of this email address implies consent to these terms. Please do not contact
me directly or ask me to contact you directly for assistance. If your
question is worth asking, it's worth posting.

And you go about creating an application pool, how?

(IIS 5.0, BTW)

Larry

"Dave Anderson" <> wrote in message
news:...
> I wrote:
> > Larry Woods wrote:
> >> Right. I have found that "unloading" the application does allow me
> >> to replace the dll, but when I click the "unload"
> >> button I get the "all applications in the application pool will be
> >> stopped" (paraphrased). What is the definition of the "application
> >> pool". IOW, will this stop OTHER applications running on the server?
> >
> > So you're using Server 2003, right? In that case, you ought to be
> > able to cycle the application pool...
>
> Ugh. I hate when people don't answer the question at hand. The answer is a
> big "it depends". The good news is that you can usually make it a "no"
even
> as you isolate it for future use. If the app is in a shared application
pool
> (which it will be by default), you can simply create an application pool
and
> reassign that pool to the application you want to cycle.
>
> So...in principle, you should be able to change that DLL without
> interrupting the other apps. In principle, anyway.
>
>
>
> --
> Dave Anderson
>
> Unsolicited commercial email will be read at a cost of $500 per message.
Use
> of this email address implies consent to these terms. Please do not
contact
> me directly or ask me to contact you directly for assistance. If your
> question is worth asking, it's worth posting.
>
>