| Author |
Topic |
|
jesus4u
Posting Yak Master
204 Posts |
 Posted - 2002-08-16 : 12:47:00
|
After making some changes to my ActiveX dll project and saving the changes, when I go to 'make' the dll I get this error Only when I restart my computer does it release and then I can recompile.What is up! |
|
|
Merkin
Funky Drop Bear Fearing SQL Dude!
4970 Posts |
Posted - 2002-08-16 : 22:45:05
|
It means the DLL is in use.You have to kill any processes that may be using it, rebooting will do that  Damian |
 |
|
|
jesus4u
Posting Yak Master
204 Posts |
Posted - 2002-08-19 : 07:56:47
|
quote:
It means the DLL is in use.You have to kill any processes that may be using it, rebooting will do that Damian
But I am trying to avoid a reboot. IS there any other way?! It is a pain when you are trying to build and test a COM component. |
|
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2002-08-19 : 08:17:48
|
| If you're testing a COM component you have to make sure you close and destroy any instances of it, like "Set obj=Nothing". |
|
|
|
jesus4u
Posting Yak Master
204 Posts |
Posted - 2002-08-19 : 08:24:50
|
| I realize that but sometimes the code errors out and shuts down leaving an instance in memory. |
|
|
|
KHeon
Posting Yak Master
135 Posts |
Posted - 2002-08-19 : 08:35:40
|
Is this something that is being instantiated via IIS? If so you might be able to get by with a shutdown of the IIS services. I did a fair amount of COM development a year or so ago and the only way you can avoid a reboot is to stop the process that has cached your dll, which will be IIS if the above is true.Next to dll hell, this is the best part of COM.  Kyle HeonPixelMEDIA, Inc.Senior Application Programmer, MCPkheon@pixelmedia.com |
|
|
|
KHeon
Posting Yak Master
135 Posts |
Posted - 2002-08-19 : 08:37:10
|
| Oh, one other solution would be to compile the dll, then create and MTS package from it. Ideally this will allow you to stop the package in MTS and recompile (it doesn't always work but it's a lot better then having to shutdown IIS everytime).Good luck!Kyle HeonPixelMEDIA, Inc.Senior Application Programmer, MCPkheon@pixelmedia.com |
|
|
|
jesus4u
Posting Yak Master
204 Posts |
Posted - 2002-08-19 : 08:38:52
|
quote:
Is this something that is being instantiated via IIS? If so you might be able to get by with a shutdown of the IIS services. I did a fair amount of COM development a year or so ago and the only way you can avoid a reboot is to stop the process that has cached your dll, which will be IIS if the above is true.Next to dll hell, this is the best part of COM. Kyle HeonPixelMEDIA, Inc.Senior Application Programmer, MCPkheon@pixelmedia.com
Thanks Kyle it used to work when I shut down IIS but it doesn't help anymore and I haven't changed the way I test it on the asp page. |
|
|
|
Merkin
Funky Drop Bear Fearing SQL Dude!
4970 Posts |
Posted - 2002-08-19 : 08:46:51
|
| Try shutting down the web publishing service, either in the Services applet or by going to a command prompt and typing NET STOP W3CSVC.I would have told you this before, but you didn't feel the need to mention where you were using the DLL.Damian |
|
|
|
jesus4u
Posting Yak Master
204 Posts |
Posted - 2002-08-19 : 08:48:17
|
quote:
Try shutting down the web publishing service, either in the Services applet or by going to a command prompt and typing NET STOP W3CSVC.I would have told you this before, but you didn't feel the need to mention where you were using the DLL.Damian
That is Great! Thanks I will try today and let you know. |
|
|
|
|
Weird Compiling Error