Readonly DLL?

[Tim Zych]

Is it possible to replace a VB.Net DLL (class library output), referenced by
an XL workbook, while the workbook is still open?

Right now, if Excel is open and referencing the DLL, it can't be replaced
until I close the workbook and also the containing XL app.

In the Setup and Deployment project, which is installing this solution, I
tried various ReadOnly attributes to get it to work, but Excel keeps a lock
on it.

Is there some way to get Excel to reference it as "read only" so that it can
be removed at any time even after XL has used it?

Thanks.

 

[Mr. Arnold]

Is it possible to replace a VB.Net DLL (class library output), referenced
by an XL workbook, while the workbook is still open?

Right now, if Excel is open and referencing the DLL, it can't be replaced
until I close the workbook and also the containing XL app.

In the Setup and Deployment project, which is installing this solution, I
tried various ReadOnly attributes to get it to work, but Excel keeps a
lock on it.

The O/S keeps a lock on it as long as some application/program has the file
in an in use state.

Is there some way to get Excel to reference it as "read only" so that it
can be removed at any time even after XL has used it?

Excel has nothing to do with it, other than, it's the one using the DLL at
the time.

And whatever this *read only* thing you're talking about is, you seem to
have some kind of mis-conception as to just what is happening when a file
any file is locked by the O/S, and it is in use.

Your answer is no, and you cannot replace a file that's in use.