upgrade .NET version with ClickOnce?

[Guest]

Hello,
I've written an application in .NET 2.0 and used ClickOnce deployment. I've
set the prerequisites options to 'download from component vendor's website'.

When users try to install it via the web, if they haven't got .NET framework
installed at all, then it asks them whether they want to open or save the
*.application file. Obviously this isn't good, so if this happens they don't
know what to do and I tell them to install the .NET framework version 2.0 and
then their machine will recognise the .application file and the app will
install, which it does.

But my question is, what if they have got version 1.0 or version 1.1 of the
..NET framework but not 2.0, will it know how to recognise the .application
file and then subsequently know that it needs to upgrade the .NET framework
to version 2.0 from the Microsoft website, or are .application files only
recognized with the advent of ClickOnce in v2.0?

 

[Lloyd Dupont]

click once being a .NET2 feature, I reckon they will still have the problem
if they only have .NET1

 

[RobinS]

If you add .Net 2.0 as a prerequisite, ClickOnce will check to see if it's
there before it installs it. It comes up and asks the user if it's okay to
install it, and if he says ok, it installs it, and then continues with the
rest of the installation.

The company I work for is getting ready to do this, but I think we're going
to publish the .Net 2.0 distributable on our own server rather than going
out to MSFT for it. That's the way I tested it, and it works the way I
describe above. I don't know if it works the same way getting it from
microsoft.com, so you'll probably want to test this.

The .Net 1.1/.Net 1.0 question is a non-issue. They are completely
different versions of the Framework, and thus irrelevant.

By the way, Brian Noyes put out a book about Click Once Deployment at the
end of last year. It is excellent. I had no idea how many variables there
were, and how many things to consider.

Robin S.