Atlas Control Toolkit Refresh Hopefully Shipping Next Week

Shawn gave a quick update on the Atlas Control Toolkit, and a potential refresh drop his team is pushing to-do next week.  His team has been doing a great job of answering posts on the Atlas Control Toolkit Forums and in getting feedback and suggestions on improvements.  It sounds like a lot of nice feature additions (including several new cool controls) and bug fixes will be coming next week -- along with expanded Safari browser support.

If you are interested in following the Atlas Control Toolkit, you should definitely subscribe to Shawn's blog here.

If you have no idea what the Atlas Control Toolkit is or what I am talking about, you should read my post about it here, and check out the cool online samples here.

Hope this helps,


P.S. We briefly posted the CSS Control Adapters on the web yesterday, but had to take it down to fix an issue this morning. We'll be putting it back on the web next week (unfortunately several key people are out today and this weekend which is one reason why the delay).  Sorry!


  • Cool!

    The previous release was already seriously nifty (except for Safari users of course, but it's good to see that being addressed).

    I'm beginning to develop a case of something dangerously close to enthusiasm...

  • Nice to know!!!

    What about a new ctp of Atlas itself?

    CSS Control Adapters are really cool. Fast people could get it ;-)

  • Fantastic!!! one week even :-)

    Thanks ScottGu's.

  • Hey Scott,

    I really like your blogs -- they are EXTREMELY helpful. Please keep it up. Just one very little thing that drives me nuts; "to do" is only hyphenated if it modifies a noun -- like a to-do list. If I say something like "this is something that we need to do", a hyphen is not used.


  • Awesome! Thanks for you guys work.

  • When you re-release the CSS adapters, are you going to leave it under the *Limited* permissive license (the one that restricts you to Windows only and hence is in no way remotely compatible with the Open Source definition) or are you going to release it under the normal Permissive License which doesn't have such a clause and is real Open Source?

    When Microsoft announced these new licenses I was a little nervous about the existence of the "Limited" variants, but was inclined to give MS the benefit of the doubt that perhaps for some extraordinary circumstances there might be value in these weird licenses, and it *wasn't* just a "bait and switch". But if you're deliberately choosing to release important code like this under the Limited variants, that would definitely cause me to reconsider my opinion of these licenses. And I've seen at least one blogger react even more strongly to seeing this clause - presumably because they hadn't noticed the existence of the Limited variants when the licenses were initially announced.

    Please do the right thing and if you want to do "open-source-like" releases, use the real open source licenses, not the bait-and-switch ones.

  • Hi Stuart,

    The licenses we released the Provider Source Code and CSS Adapter code under allows commercial and non-commercial re-use of the code and does not have a clause that ties it to Windows. It also allows you to ship your own open-source projects with it.

    For completeness, here is the full license text (copy/pasted from the EULA screen in setup):


    Microsoft Permissive License (Ms-PL)

    ASP.NET 2.0 SQL Provider

    This license governs use of the accompanying software. If you use the software, you accept this license. If you do not accept the license, do not use the software.

    1. Definitions

    The terms “reproduce,” “reproduction,” "derivative works," and “distribution” have the same meaning here as under U.S. copyright law.

    “You” means the licensee of the software.

    “Licensed patents” means any Microsoft patent claims which read directly on the software as distributed by Microsoft under this license.

    2. Grant of Rights

    (A) Copyright Grant- Subject to the terms of this license, including the license conditions and limitations in section 3, Microsoft grants you a non-exclusive, worldwide, royalty-free copyright license to reproduce the software, prepare derivative works of the software and distribute the software or any derivative works that you create.

    (B) Patent Grant- Subject to the terms of this license, including the license conditions and limitations in section 3, Microsoft grants you a non-exclusive, worldwide, royalty-free patent license under licensed patents to make, have made, use, practice, sell, and offer for sale, and/or otherwise dispose of the software or derivative works of the software.

    3. Conditions and Limitations

    (A) No Trademark License- This license does not grant you any rights to use Microsoft’s name, logo, or trademarks.

    (B) If you begin patent litigation against Microsoft over patents that you think may apply to the software (including a cross-claim or counterclaim in a lawsuit), your license to the software ends automatically.

    (C) If you distribute copies of the software or derivative works, you must retain all copyright, patent, trademark, and attribution notices that are present in the software.

    (D) If you distribute the software or derivative works in source code form you may do so only under this license (i.e., you must include a complete copy of this license with your distribution), and if you distribute the software or derivative works in compiled or object code form you may only do so under a license that complies with this license.

    (E) The software is licensed “as-is.” You bear the risk of using it. Microsoft gives no express warranties, guarantees or conditions. You may have additional consumer rights under your local laws which this license cannot change. To the extent permitted under your local laws, Microsoft excludes the implied warranties of merchantability, fitness for a particular purpose and non-infringement.


    Hope this helps,


  • Awesome, that's good to know! Thanks for the clarification.

    I didn't actually get to see the license while the code was posted so I had taken the word of another blogger that the Limited version of the license was being used. I'm glad to see that he was mistaken, or at least that the problem is being fixed for the upcoming release :)

  • very cool :)

    Thanks Scott

Comments have been disabled for this content.