none
Windows 7 Development RRS feed

  • Question

  • I am reading the Windows 7 Developer Guide at http://msdn.microsoft.com/en-us/windows/dd239181.aspx.  There is ZERO mention of .NET.  But there are seven references to Win32 API.

    Has Microsoft abandoned the .NET Framework moving forward?  Will .NET Framework be automatically shippipped with Windows 7?  If yes, what is the default version?

    Worried and thanks.
    Sunday, July 26, 2009 7:06 AM

Answers

  • Stop panicing, New OS API's always have been released first as native api's the OS is written in native code so it makes sense to release a native api first and later on wrap it into managed classes you can use from within .Net either in new versions of the .net framework or in out of band releases as the Windows® API Code Pack for Microsoft® .NET Framework  which already supports alot of the windows 7 functionality.

    So settle down, the sky isn't falling. Windows and the .Net framework always have shipped out of sync and probably always will there is no deeper meaning behind it.  .Net has never been about being cutting edge it's about making it easier and faster for you to write applications, if you want cutting edge learn C++

    • Marked as answer by K.Kong Sunday, July 26, 2009 11:55 PM
    Sunday, July 26, 2009 9:44 PM

All replies

  • There were 6000 new API additions to Vista.  They were not wrapped by .NET either.  Did you miss them?  .NET will always be a subset of the full Win32 API, one that's compatible with 99% of all machines.  P/Invoke gets you the new stuff.

    Hans Passant.
    Sunday, July 26, 2009 11:01 AM
    Moderator
  • What I meant was will .NET still be a major development model?  As it is not mentioned even once in a Windows 7 Developer Guide it could mean something.
    Sunday, July 26, 2009 12:43 PM
  • Of course.  .NET version 4 will be available within the next year or so.  It has many excellent additions that have nothing to do with the operating system.  .NET is not just a wrapper around Windows, it is a programming tool in its own right.

    Take a look at this blog post for a much better description for what's available.

    Hans Passant.
    Sunday, July 26, 2009 1:24 PM
    Moderator
  • Stop panicing, New OS API's always have been released first as native api's the OS is written in native code so it makes sense to release a native api first and later on wrap it into managed classes you can use from within .Net either in new versions of the .net framework or in out of band releases as the Windows® API Code Pack for Microsoft® .NET Framework  which already supports alot of the windows 7 functionality.

    So settle down, the sky isn't falling. Windows and the .Net framework always have shipped out of sync and probably always will there is no deeper meaning behind it.  .Net has never been about being cutting edge it's about making it easier and faster for you to write applications, if you want cutting edge learn C++

    • Marked as answer by K.Kong Sunday, July 26, 2009 11:55 PM
    Sunday, July 26, 2009 9:44 PM