97

Closed

AJAX support in WCSF

description

Guys,
 
Has any thought been given to how ASP.Net AJAX will be incorporated to applications created using the Web Client Software factory?
 
Will there be any specific Guidance in this area?
 
Or is ASP.Net AJAX something which you expect not to have any impact on the Guidance provided through WCSF?
 
Thanks,
 
Stephen ...
Closed Oct 11, 2007 at 9:11 PM by blainew
These are in the October bundles in the Releases folders.

comments

PauloMorgado wrote Jan 11, 2007 at 9:14 AM

Just have in maind that AJAX isn't just a set of nice controls that call web services to retrieve data.One of the requirements for using AJAX is not having post backs. So, we go from a flow between pages to a flow of events in the same page.

headdeball wrote Jan 16, 2007 at 12:34 AM

"One of the requirements for using AJAX is not having post backs". Is that an actual requirement or is it just 'extreme AJAX'? Is it possible to have a certain portion of your website following flow and the WCSF way of doing things whilst a given page uses lots of AJAX stuff?

blainew wrote Jan 17, 2007 at 11:57 PM

We will consider for R2. Currently it is one of the higher priority features for R2. Your vote counts:).

donhiatt wrote Jan 24, 2007 at 3:42 PM

Great web applications will have nice flow between pages that have a great event model on the same page.

simonince wrote Jan 30, 2007 at 3:26 PM

I agree that AJAX can make sites work really well, but be aware there are also a lot of sites that can only make limited use of AJAX (due to accessibility requirements).

How about a pattern that uses AJAX when appropriate, but degrades gracefully to standard ASP.NET post-backs?

avadul wrote Feb 11, 2007 at 12:57 PM

I am trying to add this fuctionality by changing the Guidance automation package.Trying to give the developer an option when creating any View Presenter page (Standalone or as part of a Biz module) to add AJAX fuctionality - via checkbox and browse for box.

If either are checked, the AJAX dll is copied in to the project ref (if not alreadly there) and Script Manager is added on the ASPX page.http://www.vadul.com/weblog/2007/02/ajaxing-web-client-software-factory-web.html

avadul wrote Feb 20, 2007 at 12:15 AM

This is going to be a mix and match - we can use page flow where needed and AJAX where its not - does not have to be all or nothing here.

gblock wrote May 14, 2007 at 8:47 PM

Thanks for voting guys. As Blaine mentioned, we are looking at AJAX for R2. There are a couple of different secenarios we will be considering.
  1. Supporting partial page updates, i.e. controls refresh data, etc without having to do a full refresh of the page. This has two parts.a. Using UpdatePanel to automagically wire up the partial postback.b. Using ASP.NET AJAX client script libraries to retrieve data from the server and you do all the work yourself.2. Exposing WCSF functionality on the client. This will entail exposing proxy classes in javascript that project some of the MVP functionality and access to services, etc similar to the way ASP.NET AJAX exposes profile, authorization, etc.
Let us know which scenarios matter most to you!

gblock wrote May 14, 2007 at 8:49 PM

Regarding Headdeball and Paulo's comments, You can still mix and match AJAX functionality with non-AJAX functionality. It is not an all or nothing game. You can do this both within a site or even within a page. Meaning you have a page that has AJAX functionality but ultimately you do a final submit which does a full postback.