Atlas July CTP and the Latest Atlas Control Toolkit

The Atlas team recently shipped a new Atlas July CTP that contains a number of bug-fixes.  You can download it off of the web-site (like all Atlas CTPs it supports a go-live license).

The Atlas Control Toolkit team – which is building up a great library of useful Atlas-enabled controls on top of the core Atlas runtime – also recently posted a binary refresh of the Atlas Control Toolkit as well.  You can read all about it in Shawn’s announcement post of it, and download it for free here. 

What is really cool about this new Atlas Control Toolkit update is that it includes Atlas controls contributed by non-Microsoft developers.  As I mentioned in an earlier post, we are building the Atlas Control Toolkit collaboratively with the broader .NET developer community as a free shared source project on the new CodePlex site.  Our goal is to have ~50 great free Atlas controls that you can download and use as part of it by the end of the year.

There are currently 21 cool Atlas-enabled controls included within the Atlas Control Toolkit download (with many more coming soon).  You can run online demos of them from the sample site here.  Below is a screen-shot of the Atlas Control Toolkit samples that you can try out from this samples site online:

Some of my favorite new controls are the ones built by the non-Microsoft contributors to the project.  These include the new FilteredTextBox developed by Christian Wenz that you can see in the screen-shot above.  Paul Glavich built the cool new PasswordStrengthExtender control which provides real-time feedback on password complexity:

Paul posted about his experiences building the above control on his blog here.  Pierre LaGarde then built the cool new PagingBulletedList, NumericUpDown, and RatingControl:

All of the controls in the toolkit are free, and all ship with full source code (including a license that allows you to take the source, modify it, and do whatever you want with it).

How to Get Started with the Atlas Control Toolkit

To learn more about the Atlas Control Toolkit and how to get started with it, visit the Atlas Control Toolkit site here.  Make sure to also then check-out the Atlas video series that Joe Stagner is working on:

Note: The CascadingDropDown control video above was just posted yesterday and shows how to use this control (which ships in the Atlas Control Toolkit) to build Ajax enabled drop-downlists that depend on each other’s values and don’t require a full server round-trip to update when changed.

Hope this helps,



  • Hi, I just want to say, nice work. Atlas is great and the way you guys roll out the a new version almost every month is great also.
    I wanted to add that you should show your appreciation to non-Microsoft contributors by giving premium MSDN subscription or Professional VS 2005, so that more people are inclined to work on these tools and share the code.

    just my 2 cents.

  • Excellent. I still hope to see a masked textbox in the control kit... :)

  • nice work scott,
    I intend to use Atlas controls in my new web project which is a great community site.

  • Hi Scott,

    You have some information on some control that has MASKEDIT.


    Ramon Durães

  • Scott, where can we email you to get a copy of the CSS and image files from your Atlas To-Do List demo? Thanks!

  • Hi Mark,

    If you send me email ( I can send you the CSS and Image files from my other Atlas video.



  • Scott,

    How can we send our controls to the Atlas team?

  • Hi Albert,

    If you want to send me email I can loop you in with Shawn Burke who runs the Atlas Control Toolkit project.



  • Hi Luis, I was away on vacation from 11:30am on Sunday until Monday evening without access to a computer, which is why your comment wasn't published until I returned. To answer some of your questions above (and in your blog post, which has comments disabled so I couldn't post these there):
    1) The Atlas July CTP contains a number of tactical bug fixes, but doesn't include new features.
    It also doesn't include fixes for every bug reported. The reason for this is that we are in the process of finishing a pretty major re-architecture of a few internal pieces of Atlas. This doesn't change the external programming model for Atlas, but does change the factoring of the Atlas libraries (making them smaller and faster), and adds more robust error handling throughout the system (which is goodness).
    This architectural work is being done within a separate source tree fork, and will form the basis for future CTP releases. Bug fixes will be rolled into this new source tree once the architectural work is complete. This work will provide a lot of stability + performance + feature gains -- but it wasn't quite ready for the July release (which is why it wasn't shipped then). We are working hard on getting this out as soon as possible though. Once this is done you'll see a bunch of new bug fixes show-up (since 95% of the Atlas team's work the last 2.5 months has been on this fork).
    2) The Atlas Control Toolkit team is actually a separate team from the core Atlas team. In fact, more than half of the Toolkit developers are now non-Microsoft employees. This is one of the reason why that download keeps making feature progress while the core Atlas download stabilizes.
    3) Atlas supports both a server-side and a client-side Ajax model. In general we find some developers prefer one over the other. One of the really powerful things about Atlas as an Ajax framework is that it has rich support for both -- and allows developers to mix and match between the two depending on their specific page/app scenarios.
    Hope this helps,

  • Hi Scott,
    Excellent tutorials.
    2 questions:
    A) The samples shown use a button action to initiate a display change. I am interested in "binding" the display to some sort of "database" such that when the value changes, the display gets updated. In this scenario the server side would initiate the update. Is this possible, are there examples?

    B) Are there workshops / demonstrations / conventions / courses planned throughout North America for ATLAS? If so, where and when, else where can I find such a schedule?

  • Hello Scott,

    I've downloaded the new Atlas July CTP and the new Atlas Control Toolkit. I'm developing an AtlasWebSite in VB.Net. When I'm using the FilteredTextBox in a DetailsView in InsertMode it works all fine. Very great, this control! But using this FilteredTextBox in a GridView I get following error messagebox when clicking on "edit" button: "Unknown error."

    What could I do to solve this problem?

    Thank you very much.


  • It's great that the Toolkit is collaborative with the .NET community. Could I put a call out for a decent Dropdown Calendar control?!? Maybe I'll have to contribute myself :)

  • Hi Scott,

    One of the techniques often used to get around the browser HTTP connection limit of 2 concurrent connections is to use multiple subdomains:

    Now we can have 6 connections back to the server.

    This is particularly important for AJAX apps doing a lot of chatty stuff, which quite frankly the current HTTP standard was not written considering this usage.

    Some of the new controls, such as the AtlasControlToolkit DynamicPopulate control do allow you to hit the server multiple times concurrently (unlike most of the controls which are limited due to the ASP.NET page lifecycle requirement of synchronous request to preserve viewstate, etc).

    I thought I might be able to do what I describe above using the DynamicPopulate control and specifying the full URL (including different subdomains) via the ServicePath attribute.

    However it appears that when the URL specified is different that the exact URL the user used to browse to the site, an error occurs. Note this is not a web server level error, so must be something wrong with either Atlas networking stack or AtlasControlToolkit?

    Please pass this onto the Atlas team as they should consider this when building Atlas.



  • Was wondering when you guys are targeting a stable production version? We are interested in using Atlas in production in 6 months time and we would like to assuage the concerns of using a CTP product.


  • Hi Adam,

    We are going to be publishing a formal roadmap in a few months. Having a formal, supported, 1.0 release is something we are looking to have in the timeframe you are after.

    Hope this helps,


  • Hi David,

    I chatted with some folks on the Atlas team, and they mentioned that there is a [WebOperation] attribute that you can add to indicate whether you can support cross domain scripting requests (in other words - go to multiple sub-site domains):

    [WebOperation(true /*getVerbEnabled*/, ResponseFormatMode.Json, true /*safeForCrossDomain*/)]

    Let me know if this makes sense, and if not I can loop you in with folks from the team.



Comments have been disabled for this content.