Community Technology Update (CTU) 2009 II

 Development  Add comments
Dec 042009
 

Community Technology Update II
I’ll be speaking at the Community Technology Update (CTU) 2009 II event on “What’s new in .NET Framework 4.0“. I’ll be covering the following:

This talk give an overview and cover as many changes in the .NET Framework 4.0 as possible in the time allocated, from the BCL (Base Class Library) to various interesting additions like the Managed Extensibility Framework, Code Contracts, Parallel Extensions and Dynamic Language Runtime.

If you’re interested in talks like this, come join us on 19th December 2009 at Microsoft Singapore, Auditorium, Level 21, One Marina Boulevard, to learn about what’s the upcoming technology coming from Microsoft and Visual Studio 2010. Remember, you have to pay a small token amount ($10 to $15) for this event.

============

It is that time of the year again. Coming 19th Dec 2009, the community alliance is coming together again. Bringing you a full day of content, by the Communities to the Communities.

We have prepared 15 different sessions, 4 slots of Hands-On-Lab with its contents refined and shared later, Door Gifts, Buffet Lunch for attendees $10 MSPress Vouchers, 20% MCP Exam discounts and many more…

To keep the place abuzz, we have MS Press appearing with discounted books, Lucky Draw at end of day, Xbox 360 with Call Of Duty (Modern Warfare 2) waiting for you.

To find out more about the agenda or to register, please visit http://ctu.geeksengaged.com

For enquiries, please first visit the FAQ, then contact the registration team.

See you there at CTU 2009 II

Related posts:

  1. Microsoft Parallel Extensions to .NET Framework 3.5, December 2007 Community Technology Preview
  2. LinuxNUS Welcome Tea September 2009
  3. Hackerspace.SG Housewarming on November 21, 2009
  4. 5 reasons to go to Singapore Twestival 2009
  5. International Conference on Functional Programming (ICFP) 2009 Videos
  • Jolufu

    I have just attended your session, and it’s great to know that the industry is working on something to simplify the work of the developers, REST.

    However, the content you covered for the topic is not “securely” RESTful to me, as it has the fundamental flaw to phishing. Yes, it’s me who approach you with the question at the end of your session.

    I am disappointed because I would have expected the implementation would have covered all aspects of security before it is being introduced to the communities, as Security is the topic of your session.

  • http://www.justinlee.sg Justin Lee

    @Jolufu:

    I agree with you completely, and it is something that the guys at Microsoft are working towards implementing this. I cannot speak for Microsoft team, but I’m very sure they are looking to release that soon.

    But with that said, I’m happy that you understood what I was talking about and came up with the exact same conclusion as quite a lot of people who attended this same topic. Kudos to you. I had exactly the same concern with you regarding phishing when I learned about this ACS technology.

    I hope you enjoyed the topic though and could see that the industry (not only Microsoft alone) is working together to create a unified specs for communicating through REST. Hope to see you at CTU!! :)

  • http://www.justinlee.sg Justin Lee

    Just to follow up on phishing, you can actually create your wrap_SWT token and hash it instead of sending your own key across. That will prevent phishing. Check out the sample from the SDK under C:Program Files (x86)Microsoft .NET Services SDK (Nov 2009 CTP)SamplesAccessControlExploringFeaturesSignedTokenRequests and it will show you how to create your own Simple Web Token which is hashed so no keys are passed around.

  • Jolufu

    Yes, that’s the very basic of securing transmission of potential data, and you should have use it during your delivery.

    However, I am still surprised that ACS still allows transmission of unencrypted keys over TCP; I would prefer them to enforce the security, forcing the developers to do their due deligents.

    And thank you for the wonderful wealth of information on the topic, let’s be RESTful!