jump to navigation

Microsoft Pre-release Software Visual Studio Code Name “Orcas” – January 2007 Community Technology Preview (CTP) January 12, 2007

Posted by Patricio in Orcas, Software Engineering.
add a comment

Visual Studio code name “Orcas” delivers on Microsoft’s vision of smart client applications by enabling developers to rapidly create connected applications that deliver the highest quality rich user experiences. This new version enables any size organization to rapidly create more secure, manageable, and more reliable applications that take advantage of Windows Vista and the 2007 Office System. By building these new types of applications, organizations will find it easier than ever before to capture and analyze information so that they can make effective business decisions.

This download is the January 2007 Community Technology Preview of Microsoft Visual Studio Code-Named “Orcas”. This CTP is available in English only.

Orcas specs published January 5, 2007

Posted by Patricio in Orcas, Software Engineering, Visual Studio Team System.
1 comment so far

There are new/updated VS specs and 3 new (and 1 updated) TFS specs.

ADO.NET Samples for Visual Studio Code Name “Orcas” – October CTP December 6, 2006

Posted by Patricio in Orcas, Software Engineering.
add a comment

This CTP contains Samples for ADO.NET features in the Visual Studio Code Name “Orcas” – October CTP.
Visual Studio Code Name “Orcas” – October CTP is a prerequisite for these samples. The link to download that CTP is included in the related resources below.

Related Resources

 

  1. ADO.NET blog
  2. Data blog
  3. ADO.NET CTP MSDN Forum
  4. Visual Studio Code Name “Orcas” – October CTP download page

ADO.NET Samples for Visual Studio Code Name “Orcas” – October CTP November 6, 2006

Posted by Patricio in Orcas, Software Engineering.
add a comment

This CTP contains Samples for ADO.NET features in the Visual Studio Code Name “Orcas” – October CTP.
Visual Studio Code Name “Orcas” – October CTP is a prerequisite for these samples.

Microsoft Pre-release Software Visual Studio Code Name “Orcas” – October Community Technology Preview (CTP) October 31, 2006

Posted by Patricio in Orcas, Software Engineering.
add a comment

Visual Studio Code Name “Orcas” delivers on Microsoft’s vision of smart client applications by enabling developers to rapidly create connected applications that deliver the highest quality rich user experiences. This new version enables any size organization to rapidly create more secure, manageable, and more reliable applications that take advantage of Windows Vista and the 2007 Office System. By building these new types of applications, organizations will find it easier than ever before to capture and analyze information so that they can make effective business decisions.

This download is the October 2006 Community Technology Preview of Microsoft Visual Studio Code-Named “Orcas”.

Note: This CTP is available only as a Virtual PC image. You will need Virtual PC or Virtual Server to run this image. Depending on your hardware the download files make take between 30-60 minutes to decompress.

This CTP targets early adopters of the Microsoft technology, platform, and tools offerings. It enables developers to experience the upcoming toolset and underlying platform improvements. We designed this release to enable developers try out new technology and product changes, but not to build production systems. This limitation is fully covered in the EULA that accompanies this CTP.

