Application.Blocks Updater Question

  • Thread starter Thread starter BuddyWork
  • Start date Start date
B

BuddyWork

Hello,

Could you please advise me on the following.

We have a product that will be installed on a network.
Each client machine will have access to the network share
and will be given the correct trust to run the
application.
The current problem we have is that when we start the
application it takes approx 5 mins to start, the reason
behind this is that it's loading the assemblies across the
network to the clients PC each time (basically it's not
cached). We understand that by using Updater Application
Block we could download each assembly to the client's
machine and cache it in a folder so next time we start the
application from the network share we would set the
codebase to check the cache first and if a new version
exist in the network share we would download it first. My
question is can we archive this by using the Updater if so
do you have an example which does a similar thing which we
can look at.

Thanks,
 
Both the AppUpdater from windowsforms.net, and the Application Updater
Application Block from P&P work best with MSI-installed apps - you really
need to have a shortcut the user uses to launch the app, which is installed
locally. The applciation block has more features, but the AppUpdater from
windowsforms.net is very easy to use, and will work for most people. With
AppUpdater, a proxy (appstart) is launched and it spins up an app-domain
that hosts the app - meanwhile it checks for updates, and uses BITS to
download any updates it finds, and place them into a version-specific
folder. After the new version is updated, the user is typically prompted,
and the running application is closed. When the app restarts, it comes up
with using the new version.

Why would you want to explictly set the codebase? Why not use private
deployment?
 
Back
Top