hi paul,
i didn't want to have to configure security policy on every client
machine to allow the COM component to work. i was also getting "drag n
drop registration failed" error messages with some components, and
couldn't figure out what was going wrong.

i'm interested to read that others have built similar
application-updating mechanisms, that are outside the .NET provided
methods, because they aren't suitable. i haven't seen anything of .net
2.0 yet, but does it have anything new in this regard?

[quoted text, click to view]

Whidbey has some significant improvements in the deployment area. There was
a talk at the PDC on these features a couple of hours ago
(http://www.mymsevents.com/MyMSEvents/search.aspx?s=1&keywords=CLI210&keywor
dtype=1), so it will be worth grabbing the slides for this session once they
are online. Based on some of the public demos I've seen and the PDC talk
there will be a feature in Whidbey VS.NET that allows a
project to be published from inside VS.NET, which will allow a simplified
deployment paradigm for applications that aren't suitable for xcopy
deployment - this is the ClickOnce stuff in the PDC presentation.

Nick Wienholt, MVP
Maximizing .NET Performance
http://www.apress.com/book/bookDisplay.html?bID=217
Sydney Deep .NET User Group www.sdnug.org


[quoted text, click to view]