Pack and Deply. creates EXE and Installer??

[al]

Greetings,

I have just finished packaging and deploying winapp. Packing went
fine and so did the deplo. However, I have noticed that there are two
files, not one, that were created by VB.NET. One is application.exe
and the other one is installer that has all the dependencies. Any
idea why is that??

MTIA,
Grawsha

[Herfried K. Wagner [MVP]]

* gr*********@yahoo.com (al) scripsit:

I have just finished packaging and deploying winapp. Packing went
fine and so did the deplo. However, I have noticed that there are two
files, not one, that were created by VB.NET. One is application.exe
and the other one is installer that has all the dependencies. Any
idea why is that??

Mhm... There should be at least an MSI file and maybe three executables
(one called "Setup.exe" and two versions of MSI).

--
Herfried K. Wagner [MVP]
<http://www.mvps.org/dotnet>

[al]

hi***************@gmx.at (Herfried K. Wagner [MVP]) wrote in message news:<eo**************@TK2MSFTNGP11.phx.gbl>...

* gr*********@yahoo.com (al) scripsit:

I have just finished packaging and deploying winapp. Packing went
fine and so did the deplo. However, I have noticed that there are two
files, not one, that were created by VB.NET. One is application.exe
and the other one is installer that has all the dependencies. Any
idea why is that??

Mhm... There should be at least an MSI file and maybe three executables
(one called "Setup.exe" and two versions of MSI).

Hi,
Should not there be only .msi file? why there is setup.exe?

[Herfried K. Wagner [MVP]]

* gr*********@yahoo.com (al) scripsit:

I have just finished packaging and deploying winapp. Packing went
fine and so did the deplo. However, I have noticed that there are two
files, not one, that were created by VB.NET. One is application.exe
and the other one is installer that has all the dependencies. Any
idea why is that??

Mhm... There should be at least an MSI file and maybe three executables
(one called "Setup.exe" and two versions of MSI).

Should not there be only .msi file? why there is setup.exe?

"Setup.exe" can do some checks before launching the setup (for example
remove previous versions, ...

--
Herfried K. Wagner [MVP]
<http://www.mvps.org/dotnet>

[Ot]

"Herfried K. Wagner [MVP]" <hi***************@gmx.at> wrote in message
news:OO**************@TK2MSFTNGP12.phx.gbl...

* gr*********@yahoo.com (al) scripsit:

Mhm... There should be at least an MSI file and maybe three executables (one called "Setup.exe" and two versions of MSI).

Should not there be only .msi file? why there is setup.exe?

"Setup.exe" can do some checks before launching the setup (for example
remove previous versions, ...

--
Herfried K. Wagner [MVP]
<http://www.mvps.org/dotnet>

That's way cool. How do I get the installer to remove prior version?

I have VB.NET Standard. In my setup project I generate an .msi file and
there is a "setup.exe" separate from that .msi file. When I send my
application to a second machine I can run the .msi and get my application
onto that computer. However, even though I set the "Remove prior versions"
to true, it stops and tells me to use add/remove to remove the prior
version.

I have executed other people's msi files and they can remove prior
versions.

Executing the "setup.exe" directly or simply running the .msi both lead the
the same window:

== window contents==
Windows Installer X

Another version of this product is already installed.
Installation of this version cannot continue. To
configure or remove existing version of this product,
use Add/Remove Programs on the Control Panel.

[ OK ]
==end window contents==

Regards,
Ot

[Herfried K. Wagner [MVP]]

* "Ot" <ur***@tds.invalid (use net)> scripsit:

"Setup.exe" can do some checks before launching the setup (for example
remove previous versions, ...
That's way cool. How do I get the installer to remove prior version?

I have VB.NET Standard. In my setup project I generate an .msi file and

Select the setup project in the project explorer and have a look at the
property window. There you will find an option to do that.
there is a "setup.exe" separate from that .msi file. When I send my
application to a second machine I can run the .msi and get my application
onto that computer. However, even though I set the "Remove prior versions"
to true, it stops and tells me to use add/remove to remove the prior
version.

That's a problem some people reported. I don't have more info on that
topic.

--
Herfried K. Wagner [MVP]
<http://www.mvps.org/dotnet>

[al]

hi***************@gmx.at (Herfried K. Wagner [MVP]) wrote in message news:<bt************@ID-208219.news.uni-berlin.de>...

* "Ot" <ur***@tds.invalid (use net)> scripsit:

"Setup.exe" can do some checks before launching the setup (for example
remove previous versions, ...

That's way cool. How do I get the installer to remove prior version?

I have VB.NET Standard. In my setup project I generate an .msi file and

Select the setup project in the project explorer and have a look at the
property window. There you will find an option to do that.

there is a "setup.exe" separate from that .msi file. When I send my
application to a second machine I can run the .msi and get my application
onto that computer. However, even though I set the "Remove prior versions"
to true, it stops and tells me to use add/remove to remove the prior
version.

That's a problem some people reported. I don't have more info on that
topic.

Wagner,

Thank you, that did clear something to me. There is another strange
behavior of vb.net P&D. My app (NorthwindApp) includes Excel related
com files. When I was doing the P&D, I went to File System option of
the setup project and added the EXE of NorthwindApp to a sub folder I
created in the "User's Program Menu". I installed NorthwindApp on my
development machine. I was able to run NorthwindApp(including opening
Excel) just fine from the installation directory. however, when I go
to Start-->Programs-->NorthwindApp, and try to open Excel, the whole
app crashes, saying some Excel related files are missing??????

Any idea how this happened??

MTIA,
Grawsha

[Ot]

"Herfried K. Wagner [MVP]" <hi***************@gmx.at> wrote in message
news:bt************@ID-208219.news.uni-berlin.de...

* "Ot" <ur***@tds.invalid (use net)> scripsit:

Select the setup project in the project explorer and have a look at the
property window. There you will find an option to do that.

That's a problem some people reported. I don't have more info on that
topic.

--
Herfried K. Wagner [MVP]
<http://www.mvps.org/dotnet>

I found some answers to my own question, but not all.

After you pointed me at the setup properties... I found this:

RemovePreviousVersions

Specifies whether an installer will remove previous versions of an
application during installation. If this property is set to True and an
earlier version is detected at installation time, the previous version's
uninstall function will be called.

Note The installer checks UpgradeCode and ProductCode properties to
determine whether the earlier version should be removed. The UpgradeCode
must be the same for both versions; the ProductCode must be different.

Important: Note the last 5 words. I found that when I did, indeed, make a
different Product Code in the deployment project it went ahead and
installed over the prior stuff.

Also...

DetectNewerInstalledVersion

Specifies whether to check for newer versions of an application during
installation on a target computer. If this property is set to True and a
higher version number is detected at installation time, installation will
end.

As near as I can tell, this checks the version number located in the
deployment project properties, not the version number found in the
assembly.vb.

Regards,
Ot