Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. Managed C++/CLI
  4. Native executable to managed Dll

Native executable to managed Dll

Scheduled Pinned Locked Moved Managed C++/CLI
c++helpcsharplinux
2 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • P Offline
    P Offline
    Polity4h
    wrote on last edited by
    #1

    Hi, A long long time ago in a compiler far far beyond now, VS2005 without sp1 ;) ... -_-, i've developed a project using native C++ and a lame shell interface, now i thought it could be fun converting the project to a C++/CLI DLL with a managed wrapper class for the main functionality normally controlled by the old shell input and an interface developed in C#, this all works great, however as soon as i switch my executable to dll build, i get a fatal error in the interface telling me he cant load the assembly updater3 wich is my managed dll. I probably thought this would be because the lack of a AssemblyInfo file, however creating a new dll, ripping the assemblyinfo and editing it doesnt help a bit. Is there someone who can tell me wich rules apply when converting a native application to a managed dll Thanks already!

    L 1 Reply Last reply
    0
    • P Polity4h

      Hi, A long long time ago in a compiler far far beyond now, VS2005 without sp1 ;) ... -_-, i've developed a project using native C++ and a lame shell interface, now i thought it could be fun converting the project to a C++/CLI DLL with a managed wrapper class for the main functionality normally controlled by the old shell input and an interface developed in C#, this all works great, however as soon as i switch my executable to dll build, i get a fatal error in the interface telling me he cant load the assembly updater3 wich is my managed dll. I probably thought this would be because the lack of a AssemblyInfo file, however creating a new dll, ripping the assemblyinfo and editing it doesnt help a bit. Is there someone who can tell me wich rules apply when converting a native application to a managed dll Thanks already!

      L Offline
      L Offline
      led mike
      wrote on last edited by
      #2

      See if this article[[^](http://this article)] helps led mike

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • World
      • Users
      • Groups