Groups | Blog | Home
all groups > dotnet distributed apps > july 2005 >

dotnet distributed apps : UAB Directory not created after Updater Application Blocks Downloa


Roy
7/20/2005 1:29:12 PM
I built an application using the Updater Application Block. Everytime I
execute it, however, the block indicates a new update is present when there's
not.

I did some research and discovered that the UAB directory containing the
manifest ID was not created in the application directory on the client
machine. Therefore, everytime I execute my application, a new update is
always detected.

I probably did something wrong in the app.config or the manifest file but I
can't find the problem. The configuration looks fine to me.

Any ideas?

Roy
7/20/2005 2:00:02 PM
The problem was that I had added a "Wait For Exit" Processor Type specified
in the manifest. For reasons I don't completely understand, this was causing
the following comparison to fail in the ApplicationUpdateManager:Activate
method:

if( task.State == UpdaterTaskState.Activated )
{
// Finally, unregister the task
RegistryManager.Current.UnRegisterTask( task.TaskId );
}

When I removed the "Wait For Exit" processor, the application ran fine and
no longer prompts for update on every execution. There's still not a UAB
subdirectory but there are 3 additional directories in the client folder:

applications
downloader
registry

AddThis Social Bookmark Button