.Net 1.1 and MinLogon

[steve]

I need to include the .Net Framework 1.1 in my image as well as the MinLogon
component. Although, the .Net Framework 1.1 has a dependency on WinLogon
(standard) which also brings in Session Manager which conflicts with
MinLogon. Is there a way to just include the .Net Framework 1.1 with out
including the WinLogon (standard) component? Thanks.

 

[KM]

steve,

You can read this:
http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&threadm=887556E9-DA49-45F
9-B1B6-06E4E5AFCD37%40microsoft.com&rnum=1&prev=/groups%3Fq%3D.Net%2B1.1%2Bs
ecurity%2BWinlogon%2Bgroup:microsoft.public.windowsxp.embedded.*%26hl%3Den%2
6lr%3D%26ie%3DUTF-8%26group%3Dmicrosoft.public.windowsxp.embedded.*%26selm%3
D887556E9-DA49-45F9-B1B6-06E4E5AFCD37%2540microsoft.com%26rnum%3D1

Here is a quote from Andy Allred [MS]: ".Net Framework requires the security
features provided by Winlogon. Using
Minlogon w/ Netfx will result in gacutil errors among other things.".

 

[Harsh Shah [MS]]

You can add .NET Framework in TD configuration and then do the dependency
check. Once the dependency check is over, you should get a few errors and
hence tasks. One of the task should be to choose Session Manger. If you
double click on that you should get two options - WinLogOn and MinLogon.
Choose MinLogon and run the dependency check again. Do you get to choose
Session Manger after dep check?

 

[Harsh Shah [MS]]

Disregard my earlier message. KM is right. Using MinLogon with .NET
framework will result in REGASM and GACUTIL errors. You must use Winlogon
when you are using .NET framework. We do not recommend and/or support Netfx
w/ MinLogon.

Thanks!
- Harsh.

 

[steve]

Thanks to you both.
I'll probably just stick with .Net 1.1 and WinLogon