Microsoft Technology Licensing, LLC

Manish S Prabhu

Gopala Krishna R Kakivaya

Jonathan C Hawkins

Caleb L Doise

Tarun Anand

Erik B Christensen

Anders Hejlsberg

Christopher Wellington Brumme

Michael M Magruder

Raja Krishnaswamy

David Bau

Brian LaMacchia

Lance Olson

Henry L Sanders

David S Ebbo

Julie D Bennett

James S Miller

Sean Edwin Trowbridge

Travis Muhlestein

Krzysztof J Cwalina

Seth Mitchell Demsey

Brian M Grunkemeyer

Christopher L Anderson

Shawn Patrick Burke

Stefan Harrington Pharies

Yung-Shin Lin

Loren Kohnfelder

Anthony J Moore

Erik B Olson

Yann Christensen

Fabio A Yeon

Jeffrey M Cooperstein

James H Hogg

Corina Eva Feuerstein

Craig T Sinclair

Adam Wade Smith

David S Mortenson

Shajan Dasan

Alan Geoffrey Boshier

Radu Rares Palanca

Suzanne Maurine Cook

Joseph L Roxe

John I McConnell

Joe Dennis Long

Ramasamy Krishnaswamy

Hany E Ramadan

Jesus Ruiz-Scougall

Jayanth V Rajan

Daniel Takacs

Gregory Darrell Fee

David Owen Driver

Stephen Peter De Jong

Petrus L Obermeyer

Yan Valerie Leshinsky

Stephen James Millet

Giovanni Moises Della-Libera

Nikhil Kothari

Scott David Guthrie

Luca Bolognese

Keith W Ballinger

Brian Keith Pepin

Mark T Anders

Jun Fang

Susan M Warren

Robert Michael Howard

Manu Vasandani

Nicholas M Kramer

Chad W Royal

Mark W Fussell

Omri Gazitt

Mark A Boulter

Sreeram Nivarthi

Nithyalakshmi Sampathkumar

Daniel Dedu-Constantin

Neetu Rajpal

Blaine J Dockter

William A Adams

Mark P Ashton

Subhag P Oak

Matthew R Smith

George D Fee

A system and method for facilitating interactions between two or more entities where the entities have different versions of a data type is provided. The system includes a data type identifier that can identify whether interacting entities have a mismatched resolvable data type and a data type resolver that can resolve the data types by employing features appearing in the different resolvable data types that are common between the data types. The system employs a resolvable data type that includes attributes, methods and metadata, where the metadata describes the resolvable data type, its attributes and/or its methods. The resolvable data type may be associated with a proxy. The resolvable data type may also be adapted to be incrementally extended on an as-needed basis.

Distributed types and proxy refinement

An application program interface (API) provides a set of functions for application developers who build Web applications on Microsoft Corporation's .NET&#x2122; platform.

Computing system and method for allowing plurality of applications written in different programming languages to communicate and request resources or services via a common language runtime layer

An application program interface (API) provides a set of functions, including a set of base classes and types that are used in substantially all applications accessing the API, for application developers who build Web applications on Microsoft Corporation's .NET&#x2122; platform.

Application program interface for network software platform

A system and method for providing a pluggable channel that can be employed to customize data communications associated with a remote method call is provided. The system includes a pluggable channel that can interact with sinks (e.g., message sinks, security sinks, transports sinks) that implement object-oriented interfaces that can be employed by a distributed object system. The system also includes a selector that can select and associate sinks with the pluggable channel, which facilitates providing a customized, pluggable channel on a per proxy basis.

Remote method calling through pluggable channels

A system and method that provides remoting services in a distributed object system is provided. The system includes a remote object monitor and a remote object manipulator. The remote object monitor can provide a human readable reference to a remote object, where the human readable reference is a URL (Uniform Resource Locator) and can include protocol information, protocol data, an application name and an object URI (Uniform Resource Identifier). The remote object monitor can also provide metadata concerning a remote object, where the metadata can include information concerning interfaces implemented by a remote object, the type of a remote object, the class hierarchy of a remote object, methods implemented by a remote object, properties implemented by a remote object and attributes implemented by a remote object. The remote object monitor can also provide entry points and code interception for custom attribute based activation processing that can be performed before, after and/or substantially in parallel with non-attribute code associated with a remote object. The remote object monitor can also monitor and/or control the lifetime of a remote object, using, for example, a lease manager. The remote object manipulator can also update metadata concerning a remote object and can control the lifetime of a remote object via a lease manager, for example.

Remoting features

Pluggable channels

Growing community of inventors

Redmond, WA, United States of America

Manish S Prabhu