Net framework???

Tri-Pacer wrote:
> Recently I have found several applications that install Microsoft Net
> Framework as part of the initial setup with NO option to not install it. I
> found myself with an unwelcome log on screen which required me to select a
> user.

This is a FAQ. Refer to:

http://support.microsoft.com/?kbid=827072

> And by the way just what is this Net Framework, and why must it install
> itself?

It supports other Windows programs that were created using .NET technologies
(particulars of which probably wouldn't interest non-programmers much). If
you have any programs that use it, it is absolutely required for those
programs to even be able to start.

That said, .NET framework also appears on Windows update as an optional
component, and thus often gets installed by users who don't yet have any
actual need for it. No harm done (they probably will need it sooner or
later), aside from the welcome screen issue.

--
Chris Priede
 >> Stay informed about: Net framework??? 

Chris Priede wrote:
> Tri-Pacer wrote:
>
>>Recently I have found several applications that install Microsoft Net
>>Framework as part of the initial setup with NO option to not install it. I
>>found myself with an unwelcome log on screen which required me to select a
>>user.
>
>
> This is a FAQ. Refer to:
>
> http://support.microsoft.com/?kbid=827072
>
>
>>And by the way just what is this Net Framework, and why must it install
>>itself?
>
>
> It supports other Windows programs that were created using .NET technologies
> (particulars of which probably wouldn't interest non-programmers much). If
> you have any programs that use it, it is absolutely required for those
> programs to even be able to start.
>
> That said, .NET framework also appears on Windows update as an optional
> component, and thus often gets installed by users who don't yet have any
> actual need for it. No harm done (they probably will need it sooner or
> later), aside from the welcome screen issue.
>
It's about time this option caught up with the 1980's

Multiple dll's? All with the same name? Slightly tweaked?

It sounds like the route map to conflicts for sure to me.

Let's invent a new paradigm: an application will first check it's root
install for a dll. If it finds it = great! If it doesn't = it will
take a global dll of the same name. Any global dll of the same name
will do (or won't if you know what I mean)

When a dll is updated it will update first the local dll (if it finds
it) otherwise it will update the global dll of the same name. If indeed
it decides to run through a local/global check first.
 >> Stay informed about: Net framework??? 

to solve the logon issue, install the .net 1.1 update from windows update.
now that you've got it on your machine, keep it updated.

note that the new .net 2.0 is NOT needed to update .net 1
they are two different beasts, and if you install 2.0 you'll
still have 1.1 on the machine. so don't "take" version 2 until
you actually have an app that needs it.
 >> Stay informed about: Net framework???