Application Setup

[Ralph]

Hi,

I have created an .msi setup file to deploy my VB app using the setup
project feature for Visual Studio .NET 2003. Everything is working fine;
However, I would like that after the installation is performed the .msi setup
files be deleted upon a successful install of the app.

Any help is greatly appreciated.

Thanks,
Ralph r.

[Vadym Stetsyak]

Hello, Ralph!

R> I have created an .msi setup file to deploy my VB app using the setup
R> project feature for Visual Studio .NET 2003. Everything is working
R> fine; However, I would like that after the installation is performed the
R> .msi setup files be deleted upon a successful install of the app.

Why do you need such behavior?

If your app will be distributed via readonly media ( CDs ), how it would delete that msi?

Also, deleting msi file will give you nothing, since MS installer caches that msi ( for installation repair process ).

--
Regards, Vadym Stetsyak
www: http://vadmyst.blogspot.com

[Ralph]

This App is to be distributed electronically. The purpose for removing the
setup files after install is to ensure that the install is only ran once.
Kind of a security measure.
Ralph R.

"Vadym Stetsyak" wrote:

Hello, Ralph!

R> I have created an .msi setup file to deploy my VB app using the setup
R> project feature for Visual Studio .NET 2003. Everything is working
R> fine; However, I would like that after the installation is performed the
R> .msi setup files be deleted upon a successful install of the app.

Why do you need such behavior?

If your app will be distributed via readonly media ( CDs ), how it would delete that msi?

Also, deleting msi file will give you nothing, since MS installer caches that msi ( for installation repair process ).

--
Regards, Vadym Stetsyak
www: http://vadmyst.blogspot

[Vadym Stetsyak]

Hello, Ralph!

R> This App is to be distributed electronically. The purpose for removing the
R> setup files after install is to ensure that the install is only ran once.
R> Kind of a security measure.

Wouldn't it be simpler, to add custom action to the installer that will check if installation had executed
already? ( by adding some kind of registry settings or checking component registration )

Deleting, msi, IMO is not good solution. Imagine situation, when customer purcheses your software, installs it and
then removes. After couple of days he wants to install it again, but msi file isn't there anymore...

--
Regards, Vadym Stetsyak
www: http://vadmyst.blogspot.com

[Ralph]

If it's a registered user we would supply them with the set up files as
needed. I know that this is not the best solution and I understand where you
are coming from, but what I'm trying to accomplish is to implement some/any
measure to avoid copying of the app and installing it at free will. I'm open
for any suggestions that you may have to accomplish same.
Ralph

"Vadym Stetsyak" wrote:

Hello, Ralph!

R> This App is to be distributed electronically. The purpose for removing the
R> setup files after install is to ensure that the install is only ran once.
R> Kind of a security measure.

Wouldn't it be simpler, to add custom action to the installer that will check if installation had executed
already? ( by adding some kind of registry settings or checking component registration )

Deleting, msi, IMO is not good solution. Imagine situation, when customer purcheses your software, installs it and
then removes. After couple of days he wants to install it again, but msi file isn't there anymore...

--
Regards, Vadym Stetsyak
www: http://vadmyst.blogspot

[Wolfgang Hauer]

Hi!

And what is , when the customer copies the msi before doing the setup?

Wolfgang
"Ralph" <Ra***@discussions.microsoft.com> schrieb im Newsbeitrag
news:88**********************************@microsof t.com...

If it's a registered user we would supply them with the set up files as
needed. I know that this is not the best solution and I understand where
you
are coming from, but what I'm trying to accomplish is to implement
some/any
measure to avoid copying of the app and installing it at free will. I'm
open
for any suggestions that you may have to accomplish same.
Ralph

"Vadym Stetsyak" wrote:

Hello, Ralph!

R> This App is to be distributed electronically. The purpose for
removing the
R> setup files after install is to ensure that the install is only ran
once.
R> Kind of a security measure.

Wouldn't it be simpler, to add custom action to the installer that will
check if installation had executed
already? ( by adding some kind of registry settings or checking component
registration )

Deleting, msi, IMO is not good solution. Imagine situation, when customer
purcheses your software, installs it and
then removes. After couple of days he wants to install it again, but msi
file isn't there anymore...

--
Regards, Vadym Stetsyak
www: http://vadmyst.blogspot

[Vadym Stetsyak]

Hello, Wolfgang!

WH> And what is , when the customer copies the msi before doing the setup?

:8-) Yeah, that will break this "protection"

As a simple protectection mechanism you can consider
developing logic, that will reside in MSI custom action.

In the setup UI there will be text fields that user will fill with its credentials, and
they will go to your server that will permit or deny that application.

This is lightweight protection, for more advanced solutions you have to use
appropriate tools that protect the application and not the setup.

The example of such software is ASProtect
( http://www.aspack.com/asprotect.html )

--
Regards, Vadym Stetsyak
www: http://vadmyst.blogspot.com

[Ralph]

Thanks for your input... That's the route I will take.
Ralph

"Vadym Stetsyak" wrote:

Hello, Wolfgang!

WH> And what is , when the customer copies the msi before doing the setup?

:8-) Yeah, that will break this "protection"

As a simple protectection mechanism you can consider
developing logic, that will reside in MSI custom action.

In the setup UI there will be text fields that user will fill with its credentials, and
they will go to your server that will permit or deny that application.

This is lightweight protection, for more advanced solutions you have to use
appropriate tools that protect the application and not the setup.

The example of such software is ASProtect
( http://www.aspack.com/asprotect.html )

--
Regards, Vadym Stetsyak
www: http://vadmyst.blogspot