Laden...

Microsoft Visual Studio 2008 SDK August 2007 Community Technology Preview

Erstellt von MagicAndre1981 vor 16 Jahren Letzter Beitrag vor 16 Jahren 2.525 Views
MagicAndre1981 Themenstarter:in
906 Beiträge seit 2005
vor 16 Jahren
Microsoft Visual Studio 2008 SDK August 2007 Community Technology Preview

Microsoft Visual Studio 2008 SDK August 2007 Community Technology Preview

The Visual Studio 2008 SDK August 2007 CTP targets Visual Studio 2008 Beta 2 and is intended to let customers work with Visual Studio 2008 Beta 2 extensibility features.

This CTP adds and updates the following features:

  1. This is the first release of the Visual Studio SDK that supports development of a custom tools environment that is based on the Visual Studio Shell (isolated mode). By using this SDK, developers can create their own instance of the tools environment and include custom branded elements such as splash screen, application title, and application icon. They can also create VSPackages to extend their own instance of the tools environment. For more information, search for "Visual Studio Shell" in Visual Studio SDK Help.

  2. New Samples

2.1. Windows Presentation Framework (WPF) Designer Extensibility
The IronPython sample is enriched with Windows Presentation Framework (WPF) designer extensibility. This sample provides guidance for customers who want to extend Visual Studio to integrate their .NET based languages with XAML and WPF Designer, which are introduced in Visual Studio 2008. This sample is intended to showcase these extensibility points. The sample shows how to write a basic WPF application for a managed proprietary language by using IronPython as an example. The sample also illustrates how to handle events by using EventBindingProvider.

2.2. Windows Communications Framework (WCF) Extensibility
There are three new samples that illustrate WCF extensibility. These samples demonstrate the following functionality:

  • Enumeration and manipulation of service references in a project.
  • Use of WSDL/policy import extensions, plus IWcfReceiveContextInformation.
  • Extending the "Discover" button with new drop-down items.

2.3. Expression Evaluator
Language integrators require an expression evaluator (EE) to work in the context of their programming language. We have created a new sample that shows how to write a basic EE for a managed proprietary language by using IronPython as an example.

2.4. Data Designer Extensibility (DDEX)
Five new Data Designer Extensibility (DDEX) samples illustrate implementing the following:

  • A very simple DDEX provider based on the .NET Framework Data Provider for SQL Server.
  • A DDEX provider based on the .NET Framework Data Provider for SQL Server that supports all common data design-time scenarios.
  • A DDEX provider based on the .NET Framework Data Provider for SQL Server with "finishing touches" that make the provider integrate well into the Visual Studio design-time experience.
  • A complete, registry-based DDEX provider based on the .NET Framework Data Provider for SQL Server.
  • A complete VSPackage-based DDEX provider based on the .NET Framework Data Provider for SQL Server.
  1. The Visual Studio Integration Package Wizard now supports the addition of an Integration Test project to the solution. The Integration Test project uses the Visual Studio integrated development environment (IDE) host type to launch and run tests inside Visual Studio. This feature lets you automate testing for your packages.

  2. Help Integration Wizard is now functional.

  3. Support for RANU (Run As Normal User) has been added for DSL Tools. You are no longer required to log in as an administrator, and on Windows Vista you are no longer required to elevate rights and permissions. All new DSL solutions that are unfolded by the wizard are configured to run as a normal user, and you can compile, execute, and debug them without administrative rights. There is no longer any machine-wide collateral damage from experimenting with the DSL Tools to create test languages that you eventually want to discard. A guide for migrating projects that were created with earlier versions of DSL Tools can be found in the folder \VisualStudioIntegration\Tools\DSLTools.

  4. All branding is changed to the official Visual Studio 2008 release name (instead of Visual Studio Code Name "Orcas").

Download:
http://www.microsoft.com/downloads/details.aspx?FamilyID=d9000e2c-bd3f-4717-a181-723960814e16&DisplayLang=en