Microsoft Technology Licensing, LLC

Unnikrishnan Ravindranathan

Harikrishna Menon Ajith Kumar

Brian Keith Pepin

Charles P Jazdzewski

Kenneth Lawrence Young

Christian Bernd Schormann

Mark A Boulter

David William Shoots

Fabian Toader

Gary Linscott

James Nakashima

Steven Brix Kirbach

Jeffrey Walter Kelly

Christophe Philippona

Alan J Gasperini

Daniel Zilcsak

Juraj Hlavac

Technologies are disclosed for providing developers with rule output indicating that issues are or may be present in the code they are developing. Such rule output can include or be accompanied by guidelines and/or best practices structured to aid developers in becoming aware of and resolving the issues. In one example, this involves identifying the issues, making available a mechanism of further investigating the issues, and providing best practices and/or recommended solutions for the issues. Finally, the technologies disclosed may automate application of the recommended solutions. The notifications and accompanying guidance/automation and the like can be provided at design-time, compile-time, and/or run-time with the notifications and accompanying guidance/automation integrated into editors, compilers, debuggers, and other development environment tools providing true real-time and in situ development experience.

System for monitoring and reporting performance and correctness issues across design, compile and runtime

Tools and techniques support troubleshooting live application visuals, including transient markup expression issues in XAML or HTML. A LADRT module supports troubleshooting without pausing application execution to help inspect and modify visual construct properties, and to identify and alter source code pertaining to a selected visual construct. Changes are serialized back to the application program source code and reflected in real time in the executing application, without a rebuild. Markup annotation preserves pre-evaluation versions of markup expressions for binding, static resource identification, and custom purposes. Markup annotation also correlates visual constructs and source code. The LADRT module operates independently of debuggers, and may autoload with the application. Program project and source code changes are not required for troubleshooting capability.

Troubleshooting visuals and transient expressions in executing applications

The present invention provides technologies for forming an editing interface for editing arbitrary objects. In particular, the present invention provides system and methods for enumerating object properties, selecting a suitable pre-existing object editor and, if no such pre-existing editor is available, constructing an object editor on the fly suitable for editing the properties of the object where the object may include properties and/or collections of objects. Construction of a suitable editor is based on enumeration of object properties and on the serialization of the object using a descriptive language such as extensible markup language ('XML') or the like. Property values specified by a user via the object interface and editors are stored in a descriptive format such as XML and generally specify the initial characteristics of the object.

Arbitrary object editing

Growing community of inventors

Issaquah, WA, United States of America

Unnikrishnan Ravindranathan