Thanks, Mike! Unfortunately, that's not the issue. I'm sending the user to
the publish.htm page. By using FF 2.0, it will provide both the "Lauch" link
which directs the user to the .application file and the "Setup" button which
directs the user to the setup.exe file. Since the system has all
dependencies installed (it works on IE), clicking the Launch link should
work fine, but the all I get is the exact same behavior seen in VS 2K5's
ClickOnce: FF doesn't recognize the extension, prompts me to either Save or
Cancel (the download), I click Save and then Run. It will start the
installation but will eventually fail.
Interestinly, I've tested this scenario in Windows 2000, XP and Vista
machines and it only worked on XP machines. I wonder if this is and issue
with Windows rather than with FF. All of them were running the same FF
version and administrator users.
"Mike {0A6FF490-CF84-4d78-BD85-FF011A0C310C}" <
[email protected]>
wrote in message
Are you trying to send the user's directly to the *.application file
via a link? Or are you sending them to the publish.htm file that got
generated during the Click-Once publish? FF 2.0 should work fine with
the publish.htm file. That file has logic in it to test what browser
you're using and provides a slightly different UI (that works) with
FireFox. BUT, if you're sending the user a link directly to the
*.application file, you're going to have exactly the problem you
describe with FireFox.
Note that a link directly to the *.application file *is* required if
your application expects to receive parameters on the query string and
in that case FireFox will not work. But, if your application does NOT
receive any query string parameters from the browser, then just send
the users to the publish.htm file.
Does that help?