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. C#
  4. Setup.exe says "<Error Message>"

Setup.exe says "<Error Message>"

Scheduled Pinned Locked Moved C#
csharpvisual-studiodebugginghelpquestion
3 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.
  • A Offline
    A Offline
    Arun Bhalla
    wrote on last edited by
    #1

    I've been developing a project using VS.NET 2003 for well over a year. Today I'm building the installer (Setup.msi), and when I test it out, I get the usual "Preparing to install files" (or whatever) message box, and then I get a message box that says "". I haven't changed that much in my solution lately. I had recently installed the .NET bootstrapper plug-in, but even after uninstalling that, I still get that when I build installers. Any ideas or tips? Any ways I can effectively debug the MSI or get some verbose logging? Thanks, Arun

    H 1 Reply Last reply
    0
    • A Arun Bhalla

      I've been developing a project using VS.NET 2003 for well over a year. Today I'm building the installer (Setup.msi), and when I test it out, I get the usual "Preparing to install files" (or whatever) message box, and then I get a message box that says "". I haven't changed that much in my solution lately. I had recently installed the .NET bootstrapper plug-in, but even after uninstalling that, I still get that when I build installers. Any ideas or tips? Any ways I can effectively debug the MSI or get some verbose logging? Thanks, Arun

      H Offline
      H Offline
      Heath Stewart
      wrote on last edited by
      #2

      If you read the Command-line Options[^] for Windows Installer, you could construct the following command-line for verbose logging:

      msiexec.exe /I Setup.msi /L*uv Setup.log

      Typically, find the first error reported (although sometimes errors occur that aren't vital for the installation to continue, so ignore those).

      Microsoft MVP, Visual C# My Articles

      A 1 Reply Last reply
      0
      • H Heath Stewart

        If you read the Command-line Options[^] for Windows Installer, you could construct the following command-line for verbose logging:

        msiexec.exe /I Setup.msi /L*uv Setup.log

        Typically, find the first error reported (although sometimes errors occur that aren't vital for the installation to continue, so ignore those).

        Microsoft MVP, Visual C# My Articles

        A Offline
        A Offline
        Arun Bhalla
        wrote on last edited by
        #3

        Thanks! Turns out it was an invalid (empty) launch condition that lingered around instead of being deleted.

        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