Title of Presentation

  • 640 views
Uploaded on

 

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
640
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
5
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • 04/29/10 09:01 © 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
  • Discussion Points: Visual Studio & .NET Framework Roadmap Visual Studio design goals Lap around new features Visual Studio multi-targeting, VSTS LINQ & CLR Add-ins Services & Workflows Windows, Web, Office, and Mobile applications I’m classifying this as a level 200 talk. There will be some slides, some demos, and I’ll show some code (primarily in C#). We have a lot of If this doesn’t sound like it’s the right session for you, then feel free to leave now. I will not be offended. For some of you who are currently using the .NET Framework 3.0 or have already started using Visual Studio 2008 and the .NET Framework 3.5, several of the things we’ll discuss will be a refresher. ---------------------- We are not going to discuss: Language enhancements Silverlight MFC – A number of the Windows Vista “look & feel” features are available simply by recompiling an MFC application. CLR enhancements ClickOnce improvements Partial trust hosting of add-ins Add-in activation: expand Activator to allow for out of process activation Jscript intellisense support for ASP.NET Ajax applications VSTS – improved support for performance tuning, testing
  • Do you or any of your customers suffer from…version confusion? I’m referring to .NET Framework versioning confusion. I know that I have frequently been asked by customers questions like: Discussion Points: So what is the .NET Framework 3.5? There is a fair amount of confusion about the different versions of the .NET Framework. It’s important that we spend a few minutes to clarify any confusion that might exist in this room. Let’s walk through this diagram: .NET Framework 3.5 The .NET Framework 3.5 is an incremental release of the .NET Framework. It provides several new enhancements including LINQ, ASP.NET 3.5, the CLR Add-in framework and several others. The .NET Framework 3.5 builds upon the previous versions of the framework, namely the .NET Framework 2.0 and 3.0. More specifically, you can think of it as though the .NET Framework 3.5 has a dependency on the .NET Framework 3.0 with SP1 and 2.0 with SP1. .NET Framework 3.0 The .NET Framework 3.0, which was formerly known as WinFx, introduced several key new technologies including: Windows Presentation Foundation – provides the ability to build rich, interactive client applications Windows Communication Foundation – provides a common programming model for building services and connecting applications Windows Workflow Foundation – provides the ability to define declarative, long-running workflows Windows CardSpace – provides a safer and more secure alternative to username and password authentication within web sites and rich client applications .NET Framework 2.0 Finally, the .NET Framework 2.0, which was initially released in 2005 provides the common language runtime and base class libraries that are used by the .NET Framework 3.0 and 3.5 components. So how will developers get the .NET Framework 3.5? The .NET Framework 3.5 will be available as an optional update through Windows Update, as a bootstrapper installation, and as a full package. With all of these packages, your machine will be examined during the installation and the .NET Framework 2.0 with SP1, 3.0 with SP1, and the new 3.5 assemblies will be installed. The setup for the .NET Framework 3.5 will only install the necessary bits. So if the .NET Framework 2.0 or 3.0 is already installed, then only the service packs and the 3.5 bits will be added.
  • © 2006 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION. Discussion Points: .NET Framework 3.0 First, if we travel back in time to November of 2006, Microsoft released the .NET Framework 3.0. .NET Framework 3.0 was installed by default with Windows Vista, however, it was also available as a installable component for Windows XP SP2 and Windows Server 2003. Visual Studio Extensions When we released the .NET Framework 3.0, we also released a couple of extensions for Visual Studio. The first extensions, called the Visual Studio 2005 Extensions for Windows Workflow Foundation, provided templates and design-time support for creating workflows within Visual Studio. It is worth noting that this was a complete and fully supported set of extensions. The second extensions were the Visual Studio Extensions for the Windows Communication Foundation and Windows Presentation Foundation November CTP. These extensions simply provided project and item templates for building WCF services and WPF applications. ASP.NET Ajax Shortly after the release of the .NET Framework 3.0, Microsoft also released the ASP.NET AJAX 1.0 extensions. These extensions are designed to enable web developers to build dynamic applications with ASP.NET 2.0. Visual Studio 2008 and .NET Framework 3.5 It’s important to understand these out-of-band releases as we look at Visual Studio 2008 and the .NET Framework 3.5. Visual Studio 2008 and the .NET Framework 3.5 include enhanced versions of the technologies that have been released out-of-band, such as AJAX and design time support for WF, WPF, and WCF applications. At this point in time the beta 2 release of Visual Studio 2008 and the .NET Framework 3.5 are available. It is also worth mentioning that there is a go-live license available with the .NET Framework 3.5. So you can deploy applications into production using this license. To be clear, there is a difference between licensed and supported. The .NET Framework 3.5 will not be supported until it is officially released. Visual Studio 2008 and the .NET Framework 3.5 are scheduled to be released at the end of 2007 and they will launch with Windows Server 2008 and SQL Server 2008 on Februrary 27 th . Beyond the release of Visual Studio 2008 and the .NET Framework 3.5 Finally, next year we plan to release a major update to Visual Studio Team System and Team Foundation Server codenamed “Rosario”.
  • Discussion Points: Of course, Windows Server 2008 is the next major release of the Windows Server operating system. This release was originally codenamed “Longhorn Server”. One of the most common questions I hear is “what version of the .NET Framework will be included with Windows Server 2008?” With a fresh installation of Windows Server 2008, you will have the .NET Framework 2.0 with SP1. The .NET Framework 2.0 is actually a required dependency for key Windows Server 2008 features such as Windows PowerShell and MMC. Of course, the .NET Framework 2.0, also includes ASP.NET 2.0 as well. The .NET Framework 3.0 with SP1 will be installed the moment you decide to configure your server with the “Application Server Role” using the new Server Manager application. Finally, the .NET Framework 3.5 will be available as an optional update on Windows Update. FAQ: What about Windows Server Core? The .NET Framework is not currently included in Windows Server Core. We are actively taking feedback and considering this for a future release.
  • Discussion Points: Now let’s start our lap around. We will first start in the center and discuss some of the Visual Studio enhancements, lifecycle tools, and some of the core .NET Framework enhancements that can be used by a wide variety of applications. Then will look at the various type of applications you can build using the .NET Framework and tools, ranging from services, to Windows client applications, to web, office, and mobile applications. I suspect that many of you are building only a few of these types of applications today, so some of these topics may not be immediately relevant to your current projects. However, I believe that it is valuable to understand what you can build with the framework and tools in case you have a need to extend your applications in different scenarios.
  • Multi-targeting Traditionally developers have required tools that are bound to the runtime platform they are building against. With Visual Studio they can now use the one toolset and target the desired platform. Additionally, command line solutions will build using the toolset appropriate for the .NET Framework version that is being targeted Simplifies upgrading Multi-targeting is useful when you’re building a new project and you cannot take a dependency on the latest version of the framework, however it is also incredibly beneficial for upgrading existing projects. With multi-targeting you can upgrade to Visual Studio 2008 very easily because your project can continue to target older versions of the framework. As an example, within our Developer & Platform Evangelism group we created a sample application called DinnerNow. DinnerNow has approximately 37K lines of code and around 24 projects/assemblies. We simple opened up the DinnerNow solution files in Visual Studio 2008, which modified the sln files, and then recompiled our solutions with 0 errors and 0 warnings. That was on Beta 1 and it was such a smooth upgrade because of multi-targeting. Move existing Visual Studio 2005 applications to .NET Framework 3.5 gradually
  • Discussion Points: TFS 2008: Now includes built-in support for Continuous Integration. All configurable via Team Build wizard. Retention policy allows, for example, to automatically keep only the latest 3 broken builds but the last 10 working builds. Migration Toolkit helps move from 3 rd party source code control and work tracking solutions to TFS. “ Get latest on checkout” helps people who are more familiar with the VSS-style checkout system. Annotate shows, line by line, who the last person to change a line was and what changeset it was associated with. Folder diff makes it easy to compare two folders – client workspace to server branch, server branch to server branch, etc. Development enhancements: Code metrics help to highlight pieces of your project which may need to be refactored. Helps developers understand pieces of code which may be brittle and risky to make changes to. Performance “hotpathing” enables developers to quickly see the paths of your code which are taking the longest to execute. Profiler baselining makes it easy to compare profiling runs and determine the impact that code changes are having on performance. Faster unit testing framework makes it easier to rapidly iterate and test code Testing enhancements: Load testing now supports AJAX applications (formerly had to use 3 rd party tool like Fiddler) UI for load testing is vastly improved to make it easier to monitor load tests and gather meaningful data. On Friday, we will have a full day focusing on the Application Lifecycle Tools including Visual Studio Team System and Team Foundation Server Notes: More info here: http://msdn2.microsoft.com/en-us/teamsystem/bb407307.aspx
  • Discussion Points: Orcas significantly improves the way developers handle data. Traditionally developers have manipulated data differently depending on where the data resides and how the user connects to it. With the introduction of Language Integrated Query developers can now deal with data using a consistent programmatic approach and perform data access with new data design surfaces. LINQ aimes to reduce the complexity for developers and help boost their productivity through a set of extensions to the C# and Visual Basic programming languages as well as the Microsoft .NET Framework, which provides integrated querying for objects, databases, and XML data. Using LINQ, developers will be able to write queries natively in C# or Visual Basic without having to use specialized languages, such as Structured Query Language (SQL) and Xpath. With Visual Studio “Orcas”, you can work with data in the way that you want. You can create entire collections of objects from a database backend if you like. You can interact with data as rows or columns – whatever makes sense to your application. Language Integrated Query or “LINQ” will dramatically change the way we work with and program against data. By creating a common querying language in LINQ, we’ve freed you, the developer to focus on things that matter most to you. LINQ will provide you the ease of use you’ve come to expect with Visual Studio offering both IntelliSense and Autocompletion right in the IDE. Language Integrated Query provides native querying syntax in C# and VB.Net. This frees the developer from having to master independent data programmability technologies (e.g. Xpath, Xquery, T/SQL) and instead offers the developer a consistent way to query data. The best part is that the LINQ code you write is consistent whether your data store is a SQL Server, contained in a ADO.NET DataSet, an XML document, an EDM you create or even objects you create in memory. With Orcas, we have taken a more general approach and are adding general purpose query facilities to the .NET Framework that apply to all sources of information, not just relational or XML data. This facility is called .NET Language Integrated Query (LINQ). With Orcas and ADO.NET 3.5, LINQ is an inherent part of the C# and VB.Net languages offering both IntelliSense and Autocompletion. LINQ provides developers with a consistent query language which they in turn may use on various types of data. Be it Objects, XML, Datasets, SQL Server (or other databases with ADO.NET providers) and Entities. Any data that may be placed into a .NET collection of type IEnumerable<T> can be queried by LINQ. If you’ve written T/SQL in the past then LINQ will offer you familiar constructs for projections, restrictions, sorting and grouping such as Select, Where, GroupBy, and OrderBy. You can also adapt the query operators to your liking by using extension methods which can override their default behavior.
  • Discussion Points: LINQ is currently integrated directly into the native syntax for both C# 3.0 and VB 9.0 – which are included with Visual Studio 2008 Other languages may also support Language Integrated Query syntax in the future. There are many flavors of LINQ which we describe by the type of data it operates over. As you can see here, LINQ may operate over Objects, SQL, Datasets, and XML. These are the four flavors of LINQ that we are shipping with the .NET Framework 3.5 LINQ to Objects SQL-like queries for any .NET collection (or anything that implements Ienumerable) The LINQ to Objects API supports queries over any .NET collection, such as arrays and generic lists. This API is defined in the System.Linq namespaces inside System.Core.dll LINQ to objects is enabled by including the System.Linq namespace. Manipulating collections of objects, which can be related to each other to form a hierary or a graph. From a certain point of view, LINQ to Objects is the default implementation used by a LINQ query. LINQ to SQL Query enabled data access framework LINQ to XML Query enabled, smaller, faster XML DOM The important thing to remember is that the querying syntax used in LINQ is consistent regardless of the type of data you’re working with. FAQ Will there be support for Oracle with LINQ to SQL? There is no provider model for DLINQ. In order for a third party provider to support DLINQ, they would need to produce an entire API that mirrors DLINQ that covers everything from query generation to examining attributes on classes to providing a designer to interact with the database schema. Because there's a lower bar for enhancing a provider to support the Entity Framework (primarily just query generation), Oracle is only planning to support the Entity Framework.  
  • Discussion Points: As most of you are probably aware, the .NET Framework 3.0 included the Windows Communication Foundation (WCF) and Windows Workflow Foundation (WF). WCF provides… WF provides… With “Orcas” there are several new enhancements to these technologies to make it easier to build and consume services and define and execute workflows. Notes: In V1, one of our themes was unification – we unified our existing managed communications stacks, pulling the features of ASMX, Remoting, System.Messaging, System.EnterpriseServices, and WSE together into a single programming model. A large batch of customers we talked to wanted to use our unified programming model, but they develop for the Web, and in V1 we didn’t make Web scenarios very easy. So in Orcas, we’re taking Unifivation one step further, adding features to make it simple for Webbie customers to use WCF, increasing our reach. A whole lot of our customers told told us that they want to use WCF and WF together, so we’ve focused on unification there as well, making it simple for workflows to be exposed as services, and services to be implemented as workflows. Many customers clearly and firmly insisted on more and more integrated design time support. In V1 we delivered a few tools for WF and WCF, but they weren’t integrated into VS, shipping in an unsupported CTP. In Orcas we’ve invested in our tooling, integrating our existing tools into VS, and adding new tools to “shorted the distance to F5”. Web Programing Model Simple approach for building REST-based services REST=Representational State Transfer. http://en.wikipedia.org/wiki/Representational_State_Transfer With RESTful services, the URI is the API WCF provides an attribute called WebGet and a URI template, which removes you from parsing segments of the URI Supports both XML and non-XML data WS* vs. REST WS-* vs. REST vs. Anything else is silly Each has its place – there is no silver bullet Choose what works for you Syndication If you wanted to do Syndication on top of WCF in V1, we didn’t give you much help – you had to plug into the WCF extensibility points to write syndication code, and you were on your own for a syndication object model. To help out in the short term, we released a sample RSS toolkit, which picked up several thousand customers despite being an unsupported sample. So today, we’re building System.Syndication for the .NET Framework. It’s the one way you do RSS in the framework. We’re giving you a common object model for Syndication, with serialization support for RSS, ATOM, or new formats that can be added as they’re invented. Managed programming model for both exposing and consuming syndication feeds. Provided in the System.Syndication namespace Unified RSS / ATOM feeds Composes with the Web Programming model WCF V1 is a powerful communications stack WF V1 is a powerful workflow engine Our customers have realized that together they form a very compelling combination. In Orcas, we’re writing that glue code for you. We’re giving you the infrastructure to easily implement WCF services with WF, or to expose your existing workflow as a WCF service. In addition, we’re making it easier for developers using WCF without WF to make their service state durable.
  • Discussion Points: Integrated Workflow & Microsoft SharePoint Support If you’re not familiar with SharePoint’s workflow support… SharePoint workflow is about business process and information flow End-users can interact via the Web browser, Office client applications, or custom UI SharePoint ships with out-of-the-box workflows installed and activated Today building workflows for Sharepoint is painful. Microsoft Office SharePoint workflow solutions are fairly combersome to start using the VS 2005 tools. We estimate that it takes about 20 minutes and about 3 pages of documented step-by-step instructions to create your first SharePoint Workflow project. With Orcas, it takes 3 steps, not three pages of steps, to create your workflow project, and then get down to creating the business rules! What a huge time savings! We have significantly reduced the number of steps to get started building SharePoint workflows with VSTO. A great deal of time is spent troubleshooting the development environment- not the customization itself Developers must read lengthy documentation and follow detailed steps to be successful The number of steps involved in a simple debugging session is excessive VSTO includes project templates, design time support, and debugging support for building workflows that run within SharePoint 2007 Two supported languages: Visual Basic .NET and Visual C# .NET Two built-in workflow template types for each language Leverages the same workflow designer used for non-SharePoint workflow applications Facilitates workflow debugging
  • Discussion Points: Visual Studio 2008 and the .NET Framework 3.5 also provide several enhancements for building mobile applications. These enhancements fall within two categories – tools enhancements and the .NET Compact Framework 3.5 enhancements For those of you that are familiar with the compact framework, you might be wondering where did version 3.0 go? 3.0 for the desktop was 2.0 + WinFX Compact Framework is skipping the 3.0 version number NetCF 2.0 SP1 in ROM for Windows Mobile 6 LINQ Compatible subset of .NET Framework functionality LINQ to Objects LINQ to XML LINQ to DataSet Less than 200K in size Unsupported (Too big for NetCF) LINQ to SQL LINQ to Entities The .NET CF 3.5 will also introduce WCF for mobile devices. Consistent programming model for Windows Mobile device and desktop Shrunk footprint from over 10MB to less than 1MB Interoperates with desktop Supported features Subset of messaging layer Subset of WS-Security and WS-Addressability HTTP Messaging Store and Forward Messaging Extensible Transports Not Supported Service Model and Contracts Compact SVCUtil WCF Store and Forward Messaging Leverages Email and its infrastructure to solve addressibility and intermitten connectivity problems Create consistent programming model for Windows Mobile on devices and Windows on PCs Leverage WCF architectural extensibility Leverage the ActiveSync “Always-Up-To-Date” feature and Exchange 2007 Web Services
  • 04/29/10 09:01 © 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Transcript

  • 1. Name SuPeng
  • 2.
    • .NET Framework & Visual Studio Roadmap
    • .NET Framework 3.5 overview
    • Visual Studio design goals
    • Lap around new features
  • 3. .NET Framework 2.0 + SP1 Windows Presentation Foundation Windows Communication Foundation Windows Workflow Foundation Windows CardSpace .NET Framework 3.0 + SP1 .NET Framework 3.5 LINQ ASP.NET 3.5 CLR Add-in Framework Additional Enhancements
  • 4. 2006 2007 2008
      • “ Rosario”
    3.0 RTM 3.5 RTM Major Releases Out of band Releases
    • VS Extensions for WF
    • VS Extensions for WCF/WPF CTP
    ASP.NET AJAX 1.0
    • VS 2008 Beta 2
    • .NET Framework 3.5 Beta 2
  • 5.
    • Next major release of Windows Server scheduled for release in Q1 2008
    • What’s included with Windows Server 2008?
  • 6.
    • Best tool set for Windows Server 2008, Windows Vista and Microsoft Office 2007
      • .NET Framework 3.5 design surfaces
      • Office 2007 support including ClickOnce and VSTO
      • MFC support for Vista common controls
    • Improvements for Web Developers
      • HTML / CSS designer enhancements
      • Integrated AJAX and JavaScript support
    • Language advances
      • .NET Framework multi-targeting support
      • Improved Data & Language integration in VB / C#
  • 7.  
  • 8.
    • Multi-targeting
      • Target multiple versions of the framework from a single tool - Visual Studio 2008
      • Supports framework versions 2.0, 3.0, and 3.5
      • Enables only features available in target framework
        • Toolbox, Project types, References, Intellisense, …
      • Making is easy to upgrade to Visual Studio 2008
    • Unit Testing
      • Now available in all editions of Visual Studio Professional
  • 9.
    • Team Foundation Server 2008
      • Built-in support for Continuous Integration
      • TFS Migration Toolkit
      • “ Get latest on checkout”
      • Annotate
      • Folder Diff
    • For developers:
      • Code metrics
      • Performance “hotpathing”
      • Profiler baselining
      • Much faster unit testing performance
    • For testers:
      • Load testing support for AJAX applications
      • Better UI for load test monitoring / reporting
    • And much more…
  • 10.
    • Designed to reduce the complexity when working with data
    • Query operators can be used against any collection
      • Built-in examples: Select, Where, GroupBy, Join, etc.
      • Extensibility model supports extending/replacing these
    • Benefits
      • Work with data in a consistent way, regardless of the type of data
      • Interact with data as objects
      • Better integration with programming languages
      • Improved productivity through IntelliSense in Visual Studio
    New programming model for data access that integrates query support directly within the .NET languages
  • 11. Objects <book> <title/> <author/> <year/> <price/> </book> XML .NET Language Integrated Query C# 3.0 VB 9.0 Others… Relational LINQ to Objects LINQ to SQL LINQ to XML LINQ to DataSets
  • 12.
    • Technologies added in .NET 3.0
      • WCF – Unified programming model and runtime for services
      • WF - Flexible, declarative workflow runtime and activities
    • New enhancements in .NET 3.5
      • Http Programming Model
      • JSON serialization & ASP.NET AJAX integration
      • Syndication
      • Integrated support for WF & WCF (“Silver”)
      • Partial Trust
    • Integrated developer tools in Visual Studio 2008
      • Add Service Reference
      • Integrated WF Designer
      • Project & item templates
      • Autohost & test client
      • WCF Configuration Editor
  • 13.
    • Visual Studio Designer for WPF (“Cider”)
      • XAML-based editing directly in the IDE
        • Changes reflected in the designer in real-time
        • XAML IntelliSense
        • Selection Synchronization
      • ClickOnce deployment support for WPF apps
      • Project templates, debugger & deployment support
      • Side-by-side support for Winforms
    • Creates a seamless designer/developer workflow with Expression Interactive Designer (“Sparkle”)
  • 14.
    • Integrated support for ASP.NET AJAX 1.0
      • Included in the .NET Framework 3.5
      • ASP.NET AJAX Project Templates
    • Web Application Projects included in Visual Studio
    • Javascript IntelliSense & Debugging
    • Richer HTML/CSS Designer Support
      • Split View (simultaneous source and designer)
      • Nested Master Page preview in designer
      • CSS Properties, Manage/Apply Styles windows, and direct style application toolbar
      • Improved CSS/HTML layout and visualization in designer
    • New Web data controls
      • LinqDataSource, ListView, DataPager
  • 15.
    • VS 2008 includes Visual Studio Tools for Office 3.0
    • Provides integrated visual designers for:
      • Word and Excel documents and templates
      • Fluent Ribbon
      • Task & Action panes
      • Outlook Form Regions
    • Integrated Workflow & Microsoft SharePoint Support
    • Data binding in Word Content Controls
    • Application-level add-ins for most client programs (both 2003 & 2007)
    • Document-level add-ins for Excel & Word 2007
    • Improved deployment and security using ClickOnce
  • 16.
    • Visual Studio Tools for Devices
      • Unit Testing for Device Applications
      • Device Emulator 3.0 – Certificate support, Xml config
      • Broad Platform and runtime Support
    • .NET Compact Framework 3.5
      • Support for LINQ (XML, Objects and Dataset)
      • Windows Communication Foundation
      • CLR Profiler / Performance Monitor
      • BCL enhancements: Compression support, Client-side certificates, Sound APIs
  • 17.
    • Visual Studio multi-targeting allows you to easily move up to Visual Studio 2008
    • LINQ simplifies data access through language extensions for C# & Visual Basic
    • WF & WCF make it easier to build rich, connected applications using a variety of types of services
    • WPF Designer provides design-time support for building WPF applications and a streamlined workflow between developers and designers
    • VSTO enables developers to build Office Business Applications for Office on the client or server
    • NetCF 3.5 brings major .NET Framework enhancements to mobile devices
  • 18. © 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.