Expose .NET version to clients about clickonceforchrome

[GoogleCodeExporter]

Issue 4 has been merged into this issue.

Original comment by [email protected] on 8 Oct 2014 at 11:07

[GoogleCodeExporter]

Issue 5 has been merged into this issue.

Original comment by [email protected] on 8 Oct 2014 at 11:07

[GoogleCodeExporter]

Option A please, or both.  Option B leaves no way for the client to detect; 
this is a problem for us in supporting Firefox.

Original comment by [email protected] on 8 Oct 2014 at 1:43

[GoogleCodeExporter]

Do you have a hunch as to why MS would go with Option B in their FF extension?

It's definitely possible to modify the user agent headers in FF too.

Original comment by [email protected] on 8 Oct 2014 at 1:56

[GoogleCodeExporter]

I haven't a clue, frankly; it make little sense to me.  With the plugin 
installed, it should behave just like IE.  Shouldn't it?  I can't see why 
FF+plugin should behave fundamentally differently from IE.

The fact that they didn't do that suggests that I am missing something, but I 
can't think of what it might be (which I guess is why I'm missing it. :)

Original comment by [email protected] on 8 Oct 2014 at 7:54

[GoogleCodeExporter]

Alright, it's good that I waited with this.

I just realized that the UserAgent may be overwritten by other extensions 
causing a conflict with ClickOnce.

This may be why Microsoft decided to add a separate header which is not 
affected by other extensions.

Still haven't decided how to go about this.

Original comment by [email protected] on 9 Oct 2014 at 9:25