Microsoft Technology Licensing, LLC

Ramasamy Krishnaswamy

Seth Mitchell Demsey

Brian M Grunkemeyer

Erik B Christensen

Anders Hejlsberg

Gopala Krishna R Kakivaya

Christopher Wellington Brumme

Michael M Magruder

Raja Krishnaswamy

David Bau

Brian LaMacchia

Lance Olson

Henry L Sanders

David S Ebbo

Julie D Bennett

Travis Muhlestein

Sean Edwin Trowbridge

James S Miller

Jonathan C Hawkins

Krzysztof J Cwalina

Christopher L Anderson

Shawn Patrick Burke

Stefan Harrington Pharies

Loren Kohnfelder

Yung-Shin Lin

Anthony J Moore

Erik B Olson

Yann Christensen

Fabio A Yeon

Jeffrey M Cooperstein

James H Hogg

Adam Wade Smith

Corina Eva Feuerstein

Craig T Sinclair

David S Mortenson

Caleb L Doise

Alan Geoffrey Boshier

Shajan Dasan

Manish S Prabhu

Radu Rares Palanca

Suzanne Maurine Cook

Joseph L Roxe

John I McConnell

Tarun Anand

Joe Dennis Long

Hany E Ramadan

Jesus Ruiz-Scougall

Jayanth V Rajan

Daniel Takacs

Gregory Darrell Fee

David Owen Driver

Christopher W Lorton

Tuan Huynh

Bruce E Johnson

Stephen Harris Toub

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

Nicholas M Kramer

Manu Vasandani

Chad W Royal

Mark W Fussell

Sreeram Nivarthi

Omri Gazitt

Mark A Boulter

Nithyalakshmi Sampathkumar

Daniel Dedu-Constantin

Neetu Rajpal

Joe Duffy

Blaine J Dockter

William A Adams

Mark P Ashton

Subhag P Oak

George D Fee

Armin Sadeghi

A cancelation registry provides a cancelation interface whose implementation registers cancelable items such as synchronous operations, asynchronous operations, type instances, and transactions. Items may be implicitly or explicitly registered with the cancelation registry. A consistent cancelation interface unifies cancelation management for heterogeneous items, and allows cancelation of a group of items with a single invocation of a cancel-registered-items procedure.

Unified and extensible asynchronous and synchronous cancelation

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

Notifications are generated in managed and native environments and propagated to an interfacing abstraction layer of native code there between. The abstraction layer assesses each received notification to determine whether the notification, or a previously received collection thereof, should be transitioned across a boundary between the managed environment and the native environment. The managed environment includes a virtual machine in a managed code portion. The native environment includes an operating system that interfaces the abstraction layer which is at a boundary between the managed code portion and the operating system. A collection of notifications are those that have been batched and/or synthesized. The abstraction layer is configured with predetermined criteria to assess whether to form a collection of received notifications and/or to prevent a transition of a notification, or collection thereof, across the boundary.

Native code exposing virtual machine managed object

One aspect relates to a process and associated apparatus that implements a user interface (UI) control within a computer environment. The computer environment includes a managed code portion and a native code portion. The implementing the UI control includes creating a plurality of control node data structures within the managed code portion. A managed UI control is virtualized within the managed code portion by associating and/or batching at least two of the control node data structures. The UI control is realized in the native code portion by migrating the managed UI control into the native code portion. In certain aspects, the UI control is populated and parented prior to the realizing.

Virtualized and realized user interface controls

Growing community of inventors

Redmond, WA, United States of America

Ramasamy Krishnaswamy