Issues Importing MSM Project And MSM Itself - Advanced Installer Community

We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

sjeslis
Posts: 308
Joined: Mon Aug 22, 2011 11:40 pm
Contact: Website

Issues Importing MSM Project And MSM Itself

Issue #1
=======
I have a merge module written as a Visual Studio deployment project (i.e. .vdproj) that when imported yields an "unsupported project type" error.

Issue #2
=======
Okay so I moved on to just importing the MSM and everything "seems happy" (Note: I have not tried running it yet). This merge module installs a windows service. Looks like the import created a custom action to a binary named "InstallUtil" BUT with no file extension! Is this file really "InstallUtil.lib", "InstallUtilLib.dll", "InstallUtil.exe"???
Scott Jeslis
Senior Software Engineer
Cicero, Inc.
sjeslis
Posts: 308
Joined: Mon Aug 22, 2011 11:40 pm
Contact: Website

Re: Issues Importing MSM Project And MSM Itself

I noticed if I change the file's extension and look at the file's properties (under Windows 7) I see the original file name apparently listed as "InstallUtilLib.dll"
(see attached dialog capture for more info).
Attachments
Capture.PNG
Capture.PNG (37.4 KiB) Viewed 4385 times
Scott Jeslis
Senior Software Engineer
Cicero, Inc.
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Issues Importing MSM Project And MSM Itself

Hello,
I have a merge module written as a Visual Studio deployment project (i.e. .vdproj) that when imported yields an "unsupported project type" error.
Unfortunately, Advanced Installer doesn't offer functionality to import a .vdproj file of a merge module created with Visual Studio. We have added this on our TODO list and it will be available in a future version of Advanced Installer.
Looks like the import created a custom action to a binary named "InstallUtil" BUT with no file extension! Is this file really "InstallUtil.lib", "InstallUtilLib.dll", "InstallUtil.exe"???

This is a normal behavior because InstallUtil represent the identifier of the dll and not the name of the related dll file. InstallUtil may be a custom action used by Visual Studio in order to install services.
If you have problems importing the MSM, then it is recommendable to use Windows Installer technology in order to install a service. So, you can use our "Service" page or the ".NET Installer Class action" custom action in order to install a service.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”