It affects all applications. However it looks like this bug shows up only on machines that do NOT have a working ASP.NET installation (the ASP.NET setup creates the user "aspnet"). If the account is missing the CLR seems to query active directory or whatever to find the account; if the network is large this could take some time.
-----Original Message----- From: Blain Timberlake [mailto:[EMAIL PROTECTED]] Sent: Freitag, 24. Mai 2002 18:23 To: [EMAIL PROTECTED] Subject: Re: [DOTNET] Very very slow startup of dotneet applications Could someone explain this to me? Is this only concerning running ASP apps or not? =Blain -----Original Message----- From: dotnet discussion [mailto:[EMAIL PROTECTED]] On Behalf Of Richard Birkby Sent: Friday, May 24, 2002 12:04 PM To: [EMAIL PROTECTED] Subject: Re: [DOTNET] Very very slow startup of dotneet applications Nick Wienholt wrote: > > From microsoft.public.dotnet.framework.performance: > > In response to your questions: > 1. Yes, we have acknowledged that this is a know bug. > 2. We have not published a KB article on this issue. This is the primary reason I prefer to see bugs posted to this mailing list, rather than to the Microsoft bugs alias. It might very well be a known bug to Microsoft people, but it certainly isn't to customers. The KB lacks a long way behind reality and usually only gets updated with bugs when a new service pack is released. Anyone fancy starting a website listing all the bugs rather that waiting for Microsoft to publish them? www.dotnetbugs.com is available... Richard You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
