Why does .NET 1.1 Framework depend on (Winlogon) Windows Standard Logon?

  • Thread starter Thread starter Kits Rege
  • Start date Start date
K

Kits Rege

Can someone please tell me in what way .NET 1.1 framework depends on
Winlogon?
I used .NET Framework 1 earlier with minlogon and it showed no
dependency on Winlogon, however 1.1 shows direct dependency on
Winlogon. Why does 1.1 need Winlogon? I built the image (turning off
auto resolve dependency) using 1.1 and minlogon and it works fine for
the time being, but I read somewhere that it may lead to gacutil
errors. In what case(s) can it cause errors?? Can someone shed some
light on this issue?
Thanks in advance,
Kits.
 
KM,
The topic deals with workaround and how to use minlogon/customize
winlogon. I would like to know why .NET 1.1 depends on Winlogon in the
first place...what kind of interaction takes place between
Winlogon/data it collects and .NET 1.1 or something like that.
Would be nice if someone could tell me that.
 
Kits,

I thought Andy's input there was clear: ".Net Framework requires the security features provided by Winlogon. Using
Minlogon w/ Netfx will result in gacutil errors among other things."

If you search NG archive you will find the mention of errors messages that appear in FBA log from regasm and gacutil utilities of
..Net on Minlogon image.

Perhaps more information about those dependencies you can get in .Net oriented newsgroups.
 
Back
Top