Microsoft Technology Licensing, LLC

Peter Christian Huene

Joshua Christopher Shepard

Shankar Vaidyanathan

Tarek Madkour

John A Cunningham

David Gray

Brian Robert Crawford

Steve Carroll

Boris V Vidolov

A primary file can be used to specify default build properties for software under development. A set of modified build properties may be stored in a supplemental file. The default build properties can be temporarily overridden with modified build properties for a given build, allowing freedom in the choice of build properties without proliferation of files used for the same purpose, which can be confusing. In addition, users can create new build commands for software under development, and associate the new commands with supplemental files. When the user invokes a new build command, the build process can override the default properties with the modified properties in the supplemental file, and then restore the defaults. Other advantages and features of the invention are described below.

Systems and methods for varying software build properties using primary and supplemental build files

Web server processes can host multiple web applications that process multiple requests from multiple clients. Recorded diagnostic information may not provide a useful separation of server execution data (e.g., functionality executed to process a request) based on a client's use of the web server process. An effective method for separating server execution data by client information is provided herein. Dye is injected into a request from a client, the dye comprises information regarding the client application making the request and a transaction (e.g., client defined set of requests) that the request is comprised within. The dye injected request is sent to a web server process (e.g., on a web server) that extracts the dye and executes the request. During execution of the request, executed functionality is associated and stored with the extracted dye. The recorded server execution data may be organized based upon the request, client, application, and/or transaction.

Dye injected request generation

Various technologies and techniques are disclosed for facilitating a feedback process regarding the impact that changes to source code will have on tests. Changes contained in at least one source code file are analyzed in combination with code coverage information contained in a data store for a plurality of tests to determine when any of the tests will be impacted by the changes. When at least one test is determined to be impacted by the changes made to the source code file, a warning notification is displayed to a user to notify the user of a possible impact of the changes on the at least one test.

Test impact feedback system for software developers

Custom build tools are integrated into a design environment build process without writing code. Properties of the tool are defined in a file describing the appropriate syntax of the tool's command line. Values are specified for a particular use of the tool in a particular project. At runtime the command line for the tool is generated from the generalized syntax as defined in the file and the stored values.

Growing community of inventors

Kirkland, WA, United States of America

Peter Christian Huene