P
P Chase
I am writing .Net Web Service using Visual Studio 2005. Part of its
functionality will be implemented by a C DLL, which I am also writing.
The Web Service and DLL are separate projects in one Visual Studio
Solution.
My question is how best to make the C DLL available to the Web
Service?
I have had success "manually" copying the the C DLL to the same
directory as the Web Service DLL. However, this is horrid for various
reasons, particularly that Visual Studio seems to keep the DLL open
all the time, so I cannot replace it with a new one until Visual
Studio is closed down. This would also seem to preclude simply
creating a custom build step to copy the C DLL to that directory, as
this would fall foul of the same problem as the "manual" copying.
How can I get Visual Studio to make the C DLL available to the Web
Service automatically?
functionality will be implemented by a C DLL, which I am also writing.
The Web Service and DLL are separate projects in one Visual Studio
Solution.
My question is how best to make the C DLL available to the Web
Service?
I have had success "manually" copying the the C DLL to the same
directory as the Web Service DLL. However, this is horrid for various
reasons, particularly that Visual Studio seems to keep the DLL open
all the time, so I cannot replace it with a new one until Visual
Studio is closed down. This would also seem to preclude simply
creating a custom build step to copy the C DLL to that directory, as
this would fall foul of the same problem as the "manual" copying.
How can I get Visual Studio to make the C DLL available to the Web
Service automatically?