dynamic link library

[himmatpatil]

hi all

I created dll using visual basic and register with regsvr32.exe there is no problem with this . but now i want to change the dll functionality. I unregister the dll with regsvr32 /u it unresiter suceess full but sencond time i make the dll with same name it will give me error file is in use. why it will give me error i unregisted the dll file


can u help me

 

[CasperTFG]

Welcome to DLL hell....

The problem is in your registry. Try a utility called reg-clean, or Super Rabbit registry editor.

1) Unregister the DLL regsvr32 /u
2) Delete the file, make sure it does not exist on the drive anywhere.
3) Run a registry cleaning utility like RegClean
4) Put the file back
5) Register it again with regsvr32

Hope that works. Craig, mailto:sander@cogeco.ca

Remember not to name the Lambs...
It only makes the chops harder to swallow

 

[jmerencilla]

i encountered your problem several times when accessing md DLL in an ASP page. i simply run IISRESET.EXE and continue working.

here's how:

1. on the command prompt, type IISRESET and press ENTER.

inform me if my case works fine with yours.

 

[johnwm]

Doesn't IISRESET just reset an IIS server? Let me know if this helps
________________________________________________________________
If you are worried about how to post, please check out FAQ222-2244 first

'There are 10 kinds of people in the world: those who understand binary, and those who don't.'

 

[cdukes]

The problem is not the regisrty, it is the fact that either your process or another process currently has the DLL loaded and it is being used. If the DLL is being called from ASP then IIS server might be using it and thus restarting IIS will release the file. On the other hand it could be an application that you are running / a group file in VB running your application etc.

Before making the DLL make sure that any application/Asp etc has been closed so that the DLL is not currently being used.

Hope this helps,

Chris Dukes

 

[jmerencilla]

johnwm, yes, IISRESET just reset an IIS server. but I did said that I encountered this problem when I was accessing my dlls in an ASP page, didn't I?