The highlights of this CTP include:

  • ADO.NET 3.0 Advancements
    • Enhanced the existing .Net Data Provider to work with the new features in ADO.Net 3.0 such as LINQ and object services
    • Database and application object isolation assists in minimizing the impact of database schema changes in existing applications
    • Developers can build can create scripts as actual programs –instead of VBS scripts- that are still completely self-contained in a single file and can be trivially modified, compiled and executed in any environment that has .NET installed.
    • eSQL language support enables developers to build applications that provide users with an ad-hoc query capability.
  • LINQ over XML (XLinq)
    • Core functionality of the XLinq API such as load, modify, and save XML documents
    • Annotation support with a lightweight, typed, but general purpose annotation mechanism that can be used to associate information such as line numbers, schema types, and application objects with specific nodes in an XLinq tree.
  • Multi-targeting
    • Support multitargeting within the IDE by enabling Visual Studio to leverage MSBuild using the tasks and targets that were shipped in Visual Studio 2005. Additionally, command line solutions will build using the toolset appropriate for the .NET Framework version that is being targeted.
  • Improved 64bit application working set
    • On 64bit systems better code layout in system assemblies will result in improved working set.
  • Lightweight reader/writer lock with deadlock-free upgrade support.
    • The new System.Threading.ReaderWriterLockSlim class supports basic read and write locks, allowing for better scalability for read-only concurrent worker scenarios. As its name implies, this lock performs anywhere from 2x to 5x better than the existing ReaderWriterLock class, and scales better on multi-processor and multi-core machines. This type also supports upgradeable-read support: if code needs to inspect some state before deciding to acquire the write-lock, upgradeable-reads allow concurrency-safe reading with an optional deadlock-free upgrade to write. Recursion is also disabled by default, helping to write correct code, with an optional recursive mode turned on at lock instantiation time.
  • A high performance trace listener which logs XML to disk in the event schema.
    • The System.Diagnostics.EventSchemaTraceListener is the first listener in the namespace which is highly tuned for logging performance. Similar to the XMLWriterTraceListender, this trace listener logs XML to disk. In particular, this type logs in the event schema, which is shared by some other new technologies. This tracelistener has performance which is drastically improved over previous logging tracelisteners, especially on machines with multiple processors. Additionally, this is the first trace listener which allows many different disk logging options, such as circular logging across multiple files
  • Getting VSTO and/or controls off machine policy/legacy policy migration
    • Developers of managed browser controls can now create manifests for their controls and Authenticode sign the manifests. An enterprise can then choose to trust the controls by manifest signature, rather than modifying CAS policy. This provides a bridge from the CAS policy trust model to the trusted publisher model in Orcas.
  • Security Platform Parity – Suite B support: AES
    • Cryptography developers can now use the FIPS-certified implementations of advanced SHA hashing algorithms and AES encryption algorithm in managed code. These classes follow the same familiar patterns as the existing cryptography algorithms, making it easy for developers to use the new classes right away.
  • A new date time data structure that can specify an exact point in time relative to the UTC time zone.
    • The current DateTime is insufficient at specifying an exact point in time. DateTimeOffset represents a date time with an offset. It is not meant to be a replacement for DateTime; it should be used in scenarios involving absolute points in time. DateTimeOffset includes most of the functionality of the current DateTime API and allows seamless conversion to DateTime as well.
  • New IO types that expose almost all pipe functionality provided by Windows.
    • Pipes can be used to achieve inter-process communication (IPC) between any process running on the same machine, or on any other windows machine within a network. We’ve added managed support for both anonymous pipes and named pipes. Anyone familiar with streams should be comfortable using these new APIs to achieve IPC.
  • A new high performance set collection.
    • HashSet is a new generic collection that has been added to the System.Collections.Generic namespace. It is an unordered collection that contains unique elements. In addition to the standard collection operations, HashSet provides standard set operations such as union, intersection, and symmetric difference.

The relationship between .NET 2.0, .NET 3.0, VS2005, “Orcas”, ATLAS, C#3, VB9, LINQ and ADO.NET vnext October 3, 2006

Posted by Patricio in Coding, Orcas, Software Engineering, WCF, WF, WPF.
4 comments

.NET 3.0 was a wierd marketing move because it sure as heck sounds like it’s a whole new version of .NET, but it’s really not.First a pretty picture:

The Framework

.NET 3.0 is.NET 2.0 plus the four new components. Those four core technologies are called the “.NET 3.0 Components“.

When you install .NET 3.0, it will put the .NET 2.0 framework and the .NET 3.0 components on your computer. If you already have .NET 2.0, then it will just add the 3.0 components. If you have Vista, it’s all there already since those .NET 3.0 tools are a core part of Vista as well. Looking in your folders, you will see the .NET 2.0 stuff where you are used to seeing it – in Microsoft.NET\Framework\V2.0.50727. There will also be a Microsoft.NET\Framework\V3.0 folder that has just the four .NET 3.0 components in it.

Nothing in .NET 2.0 is changing.

.NET 3.0 and Vista

The .NET 3.0 components are part of Vista. So programming with these components also allows you to leverage what is new and shiny about Vista.

Visual Studio “Orcas“

Like the relationship between .NET 2.0 and .NET 3.0, so goes the relationship between Visual Studio 2005 and “Orcas“. Orcas adds stuff on to what is already in VS2005: development tools that let you work with the .NET 3.0 stuff. For example, UI tools for building XAML (“Cider“), project templates and intellisense for the components, a UI tool for WCF as well. The last is not in the current CTP, by the way. So everything you already can do with VS2005, plus more.

