Experiences with Whidbey Beta 1
ClickOnce Deployment
Trying to install an application that requires FullTrust from the internet or non-local UNC is still either very difficult or impossible.
Found the following reference:
Also, the manifests you create are strong named signed and ClickOnce will block the install of strong named signed manifests that request full trust permissions (like the ones we're making here) over the internet in Beta 1. We're working on ways for small shops to use ClickOnce over the internet in Beta 2 but the best way to get things going in Beta 1 is to zip up the files and place that zip on the internet and your users can download the zip, unzip it, and install the app. You'll still get all the benefits of ClickOnce updates and app management. (from Sampy's Blog)
Intalling from a downloaded zip did not help with security blocking access to updates. They are detected, but the same installation denied dialog appears.
There may be a way to adjust security settings to permit installation of “publisher unknown” applications, but I haven’t found it yet and the reference above suggests there may be no way.
Generic Windows.Forms
The IDE’s Windows.Forms.Form designer can’t handle generic classes derived from Form. An “Unknown Error” screen appears. Temporarily hiding the generic aspects of the class and rebuilding the project allowed the designer to work again.
Changing the signature of a Form derived class appears to be tricky when using designer generated partial classes. Adding a “public” modifier is okay so long as the designer file doesn’t use “private”. The class name and generic-type parameters must be identical but modifiers must only not conflict. It appears that base classes and implemented interfaces also don’t need to be identical as long as they don’t conflict (i.e. two different base classes).