Re: DLL Troubles

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Tommy Vercetti (vercetti953_at_hotmail.com)
Date: 02/24/05

  • Next message: Tommy Vercetti: "Using COM within .NET" 
    Date: Thu, 24 Feb 2005 15:33:40 -0600

    Short answer: Managed C++ DLLs don't work yet (as of Visual Studio 2003).

    You probably don't believe this but, really, it's true.

    Apparently, some people have done this but you have to:
            1) Not link in any Managed libraries including the standard .NET
    runtime which is basically impossible
            2) Not link in any unmanaged libraries uncluding the standard C/C++
    ryntime which is also basically impossible.
            3) Deal with all kinds of bizarre errors since no static/global
    variables work correctly. Even those used internally by unmanaged
    libraries (including the runtime).

    Visual Studio 2005 hopefully will have a better solution.

    Tom Andrecht wrote:
    > I'm trying to write two managed C++ .DLL files for use in a project, and am
    > running into some trouble that I'm not sure if it's something I'm doing
    > wrong (this is my first time trying this) or if it's something VS .NET 2k3
    > is doing to me. My problems are this:
    >
    > 1. The projects will not find standard functions like strcpy and new.
    > doesn't seem to even know what they are despite my having added the header
    > files for everything plus.
    >
    > 2. When I try to use these in my main project file (built in C#), it tells
    > me that my classes in the DLL's do not exist in my namespace and asks if I'm
    > missing an assembly reference. I know I have them referenced in the project
    > file, and the build order is such that both are compiled at the appropriate
    > times to ensure (theoretically) that everything that is depended on gets
    > compiled first, and in the case of my C# DLL projects, everything works
    > fine. Any ideas from anyone? Thanks
    >
    > Tom
    >
    >

  • Next message: Tommy Vercetti: "Using COM within .NET"

    Relevant Pages

    • Output folder for my ASP 2.0 Web Site.
      ... Im developing a web service in ASP Net 2.0 using Visual Studio 2005, ... want it to get compiled to dlls, so I can distribute it and nobody can ... The output folder ... using directive or an assembly reference?) ...
      (microsoft.public.dotnet.framework.aspnet)
    • RE: How do you specify build type for binary reference?
      ... reference instead of assembly reference. ... Visual Studio will automatically ... Microsoft Online Community Support ... nature are best handled working with a dedicated Microsoft Support Engineer ...
      (microsoft.public.vsnet.ide)
    • Re: side-by_side error on Vista
      ... Platform SDK Jan 2006 ... I'm compiling an application on an XP machine and testing it on Vista. ... I tried just copying the newer DLLs to the app's startup directory, ... look in the directory where Visual Studio is installed for the file redist.txt which will tell you what files you are allowed to redistribute with your application. ...
      (microsoft.public.win32.programmer.ui)
    • Re: Output folder for my ASP 2.0 Web Site.
      ... Jon ... > Im developing a web service in ASP Net 2.0 using Visual Studio 2005, ... > project's Propety Pages\MSBuild options, you can set an output folder, ... > using directive or an assembly reference?) ...
      (microsoft.public.dotnet.framework.aspnet)
    • Re: VS 2005 and Manifest for runtime dlls
      ... My problem was that I wasn't sure if I need to deploy the dlls and ... would I need also the manifest from that directory. ... For me it turned out that I was including a third party dll that didn't have ... I'm having some problems with Visual Studio 2005 and even though I read ...
      (microsoft.public.vsnet.general)