ATLAS

First of all, ATLAS isn’t ATLAS any more it’s “ASP.NET AJAX“. AJAX is an extension to ASP.NET 2.0 that provides client side scripting libraries. It also has ton of controls that come with it. ATLAS, err, ASP.NET Ajax is not part of any of these other releases. It is currently autonomous and it works right along with VS2005 (though it’s still a CTP). Hopefully it will RTM by the end of the year. That will be v1.0. Then it will be wrapped into Orcas and get more goodies as well.

LINQ/C#3/VB9

These will be part of Visual Studio “Orcas“.

ADO.NET vNext

It’s very tempting to call this ADO.NET 3.0, but that makes it sound too integrated with .NET 3.0 which it is wholly unrelated to. ADO.NET vNext will be fully integrated with LINQ as well as adding some other awesome data access capabilities. But it is not coming out any time soon that I know of.

In addition to what I thought I already knew, I have spent a lot of time reading through “futures” documentation on the C# , VB9 and LINQ sites, on the ADO.NET site, on the Visual Studio site, on the .NET Framework site, the ASP.NET AJAX site, in forums and in blogs written by Microsofties.

by Julia Lerman

Microsoft Pre-release Software Visual Studio Code Name “Orcas” – September Community Technology Preview (CTP) September 29, 2006

Posted by Patricio in Orcas, Software Engineering, Visual Studio Team System.
1 comment so far

The first “Orcas” public CTP release of Visual Studio is now available for download as a virtual machine from Microsoft Downloads (Download details: Visual Studio Code Name “Orcas” September 2006 CTP).

The highlights of this CTP include:

  • Improvements on the widely acclaimed Visual Studio 2005 product set
  • Significant investments in improving product quality
  • LINQ to Objects API
    • LINQ to Objects API supports queries over any .NET collection, such as arrays and Generic Lists. This API is defined in the System.Query namespaces inside System.Core.dll. Click here for more details about LINQ.
  • Partial C# 3.0 Language Support: This CTP implements some of the new language features of C# 3.0
    • Local variable type interface
    • Lambda expressions
    • Object initializers
  • Partial C# 3.0 IDE Support: In addition to the C# 3.0 language features there is partial IDE support
    • Colorization and New Keywords in Completion List
    • Edit and Continue Rude Edit Detection
  • Partial VB 9.0 Language support (Due to differences in feature delivery schedules VB implementations of the above C# features will appear in a future CTP)
    • Local variable type inference and Option Infer switch
  • VSTS Improvements in load & unit testing such as unit test for devices
  • Device development improvements
    • VSTS integration
    • Access and modify device security configuration from the IDE
  • Enables developers to build and debug a Windows Vista Application
  • Enables Visual Studio Tools for Office developers to build document-level customizations for Word and Excel 2007
  • Enables eMbedded Visual C++ 4.0 developers to use Visual Studio Code Name “Orcas” to build their existing applications
  • NET Framework improvements such as:
    • New managed add-in model enables developers to add a version-resilient extensibility model to their products.
    • Support for time zone conversion, enumeration and serialization, including cases where Daylight Saving Time rules change over time.
    • Reflection in Partial Trust, enabling sand box scenarios for all applications that depend on these features.
    • The ability to control the garbage collector’s latency mode
    • Improved CLR ThreadPool micro-performance and throughput for worker and IO completion

Microsoft Visual Studio Code Name “Orcas” Community Technology Preview – Development Tools for .NET Framework 3.0 September 7, 2006

Posted by Patricio in Orcas, Software Engineering.
add a comment

The Development Tools for .NET Framework (RC1) provides developers with support for building .NET Framework 3.0 applications using the final released version of Visual Studio 2005. This support includes XAML Intellisense support through schema extensions for the editor, project templates for the Windows Presentation Foundation and the Windows Communication Foundation, and .NET Framework 3.0 SDK documentation integration. This release contains a preview of the Visual Designer for Windows Presentation Foundation (code name “Cider”), more information can be found on the Channel 9 Wiki site for Cider. This release does not include a graphical design surface for the Windows Communication Foundation.