> Microsoft when they rolled out .Net 3.5 SP1. Originally they installed > it without giving the user the ability to remove it. Caused a bit of a > stir when it happened, and several people documented ways around > removing it. After all the issues, I believe Microsoft released an > update that made removal easier. > > I think it was an add-in called Microsoft Framework Assistant, or > something to that effect. A quick google search for "firefox disable > ClickOnce" comes up with some information.
Jon, I'm impressed how much you know (or both to google around) regarding ClickOnce. Thanks for the info and effort. The one source of confusion I'm feeling now is - ClickOnce isn't a browser specific thing. The sites that come up from "firefox disable clickonce" are of course browser specific. There must be some way to disable it globally too, right? All the ways to disable clickonce that I have found, are either browser specific, or under control of the application developer, not the client receiving the application. I guess it's not such a terrible thing. Usually when you're at one of these sites, you're there because you want to download & install some app. But it feels a little more comfortable to first be prompted to save or download some installer. Plus, I'm and IT person. I normally save all my downloaded installers to a network share, incase I want to run them multiple times, or incase I can't find it again later. Not a huge deal, but my preference is clear. _______________________________________________ Discuss mailing list Discuss@lopsa.org http://lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
