Re: Updater Application Block to ClickOnce

I've used both. From the way I understand ClickOnce there really is nothing
special you have to do to your code in order to enable its
installation/updating functionality.  It's all done externally to the app.
This would be akin to using the Block to install a stub that installed the
application.

If you made changes inside your app to handle the mechanics of upgrades then
I would guess (though if I were you I would certainty get other opinions
than mine) you wouldn't need it any more.

I've deployed ClickOnce apps over the I-net via IIS server and internally at
my employer using file share and both scenerios are basically the same steps
as each other. Vastly more simple than I remember the block being.

I would suggest creating a test app, and then going through the VS2005
Documentation, that's all I had as far as resources to learn from and I
managed ok.

---
Vince

> -----Original Message-----
> From: Discussion relating to the specifics of the C# and Managed C++
languages
> [mailto:[email protected]] On Behalf Of Mark Gregory
> Sent: Saturday, August 05, 2006 00:41
> To: [email protected]
> Subject: [DOTNET-CX] Updater Application Block to ClickOnce
>
> Is there a guide on how to go from the Updater Application Block to
ClickOnce?
>
> Regards
> Mark
>
> ===================================
> This list is hosted by DevelopMentor.  http://www.develop.com
>
> View archives and manage your subscription(s) at
http://discuss.develop.com

===================================
This list is hosted by DevelopMentor®  http://www.develop.com

View archives and manage your subscription(s) at http://discuss.develop.com