Hi All

Sorry to CC you all but I guess I have been able to put in my thought as best I could regarding putting up the original post. Hope it is as Rod said constructive.

>Thaknks for your response. I can understand your concern if everything else runs quickly on the box, but the .NET app seemed sluggish. Again, the framework can take several seconds, but 30 or even 15 seconds on a hefty machine is quite a bit.

Thanks for your understanding comment, I seriously was not out to bad-mouth just for the sake of bad-mouthing, but I noticed something which was worth a mention, ie. the speed of loading on a high-end machine.

For arguments sake, forget I ever mentioned any seconds. But double-clicking and waiting for the first screens (splash, app backgound, whatever) is the waiting time for dll, frameworks, etc. to load, that was the point. Once a form / screen is shown the app is in control and any sluggishness, slowness is the fault of the app, this is not the discussion point.

>If the app takes roughly the same amount of time to load after closing the app and restarting, then you may want to ask what's going on under the hood when someone puts the keys in.

The second load is generally faster for all apps irrespective of the language used as due to Windows caching, so second and subsequent loads, IMO are not good for argument as it is more of the windows cache doing the good work.

>Out of curiosity...after you eventually got into the software, how did the rest of the app perform?

But once loaded it was fast, but then so was my VFP6 app, as was the processor.

>I did see your post to Rod. I'm not trying to be harsh (well, maybe a little bit), but it sounds like you agree you need to get some more details before drawing any general conclusion.

Like I had mentioned that I was on limited time and didn't want to waste it on peripheral exploration, but as it is said curiousity killed the cat and I was curious what a latest / future tech app look like.

As for the general conclusion see above "For arguments sake, ...", just imagine on a high-end machine the first double click loads in x seconds, what will happen on regular processors. We can't expect all the machine we are deploying to, to be the top-of-the-line stuff, nor can we say "else I will not deploy on your machine".

If I am not mistaken, the slower the processor the wait will grow exponentially (I mean, not propotionately) with each slower processor. I will repeat, this is a local app, local data, high-end machine, high-end HDD, no network traffic, no unnecessary apps loaded, no office tools or toolbars, in short it is as light as can be.