Noscript blocking Microsoft .NET Framework assistant?

[Morac]

I had removed the Microsoft .NET Framework Assistant addon from my machine and when I say removed, I mean completely removed (the registry entry and the DotNetAssistantExtension folder). I decided to restore it (since Windows Update was bugging me) and let the bootstrap.js file reinstall the real add-on, but for reasons I still can't understand the bootstrap.js file never installed the real add-on. I could have just installed the real add-on manually, but I wanted to figure out why it wasn't installing.

I finally tracked the issue down to Adblock Plus 1.1.1 and NoScript 1.9.9.11. If either (or both) is (are) enabled, then the bootstrap.js file is simply never executed. It won't even show up in the Javascript debugger which seems to indicate it is never read in at all. Once I disabled both Adblock and Noscript, the bootstrap.js code kicked off and installed the real Microsoft .NET Framework Assistant addon. I could then re-enable ADP and NoScript and everything was fine.

Any ideas why ADP and NoScript were preventing the bootstrap.js file from executing?

[Alan Baxter]

I don't know. Does this help explain it, Morac? From http://adblockplus.org/blog/the-return- ... -assistant

I was able to include a workaround in the current Adblock Plus development build that cures the problems (this is also going to be included in Adblock Plus 1.1.1, to be released very soon).

The technical details, if you are interested: the “bootstrap” extension defines a browser overlay in its chrome.manifest file. However, on that particular machine its chrome directory was empty, no UI files whatsoever (I guess they were there originally but were removed after installation of the “real” extension to make sure it is not installed again). So Firefox tries to apply an overlay and fails because the file doesn’t exist. This makes Firefox cranky enough that it doesn’t apply other outstanding overlays (is there a bug on that? need to check). The workaround was to override the overlay URL with a data: URL, that way the overlay exists and Firefox is happy.

Also, from NoScript changelog: v 1.9.8

x Work around for breakages caused by the .NET Framework Assistant,
http://adblockplus.org/blog/the-return- ... -assistant

Edit: Added a little more context from blog and added NoScript changelog.

[Tom T.]

I had removed the Microsoft .NET Framework Assistant addon from my machine and when I say removed, I mean completely removed (the registry entry and the DotNetAssistantExtension folder). I decided to restore it (since Windows Update was bugging me) ...

Any ideas why ADP and NoScript were preventing the bootstrap.js file from executing?

Not immediately -- I'm sure Giorgio will know -- but FWIW, being bugged by Windows Update does not require you to obey.

My OEM *does not support* XP's Service Pack 3, due to problems many users had with it, just as with SP1. If you call Support, they'll tell you not to install it.

MS originally issued a "SP3 Blocker" bit in response to this negative reaction -- middle of 2008, I think. It expired in a year, and since then, MS Update has been bugging me to install SP3, although you can bypass that and get to the rest of the updates, which I did.

Similarly, they always bugged me to install IE 7, which is easy to refuse (just uncheck it). And 8 (ditto).

This is with AutoUpdate set to "notify, but don't download or install", which gives you these better options to pick and choose.

Epilogue: This user finally said the heck with MS Update altogether, and now gets his own updates manually, with Firefox, without being bugged by MS. (Obviously, you have to be well-enough plugged in to the security world to hear if MS issues one of their rare out-of-cycle emergency patches.)

This removed the last possible reason ever to use IE, thank goodness.

But the "how" is a whole other story, perhaps to be posted if there is any sign of significant interest. Just wanted to put in two cents' worth: not to be pressured by MS into installing *anything* just because *they* want you to have it. We've had a lot of posts here from people having problems with .NET. Not that you should re-remove it if you don't want to, but since you did once...

Sorry to go a little off-topic, but it's pertinent to "I installed because MS pushed me into it". I'm sure your main question will be answered soon.

Cheers.

Edit: Typed and posted simultaneously with Alan Baxter's reply, and therefore without having seen his reply.

[Morac]

I don't know. Does this help explain it, Morac? From http://adblockplus.org/blog/the-return- ... -assistant

I was able to include a workaround in the current Adblock Plus development build that cures the problems (this is also going to be included in Adblock Plus 1.1.1, to be released very soon).

The technical details, if you are interested: the “bootstrap” extension defines a browser overlay in its chrome.manifest file. However, on that particular machine its chrome directory was empty, no UI files whatsoever (I guess they were there originally but were removed after installation of the “real” extension to make sure it is not installed again). So Firefox tries to apply an overlay and fails because the file doesn’t exist. This makes Firefox cranky enough that it doesn’t apply other outstanding overlays (is there a bug on that? need to check). The workaround was to override the overlay URL with a data: URL, that way the overlay exists and Firefox is happy.

Also, from NoScript changelog: v 1.9.8

x Work around for breakages caused by the .NET Framework Assistant,
http://adblockplus.org/blog/the-return- ... -assistant

Edit: Added a little more context from blog and added NoScript changelog.

This is likely the cause. I didn't realize NoScript implemented the same work around. For what it's worth, the chrome folder on my machine is not empty.

Also the reason I re-installed it, was to mainly keep Windows Update from complaining. I can simply disable it or uninstall it if I don't want to use it. I'm bringing this up for people who do want to use it, and haven't yet installed The 3.5 .NET framework.

[Tom T.]

...Also the reason I re-installed it, was to mainly keep Windows Update from complaining....

One last tip, for anyone reading: If you do use Windows Update, you can check "Don't show me this update again" (on most of them), and it will store that preference on your machine. At the next update, you'll see a prompt, "You've hidden important updates", and a box to check to show them, which you can ignore. FWIW. Cheers.