Databases
StackOverflow2013
Postsdbo
POJavascript slow when Upgrading from .NET 2.0 to .NET 3.5
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POJavascript slow when Upgrading from .NET 2.0 to .NET 3.5
    primarykey
    data
    text
    <p>I would like to move our solution to .NET 3.5 and VS 2008. We are still on VS 2005 and 2.0. Some tools we would like to use are phasing out 2.0 and 2005 support, so I thought I'd test our solution after upgrading to 3.5.</p> <p>I converted the project in VS 2008. I fixed some compile errors that popped up, and then fixed up some javascript name change that occured involving the AjaxToolkit.</p> <p>Everything looked ok, but when I came to a particular page that is quite heavy with validators and javascript...the page slowed to a crawl on loading.</p> <p>I used the IE 7 javascript profiler, and saw some completely crazy numbers in the .NET javascript methods. I don't know what is going on. </p> <p>Has anyone run into the problem? Do I having something misconfigured.</p> <p>I'm including below 2 profiles. One captured when running in .NET 2.0. Another when running on .NET 3.5. At this point, I can't even consider 3.5, if I can not solve this problem.</p> <p>2.0 Profile</p> <p><a href="https://spreadsheets.google.com/spreadsheet/ccc?key=0AvxeS-OgIIkCdERSYVprOTRXZ2lkaFpqMkFFSkkxMXc&amp;hl=en_US&amp;authkey=CKKB5t0I" rel="nofollow">https://spreadsheets.google.com/spreadsheet/ccc?key=0AvxeS-OgIIkCdERSYVprOTRXZ2lkaFpqMkFFSkkxMXc&amp;hl=en_US&amp;authkey=CKKB5t0I</a></p> <p>3.5 Profile</p> <p><a href="https://spreadsheets.google.com/spreadsheet/ccc?key=0AvxeS-OgIIkCdGhHdVJRS0FWcEp4azN0SHkxNWF5eUE&amp;hl=en_US&amp;authkey=CNHyu6cG" rel="nofollow">https://spreadsheets.google.com/spreadsheet/ccc?key=0AvxeS-OgIIkCdGhHdVJRS0FWcEp4azN0SHkxNWF5eUE&amp;hl=en_US&amp;authkey=CNHyu6cG</a></p> <p>Please help...this is crazy.</p> <p>Thanks, Rich</p> <p>---Update</p> <p>Omar, I did as you suggested and set debug=false in the web.config file. This solved the problem. I put timing code in the page's javascript, and the javascript went from taking 17-18 seconds, back down to ~5 seconds. This is around the same time the page takes in .NET 2.0, so I'm satisfied with that (though, would love for IE to run this code faster).</p> <p>My only problem now is that, I obviously run the solution with debug=true during development. This is a serious hit to my productivity, as this page is used quite frequently. I'm guessing the new javascript debugging abilities introduced in VS 2008 are responsible for all this. When debug=true, I'm guessing a debug build of the .NET javascript libraries are used. </p> <p>Does anyone have any advice for work-around? Thanks - Rich</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USawhig
    1. USawhig
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POJavascript slow when Upgrading from .NET 2.0 to .NET 3.5
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThe problem is in the code. try removing parts of the javascript that a seems to be slow in the profiler. then see if there is any differences. if you isolate what functions are slow u can post them here and we will be glad to help you
      singulars
      1. POJavascript slow when Upgrading from .NET 2.0 to .NET 3.5
      1. USIbu
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload