Microsoft Technology Licensing, LLC

Christopher Joseph Burrows

Mads Torgersen

Samuel Ng

James J Hugunin

Anders Hejlsberg

Matthew J Warren

C Douglas Hodges

Rahul Sudhir Kumar

Neal M Gafter

Izydor Gryko

Lucian Wischik

Robert Eric Lippert

Anson Tsao

Joshua Christopher Shepard

Alex Christopher Turner

Kevin Perry

Svetlozar Emilov Keremidarski

Martin Maly

Ryan Molden

Diane Melde

Jemy Huang

A static type, called 'dynamic', is introduced into a statically bound programming language. An expression or subexpression that is defined as a static type called 'dynamic' in the source code of a program written in the statically bound programming language, is bound based on its runtime type instead of on its compile time type. Binding can be performed based on a mixture of compile time and runtime types that are based on the specification of types of expressions in source code. This type of binding is called hybrid binding. Operations are bound using the runtime type of constituent expressions (i.e., the runtime type of a receiver, an argument, or an operand) typed as dynamic and the compile time type of static constituents. If any constituent expression of an operation is dynamic, binding occurs at runtime instead of at compile time.

Dynamic binding directed by static types

Compile-time context information is captured and provided to a runtime binder for dynamic features in programming languages. For example, a C# run-time binder uses the information to perform a run-time bind with semantics matching the compiler's binding behavior. Dynamic programming language features supported relate to compound operations, events, delegates, member accessibility, dynamic-typed objects, structs passed by ref, arguments passed by name rather than position, extension methods, conditionally compiled methods, literal arguments, overflow checking, dynamic indexed properties, dynamic method groups, and static method groups.

Compile-time context for dynamically bound operations

Techniques are described for representing commands of a user interface of an application. One or more command descriptions for one or more commands are received. Each of the command descriptions has one or more properties and represents an instance of one of the commands. One or more command group descriptions for one or more command groups are received. Each of the command group descriptions has one or more properties, represents an instance of one of the command groups at a level in a group hierarchy, and specifies one or more group members. Each of the group members represents a derived instance of one of the commands or a derived instance of one of the command groups. Properties of each derived instance of a command and each derived instance of a command group inherit properties from one or more ancestor instances.

Techniques for representing and organizing user interface data

An extensible project system for software development is provided by allowing a flavor, with a specific purpose, to be applied to a base project system. More than one flavor may be applied. Where components are distributed objects, such as where COM (component object model) is used, the project system is assembled by aggregation of a base project object, which contains some data for creating a project system with a flavor object, which modifies the project system. The base project object is the participating object in the aggregation and the flavor object is the controlling object. Multiple flavors may be applied to create a project system intended for multiple purposes, corresponding to the applied flavors.

Reusable customized project system

Growing community of inventors

Seattle, WA, United States of America

Christopher Joseph Burrows