possible .net myth

[vinifera]

been doing various things lately

now I'm strictly talking about win 7

 

and even by default .net 3 and 2 are "system integrated"

user can actually yank them out

 

now v3 is already out of my system and I have no sideeffects whatsoever

except when running stupid apps that are made in VS.NET

 

but what is more interesting is that WPF which is "core" component of .net 3

"needs" to be in win7 just like in vista, because DWM (because milcore.dll)

uses it, and OS also uses milcore.dll for rendering UI (DWM) and hangling images themself (PNG, BMP)

 

what is funny, is that I have no dn3 file nor milcore on my system, yet all these things work flawlesly (lol ?)

 

then again since .net3 is PENDING on CLR 2 (.net 2), it cannot even exist/run without it

which is also system integrated

 

in next few days I intend to yank out .net 2 completely

and will have no .net files on system, can't wait to see what will work and what not

Edited August 22, 2015 by vinifera

[dencorso]

how exactly are you removing them?

Are you using some modified version of Aaron Stebner's removal too? 

[vinifera]

v3 was removed with 7lite when I did iso few yrs ago

but v2 is always blocked by such tools

 

so I'll do it manually as I have full list of files and paths that are linked including registry

(in vm ofc) but it should be fine in my opinion

 

only mscore.dll needs to stay in sys32 as explorer has sometime calls to it

 

if that experiment works (yet to be seen)

it might prove MS is full of s*** with integrating that thing into win7, maybe even vista

 

I know that during vista alpha (longhorn) it was needed, as .net was very integrated then into system

parts of explorer and shell used it including all graphic crap, but since reset to vista they dumped

all that approach, avalon (WPF) was no more "a must", it was just a trick for masses

Edited August 22, 2015 by vinifera