Microsoft Technology Licensing, LLC

Saji Abraham

Sermet Iskin

Harris Syed

Tassaduq Basu

Max A Feingold

Andrew D Milligan

Hart Wilson

Liang Zhao

Lin Xu

Donald F Box

Jackson Michael Davis

John David Doty

Brent Rector

An isolation execution environment provides an application with limited resources to execute an application. The application may require access to secured resources associated with a particular trust level that are outside of the isolation execution environment. A trust activation engine determines the trust level associated with a request for a resource and operates differently based on the trust level. A broker process may be used to execute components providing access to resources having a partial trust level in an execution environment that is separate from the isolation execution environment.

Trust level activation

The claimed subject matter provides for systems and/or methods for debugging a computer-executable file. The computer-executable file may be executing in a first runtime environment and located in a first process. The file may further comprise on object having a proxy in that first runtime environment. One method embodiment comprises the steps of debugging said computer-executable file; detecting a proxy for an object called by said file; decoding said proxy to obtain physical information regarding said object; returning said physical object information; and transforming said physical object information into logical object information. In addition, one embodiment of a system is provided that comprising a debugger, said debugger debugging client code; a proxy decoder, said proxy decoder providing information to said debugger about the object pointed by said proxy; and an abstraction transformation, said abstraction transformation transforming physical expressions of a proxy into higher level logical expressions.

Debugging object abstractions

Example embodiments of the present invention provide a mechanism for allowing developers to define new interfaces and insert custom translational code that implements these new interfaces for legacy components that otherwise cannot communicate in a web service environment. These new interfaces are then exposed to the web service client in such a way that abstracts the web service client from the legacy components interfaces. The objects that implement the new interfaces are referred to herein as 'service surrogates' and the new interfaces will be commonly referred to as a, 'surrogate interfaces.' These surrogate interfaces may be initialized along with an instance of the service surrogate upon startup of an application that offers the services. In addition, a dynamic web service can simultaneously run along with the service surrogate for those services that may not need the features offered by the service surrogates.

Generating a dynamic web service and dynamic service surrogate for legacy application components

The present invention provides a mechanism that allows an administrative event to trigger or cause the generation of a dynamic web service during initialization of legacy application components. Similar to other types of static tooling approaches, the dynamic approach&#x2014;as supported herein&#x2014;uses available metadata describing an interface for communicating with legacy components. Rather than generating and manifesting the web service via tooling on a one time or occasional bases, however, example embodiments provide for the generation of the web service by the supporting infrastructure as a standard part of application initialization. Upon stopping the application, a termination sequence is provided that stops the corresponding dynamic web service and deletes the web service description used to generate the dynamic web service. Accordingly, every time the application is started the available metadata will need to be consulted and a consistent service will be built on-the-fly.

Dynamic service generation for legacy components

Growing community of inventors

Kirkland, WA, United States of America

Saji Abraham