Gunnar Peipman's ASP.NET blog

ASP.NET, C#, SharePoint, SQL Server and general software development topics.

Sponsors

News

 
 
 
 
 
DZone MVB

Links

Social

Windows 7: Links for developers

As Windows 7 is now available to MSDN and TechNet users it is time to give some references for developers who are interested in Windows 7 software development.

  • Microsoft Windows SDK for Windows 7 and .NET Framework 3.5 SP1 (ISO)
    The Windows SDK for Windows 7 and .NET Framework 3.5 SP1 provides the documentation, samples, header files, libraries, and tools (including C++ compilers) that you need to develop applications to run on Windows 7 and the .NET Framework 3.5 SP1. To build and run .NET Framework applications, you must have the corresponding version of the .NET Framework installed. This SDK is compatible with Visual Studio® 2008, including Visual Studio Express Editions, which are available free of charge.
     
  • Windows® API Code Pack for Microsoft® .NET Framework
    The Windows® API Code Pack for Microsoft® .NET Framework provides a source code library that can be used to access some new Windows 7 features (and some existing features of older versions of Windows operating system) from managed code. These Windows features are not available to developers today in the .NET Framework.
     
  • Windows 7 Training Kit For Developers
    The Windows 7 Training Kit for Developers includes presentations, hands-on labs, and demos designed to help you learn how to build applications that are compatible with and shine on Windows 7

If you are upgrading your system from Windows Vista and you have Visual Studio 2010 Beta 1 then please read Scott Hanselman’s blog entry Vista Users - Uninstall Visual Studio 2010 Beta 1 before upgrading to Windows 7.


kick it on DotNetKicks.com pimp it Progg it 顶 Shout it

Comments

DotNetBurner - Visual Studio said:

DotNetBurner - burning hot .net content

# August 9, 2009 9:41 AM

PimpThisBlog.com said:

Thank you for submitting this cool story - Trackback from PimpThisBlog.com

# August 9, 2009 9:42 AM

DotNetKicks.com said:

You've been kicked (a good thing) - Trackback from DotNetKicks.com

# August 9, 2009 9:43 AM

progg.ru said:

Thank you for submitting this cool story - Trackback from progg.ru

# August 9, 2009 9:44 AM

9eFish said:

9efish.感谢你的文章 - Trackback from 9eFish

# August 9, 2009 9:45 AM

Windows 7: Links for developers | Windows (7) Affinity said:

Pingback from  Windows 7: Links for developers | Windows (7) Affinity

# September 27, 2010 3:51 AM

Bhawana said:

Оставьте свой комментарий                                                            Вы можете использовать следующие HTML тэги: <a> <abbr> <acronym> <b> <blockquote> <cite> <code> <del> <em> <i> <q> <strike> <strong>                                                                                                               var RecaptchaOptions = { theme : 'clean', lang : 'en' , tabindex : 5 };                                                                                                #submit {display:none;}

# May 9, 2012 6:31 AM

Ayu said:

, "We at GE only have two sources of covpetitime advantage: 1. the ability to learn more about our customers faster than the competition, 2. the ability to turn that learning into action faster than the competition". Ultimately IT is for the better of the business. Agility leads to business success. .NET can build for you an agile system that's both easy to extract insights and easy to execute your new strategy from decisions made based on those insights.These all sound like marketing. But it's real. Other IT vendors are talking the same things, XML, Web Services, SOA, agility, connectedness. Maybe they use different terms (for the purpose of differentiation), but the idea behind those terms are the same.So you will find out an interesting phenomenon among IT vendors. We support the same set of open standards, i.e., XML and Web Services. We all think enterprise should go SOA. We share the same vision, i.e. agility. So now what's the difference? It's the implementation. XML, Web Services, SOA are just specifications and concepts. They need to be implemented using some kind of platform technology..NET is Microsoft's technology to realize XML, Web Services, SOA and agility.So When I explain .NET to my customers, I often first give them an introduction on the landscape of why they need XML, Web Services and SOA.IT people are used to see Microsoft, as a platform vendor, provides application platforms on which they can build their IT systems. So sometimes I give the following definition of .NET:.NET is Microsoft's next-generation application platform to build connected solutions for an agile business. These solutions are standard-based, connected, flexible to change, secure, reliable and best performing.For a technology standpoint, a .NET application is an application that runs on top of .NET Framework (or more precisely, an application that is built with .NET Framework classes and runs on Common Language Runtime). If an application has nothing to do with .NET Framework, it can't be called as a .NET application. For example, using XML doesn't make it .NET. Using SOAP SDK to consume a Web Services doesn't make it .NET, either.What are Microsoft's .NET technologies? .NET Framework certainly is the core component. Visual Studio.NET 2002 and 2003 is the integrated development environment to build .NET solutions. Visual Studio Tools for Office (VSTO) can be used to extend Word and Excel capability with .NET components. Web Service Extensions (WSE) are a set of .NET classes to build Web Services-based solutions using advanced Web Services standards such as WS-Security, WS-Policy, WS-ReliableMessaging, and WS-Attachments. I mentioned a few here. But you got the idea.Is .NET all about Web Services? Certainly not, as some people correctly pointed out. It's Microsoft's next-generation application platform, on which you can build any type of systems. Traditional Windows desktop applications, Web applications, Office applications, mobile applications, smart device applications. All these. On a Dopod Pocket PC (Phone Edition), you can use .NET Compact Framework to build a client application that runs on it. Or you can develop a mobile Web application and put it up on some IIS server and use the Internet Explorer browser on the Dopod to visit that website, where its pages are tailored to fit on the small screen of your device.

# May 12, 2012 12:03 AM
Leave a Comment

(required) 

(required) 

(optional)

(required)