Are you just dealing with initial load time? If so, you may or may not be
able to alleviate the situation and should attempt to run the JITTer when
you deploy through the precompile.axd file. More and more of the code is
being compiled when you compile a web project.
Could there be a bug in 3.5 Extensions? Certainly. It is still in beta. I
would log your findings, along with code, and a step by step description of
what you did. The place to log is one Connect. You can also get to the team
via the forums on
www.asp.net.
In addition, if you want someone to figure out what is wrong with your code,
or if it is a bug, you should post code here, as well. The more info, the
easier it is for other people to help you.
--
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA
*************************************************
| Think outside the box!
|
*************************************************
<ms******@gmail.comwrote in message
news:f3**********************************@v3g2000h sc.googlegroups.com...
>I have been experimenting with VWD Express Extension 3.5 and noticed
that quite often it takes up to 1..2 min to load external js or css
files. This occurs often after rebuilding the site. The problem seems
to be linked to retrieving small ( approx 200 bytes) graphics files,
as evidenced in Firefox' Firebug tracing graphics.
Currently, the script manager is included in the master page, the
external js file in the header section, and the page theme referenced
in the config file. Is this the right approach or does Ext 3.5 have
some bugs? With ASP.NET 2.0 load-up time was satisfactory. I tried
deleting the external js file to no avail. How can I speed up loading
time?
TIA for sharing any thoughts.
