The patent badge is an abbreviated version of the USPTO patent document. The patent badge does contain a link to the full patent document.
The patent badge is an abbreviated version of the USPTO patent document. The patent badge covers the following: Patent number, Date patent was issued, Date patent was filed, Title of the patent, Applicant, Inventor, Assignee, Attorney firm, Primary examiner, Assistant examiner, CPCs, and Abstract. The patent badge does contain a link to the full patent document (in Adobe Acrobat format, aka pdf). To download or print any patent click here.
Patent No.:
Date of Patent:
Apr. 06, 2010
Filed:
May. 14, 2003
Paul J. Yuknewicz, Redmond, WA (US);
Scott M. Wiltamuth, Seattle, WA (US);
John J. Rivard, Redmond, WA (US);
Bradley J. Bartz, Lynnwood, WA (US);
Izydor Gryko, Sammamish, WA (US);
Michael Eng, Issaquah, WA (US);
William E. Hiebert, Redmond, WA (US);
Baiju K. Nair, Redmond, WA (US);
Paul J. Yuknewicz, Redmond, WA (US);
Scott M. Wiltamuth, Seattle, WA (US);
John J. Rivard, Redmond, WA (US);
Bradley J. Bartz, Lynnwood, WA (US);
Izydor Gryko, Sammamish, WA (US);
Michael Eng, Issaquah, WA (US);
William E. Hiebert, Redmond, WA (US);
Baiju K. Nair, Redmond, WA (US);
Microsoft Corporation, Redmond, WA (US);
Abstract
A client or Web application assembly or group of assemblies is bound to a version of shared assemblies associated with a particular targeted execution environment. The targeted execution environment (and thus the version of shared assemblies associated with it) may be selected or detected. A file such as a configuration file is automatically modified. The selected or detected execution environment may be the same as or different than the local version. The client or Web assembly is automatically bound to the targeted shared assemblies. A user interface enables the selection of a particular execution environment. Alternatively, a user interface informs of the detected targeted execution environment and enables the reconfiguration of the Web assembly. This invention provides a mechanism and process for maintaining legacy software after a new software development tool is installed, without deploying a new version of shared assemblies.