fatal error LNK1168: cannot open x.dll for writing
-
I'm writting a COM plug-in for a service. I'm able to register and unregister the dll with the service. Even after i unregister the dll I still get that error because the file is still in use. When I check with the service it reports that its not using my dll. I thought that the COM library knew when nothing was using a component and would release it. I'm adding features and debugging my dll so I have to compile it often. I don't want to reboot my computer each time I want to comple the component. Is there a way to manually release this dll?
-
I'm writting a COM plug-in for a service. I'm able to register and unregister the dll with the service. Even after i unregister the dll I still get that error because the file is still in use. When I check with the service it reports that its not using my dll. I thought that the COM library knew when nothing was using a component and would release it. I'm adding features and debugging my dll so I have to compile it often. I don't want to reboot my computer each time I want to comple the component. Is there a way to manually release this dll?
Is it a COM+ app ? It could be getting pooled and need stopping in COM+ Christian The tragedy of cyberspace - that so much can travel so far, and yet mean so little. "I'm somewhat suspicious of STL though. My (test,experimental) program worked first time. Whats that all about??!?! - Jon Hulatt, 22/3/2002
-
I'm writting a COM plug-in for a service. I'm able to register and unregister the dll with the service. Even after i unregister the dll I still get that error because the file is still in use. When I check with the service it reports that its not using my dll. I thought that the COM library knew when nothing was using a component and would release it. I'm adding features and debugging my dll so I have to compile it often. I don't want to reboot my computer each time I want to comple the component. Is there a way to manually release this dll?
Did you find a solution to this? I'm facing a similar problem working on creating ShellExtensions. Thanks!
-
Did you find a solution to this? I'm facing a similar problem working on creating ShellExtensions. Thanks!
Happened to me as well. Attached the shell extension dll to SearchFilterHost.exe for debugging purpose, after the debugging finished I need to rebuild the dll but encountered the problem abovementioned. Solution is to stop SearchFilterHost.exe in task manager afterwards.