Updating DLL file on the network

[TL]

So I added a couple of new bmp's to my current DLL file and tried to copy this updated DLL file to the network, replacing the old one. One problem... a message saying ".... Access is denied. The source file may be in use." I found out that all the cad sessions that have this DLL loaded have to be closed in order for me to copy and replace the file. Luckily I only have it loaded on 2 machines so far. What if I have it loaded on more machines.... it would be tough to find out which pc has autocad running and tell it to close autocad so I can update the file. How's everyone handling this problem? Guess I can always wait until everyone has gone home 🙂 or leave them as bmp's.

[Anonymous]

TL wrote:
> So I added a couple of new bmp's to my current DLL file and tried to
> copy this updated DLL file to the network, replacing the old one.
> One problem... a message saying ".... Access is denied. The source
> file may be in use."

> How's everyone handling this problem? Guess I
> can always wait until everyone has gone home 🙂 or leave them as
> bmp's.

I reverted to using bmp files when I ran into this issue... it's just
plain easier.

In my set up, everyone's machine has a path in their support file search
path that points to a folder on the network. That folder conatins the
partial menu file, the associated mnl, and the bmps for the toolbars in
the menu. When I make a change, say add a new button, I:
1. put the bmp in that folder,
2. add the button definition to the mns,
3. close out of autocad
4. delete the mnr and mnc files
5. start autocad

That forces the menu to be recompiled, and new mnc and mnr files are
created. Everyone else will see the update the next time they start
autocad.

[I *think* that all you really need to distribute are an mnc, an mnr,
and the mnl (if there is one). So I think you could develop your mns in
some private directory, and once the mnc and mnr are generated, copy
those files to the shared network location. But I haven't tried this yet.]