Partager via

Visual Studio 2010 Feature Pack 2– Pre-requisite hotfix details

  • Article

Visual Studio 2010 Feature Pack 2 is now available. This required some changes in the core Visual Studio 2010 product to enable the new functionality. We have created a hotfix (KB2403277) for these product changes. A detailed description of each change is given below.

 

Fix 1-

Issue/Description: A new startup attribute has been added in the Coded UI Test builder’s configuration file to enable loading of mixed-mode assemblies in CodedUITestBuilder process. This fix is done to support loading of assemblies that are built on previous .net versions (.e.g. .net 2.0). For more details, refer https://msdn.microsoft.com/en-us/library/bbx34a2h(VS.100).aspx.

Files affected: CodedUITestBuilder.exe.config

Fix 2 –

Issue/Description: Some changes has been done in to improve the following experiences/feature:

1. Navigation across controls of different UI Technology

2. Search of nameless controls for custom plug-ins.

Files affected:

· Microsoft.VisualStudio.TestTools.UITest.Playback.Engine.dll

· Microsoft.VisualStudio.TestTools.UITest.Extension.MSAA.dll

· Microsoft.VisualStudio.TestTools.UITest.Framework.dll

Fix 3-

Issue/Description: In Visual Studio 2010, if a user tries to locate a control inside an application that is not in focus, the Coded UI Test builder will not bring the application to the focus. This issue is fixed now and the application will get the focus while Coded UI Test builder is locating the control.

Files affected:

· Microsoft.VisualStudio.QualityTools.CodedUITest.Controls.dll

Fix 4-

Issue/Description: By default all the custom plug-ins written by user have to be put in “%commonprogramfiles%\microsoft shared\VSTT\10.0\UITestExtensionPackages” (or “%commonprogramfiles(x86)%\microsoft shared\VSTT\10.0\UITestExtensionPackages” in case of 64bit machines) folder. User will face build errors for his plug-in assemblies in following scenarios:

1. User has created a Coded UI Test project using his custom plugin on 64bit box and now he is trying to use the same project on a 32bit machine or vice versa.

2. If system drive changes across machines.

Following registry key has been added to remove the dependency on reference paths added in Coded UI Test project file.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319\AssemblyFoldersEx\VSTT v10.0 Reference Assemblies (or HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319\AssemblyFoldersEx\VSTT v10.0 Reference Assemblies in case of 64bit machine)

 

Deepak Singhal

Visual Studio ALM.

Comments

  • Anonymous
    November 30, 2010
    Has it become much more easier to navigate through MS Office controls?

  • Anonymous
    December 19, 2010
    No. We have not done anything specific to this.

  • Anonymous
    July 04, 2012
    Hi, The fix mentioned above in the Microsoft.VisualStudio.TestTools.UITest.Framework.dll was broken and it results a crash of Coded UI Test builder... I have posted the Stack trace here.. social.msdn.microsoft.com/.../04f3d110-ed49-49e8-8b20-8a465715bfcc