ClickOnce and not IE

[Chuck P]

Does ClickOnce work with browsers other than IE now (didn't in
January).
If not what's the best workaround?
thanks,

 

[Jeffrey Tan[MSFT]]

Hi Chuck ,

Thanks for your post.

There is no special requirement regarding the client browser in ClickOnce.
Once the browser can support Windows URL handler, it will support
ClickOnce. This is because the .Net Framework associate MIME type with a
shim dll to do the actual ClickOnce URL activation.

Our MSDN developer gives an explanation in his blog:
http://blogs.msdn.com/rfustino/archive/2005/03/18/398851.aspx

"1) Using no-touch deployment in vs 2003, it was required to have
Internet Explorer 6.0 or higher on the client machine to make sure all the
hand shakes were done correctly. Is this still a requirement or is the only
requirement now the 2.0 framework? "

Hope this helps!

Best regards,
Jeffrey Tan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

 

[Chuck P]

This really differs from what I've been hearing:

http://channel9.msdn.com/ShowPost.aspx?PostID=138273
http://channel9.msdn.com/ShowPost.aspx?PostID=138879

I tried doing an app last month with firefox and it failed.
I wonder if there was some double talk going on?

That is "You only need a web browser that supports the standard
Windows URL handlers.", maybe only IE meets this requirement?

 

[Jeffrey Tan[MSFT]]

Hi Chuck ,

Thanks for your feedback.

Oh, yes, I have found some MSFT has reported this as a ClickOnce bug
internally. The bug reporting comes from the blog link below:
http://www.hanselman.com/blog/CommentView.aspx?guid=7ce42ccd-e531-4d43-a93f-
73483c0afd3d

So ClickOnce will not work with FireFox. Our product team may fix this
issue in future release.

Thanks

Best regards,
Jeffrey Tan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

 

[Chuck P]

Thanks, that was good link.
It also contained one with a partial work around:
http://blogs.msdn.com/saurabh/archive/2006/03/02/541988.aspx
Haven't tried it yet though.