access to unmanaged code

Discussion in 'Visual Studio' started by Bruce, May 12, 2008.

Thread Status:
Threads that have been inactive for 5 years or longer are closed to further replies. Please start a new thread.
  1. Bruce

    Bruce DiscountASP.NET Staff

    Jim,

    This won't work on our server because COM object actually needs to be registered on the server which we don't support.

    Bruce

    DiscountASP.NET
    www.DiscountASP.NET
     
  2. I am trying to access a dll for some unmanaged C codedeveloped with pre-.netVC++ 6.0. I can write a wrapper using asp.net 3.5 that works fine on my desktop webproject. I just put the two dlls (unmanaged dll and the managed dll wrapper)into a /bin folder in my webproject and all works as expected.

    However, when I upload the webproject to DASP the application cannot find the unmanaged dll. I am told by DASP tech support that i need to re-write the unmanaged code to managed code -- but that's not an option for this extensive public domain legacy code base that is widely used.

    I have been told by responses at the asp.net forum that the webhost doesnt actually use the dlls in the /bin directory by copies these to a folder in the webhost PATH environment. However apparently, DASP does not copy the unmanaged code dlls (i'm guessing here).

    Has anyone else come up with this requirement and been able to solve it?

    ---Jim
     
Thread Status:
Threads that have been inactive for 5 years or longer are closed to further replies. Please start a new thread.

Share This Page