yakshasa
New member
Once we have distributed our application "App" to a new customer via CD
Installation, we usually do minor updates via web download.
On our VB6 version this usually just entailed the customer downloading
an up dated App.exe file.
For our .Net(2008) version, I need to find out if three other files
that are created along with App.exe should be downloaded with it
(App.application, App.exe.manifest and App.xml).
I copied an updated .Net App.exe -by itself - over to my test machine
that I had done the original .Net version installation on, and it ran without
incident, at least for the things I tested.
I still have a feeling that if I renamed some controls, or added a new
class or some such, it would probably require that the other App files
that I mentioned were updated.
Our application is a winforms based desktop application.
The customer would have the .Net framework (3.5) installed, if
necessary, during the initial CD based installation, which uses
InstallShield 2009.
As I mentioned, we do our current (VB6) updates via web download (but
not using Installshield's web update service).
Given that the customer has the complete original installation,
should adding the .Application, .XML, and .Manifest files to the
web download be sufficient?
Does anyone have a definitive answer?
Installation, we usually do minor updates via web download.
On our VB6 version this usually just entailed the customer downloading
an up dated App.exe file.
For our .Net(2008) version, I need to find out if three other files
that are created along with App.exe should be downloaded with it
(App.application, App.exe.manifest and App.xml).
I copied an updated .Net App.exe -by itself - over to my test machine
that I had done the original .Net version installation on, and it ran without
incident, at least for the things I tested.
I still have a feeling that if I renamed some controls, or added a new
class or some such, it would probably require that the other App files
that I mentioned were updated.
Our application is a winforms based desktop application.
The customer would have the .Net framework (3.5) installed, if
necessary, during the initial CD based installation, which uses
InstallShield 2009.
As I mentioned, we do our current (VB6) updates via web download (but
not using Installshield's web update service).
Given that the customer has the complete original installation,
should adding the .Application, .XML, and .Manifest files to the
web download be sufficient?
Does anyone have a definitive answer?
