Moving to the .NET 3.0 framework

Hi all,

I know that it is currently impossible to change a prerequisite of using the .NET 2.0 framework to the .NET 3.0 framework. But I wonder what other people have been using to change their click once deployment.

• Create a separate product installation. (Branch the product and leave current customers without an automatic update)
• Write some script that detects the current framework version in the client application, and warn the user that the next update does require a new prerequisite. (Or even direct them directly to the prerequisite installation)

What will be the case for the 3.5 framework. Are we loosing the automatic update again?

I really hope this issue will be addressed by the next release of the Click Once. That there is a smoother path to assist the client installations with new prerequisites.

Love to hear other reactions.

[914 byte] By [Sentient] at [2008-1-4]