msi package remote install

Question

0.00/5 (No votes)

See more:

VS2012

I have created a set up in vs 2012
to deploy my application.

After settting up the install to create the msi.

I get error -7235: InstallShield could not create the software identification tag because the Tag Creator ID setting in the General Information view is empty. ISEXP : warning : -7235: InstallShield could not create the software identification tag because the Tag Creator ID setting in the General Information view is empty.

also i get -6245: One or more of the project's components contain .NET properties that require the .NET Framework. It is recommended that the release include the .NET Framework. ISEXP : warning : -6245: One or more of the project's components contain .NET properties that require the .NET Framework. It is recommended that the release include the .NET Framework.

However the msi package is created but will not work remotely..

any one knows how to fix in vs 2012 so i dont get any warning messages..

HELP ANY1!

Posted 19-Jan-15 11:00am

mrukr

Updated 19-Jan-15 11:01am

v2

Add a Solution

Comments

mrukr 19-Jan-15 17:02pm

i use this to run remote install old msi and it works
but my msi from vs 2012 dont work using below:
psexec \\remotecomputer -u Domain\Username -p Password msiexec.exe /i "\\networkservername\sharename\my.msi" /quiet /norestart

so this got me to think that error messages while deploying should be fix .

any ideas guys?

Sergey Alexandrovich Kryukov 19-Jan-15 17:09pm

Does it install locally? Does it install locally on that host? The problem could be unrelated to remoting, and even pretty likely unrelated. And I would never use InstallShield. Presently, I usually recommend open-source WiX Toolset.
—SA

mrukr 19-Jan-15 17:42pm

well i use other msi created from old vs etc vs 2008 etc my remote application install locally .however whatever msi package i build on vs2012 wont install remote getting 1603 as msi failed.
yeah so after msi is ready to install

Wix is free?

Sergey Alexandrovich Kryukov 19-Jan-15 17:57pm

You did not clearly answer what happens for local installation.

Wix? Open-source. How it can be not free? WiX is "legitimate", because it fully conforms to MSBuild format (the product also has excellent Visual Studio integration), and IntelliSense and even old Visual Studio "Setup" template are not, that's probably on reason why Microsoft deprecated it.

—SA

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Answer 1 · 2015-01-19T12:00:00

As you expressed some interest in WiX:

Installshield is awful. And the setup project type bundled with many versions Visual Studio is not good, too; Microsoft is getting rid of it without replacing it with anything else. So, what to do?

My solution is using open-source WiX, the open-source installation toolset:
http://en.wikipedia.org/wiki/WiX[^],
http://wixtoolset.org[^].

I recently made a migration to it and am very glad I did. It's not perfect too (and the whole Microsoft Installer and its API is well behind other technologies), but it is much better than anything I ever heard of so far. Actually, if you use WiX, you will understand that the tools mentioned above are actually nearly illegal (technically), they are using their proprietary project files. Only WiX provide excellent compliance with the contemporary MSBuild and related XML-based project standard, so you can use WiX projects using standard MSBuild techniques: customize it, integrate with bigger master projects or solutions, write your own extensions, if you need some, and so on.

Also, it has very good and smooth integration with Visual Studio of different versions.

Finally, one big benefit is: WiX code is non-visual. Everything is explicitly declared in XML code using some official documented XML scheme. Nothing is hidden behind the XML code files.

As to the behavior and features, many advanced features are not comprehensively documented, unfortunately. But communities already collected considerable experience and provide a lot of useful advice. So far, I was able to find solutions to all chores I practically needed. And the set of ready-to-use solutions is wider that that I found in a legacy Setup project. Some actions which required development of custom steps are already embedded in WiX. It includes adjusting Windows Firewall to your application, setting permissions of files and directories, different action depending on the project platform and target platform, and a lot more.

Please see my past answers:
Custom setup project[^],
How to conditionally install components based on processor architecture type (32-bit or 64-bit)?[^],
How to conditionally install components based on processor architecture type (32-bit or 64-bit)?[^].

—SA