Application Updater - How to Install MSM's

  • Thread starter Thread starter Alex Stevens
  • Start date Start date
A

Alex Stevens

Hi,

I'm trying to find method by which we can deploy our windows forms
application at the client.
It is a windows form application, updating a SQL server database.
Simple.

I've looked at the Microsoft Application Updater Blocks and also the
www.gotdotnet.com .NET Application Updater. Neither of these seem to
overcome some simple tasks, and have glaring limitations that I can see, and
I would appreciate some guidance on these.

I have compiled my application using a setup & deployment project, and have
bundled crystal and all it's MSM.
My application uses some local assemblies in the copied to the bin folder,
and some assemblies from the GAC.

From what I can tell, the UAB provides a method to copy files to the client
when an update is available via ftp / http / UNC paths, and reads this from
a manifest.

So, using this how do I:

1.Create Shortcuts on the desktop?
2. Install / register Crystal reports from the MSM files?
3. Install any MSM files which are designed to included in deployment msi's?
4. Install files which get copied to the GAC?

I surely shouldn't have to pick apart the MSM files and install all the
components myself?
If you should install crystal reports in the initial install on the client,
what happens if I include crystal reporting in a later revision / version?
What should I do when the user logged in doesn't have administrative rights
(which is likely!!).

Is the application updater block, simply for providing x-copy functionality?

Would somebody be able to put me better in the picture?
Is there another product I should use to distribute my application, and have
it automatically update when a new version is available?

Thanks

Alex
 
Hi,

check out my response inline:

Alex Stevens said:
Hi,

I'm trying to find method by which we can deploy our windows forms
application at the client.
It is a windows form application, updating a SQL server database.
Simple.

I've looked at the Microsoft Application Updater Blocks and also the
www.gotdotnet.com .NET Application Updater. Neither of these seem to
overcome some simple tasks, and have glaring limitations that I can see, and
I would appreciate some guidance on these.

I have compiled my application using a setup & deployment project, and have
bundled crystal and all it's MSM.
My application uses some local assemblies in the copied to the bin folder,
and some assemblies from the GAC.

From what I can tell, the UAB provides a method to copy files to the client
when an update is available via ftp / http / UNC paths, and reads this from
a manifest.

That is correct
So, using this how do I:

1.Create Shortcuts on the desktop?
2. Install / register Crystal reports from the MSM files?
3. Install any MSM files which are designed to included in deployment msi's?
4. Install files which get copied to the GAC?

You can't do that - or at least you shouldn't.
Use Windows Installer for that. All those features are part of it.
The purpose of UAB is to update once you've installed the app.
Something like the Windows Update feature in Windows XP
I surely shouldn't have to pick apart the MSM files and install all the
components myself?
If you should install crystal reports in the initial install on the client,
what happens if I include crystal reporting in a later revision / version?

Just build another package and install it as an upgrade.
If that doesn't work for you, you can always use the UAB - download the
assemblies and isntall them accordingly.
What should I do when the user logged in doesn't have administrative rights
(which is likely!!).

You'll need admin rights in order to access folders others than My Documents
and the shared app data.


Is the application updater block, simply for providing x-copy functionality?

No. The Application Updater Block, intends to give you the ability to update
an application, while and not have to install it from scratch.
It is always better to separate the different versions of the app - that's
why Windows Installer have the ability to upgrade from previouse versions
(if it finds any)
Would somebody be able to put me better in the picture?
Is there another product I should use to distribute my application, and have
it automatically update when a new version is available?

Thanks

Alex

Rgrds,
 
Back
Top