[RESOLVED] Firefox 3.5 -- NET framework assistant

[mbarton]

I like to be extremely cautious and just saw that if I download the new FF 3.5 that the "net framework assistant 1.0" will be disabled?

Anything to be concerned with? Any problem with my VB.NET that I have installed?

Thanks.

[JuggaloBrotha]

That's just a Firefox extension, you dont actually need it for anything .Net. But they'll eventually update it so it'll work in FF 3.5

[Nightwalker83]

Firebug 1.3.3 is also non compatible with FF 3.5! I should check if there is a new version of Firebug available.

Edit:

That's useful the browser automatically finds updates to any plug-ins you have installed.

[mbarton]

Thanks.

[JuggaloBrotha]

Firebug 1.3.3 is also non compatible with FF 3.5! I should check if there is a new version of Firebug available.

Edit:

That's useful the browser automatically finds updates to any plug-ins you have installed.

FireFox has done that since v2.0.0.x (I don't remember the exact version) but it's been been doing that for over a year.

[TheBigB]

Just a remark;
I've read that some people saw the .NET thing as a security flaw, because it's M$...
So no real loss really.

(You must love FF fanboys )

[JuggaloBrotha]

I happened to do an MS update today and I upgraded to FF 3.5 yesterday and noticed that MS has an update to their "net framework assistant 1.0"

Also FireBug works fine in FF 3.5, the installer didn't find any updates for it either, it just works.

[Nightwalker83]

Also FireBug works fine in FF 3.5, the installer didn't find any updates for it either, it just works.

You probably had version 1.4.0b4 or another later version! As I mentioned above the version I was using was 1.3.3.

[JuggaloBrotha]

That could be, I normally have FireBug disabled cause I never really need it, but this last week I've been using it a lot.

[kfcSmitty]

Just a remark;
I've read that some people saw the .NET thing as a security flaw, because it's M$...
So no real loss really.

(You must love FF fanboys )

The flaw was actually because MS actually included the addin secretly in an auto update and there was no way to remove it, only disable it....without registry edits.

[Lord Orwell]

The flaw was actually because MS actually included the addin secretly in an auto update and there was no way to remove it, only disable it....without registry edits.

there's a reason they did that. They were aware of the large user base using firefox that were having issues with their download center. Windows validation didn't work before but thanks to the addon that has been fixed. You still can't use windows update through it, but that's a smaller issue. Frankly the whole "run the validator on your computer and enter this code" had a huge flaw in it. You didn't actually have to run it on the system in question.

[leinad31]

http://www.annoyances.org/exec/show/article08-600