Net framework???

  • Thread starter Thread starter Tri-Pacer
  • Start date Start date
T

Tri-Pacer

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.

I have XP Pro and was able to defeat the log on screen. However I have
forgotten how I did it!!!

My wife has XP Home on her computer and we ran into the same problem. I
cannot for the life of me remember how I defeated the log on screen.

Any help would be greatly appreciated.

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

Thanks

Paul Anton
 
Remember DLL hell? This was caused when different installed applications are
tied to a particular version of a DLL file. Well, the dot net framework is
Microsoft's answer to this. Thanks to dot net framework we no longer have to
suffer with DLL hell. Instead we now have Assembly (or GAC) hell. Same
problem - different name.
 
Tri-Pacer said:
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.
Click to expand...

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?
Click to expand...

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 said:
This is a FAQ. Refer to:

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




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.
Click to expand...
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.
 
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.
 
Back
Top