Mr Mathwani,
Denis and Cetin are partially correct. You probably should be flamed for this topic. I'm not going to do it. But I am going to point out where your logic is flawed.

Your topic to begin with... .NET Framework apps are slow. So is this an indictment of all .NET framework applications. If you recall around 6+ months ago I created a small .net framework/winforms application, using the VFP OLEDB provider we had a number of people here run the app, and report back the load times on a number of types of machines. The results were varied greatly. The general concensus was that after it's initial load you could unload the application, reload it, and it would load dramatically faster. But overall, I think the results were fine.

As to this specific application... What was the application doing while it loads. Was it connecting to a database, was this application connecting to that database via a lan, was the network it was running on overloaded, was the machine running other software, was it creating local stores of data, was it querying a number of tables, was it doing calculations, etc....

There are a number of reasons an application is slow. So do you have any answers to these questions ?

This is where I generally have a problem with posts like this. These types of threads end up as he-said, she-said types of threads. There is generally no real scientific discussion of these topics.

Sometimes these topics do turn constructive like the VFPConversion thread and the discussion of strong vs dynamically typed languages.
languages.

So food for though. What do you hope to gain by posting topics like this? Does this type of topic add value to the UT? Or do you just like stirring the pot ?

Thanks

Rodman