All,

Apologies if this isn't in the right newsgroup, but I was just taking my
best stab at where it may go!

I've written a C# app with VS.Net 2003, then for deployment created a setup
application. Everything works fine except that every now and again clicking
on the short-cut suddenly asks for the MSI package. Because it can't find
it, the load up cancels...

Because this application is for a corporation network, there's an IT
administrator required to install the application on a PC and they're not
convinced the application should need the MSI once it's installed, hence it
not being there.

Am I doing something wrong in the way the application is being created or
the install is being setup, or is it this a feature implemented by design
into the MSI package?

Thanks.

Dan.

See if any of the "Windows Installer launches unexpectedly" topics help
here:
http://www.installsite.org/pages/en/msifaq/msifaq.htm
and here in the Troubleshooting section, Every time I launch my application,
Windows Installer performs an installation...
http://www.microsoft.com/windows2000...t/msi_faq.mspx
--
Phil Wilson [MVP Windows Installer]
----
"Dan =o)" <danielbass [at] postmaster [dot] co [dot] uk> wrote in message
news:(E-Mail Removed)...
> All,
>
> Apologies if this isn't in the right newsgroup, but I was just taking my
> best stab at where it may go!
>
> I've written a C# app with VS.Net 2003, then for deployment created a
setup
> application. Everything works fine except that every now and again
clicking
> on the short-cut suddenly asks for the MSI package. Because it can't find
> it, the load up cancels...
>
> Because this application is for a corporation network, there's an IT
> administrator required to install the application on a PC and they're not
> convinced the application should need the MSI once it's installed, hence
it
> not being there.
>
> Am I doing something wrong in the way the application is being created or
> the install is being setup, or is it this a feature implemented by design
> into the MSI package?
>
> Thanks.
>
> Dan.
>
>

One of the files that you have installed (contained in the Deplyment
project) has got changed such that it is detected by Windows; Windows then
tries to repair this problem by reverting this changed file to as was when
first time it was installed.

Due to this, it is asking for the .MSI file path. You need to recreate the
deployment project so that such a dependency os not generated.

Regards
Vipul


PS: Try this only if the solutions suggested by Phil dont yield the results.

"Dan =o)" <danielbass [at] postmaster [dot] co [dot] uk> wrote in message
news:(E-Mail Removed)...
> All,
>
> Apologies if this isn't in the right newsgroup, but I was just taking my
> best stab at where it may go!
>
> I've written a C# app with VS.Net 2003, then for deployment created a
> setup application. Everything works fine except that every now and again
> clicking on the short-cut suddenly asks for the MSI package. Because it
> can't find it, the load up cancels...
>
> Because this application is for a corporation network, there's an IT
> administrator required to install the application on a PC and they're not
> convinced the application should need the MSI once it's installed, hence
> it not being there.
>
> Am I doing something wrong in the way the application is being created or
> the install is being setup, or is it this a feature implemented by design
> into the MSI package?
>
> Thanks.
>
> Dan.
>
>

Vipul,

I know of at least one file that changes... The application holds a
username/password file that can be updated within the application, and is
used by a scanner application with which the scanner interacts.

Thanks for your feedback on this!

Dan.

"Vipul Patel" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> One of the files that you have installed (contained in the Deplyment
> project) has got changed such that it is detected by Windows; Windows then
> tries to repair this problem by reverting this changed file to as was when
> first time it was installed.
>
> Due to this, it is asking for the .MSI file path. You need to recreate the
> deployment project so that such a dependency os not generated.
>
> Regards
> Vipul
>
>
> PS: Try this only if the solutions suggested by Phil dont yield the
> results.
>
> "Dan =o)" <danielbass [at] postmaster [dot] co [dot] uk> wrote in message
> news:(E-Mail Removed)...
>> All,
>>
>> Apologies if this isn't in the right newsgroup, but I was just taking my
>> best stab at where it may go!
>>
>> I've written a C# app with VS.Net 2003, then for deployment created a
>> setup application. Everything works fine except that every now and again
>> clicking on the short-cut suddenly asks for the MSI package. Because it
>> can't find it, the load up cancels...
>>
>> Because this application is for a corporation network, there's an IT
>> administrator required to install the application on a PC and they're not
>> convinced the application should need the MSI once it's installed, hence
>> it not being there.
>>
>> Am I doing something wrong in the way the application is being created or
>> the install is being setup, or is it this a feature implemented by design
>> into the MSI package?
>>
>> Thanks.
>>
>> Dan.
>>
>>
>
>

Thanks for that, I'll take a look into those!

Dan.


"Phil Wilson" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> See if any of the "Windows Installer launches unexpectedly" topics help
> here:
> http://www.installsite.org/pages/en/msifaq/msifaq.htm
> and here in the Troubleshooting section, Every time I launch my
> application,
> Windows Installer performs an installation...
> http://www.microsoft.com/windows2000...t/msi_faq.mspx
> --
> Phil Wilson [MVP Windows Installer]
> ----
> "Dan =o)" <danielbass [at] postmaster [dot] co [dot] uk> wrote in message
> news:(E-Mail Removed)...
>> All,
>>
>> Apologies if this isn't in the right newsgroup, but I was just taking my
>> best stab at where it may go!
>>
>> I've written a C# app with VS.Net 2003, then for deployment created a
> setup
>> application. Everything works fine except that every now and again
> clicking
>> on the short-cut suddenly asks for the MSI package. Because it can't find
>> it, the load up cancels...
>>
>> Because this application is for a corporation network, there's an IT
>> administrator required to install the application on a PC and they're not
>> convinced the application should need the MSI once it's installed, hence
> it
>> not being there.
>>
>> Am I doing something wrong in the way the application is being created or
>> the install is being setup, or is it this a feature implemented by design
>> into the MSI package?
>>
>> Thanks.
>>
>> Dan.
>>
>>
>
>