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. The string binding is invalid

The string binding is invalid

Scheduled Pinned Locked Moved Managed C++/CLI
wpfwcfhelp
4 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.
  • H Offline
    H Offline
    hansipet
    wrote on last edited by
    #1

    Hello, I have a problem with a mixed mode dll. In this dll it is a class (#pragma unmanaged) which contains a singleton. But now I have a porblem during unloading the program. During unload the program I became allways the message "Unhandled exception at 0x7c812a5b in Test.exe: 0xC0020001: The string binding is invalid". I have searched already a lot around the internet but there are a lot of messages regarding this problem. The most have only a solution for VS2003 and not VS2005. I have tested all what I have found. It is really easy to reproduce this problem. You need only a mixed mode dll and a unmanaged class with an singleton (the problems happens also with automatic atexit registration and also in manual) Best regards Hansjörg

    L 1 Reply Last reply
    0
    • H hansipet

      Hello, I have a problem with a mixed mode dll. In this dll it is a class (#pragma unmanaged) which contains a singleton. But now I have a porblem during unloading the program. During unload the program I became allways the message "Unhandled exception at 0x7c812a5b in Test.exe: 0xC0020001: The string binding is invalid". I have searched already a lot around the internet but there are a lot of messages regarding this problem. The most have only a solution for VS2003 and not VS2005. I have tested all what I have found. It is really easy to reproduce this problem. You need only a mixed mode dll and a unmanaged class with an singleton (the problems happens also with automatic atexit registration and also in manual) Best regards Hansjörg

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

      Have you tried freeing the Singleton prior to the process exiting?

      led mike

      H 1 Reply Last reply
      0
      • L led mike

        Have you tried freeing the Singleton prior to the process exiting?

        led mike

        H Offline
        H Offline
        hansipet
        wrote on last edited by
        #3

        How I should free the singleton prior to process exiting? It is freeing automatically and I don't wont an explicitly call to a function. Best regards Hansjörg

        L 1 Reply Last reply
        0
        • H hansipet

          How I should free the singleton prior to process exiting? It is freeing automatically and I don't wont an explicitly call to a function. Best regards Hansjörg

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

          hansipet wrote:

          I don't wont an explicitly call to a function.

          Just as a way of testing to see if it solves the problem, why not? :rolleyes:

          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