Yes that takes time. However turning it off only speeds up some (not loading online content), still it's slow. Compiling is awfully slow. If you just switch from code window to UI windo it's slow, if you want to check something in help (local) it's slow. Bottom line we were spoiled with the speed of foxpro for years (I gave my old Toshiba notebook to my wife and she is playing solitaire because I was about to throw it out of window due to frustration of waiting few lines of code to compile in VS2003. VS2005 is much better but still nowhere near foxpro). I have many friends here from other camps like coming from J2EE,Delphi,C++ etc and started to use .Net and all complain about its being slow. So it's not just me. Only those who started with .Net think waiting few seconds for a simple form to load is normal.
In general it's great so performance is not the most important issue.
Cetin

>Hi Cetin.
>So this is a thing with Visual Studio... its just slow in loading up and even in compiling ??... I dont think adding extra memory helps as there was one respndent here who has 2 gigs memoty and it still is slow.
>Anything to be gained from turning off a few parameter... I know for instance it looks at web and sometimes posts latest news..maybe this takes time ???
>Regards,
>Gerard
>
>
>
>
>>>Hi.
>>>I have been using Dot Net for a while now , and am wondering is there anything I can do to improve the speed. It is painstakingly slow, and thats just at the opening stage. I give comaprsions below for VFP, just to illustrate that I dont think it is anything to do with my PC
>>>(Using Stand alone Dell Inspiron 5150, and XP)
>>> VFP .Net
>>>Open up 5 secs. 15 seconds at least
>>>
>>>Open a website Just with 10 forms) 40-60 seconds
>>>Open a VFP Project (with 250 forms,reports,prg etc) 3-5 seconds
>>>
>>>It is extremely frustrating to do anything because of the slowness. Perhaps there are things I can turn off to improve the speed ??
>>>
>>>Any help appreciated.
>>>
>>>Gerard
>>
>>The only solution is to write a startup program for VFP that doesn't set _screen.visible = .t. for at least a minute and prefarably execute a do while loop to keep the CPU as busy as it can. That way frustration of VS slowness tend to turn into happiness. Another possible solution is add more and more RAM, a faster CPU maybe double or quad core, faster disks etc. VS then speeds but VFP still opens in a second:)
>>Cetin