Related Resources
Scenarios and objectives
Here is a installation notes for Visual Studio Team Foundation Server 2010.
This article is based on Visual Studio Team Foundation Server 2010 (30319.01.10).
1Launch setup exe file. Just click [Next]. 
2Read the license agreement and choose your answer. Click [Next]. 
3Set destination folders and check components you would like to install. Normally, default is enough. Click [Next]. 
4The installation starts immediately. 
5That's all for installation. You can check the release notes. 
For more informations
Related Resources
Here are posts for Microsoft Connect.
SQL Server 2005 Tools Windows Installer dialog runs and errors when building a Setup project (VS 2008)
http://connect.microsoft.com/VisualStudio/feedback/details/327997
Windows Installer dialog runs and errors when building a Setup project
http://connect.microsoft.com/VisualStudio/feedback/details/113155
Scenarios and objectives
Even if you use Visual Studio 2010, the phenomenon is completely same. Probably the same reason causes this same result.
Also, fortunately, the workaround still affect.
Microsoft said:
Installing a later version of mergemod.dll seems to fix the issue. You can install a later mergemod.dll by installing Orca:
http://connect.microsoft.com/VisualStudio/feedback/details/113155
So, I downloaded a newest Windows 7 SDK which contains ORCA and installed it. Success!
Windows 7 SDK
Here is a installation note for Windows 7 SDK.
Microsoft Windows SDK for Windows 7 and .NET Framework 4
1Download web setup exe file and double click it. Just click [Next]. 
2Read the license agreement and choose your answer. Click [Next]. 
3Set destination folders. Click [Next]. 
4Check components you would like to install. Normally, default is enough. Click [Next]. 
5Confirm and click [Next]. 
6The installation starts immediately. 
7That's all for installation. You can check the release notes. 
Orca
Next step is a installation of Orca.
hint
Default path of Orca (Windows 7 SDK)
%Program Files%Microsoft SDKs\Windows\v7.1\Bin\Orca.Msi
1Double click .msi file. Just click [Next]. 
2Read the license agreement and choose your answer. Click [Next]. 
3Choose installation type. [Complete] is best. Click [Next]. 
4Confirm and click [Next]. 
5The installation starts immediately. 
6That's all for installation. 
Related Resources
Objective
Our final goal is to catch the history and growth curve of the source code. .Metrix has two main features. 
How to use [History commenter]
One of main feature is code history commenter. In [TLC.com .Metrix Options], there are 4 types of code history keyword. 
Revising a code
1 If you'd like to revise your code, type ['&U] (by default) and hit enter. 
2 Then you get special comment clip. 
3 Put old source codes into the clip and commentize it then add new codes inside of the clip. 
It will be revise mark for analyzer. In option setting, you can change a keyword for each comment type. Also you can change a comment string and start-end mark, too.
Reason for change
If you turn on [Ask the reason for each change] option, .Metrix asks you a reason of change automatically and add it into comment. 
Bug tracking
Bug mark helps you to log a bug.
If you would like to log a bug, just add bug mark after keyword (for example, ['&U@] will be bug fix revising). 
How to use [History commenter]
Code analyzer analyzes your code's basic metrix.
Growth curve
It shows all code, code (body), comment and blank. Also it shows history of code change marked with history commenter.
Here is an example which is marked last commenter's example. There is 4 lines updated code. 
Bug tracking
Also it shows history of bug count marked with history commenter. 
Options
Options are in [Analyzer] tab.
If you turn on [Analyze code on Build], .Metrix walk-through your code and save metrixes.
If you turn on [Ignore generated code], analyzer skips [.designer.vb] files.
If [Display report after build] is on, metrix report will be shown automatically.
At last, [Target date] filters a start point of history and bug count on next analyze.
Additional function: [Code snippet]
[Use code snippet] provides simple method to resist and use a snippet.
Insert a code snippet
1 If you'd like to insert code snippet, type ['&S] (by default) and hit enter.
2 You can select which code should be inserted. Click [OK]. 
3 Selected code snippet will be insert. 
Add new code snippet
1 In [TLC.com .Metrix Options], click [Edit] button.
2 You can [Add], [Edit] and [Delete]. 
3 You should fill [Keyword] and [Code snippet] at least. 
For more informations
Scenarios and objectives
This article describes installation of TLC.com dotMetrix 4.0 Beta1.
This article based on TLC.com dotMetrix 4.0 Beta1 version.
Related Resources
Enum
Here is a step-by-step installation for TLC.com .Metrix 4.0 Beta1. The installation requires administrator login.
1 Download .msi file and double click it. Just click [Next]. 
2 Select installation folder and choose user it will be installed. Then click [Next]. 
3 Confirm and click [Next]. 
4 The installation starts immediately. 
5 If you face UAC window, click [yes]. 
6 That's all for installation. 
Check
If successfully installed, you will see a .Metrix menu on [Tools] option.
See also
TLC.com .Metrix 4.0 Beta1
TLC.com .Metrix 4.0 Beta1 release note
[Installation notes]
The installation requires administrator login. If you get UAC window, permit it. If a previous version of .Metrix is already installed, please remove it. If you receive notification that the installation failed, refer to the following log file.
%Program Files%\TimberLandChapel.com\.Metrix4.0.log
[Requirement and support]
- .Metrix 4.0 requires Visual Studio 2010.
- .Metrix supports for Visual Studio 2010 and Visual Basic.NET.
Visual Studio is product of Microsoft.
[End user license agreement]
1. AGREEMENT.
You may install .Metrix on a single computer. If you do not agree to the terms of this Agreement, you may not use .Metrix.
2. COPYRIGHT.
.Metrix is owned by TimberLandChapel.
3. "AS IS"
TimberLandChapel provides .Metrix "AS IS" WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES INCLUDING, BUT NOT LIMITED TO, IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT.
4. Version
.Metrix 4.0 is currently in beta version. If you encounter a bug, please wait later version or feedback to me. This version supports only primitive syntaxes based on VB.NET 2005.
[How to use]
.Metrix has two main features. Our final goal is to catch source code history and curve of growth.
1. History commenter
One of main feature is code history commenter. In [TLC.com .Metrix Options], there are 4 types of code history keyword. If you revise your code, type ['&U] (by default) and hit enter. Then you get special comment clip. Put old source code into clip and commentize it and add new code inside of clip. It will be revise mark for analyzer. In option setting, you can change a keyword for each comment type. Also you can change a comment string and start-end mark, too.
If you turn on [Ask the reason for each change] option, .Metrix asks you reason of change automatically and add it into comment.
Bug mark helps you to log a bug. If you would like to log a bug, just add bug mark after keyword (for example, ['&U@] will be bug fix revising).
2. Code analyzer
Code analyzer analyzes your code's basic metrix. It shows all code, code (body), comment and blank. Also it shows history of code change marked with history commenter and bug count.
Options are in [Analyzer] tab.
If you turn on [Analyze code on Build], .Metrix walk-through your code and save metrixes.
If you turn on [Ignore generated code], analyzer skips [.designer.vb] files.
If [Display report after build] is on, metrix report will be shown automatically.
At last, [Target date] filters a start point of history and bug count on next analyze.
3. Others
[Use code snippet] provides simple method to resist and use a snippet.