I have a sort-of-related problem. My application needs to be tested on factory equipment where access is tightly controlled, individual users do not have administrator privilege, and installing anything requires a lengthy managerial approval process. We require .NET 2.0,but can get this installed when the machine is built, and this doesn't need to change, so that's OK.
Our problem is how to try new versions of the application, which is a .NET DLL referenced from an Excel application. For older projects using Visual C++,we could just copy over the C++ DLL into the proper path location to make it available to Excel, and it would work without running an installation procedure. With .NET DLL's it appears the installation requiring administrator privilege is mandatory to be able to use the DLL at all.
Is there any way to reference/startup/link/deploy/whatever a .NET DLL without being administrator? Is deployment of the components over the network instead of local installation a possible solution?
My customer just knows this wasn't a problem before, and why can'twe keep doing it the old way... but I don't want to go back to C++!
Thanks, JS2
|