Archive of #ASP.NET Posts

A quick note about the recently released Advanced ASP.NET Ajax Server Controls book...

This post describes a prototype for an Ajax templating solution, combined with an Ajax-friendly server-side solution that hints at what is coming down the road in ASP.NET Ajax.

This post describes using tag mapping and a derived form control to fix URL rewriting in asp.net pages.

This post presents a few basic Ajax features (similar to partial rendering and behaviors in terms of concepts) running on top of the ASP.NET MVC framework... some early ideas, experimentation and app-building results.

A little known attribute, configSource, enables some level of configuration factoring and splitting for the ever-growing web.config...

The first revision to the UpdateControls ASP.NET AJAX server controls package including bug fixes for reported bugs on UpdateHistory and AnimatedUpdatePanel, as well as the addition of another control, UpdateAction.

The big news for the day: ASP.NET AJAX 1.0 is finally out and available...

This post introduces a prototype of a server control for implementing back button and bookmarkability in pages using UpdatePanel and partial rendering.

A somewhat 'undocumented' Atlas technique for loading script sooner than window.onload and improving perceived page performance.

The June Atlas CTP fixes some bugs, and adds support for dynamic UpdatePanels opening up scenarios such as UpdatePanels within data-bound controls or WebParts, and more importantly, custom control scenarios. This post demonstrates the control development usage.

My own wish list for what I'd love to see in the browser/scripting/Ajax space...

A brief writeup on one of the driving forces behind the Atlas UI framework: enabling structural markup and design... now illustrated via an example.

The March CTP of Atlas is now online... along with the ability to use it live on your sites... and participate in a mashup contest.

The third and final part of this series covers the implementation of the InPlaceEditExtender server control that allows ASP.NET page developers to easily incorporate in-place editing functionality without having to delve into client-side programming.

Another quick tour of the enhancements to ScriptManager and the partial rendering/async post-back model added in the Atlas M1 (January) refresh build that further enable the server-control based AJAX model.

As a followup to my original in-place editing Atlas sample, this post takes a deeper look at the sample by providing a step-by-step approach to writing script behaviors that work cross-browser, and some insight into the topic of component authoring atlas-style.

Atlas samples from a recent conference...

This post demonstrates a custom Atlas script component and associated extender control to enable in-place editing (i.e., Labels that morph into TextBoxes upon focus in an AJAXish manner). Source code included...

This post describes the role and functionality of the Atlas ScriptManager control, which is in some sense the brains of an Atlas page. It also points out some of the changes from prior releases where functionality has been consolidated into this control.

This post outlines the focus of the December '05 release of Atlas CTP bits, and walks through the key integration points with ASP.NET server controls to enable incremental enrichment of ASP.NET server-centric applications with scenarios such as incremental page refreshes, auto-complete, draggable panels etc.

A brief introduction to one of the lesser known Whidbey features for control developers: Single Instance Templates, and some context around the problems it solves: specifically the need to use FindControl to access controls inside templates.

A discussion of client and server development models for rich Web application development using Atlas, and a quick overview of the framework and runtime modes of the Atlas script library.

A sample of XML script introduced in atlas, and general thoughts and opinions (go ahead and share your own thoughts...)

This post presents a high level overview of whats in Atlas today, along with the architecture diagram from yesterday's PDC session.

Finally, Atlas has been publicly demoed... and there is more to come.

Opinions on documentation, API naming, and a quiz for readers...

A summary for data source control series, a screenshot, and finally (most importantly) the source code for the data source, the designer, the sample, and the async data source framework.

In part 5, the final installment of this series, I will cover adding design-time functionality and enabling design-time experiences associated with a data source control, and its associated control designer.

Part 4 of the series describes how to incorporate caching into data access logic, enabling further performance gains, and improvements in end-user experience.

Part 3 of the series describes how to perform and encapsulate asynchronous data access, while presenting a reusable asynchronous data-access framework that builds upon what is available in Whidbey.

The next installment in the data source control series shows how you can add support for declarative master/detail scenarios...

The first in a series of posts on authoring data source controls...

The word is out on Atlas, a project within our team to build in AJAX support ... in a big way.

Overview of a technique for scoping the lifetime of a URL to a fixed time period.

Some reflections on the past week, and some thoughts about future posts on this blog...

I'll be in Orlando next week, at TechEd 2005. Looking forward to meeting, and talking to folks...

A few notes about view state display in the ASP.NET Development Helper tool, and information about the beta 2 sparse array optimization technique.

My personal thoughts and opinions, along with a bit of history, on the Whidbey DataSource control model, as well as the idea of making programming more declarative.

A listing of blogs from various folks on the team...

Anecdote on client-script related compatibility issues with ASP.NET v2.0 and some interesting personal observations...

Upates on whats going on (IIS7, ASP.NET and future stuff, etc.)

The first article on IIS7 is now online... check out whats coming down the road...

This post explains a new caching feature introduced in ASP.NET Whidbey that can be used by controls needing to display dynamic and different content on each request, even if the containing page is being output-cached. While illustrating this mechanism, I have also provided a helper class that creates the equivalent of the already established Render semantics within a Control to simplify usage of the underlying infrastructure.

A quick introduction to concepts and terminology about the connections feature within the ASP.NET Whidbey Web Parts Framework, followed by a discussion of building support for cross-page connections using the extensibility mechanisms, along with associated code to download and play with...

We found a potential Denial of Service (DOS) attack using Web resources, and fixed it...

Theres a potential XSS attack to watch for when allowing entry of Color values.

Thoughts on non-visual controls in ASP.NET Whidbey such as SqlDataSource, and the new NonVisualControl metadata attribute.

Neat little trick for zooming browser content for presentations...

To bind or not to bind to fields?

A discussion (and some early thoughts) on enabling greater control over server-generated markup in ASP.NET...

Automatic metadata-driven schema generation for server control intellisense in Whidbey

A bit about the new control state feature and view state serializer improvements in Whidbey, that should help go a long ways into minimizing view state on aspx pages.

A discussion about the "Callbacks" feature in ASP.NET Whidbey, and a sample control and slide deck to go along with it.

Some thoughts on whether or not to use postbacks in authoring an ASP.NET Web application, what are some of the side-effects, and what we're doing in Whidbey to improve the postback model...

Blogging again :-)

Blogs dedicated to server controls...

A bit about the Mort, Elvis and Einstein personas, and how they apply in the realm of server controls in ASP.NET Whidbey.

Web Resources just work as you'd want to at design-time. Automatically!

A bit about WebResourceAttribute in ASP.NET Whidbey and the related Web Resources feature.

Rant on couple of W3C guidelines (Accessibility and XHTML 1.1) not 'inter-operating'...