another post

http://www.chadgreen.com/post/2008/02/Visual-Studio-2008-Performance-Issues.aspx

it said that the hotfix should solve the problem, but it didn't.

at least for me...

thanks. i'll try that.

meanwhile, you can produce the bug yourself (if you got time):

make a clean install of dnn 4.8.2 (with clean database of course) , and check the store module (02.01.00) to install as well.

you don't even have to setup the module into new pages in the portal  - just make sure the module is installed and you see it in the module definitions page.

now , go to the vs2008 solution file (DotNetNuke_VS2008.sln) , open it with vs2008. (the default is for 2.0 framework). make a full solution build (Rebuild Solution)

and open the website in the browser (localhost/dotnetnuke_2).

you'll see that the response time for the first page, login page, admin pages etc, is fairly fast and good.

now.

go back to the solution- change only the website (\dotnetnuke_2) the framework to 3.5 (at the wesite properties of course) , make full rebuild solution. (the site itself is set not to be build - it's ok).

now when you browse the site - 1. -take a look how much time it take to see the home page at first,  2 - click on the login skin object and see how much time it takes to load the login control . enter your credentials and see how much time it takes to go back to home page , and then to other page (like admin pages or host pages)

-you'll see it's a lot of time - and the vbc.exe is exploding the cpu ( 50% all the time).

of course it's only for the first time - and after that it go smoothly. but for me the developer when i'm making every time a new build - the hole story restarts.

see it for yourself ,  and let me know...

thanks

zahi.

Have you tried right clicking the website, select properties, then click build, and for Before running startup page, select build page instead of build web site?

Just a thought.