Help shape future MSDN TV episodes

We’re trying to put together a series of MSDN TV episodes to air once every month
on Visual Studio
covering the things that developers would want to know in a particular
area.  My question to you is, what do you, as a developer, want
to know about Whidbey?
  Below is a rough draft of the topics I think
would be good to cover: 

  • Visual C++
  • C#
  • VB.NET
  • J#
  • JLCA
  • MSBuild
  • Whitehorse
  • .NET Framework
  • ObjectSpaces
  • Windows Forms
  • ClickOnce

Please send me any feedback!

Comments (13)

  1. Catatonic says:

    I’d love to see MSDN TV cover the changes to managed C++, e.g. the brand new keywords which apparently are becoming a standard part of C++.

  2. Len says:

    1. Yukon features:
    – snapshot locking
    – service broker

    2. Smart client:
    – Convergence of the desktop and web apps.
    – what to do now to prepare to the future

    3. Indigo transactions

  3. Robert Cannon says:

    I would like to see coverage of the new Whidbey features. Object Spaces and the new ASP.NET data binding are two that come to mind.

    Also, how about some of the stuff from the PDC keynotes ( in addition to Lap around Longhorn)?

  4. Lots of good suggestions, thanks everyone! WRT Longhorn/Indigo, there is another group that will be shooting a series of MSDN TV episodes for Longhorn, so I wouldn’t cover any topics that they would be covering, just things within the Whidbey/Yukon timeframe.

  5. Mobility and Pocket PC related stuff

  6. Mikel Berger says:

    compact framework and ClickOnce

  7. Chris Garty says:

    Don’t do languages. They are so specific. Maybe cover clr changes (generics) but stay on the stuff that everyone can leverage. Also… did you see the dozen people that put up their hands at the PDC talk by Don Box when he asked "how many people use VB.Net?"?

    .NET Framework

  8. Anand says:

    New IDE Features

  9. Tony Pino says:

    – VB.NET
    – New IDE Features
    – ASP.NET
    – Windows Forms
    – ClickOnce

  10. Simon says:

    How about using partial postback?