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. NET-1.1: Setup didn't include all assemblies

NET-1.1: Setup didn't include all assemblies

Scheduled Pinned Locked Moved Visual Basic
csharpvisual-studiohelpquestion
1 Posts 1 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.
  • M Offline
    M Offline
    Marco Turrini
    wrote on last edited by
    #1

    Hi to everyone, I'm writing, maintaining and deploying some applications: every aplication is made up by an executable (winexe) and some dlls (class library). To distribute them, I generate a Setup program for each application using the standard Setup project included in Visual Studio 2003. Everything used to work fine but, a couple of weeks ago, the generated Setup for one application "lost" one library: it was simply missing from the .msi file and I had to include manually into the project to force the installation. Last week another Setup "forgot" three assemblies. I also wrote a little vb.net program to scan - through reflection - all the referenced assemblies in the winexe and copy these assemblies in another folder and actually I found out that the same assemblies were missing from the new destination folder (but still there in the bin directory) Given that: - each application has all the references to the assemblies, with LocalCopy=True (indeed, I can find them in the bin directory) - each Setup project is in a different solution than the application - each Setup project is SourceSafe'd - each assembly (winexe and library) is obfuscated and strong-named - I checked version and date properties for the missing assemblies and they were coherent with the application (same version and date/time) am I doing something wrong (or missing something important) or did? Thanks in advance to anyone will help.

    Marco Turrini

    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