Does .Net really require Winlogon?

  • Thread starter Thread starter Guest
  • Start date Start date
The part that seems odd is that .Net inherently requires user accounts and
lsass.
I can think of lots of little C# apps that you could write without security
being required (or so I believed).

BTW, when I was trying to get the office handwriting components to load,
this is probably the root problem. I remember that one of the components had
a registry setting "Assemblies" - possibly related?

thanks,

John
 
John,
The part that seems odd is that .Net inherently requires user accounts and lsass.
Click to expand...

Some features of .Net do require those components. Just look at the .Net APIs and you will notice some user account specific
methods.
It is also known that .Net can leverage the traditional Windows security subsystem via the WindowsPrincipal object, allowing the
easy mapping of roles to existing Windows user accounts and groups.
I can think of lots of little C# apps that you could write without security
being required (or so I believed).
Click to expand...

In general, you are absolutely right. The .Net Framework should be componentized better for an embedded application.
What I don't really like about .Net on XPe is that it is really just one huge component now. For an embedded system it is sometimes
not required to have all the features of .Net (unles syou want a system that runs *any* .Net app).

However, XPe is based on XP Pro binaries. So, I guess, there is no *easy* way for XPe Product Team to fix such dependency issues
without affecting XP Pro world.
BTW, when I was trying to get the office handwriting components to load,
this is probably the root problem. I remember that one of the components had
a registry setting "Assemblies" - possibly related?
Click to expand...

Hmm.. IIRC, wasn't your problem that time related to ctfmon? What's the connection to .Net?
 
All right, I'll take back odd and resubmit that it is disappointing... :-)

I don't know if ctfmon has any relation to .Net for certain but it is
loading msctf.dll which in turn fails to load imm32.dll. The registry
entries under HKEY_CURRENT_USER\Software\Microsoft\CTF has a bunch of
Assemblies keys. Perhaps just a coincidence in naming and not really .Net?

thanks KM,

John
 
John,

This must be a coincidence in naming as the feature should work without .Net installed.
However, the Assemblies key under CTF is not documented so I can't be positive.
 
OK, so Konstantin has addressed the primary concerns you have here. Let me
write up a short blog article on this subject. It will not provide any
technical details but rather provide some history here and insight and
personal comments, these are not directed at you directly but for archival
purposes since we can refer to this article going forward since it's a
popular topic.

The article will provide what i think may be a happy medium between me being
laughed out of the CLR team's building and customers that are more
satisified than they are now with NetFX+Winlogon.<grin>

Thanks
Andy


This posting is provided "AS IS" with no warranties, and confers no rights.
 
Back
Top