locked
Windows Installer issues building Setup Deployment Project in Visual Studio 2005 RRS feed

  • Question

  •   I'd posted a question to "microsoft.public.vstudio.general" via Google with the subject "Build Setup and Deployment Project Problems" but got no response.

    http://groups.google.com/group/microsoft.public.vstudio.general/browse_thread/thread/f23b7c48050dfc40/7fdc1e6b2ca7e462?hl=en#7fdc1e6b2ca7e462

    I'm not sure whether the problem is with Setup & Deployment (MSBuild) or Windows Installer (or a combination).There are two problems that may or may not be related:

    1. During installation of the setup via the .msi file the following
    error occurs:
    "Error writing to file <filename>. Verify that you have access to that
    directory"
    This appears to occur because the same .dll is packaged into a
    contained .msm multiple times.
    The workaround is to manually copy the .dll into the GAC (C:\Windows
    \Assembly)…I assume that the setup detects the version of the .dll is
    already installed and then skips the extraction of the .dll(s) from
    the package into the temp install folder.

    2. (This may be the cause of problem 1, I just don’t have another
    workaround for this problem yet.)
    Each time the solution is built the setup deployment project appears
    to add another instance of one of the .dlls (built by another project
    in the solution) to the package.

    Monday, October 6, 2008 8:02 PM

Answers