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. Visual Basic
  4. Determine DLL/EXE Version number

Determine DLL/EXE Version number

Scheduled Pinned Locked Moved Visual Basic
helpquestionannouncement
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.
  • N Offline
    N Offline
    nikneem2005
    wrote on last edited by
    #1

    Hello there, I'm having problems reading a DLL Version number. I used the System.Reflection in order to load the assembly, and then read the version number. No problem, it works fine! But since we cannot unload, the dll is locked untile my app shuts down. My app is a WebService, so won't shut down every second ;-) Is there another way to get the version number of a dll/exe, or to unload an assembly so that it's overwritable again? Thnx


    I love it when a plan comes together

    D 1 Reply Last reply
    0
    • N nikneem2005

      Hello there, I'm having problems reading a DLL Version number. I used the System.Reflection in order to load the assembly, and then read the version number. No problem, it works fine! But since we cannot unload, the dll is locked untile my app shuts down. My app is a WebService, so won't shut down every second ;-) Is there another way to get the version number of a dll/exe, or to unload an assembly so that it's overwritable again? Thnx


      I love it when a plan comes together

      D Offline
      D Offline
      Dave Kreskowiak
      wrote on last edited by
      #2

      You can check into creating a new AppDomain and loading your .DLL into that. I don't have any example code, because frankly, I've never done it. But, I have seen it discussed in the c# Forum about 6 months ago. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome

      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