Microsoft Technology Licensing, LLC

John Joseph Rivard

Sam Spencer

Brian Robert Crawford

Izydor Gryko

Stephen Wharton Provine

Michael Eng

Li Zhang

Patrick Henri Dussud

Michael M Magruder

Vance Palmer Morrison

Niklas Gustafsson

C Douglas Hodges

Steven P Anonsen

Sean Edwin Trowbridge

James S Miller

John Lawrence Hamby

Peter A Hallam

Elliot H Omiya

Bradley Bartz

David Paul Hill

Scott Michael Wiltamuth

James H Hogg

Jason L Zander

William G Evans

Paul Yuknewicz

Thomas E Quinn

Douglas Jay Rosen

Eric Hyde Carter

Ian H Carmichael

Steven J Steiner

Mario Chenier

Robert Allan Brigham, Ii

Jennifer A Hamilton

Paul Stanley Kuklinski, Jr

William Edwin Hiebert

Sean Conway Draine

James Roy Schmelzer, Jr

Lawrence B Sullivan

Habib Heydarian

James Gordon Cantwell

Svetlozar Emilov Keremidarski

Joseph Tyler Whitney

Adam Krantz

Shamez Rajan

Baiju K Nair

Michal Sampson

Stephen W Provine

A user interface can be maintained in a responsive state on a user interface thread while synchronous application logic is running on a background thread. The application logic can access an object on the background thread, and the user interface can access the same object on the user interface thread. Additionally, a request for work to be done on an object can be received. If the request is to be dispatched to a background thread, then the work can be dispatched to the background thread without blocking the user interface thread. However, if the request is to be dispatched to the user interface thread, then the work can be dispatched to the user interface thread, and the background thread can be blocked.

Responsive user interface with background application logic for working on an object

Techniques for determining and tracking dependent properties for a calculated property are provided. A request for a value of a first property is received. The value for the first property is calculated, including accessing values for one or more properties used to calculate the value for the first property. The accessing of the values for the one or more properties may be detected, and the one or more properties may be tracked as dependent properties for the first property in a first set of dependent properties. A change in the value of a second property may subsequently be detected. If the second property is determined to be included in the first set of dependent properties, the value of the first property is invalidated.

Runtime dependency analysis for calculated properties

Systems and methods for using private keys in software development that minimizes the risks of the private key being lost or stolen. A strong name consists of the assembly's identity, e.g., its simple text name, version number, and culture information (if provided), plus a public key and a digital signature. It is generated from an assembly file using the corresponding private key. The private/public key pair is persisting in a password-encrypted file using a standard encryption format that can be made available to everyone. The first time any subsystem of the development environment requires use of the private key contained in an encrypted file format, the developer is prompted to provide the password to decrypt the key. The user supplies the password and the public/private key is imported into a non-exportable key container in the local cryptographic store.

Persisting private/public key pairs in password-encrypted files for transportation to local cryptographic store

The isolation of user-interactive components form the logical components of an exemplary computing application environment is provided. In an illustrative implementation, an exemplary computing application environment comprises one or more user interface (UI) elements that run on an exemplary user-interface processing thread and application logic that illustratively operatively runs asynchronously on at least one other processing thread. In an illustrative implementation an isolation boundary is provided between an exemplary user interface and the application logic of the exemplary computing application environment. In the illustrative implementation, the isolation boundary can comprise an asynchronous view contract comprising a channel between an exemplary view layer of an exemplary user interface (e.g., one or more user-interactive components) and application logic.

Isolation of user-interactive components

A client or Web application assembly or group of assemblies is bound to a version of shared assemblies associated with a particular targeted execution environment. The targeted execution environment (and thus the version of shared assemblies associated with it) may be selected or detected. A file such as a configuration file is automatically modified. The selected or detected execution environment may be the same as or different than the local version. The client or Web assembly is automatically bound to the targeted shared assemblies. A user interface enables the selection of a particular execution environment. Alternatively, a user interface informs of the detected targeted execution environment and enables the reconfiguration of the Web assembly. This invention provides a mechanism and process for maintaining legacy software after a new software development tool is installed, without deploying a new version of shared assemblies.

Cross version customization of design environment

A system and method of providing edit and continue support in a software program debugging environment. 'Edit and continue' support allows a user (e.g., programmer and/or developer) to update the code and/or data structure(s) of an executing program while it is running. After the user has finished editing their code and resumes execution, an integrated development environment (IDE) propagates the edit(s) into a common language runtime (CLR) environment before continuing. Therefore, from the CLR environment's perspective, an edit is a block of intermediate language code (IL) and/or metadata that is inserted into a running process. Moreover, The IDE can facilitate: determining 'legality' of an edit; building the edit; sending the edit to the CLR environment; and/or, facilitating the CLR environment switch execution to the edited code.

Method and system for program editing and debugging in a common language runtime environment

Specific tasks associated with debugging are performed in the background, prior to a user of an application development tool invoking the debugger. The tasks including (1) starting a hosting process, (2) loading a hosted runtime environment (e.g., .NET runtime) in the process, and (3) attaching a debugger to the hosting process, are performed in the background before the user commences debugging. Once the user invokes the debugger, the user's application is executed and debugged. Thus, the perceived time to start debugging is greatly reduced.

Method and system for fast application debugging

Architecture for developing an application. The architecture provides an entry point to commonly used classes of an application development framework. A developer begins a project which predefines a set of collection classes. An exposer component includes an identifier component and a compiler for generating accessors to the collected classes. The identifier uses an attribute on a collection class which a compiler dynamically extracts in order to generate accessors to the desired collected classes and compiles the generated collection classes for use in the namespace.

Extensible productivity tool for exposing common classes in application building

Interoperability of a first framework or platform (e.g., COM) and a second different framework or platform (e.g., .NET) is provided via an attribute mechanism. The attribute mechanism is provided in a non-COM based platform (e.g., .NET) to expose classes to COM. In this manner, a compiler (e.g., the .NET compiler) creates class and events interfaces and adds attributes to the class and interfaces as appropriate for correct interoperability and marshaling. By adding this attribute mechanism to a class in .NET, the .NET compiler is able to use the class declarations (such as public methods, properties, and events) to automatically generate a class interface and an events interface, including appropriate dispatch IDs and GUIDs. Validation is performed on the class being mapped to provide an indication, such as an error message or warning, to the user that the underlying framework marshaling layer cannot marshal certain data types as desired or expected.

Interoperability of objects between various platforms

Growing community of inventors

Redmond, WA, United States of America

John Joseph Rivard