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. Assembly probing

Assembly probing

Scheduled Pinned Locked Moved Managed C++/CLI
helpcsharpcomwindows-adminquestion
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.
  • K Offline
    K Offline
    KrunalC
    wrote on last edited by
    #1

    Currently, I'm working on COM Interoperability project. In that client application (in vb 6.0) need to launch my application developed in .net. Now the problem is the assemblies referenced by my .net application is spread across 2-3 folders and not in the same folder where my .net executable is placed. Also, the client application is also not in the same path where my .net executable is. If I keep everything (i.e. .net executable and client application) in same location everything works fine but if I move my client application to location different than my .net executable path, client application fails to load. I register the assembly into the registry withoug codebase. Also, I tried setting the private path in probing attribute in app.config file but it didn't work. Can any one pls help in how I can resolve the assembly reference issue? Thanks...

    G 1 Reply Last reply
    0
    • K KrunalC

      Currently, I'm working on COM Interoperability project. In that client application (in vb 6.0) need to launch my application developed in .net. Now the problem is the assemblies referenced by my .net application is spread across 2-3 folders and not in the same folder where my .net executable is placed. Also, the client application is also not in the same path where my .net executable is. If I keep everything (i.e. .net executable and client application) in same location everything works fine but if I move my client application to location different than my .net executable path, client application fails to load. I register the assembly into the registry withoug codebase. Also, I tried setting the private path in probing attribute in app.config file but it didn't work. Can any one pls help in how I can resolve the assembly reference issue? Thanks...

      G Offline
      G Offline
      George L Jackson
      wrote on last edited by
      #2

      Have you included the paths of the files in the computer's "PATH" environment variable?

      "We make a living by what we get, we make a life by what we give." --Winston Churchill

      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