I'd also suggest trying to use your XmlTextReader in a console application. I hate to see the good name of my favorite .NET technology sullied unnecessarily. : )
Chris Sells http://www.sellsbrothers.com/ > -----Original Message----- > From: dotnet discussion [mailto:[EMAIL PROTECTED]] On Behalf Of > Isaac Hwak Han > Sent: Tuesday, May 28, 2002 3:48 PM > To: [EMAIL PROTECTED] > Subject: Re: [DOTNET] Windows Application painfully sluggish > > I've experienced the similar performance degeneration with > XmlTextReader. The culprit was remote DTD processing. Try to set > XmlTextReader.XmlResolver to null, if you don't need external entity > replacement or DTD syntax validation. If you do need these feature try > to provide custom XmlResolver. > > -- > Isaac Hwak Han > mailto:[EMAIL PROTECTED] > http://www.technonia.com > > > William Oliveri wrote: > > >So the performance hit is when the user opens the app/form for the first > >time? > > > >What factors altered would produce another performance hit? > >ReComplile and deploy? > > > >In my example the biggest visible drag was on the XMLReader(). I tried > >adding records to the xml file and it still ran fast so what is it doing > >the first time that slows it down? JIT? > > > >thanks, > > > > > > 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.
