none
Why does building a Setup and Deployment / Windows Installer project crash VS2017 Community edition? RRS feed

  • Question

  • I've been learning about deployment of various application types (eg. console applications, windows service applications, windows forms, wpf etc) built using Visual Studio 2017.

    In particular I was looking at what I understand are referred to as Setup and Deployment Projects or Windows Installer Setup Projects: https://msdn.microsoft.com/en-au/library/wx3b589t(v=vs.100).aspx

    I couldn't locate the Setup and Deployment Projects in Visual Studio 2017 at first. However I located an extension to Visual Studio from Microsoft called Microsoft Visual Studio 2017 Installer Projects https://marketplace.visualstudio.com/items?itemName=VisualStudioProductTeam.MicrosoftVisualStudio2017InstallerProjects

    After installing the extension for Visual Studio I could locate Visual Studio Installer under Other Project Types in the Add New Project window. I haven't been able to successfully build an installer however for a project however.

    On different occasions and with different solutions using a standard default Windows Form project or a default console application, when I right click the Setup project in the Solution Explorer Window and select build the following happens:

    A dialog window relating to SQL Management Studio appears with the following

    Please wait while Windows configures SQL Server 2008 R2 SP2 Management Studio.
    On top of that dialog window a further dialog window appears with:

    0: Watson 1: 1304 2: STreamSupportFiles 3:streamBinaryToDisk 4:5 5:e:\sql10_main_t\sql\setup\darmwin\sqlcastub\streamca.cpp 6:238 7:sqlcastub.dll 8:sqlrun.msi

    and an ok button.
    If i pres the ok button on the dialog identified in 2 I end up with a further dialog with a title of SQL Server 2008 R2 SP2 Management Studio. The content of the window is:

    Error writing to file: Access is denied. Verify that you have access to that directory. An OK button appears in the window.
    I'm not sure what "that" directory actually refers to in this context as it wasn't expected.

    If I click Ok on the dialog window then I see a Windows Installer dialog window with the message "Preparing to Install" and a cancel button.
    After a prolonged period with nothing seemingly occurring, and the Visual Studio main window now having (not responding) as part of its title I ultimately end up clicking the cancel button on the Windows installer dialog. This results in the installer freezing and ultimately either Visual Studio crashes or has become so unresponsive that I end up terminating it with the task manager.
    I watched a video in which someone had built a Setup Project for a Windows Service and at no stage did i see the Windows relating to SQL Server or the Windows Installer Preparing to Install window. I didnt expect to receive any of the mentioned windows, nor Visual Studio to become unresponsive and essentially crash.

    I went to Tools > Options > Projects and Solutions and changed the MS build output and log verbosity to Diagnostic, but didnt find anything related to SQL Server 2008.

    Does anyone have any thoughts as to what may be causing this and how I could resolve?

    Further, should I perhaps be looking at some other solution/tool to be used for deployment purposes instead of the Setup and Deployment projects? Given the nature of the question instead of leaving it at just this perhaps some other questions : 1. Are Setup and Deployment projects still a tool/solution actively used by other developers? If so, are they extensively used? Or how extensively are they used relatively to other technologies/tools/solutions for deployment?
    Tuesday, July 4, 2017 11:36 PM

Answers

  • Hi Darmath,

    From this similar link we can get this message that say:

    When you build a Microsoft Visual Studio setup project a Microsoft SQL Server 2008 R2 setup might start.

    Please try to solve it on a x64 system:

    regsvr32.exe /u "C:\Program Files (x86)\Common Files\microsoft shared\MSI Tools\mergemod.dll"
    regsvr32.exe "C:\Program Files (x86)\Common Files\microsoft shared\MSI Tools\mergemod.dll"

    On a x86 system:

    regsvr32.exe /u "C:\Program Files\Common Files\microsoft shared\MSI Tools\mergemod.dll"
    regsvr32.exe "C:\Program Files\Common Files\microsoft shared\MSI Tools\mergemod.dll"

    And just as LeonCS said, ClickOnce is also a very practical deployment of technology.

    Best Regards,

    Stanly


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    • Marked as answer by Darmath Thursday, July 6, 2017 2:14 AM
    Wednesday, July 5, 2017 6:30 AM
    Moderator

All replies

  • Hi

    I am only an amateur, - - so hopefully more qualified answers will ensue.

    But, as I understand it, with Community version being free, does not provide full installation and other components like a paid for yearly prescription provides access to.

    Nevertheless, ClickOnce is fairly powerful and it is included in the free version.


    Pride is the most destructive force in the universe

    Wednesday, July 5, 2017 12:04 AM
  • Thanks for the response, it's appreciated. It's an interesting thought. However, I note from the comments from the web page for the extension that apparently it can only be installed on Community Edition, which was one of the reasons why I installed the extension at all: https://marketplace.visualstudio.com/items?itemName=VisualStudioProductTeam.MicrosoftVisualStudio2017InstallerProjects

    Yes I'm aware of ClickOnce, but from my preliminary research I was coming to the conclusion that the Setup and Deployment projects were more powerful and so thought learning to work with them made more sense than learning a technology, hitting a limitation and then having to go back and waste more time to learn YANT (yet another technology).


    • Edited by Darmath Wednesday, July 5, 2017 1:06 AM
    Wednesday, July 5, 2017 1:04 AM
  • Hi Darmath,

    From this similar link we can get this message that say:

    When you build a Microsoft Visual Studio setup project a Microsoft SQL Server 2008 R2 setup might start.

    Please try to solve it on a x64 system:

    regsvr32.exe /u "C:\Program Files (x86)\Common Files\microsoft shared\MSI Tools\mergemod.dll"
    regsvr32.exe "C:\Program Files (x86)\Common Files\microsoft shared\MSI Tools\mergemod.dll"

    On a x86 system:

    regsvr32.exe /u "C:\Program Files\Common Files\microsoft shared\MSI Tools\mergemod.dll"
    regsvr32.exe "C:\Program Files\Common Files\microsoft shared\MSI Tools\mergemod.dll"

    And just as LeonCS said, ClickOnce is also a very practical deployment of technology.

    Best Regards,

    Stanly


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    • Marked as answer by Darmath Thursday, July 6, 2017 2:14 AM
    Wednesday, July 5, 2017 6:30 AM
    Moderator
  • Hi Stanly_F, 

    Thank you that resolved the issue.

    Regards,

    Darmath

    Wednesday, July 5, 2017 11:52 PM
  • Hi Darmath,

    Congratulations.

    And if my reply provided you with a solution please mark the reply as answered as this will help others looking for the same or similar issues down the road.

    Thanks.

    Best Regards,

    Stanly


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Thursday, July 6, 2017 12:55 AM
    Moderator