Microsoft Technology Licensing, LLC

Chad W Royal

Anders Hejlsberg

Seth B Pollack

James E Allard

David S Stutz

Kyle W Geiger

Vincent Fernandes

Giovanni Moises Della-Libera

Shawn Patrick Burke

Christopher L Anderson

Brian Keith Pepin

Nicholas M Kramer

Sreeram Nivarthi

Mark A Boulter

Stephanie Sweeny Saad

Stephen L Rakonza

Craig Skibo

Subhag P Oak

Erik B Christensen

Gopala Krishna R Kakivaya

Yan Valerie Leshinsky

Christopher Wellington Brumme

Stephen James Millet

Michael M Magruder

Nikhil Kothari

Alex A Kipman

Raja Krishnaswamy

David Bau

Michael Joseph Toutonghi

Brian LaMacchia

Gregory Darrell Fee

Scott David Guthrie

Lance Olson

Henry L Sanders

David S Ebbo

Julie D Bennett

James S Miller

Sean Edwin Trowbridge

Travis Muhlestein

Jonathan C Hawkins

Krzysztof J Cwalina

Seth Mitchell Demsey

Brian M Grunkemeyer

Luca Bolognese

Stefan Harrington Pharies

Yung-Shin Lin

Keith W Ballinger

Loren Kohnfelder

Mark T Anders

Anthony J Moore

Jun Fang

Erik B Olson

Yann Christensen

Fabio A Yeon

Jeffrey M Cooperstein

Susan M Warren

Scott Michael Wiltamuth

James H Hogg

Jomo Fisher

Adam Wade Smith

Robert Michael Howard

Corina Eva Feuerstein

Manu Vasandani

Craig T Sinclair

Tracy Sharpe

David S Mortenson

Peter H Golde

Caleb L Doise

Alan Geoffrey Boshier

Shajan Dasan

Manish S Prabhu

Radu Rares Palanca

John I McConnell

Tarun Anand

Mark W Fussell

Suzanne Maurine Cook

Joseph L Roxe

Hany E Ramadan

Jesus Ruiz-Scougall

Omri Gazitt

Joe Dennis Long

Ramasamy Krishnaswamy

Daniel Takacs

Nithyalakshmi Sampathkumar

Jayanth V Rajan

Edward H Wayt

Daniel Dedu-Constantin

Neetu Rajpal

Blaine J Dockter

William A Adams

Mark P Ashton

Rajeev Goel

Christopher A Flaat

Architecture that facilitates management of a build process according to a level of trust of a build entity. The build process processes one or more build entities, each of which is associated with a level of trust. These associations are stored in a policy file that is run against the one or more entities at the start of the build process. The build process runs at a permission level that is representative of the lowest level of trust of the build entities. The levels of trust include at least trusted, semi-trusted, and untrusted levels. If the lowest level is untrusted, the build process fails, and the user is notified.

Architecture that restricts permissions granted to a build process

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

A user can package one or more file(s) into a group and specify that the group is to be converted into a template. An IDE process can automatically index the content of the group and create a metadata file to represent the indexed content. The indexed file group and metadata can serve as a template for creating new files with properties of the original file(s). Completed templates are packaged together in one file such as a .zip file. Completed templates can be added to a User Interface (UI) accessible location, such as a collection of templates accessible to UI dialog processes for opening new files. The metadata file authored in a declarative programming language such as XML.

Systems and methods for creating and providing templates in a single file

Application program interface for network software platform

A method and system for invoking by a client computer system of a function of an object of an object class provided by a server computer system. The client sends a request to a server that comprises a Universal Resource Locator (&ldquo;URL&rdquo;) that identifies a script, an object class, and a function of the object class to invoke. In response to receiving the request, the server starts the script and transfers control to the script. The script instantiates an object of the object class identified in the URL of the received request and invokes the function identified in the URL of the received request. The invoked function performs the behavior of the function, creates a response to be sent to the client, and sends the response to the client. The response contains state information describing a state of the object after the behavior of the function is performed. When the client subsequently sends a request to invoke a function of the object class, the state information is included in the request so that the function can perform its behavior based on the state information.

Method and systems for invoking methods of objects over the internet

Method and apparatus for encapsulating a reference to a method in object-based programming systems and ensuring that the reference is safe are disclosed. The method of encapsulation provides for: a) defining an entity that defines the shape of the method to be referenced; b) obtaining a reference to a method; c) storing this reference in arbitrary data structures; d) passing the reference to code written by other parties; e) enabling invocation of the method by anyone holding the method reference; and f) enabling the holder of a method reference to determine the target object and method being referenced. These objectives are achieved in a strongly typed manner, making it possible for: a) developers to learn of type mismatch problems early (at compile-time) rather than late (at run-time); and b) development tools to present information to developers about the shape of components that use delegates. In addition, a model of event based programming is disclosed, wherein event-related code can be encapsulated in delegates.

Method, software and apparatus for referencing a method in object-based programming

Method and system for invoking methods of objects over the internet

A method and system for invoking by a client computer system of a function of an object of an object class provided by a server computer system. The client sends a request to a server that comprises a Universal Resource Locator ('URL') that identifies a script, an object class, and a function of the object class to invoke. In response to receiving the request, the server starts the script and transfers control to the script. The script instantiates an object of the object class identified in the URL of the received request and invokes the function identified in the URL of the received request. The invoked function performs the behavior of the function, creates a response to be sent to the client, and sends the response to the client. The response contains state information describing a state of the object after the behavior of the function is performed. When the client subsequently sends a request to invoke a function of the object class, the state information is included in the request so that the function can perform its behavior based on the state information.

Growing community of inventors

Redmond, WA, United States of America

Chad W Royal