http://weblogs.asp.net/scottgu/archive/2008/09/28/jquery-and-microsoft.aspx

Was very happy to read this since internaly here we have allready chosen to use this javascript framework for all our development. We hardly ever use the the asp.net ajax functionaliteies and cleintside library of DNN because of the ease of development of jQuery scripts. Now that Microsoft has recognized this as well it will be made even easier.

There will be serverside helpers for asp.net MVC, intellisense and online help and to top it of PPS service support calls regarding to jQuery.

Will this impact DNN as well and we will get rid of the clientside library and semi Ajax as there is now and adopt jQuery as well?

Armand Datema

Get my new skin ( lots of design variations [18 headers, 30 titlebars, 30 breadcrumbs, 3 footers ], 50+ typography containers , 50+ page templates and an online theme builder for unlimited skin variations) Aura>

For all your skin conversions

2DNN

Follow me on Twitter

This is great news and I'm encouraged that the DNN team is having a look at this. 

Jquery is an aggressive library however and doesn't play well with itself even.  Two instances of the same library will cause all sorts of issues.  Official support  would have to be centrally managed so that skin designers, module developers and the core aren't tripping over themselves.  I would love to see ideas around  an intelligent central system for all page support files (CSS and JS).

Google and I think also AOL or Yahoo, I'm not sure, host the jQuery library on their servers, in a compressed format too possibly.

Therefore, put a conditional in the module, if the server hosting can be reached, use that and tell the developer, else use a local copy and inform the developer et al. to download a more current local copy.

I'm not a programmer, but I should think this all only takes a few lines of code to implement.

DNN and module developers could easily do this...the best thing would be for DNN 5 to default to this method for jQuery implementation so that module developers don't have to worry about this, they could just know that jQuery will somehow be there and available for their modules.

HTH Tom