>>Hello all,
>>
>>First of all, if this gets posted twice I appologize. I clicked send and got a blank form back so it doesn't appear to have been posted. I am retyping the entire question again.
>>
>>I am reviewing some code that I did not write and wondering if you can help me understand why this might have been done this way. Why not just call the method directly. This application is a WPF application.
>>
>>

>>public App()
>>{
>>      fSplashScreen = new SplashScreen("/Resources/Splash.png");
>>      fSplashScreen.Show(false);
>>      GISGlobals.GISCommunicator = GISCommunicator.Current;
>>
>>      // Why might this be done this way.
>>      InitStartUpXmlSerializiersExecute lInitSerializers = new InitStartUpXmlSerializiersExecute(InitStartUpXmlSerializiers);
>>      lInitSerializers.Invoke();
>>}
>>
>>protected void InitStartUpXmlSerializiers()
>>{
>>      Communicator.GetXmlSerializer(typeof(DBSearchResultList));
>>      Communicator.GetXmlSerializer(typeof(DBSiteList));
>>      Communicator.GetXmlSerializer(typeof(DBRanges));
>>      // Times 17 of these Serializers
>>}
>>

>>
>>This application takes about 8-13 seconds just to show a login form. This portion is taking about 30% of that time. The question though is why would they have not just called this method directly?
>
>What does 'InitStartUpXmlSerializiersExecute' look like ?

'protected delegate void InitStartUpXmlSerializiersExecute();