Public report of NetOfficeFw/NetOffice, published 17 November 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey → Signed and filed in the standard's public register, 17 November 2026, 00:52 UTC · Survey ID cd_2af3aece79d54c6abcb62696863bf070

NetOfficeFw/NetOffice

Measured 17 November 2026, 00:42 UTC, at code version 193ef43

Code coverage is not measured: Suite not runnable in-image.

Boundary Type-Coupling is not measured: Bounded contexts not declared.

Knowledge freshness is not measured: History too condensed to judge knowledge freshness.

CAI score 49.9out of 100 Provisional

The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.

A very large codebase: 1,242,095 lines of product code in 82 projects, tests not counted · Estimated rebuild effort: about 4.0 person-years · Weakest lens: Security and Compliance, 33.0

Findings by how serious they are

278 critical 2333 serious 160 minor

13 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.

This survey was produced by

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
17 November 2026, 00:42 UTC

A measurement, not a certificate. The Code Assurance Index records a number together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that implements it, and today the Canine Code Analyzer is the only one that does.

The code didn't build, so the score is provisional
We couldn't build the code: the build stopped with 960 errors. The dimensions that need a working build, such as complexity, duplication and dead code, were measured on an incomplete picture of the code, so their grades and the score are provisional. Fix the build errors and run the survey again for a final score. The first errors: CS2001: Source file 'Toolbox/Toolbox/Controls/Text/RichTextEditor.designer.cs' could not be found.; CS2001: Source file 'Toolbox/Toolbox/Controls/Text/Scroller.designer.cs' could not be found.; CS0246: The type or namespace name 'NetOffice' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'COMAddin' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'COMAddinAttribute' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'TweakAttribute' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'Tweak' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'CodebaseAttribute' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'Codebase' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'Extensibility' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'IDTExtensibility2' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'ext_ConnectMode' could not be found (are you missing a using directive or an assembly reference?); CS0538: 'IDTExtensibility2' in explicit interface declaration is not an interface; CS0246: The type or namespace name 'CustomPaneAttribute' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'CustomPane' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'ICOMObject' could not be found (are you missing a using directive or an assembly reference?)

The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸

57of 57 dimensions measured by tools.
2758of 2771 findings point to an exact file and line, so you can open each one in the code. The other 13 concern the repository as a whole, such as missing documentation.
57dimensions across 6 lenses, read from 1,242,095 lines of product code in 82 projects.
Chapters

Executive summary

NetOfficeFw/NetOffice has a provisional result, because the code didn't build. Its score is held back because we found no encryption of stored data, no key vault and no enforced HTTPS, and it has passwords or keys in the code's history. It scores 49.9 out of 100, and the ratings may change once the code builds. 245 of its 278 critical findings are security problems.

Security and Compliance, at 33.0, is the weakest lens and counts most in the score. The best first step is encrypting the sensitive stored data and keeping its keys in a vault, worth about 13.9 points. Raising Security and Compliance to 70 would lift the score to about 63.9.

106 passwords or keys in the code's history and 104 in the code are open to anyone who can read the repository. Twenty pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and nine secrets can leak from the build pipeline. Replacing each exposed password or key, pinning each tool to an exact version and limiting each secret to its own step would close these risks. Fixing the weaknesses the scanner points to would fix the four security weaknesses in the code, and passing outside input through environment variables would deal with the two pipeline steps that put outside input straight into a shell command. The 20 data fields that are written but never read need removing.

The product code is 1,242,095 lines, about €580,000 to rebuild.

A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Security and Compliance 33.0 · counts for 46%Maturity 59.6 · counts for 25%Code Health 63.7 · counts for 14%Production Readiness 66.9 · counts for 8%Architecture 71.4 · counts for 4%Performance 100.0 · counts for 2%

If Security and Compliance rose from 33.0 to 70, the lowest score rated Strong, the score would rise from 49.9 to about 63.9.

Code composition: what the lines of code are Most of the hand-written code is supporting code, such as wiring, settings and declarations, and business logic is 4% of it. That is normal for a service that mainly connects other systems or stores and fetches records, and worth a look if this product is meant to hold complex business rules.
Business logic 4%Supporting code 91%Tests 2%Generated by tools 3%Code analyzers 0%
Rebuild cost: about €580,000 · Estimate
Cost to rebuild€200,000 to €960,000, for 3,333 to 10,078 hours of work, about 4.0 person-years for 2 to 8 engineers
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.7 at a score of 50. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeVery large: 1,242,095 lines of product code, of which 56% is declarations and boilerplate, 39% straight logic and 4% logic with branches
Comment linesThe estimate prices 780,730 lines. Comment lines count towards the size of 1,242,095 lines but aren't priced as work.
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty.

Top priorities

The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.

1
Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault.
Skip if delegated to infra (Postgres TDE, KMS, etc.).
Raises the score by about 13.9 points · Medium effort · Data Protection
2
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with NOBuildTools.ReferenceAnalyzer.csproj.
Raises the score by about 2.4 points · Low effort · ADR Quality
3
Resolve the 1 Build failed finding(s) in Solution Shape.
Raises the score by about 1.9 points · Low effort · Solution Shape

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

If you do one thing first · First action
Fix the build. The code didn't build, so the dimensions that need a working build were measured on an incomplete picture of the code, and every grade in this report is provisional. Once the build works, the next survey gives a final score. The compiler's first errors: CS2001: Source file 'Toolbox/Toolbox/Controls/Text/RichTextEditor.designer.cs' could not be found.; CS2001: Source file 'Toolbox/Toolbox/Controls/Text/Scroller.designer.cs' could not be found.; CS0246: The type or namespace name 'NetOffice' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'COMAddin' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'COMAddinAttribute' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'TweakAttribute' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'Tweak' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'CodebaseAttribute' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'Codebase' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'Extensibility' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'IDTExtensibility2' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'ext_ConnectMode' could not be found (are you missing a using directive or an assembly reference?); CS0538: 'IDTExtensibility2' in explicit interface declaration is not an interface; CS0246: The type or namespace name 'CustomPaneAttribute' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'CustomPane' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'ICOMObject' could not be found (are you missing a using directive or an assembly reference?)
Based on: Solution Shape
Where the investment is most exposed · Value at risk
This code would cost about €580,000 to build again, about 4.0 person-years of work. Its weakest lens is Security and Compliance, at 33.0 (Weak). Security and Compliance is about how well the product is protected, and how it handles personal data. Because the weakest lens counts most in the score, work on Security and Compliance also moves the score most.
Based on: the rebuild estimate · the Security and Compliance grade · how much each lens counts
What to do: Start with the Security and Compliance actions in Top priorities.
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 6.7 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 3% to 7% on every change. The history of the code shows how much it changes: about 33 lines over the last 90 days, which is about 134 lines a year. At that pace, the extra work comes to an estimated 0 to 0.1 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.

Architecture — bounded-context dependency graph

Each box is a bounded context (its layer projects grouped, or a project count when large); arrows show dependencies between contexts. A shared kernel is where many arrows converge.

arch ADODBApi ADODBApi NetOffice (Source/NetOffice) NetOffice) ADODBApi->NetOffice (Source/NetOffice) AccessApi AccessApi AccessApi->ADODBApi DAOApi DAOApi AccessApi->DAOApi MSComctlLibApi MSComctlLibApi AccessApi->MSComctlLibApi MSDATASRCApi MSDATASRCApi AccessApi->MSDATASRCApi AccessApi->NetOffice (Source/NetOffice) OWC10Api OWC10Api AccessApi->OWC10Api OfficeApi OfficeApi AccessApi->OfficeApi VBIDEApi VBIDEApi AccessApi->VBIDEApi ClientApplication ClientApplication ClientApplication->ADODBApi ClientApplication->AccessApi ClientApplication->DAOApi ExcelApi ExcelApi ClientApplication->ExcelApi ClientApplication->MSComctlLibApi ClientApplication->MSDATASRCApi ClientApplication->NetOffice (Source/NetOffice) ClientApplication->OWC10Api ClientApplication->OfficeApi OutlookApi OutlookApi ClientApplication->OutlookApi PowerPointApi PowerPointApi ClientApplication->PowerPointApi ClientApplication->VBIDEApi WordApi WordApi ClientApplication->WordApi ConsoleApplication1 (Tests/Concept Tests/CommonUtils/ConsoleApplication1) ConsoleApplication1) ConsoleApplication1 (Tests/Concept Tests/CommonUtils/ConsoleApplication1)->ADODBApi ConsoleApplication1 (Tests/Concept Tests/CommonUtils/ConsoleApplication1)->AccessApi ConsoleApplication1 (Tests/Concept Tests/CommonUtils/ConsoleApplication1)->DAOApi ConsoleApplication1 (Tests/Concept Tests/CommonUtils/ConsoleApplication1)->ExcelApi ConsoleApplication1 (Tests/Concept Tests/CommonUtils/ConsoleApplication1)->MSComctlLibApi ConsoleApplication1 (Tests/Concept Tests/CommonUtils/ConsoleApplication1)->MSDATASRCApi ConsoleApplication1 (Tests/Concept Tests/CommonUtils/ConsoleApplication1)->NetOffice (Source/NetOffice) ConsoleApplication1 (Tests/Concept Tests/CommonUtils/ConsoleApplication1)->OWC10Api ConsoleApplication1 (Tests/Concept Tests/CommonUtils/ConsoleApplication1)->OfficeApi ConsoleApplication1 (Tests/Concept Tests/CommonUtils/ConsoleApplication1)->OutlookApi ConsoleApplication1 (Tests/Concept Tests/CommonUtils/ConsoleApplication1)->PowerPointApi ConsoleApplication1 (Tests/Concept Tests/CommonUtils/ConsoleApplication1)->VBIDEApi ConsoleApplication1 (Tests/Concept Tests/CommonUtils/ConsoleApplication1)->WordApi ConsoleApplication1 (Tests/Concept Tests/CreateInstanceEvent/ConsoleApplication1) ConsoleApplication1) ConsoleApplication1 (Tests/Concept Tests/CreateInstanceEvent/ConsoleApplication1)->ADODBApi ConsoleApplication1 (Tests/Concept Tests/CreateInstanceEvent/ConsoleApplication1)->AccessApi ConsoleApplication1 (Tests/Concept Tests/CreateInstanceEvent/ConsoleApplication1)->DAOApi ConsoleApplication1 (Tests/Concept Tests/CreateInstanceEvent/ConsoleApplication1)->ExcelApi ConsoleApplication1 (Tests/Concept Tests/CreateInstanceEvent/ConsoleApplication1)->MSComctlLibApi ConsoleApplication1 (Tests/Concept Tests/CreateInstanceEvent/ConsoleApplication1)->MSDATASRCApi ConsoleApplication1 (Tests/Concept Tests/CreateInstanceEvent/ConsoleApplication1)->NetOffice (Source/NetOffice) ConsoleApplication1 (Tests/Concept Tests/CreateInstanceEvent/ConsoleApplication1)->OWC10Api ConsoleApplication1 (Tests/Concept Tests/CreateInstanceEvent/ConsoleApplication1)->OfficeApi ConsoleApplication1 (Tests/Concept Tests/CreateInstanceEvent/ConsoleApplication1)->OutlookApi ConsoleApplication1 (Tests/Concept Tests/CreateInstanceEvent/ConsoleApplication1)->PowerPointApi ConsoleApplication1 (Tests/Concept Tests/CreateInstanceEvent/ConsoleApplication1)->VBIDEApi ConsoleApplication1 (Tests/Concept Tests/CreateInstanceEvent/ConsoleApplication1)->WordApi ConsoleApplication1 (Tests/Concept Tests/PerformanceTrace/ConsoleApplication1) ConsoleApplication1) ConsoleApplication1 (Tests/Concept Tests/PerformanceTrace/ConsoleApplication1)->ADODBApi ConsoleApplication1 (Tests/Concept Tests/PerformanceTrace/ConsoleApplication1)->AccessApi ConsoleApplication1 (Tests/Concept Tests/PerformanceTrace/ConsoleApplication1)->DAOApi ConsoleApplication1 (Tests/Concept Tests/PerformanceTrace/ConsoleApplication1)->ExcelApi ConsoleApplication1 (Tests/Concept Tests/PerformanceTrace/ConsoleApplication1)->MSComctlLibApi ConsoleApplication1 (Tests/Concept Tests/PerformanceTrace/ConsoleApplication1)->MSDATASRCApi ConsoleApplication1 (Tests/Concept Tests/PerformanceTrace/ConsoleApplication1)->NetOffice (Source/NetOffice) ConsoleApplication1 (Tests/Concept Tests/PerformanceTrace/ConsoleApplication1)->OWC10Api ConsoleApplication1 (Tests/Concept Tests/PerformanceTrace/ConsoleApplication1)->OfficeApi ConsoleApplication1 (Tests/Concept Tests/PerformanceTrace/ConsoleApplication1)->OutlookApi ConsoleApplication1 (Tests/Concept Tests/PerformanceTrace/ConsoleApplication1)->PowerPointApi ConsoleApplication1 (Tests/Concept Tests/PerformanceTrace/ConsoleApplication1)->VBIDEApi ConsoleApplication1 (Tests/Concept Tests/PerformanceTrace/ConsoleApplication1)->WordApi DAOApi->NetOffice (Source/NetOffice) ExcelApi->NetOffice (Source/NetOffice) ExcelApi->OfficeApi ExcelApi->VBIDEApi IDTExtensibility2 - SuperAddin IDTExtensibility2 - SuperAddin IDTExtensibility2 - SuperAddin->ADODBApi IDTExtensibility2 - SuperAddin->AccessApi IDTExtensibility2 - SuperAddin->DAOApi IDTExtensibility2 - SuperAddin->ExcelApi IDTExtensibility2 - SuperAddin->MSComctlLibApi IDTExtensibility2 - SuperAddin->MSDATASRCApi IDTExtensibility2 - SuperAddin->OWC10Api IDTExtensibility2 - SuperAddin->OfficeApi IDTExtensibility2 - SuperAddin->OutlookApi IDTExtensibility2 - SuperAddin->PowerPointApi IDTExtensibility2 - SuperAddin->VBIDEApi IDTExtensibility2 - SuperAddin->WordApi MSComctlLibApi->NetOffice (Source/NetOffice) MSDATASRCApi->NetOffice (Source/NetOffice) NetOffice Tools - SuperAddin NetOffice Tools - SuperAddin NetOffice Tools - SuperAddin->ADODBApi NetOffice Tools - SuperAddin->AccessApi NetOffice Tools - SuperAddin->DAOApi NetOffice Tools - SuperAddin->ExcelApi NetOffice Tools - SuperAddin->MSComctlLibApi NetOffice Tools - SuperAddin->MSDATASRCApi NetOffice Tools - SuperAddin->OWC10Api NetOffice Tools - SuperAddin->OfficeApi NetOffice Tools - SuperAddin->OutlookApi NetOffice Tools - SuperAddin->PowerPointApi NetOffice Tools - SuperAddin->VBIDEApi NetOffice Tools - SuperAddin->WordApi NetOffice.DeveloperToolbox DeveloperToolbox NetOffice.DeveloperToolbox->ADODBApi NetOffice.DeveloperToolbox->AccessApi NetOffice.DeveloperToolbox->DAOApi NetOffice.DeveloperToolbox->ExcelApi NetOffice.DeveloperToolbox->MSComctlLibApi NetOffice.DeveloperToolbox->MSDATASRCApi NetOffice.DeveloperToolbox->OWC10Api NetOffice.DeveloperToolbox->OfficeApi NetOffice.DeveloperToolbox->OutlookApi NetOffice.DeveloperToolbox->PowerPointApi NetOffice.DeveloperToolbox->WordApi OWC10Api->ADODBApi OWC10Api->MSComctlLibApi OWC10Api->MSDATASRCApi OWC10Api->NetOffice (Source/NetOffice) OfficeApi->NetOffice (Source/NetOffice) OutlookApi->NetOffice (Source/NetOffice) OutlookApi->OfficeApi PowerPointApi->NetOffice (Source/NetOffice) PowerPointApi->OfficeApi PowerPointApi->VBIDEApi VBIDEApi->NetOffice (Source/NetOffice) VBIDEApi->OfficeApi WordApi->NetOffice (Source/NetOffice) WordApi->OfficeApi WordApi->VBIDEApi __more__ +72 more projects

Architecture: which parts of the code depend on which

The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.

153 modules, with 290 dependencies between them. 5 loops run through 12 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 113 more are left out to keep it readable.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 Attributes2 DeveloperToolbox3 DeveloperToolbox.Utils.Animation4 OfficeApi.Enums5 NetOffice6 DeveloperToolbox.ToolboxControls.RegistryEditor7 DeveloperToolbox.Utils.Animation.Colors8 OfficeApi.Native9 CollectionsGeneric10 DeveloperToolbox.ToolboxControls.ProjectWizard.Controls11 Tools12 ADODBApi13 DAOApi14 DeveloperToolbox.ToolboxControls.ProjectWizard15 MSComctlLibApi16 OfficeApi17 OfficeApi.Extensions.TrayMenuUtils18 OWC10Api19 OfficeApi.Tools20 OutlookApi21 VBIDEApi22 AccessApi23 ExcelApi24 OfficeApi.Tools.Contribution25 OutlookApi.GlobalHelperModules26 PowerPointApi27 WordApi28 AccessApi.GlobalHelperModules29 AccessApi.Tools.Contribution30 ExcelApi.GlobalHelperModules31 ExcelApi.Tools.Contribution32 OutlookApi.Tools.Contribution33 PowerPointApi.GlobalHelperModules34 PowerPointApi.Tools.Contribution35 WordApi.GlobalHelperModules36 WordApi.Tools37 AccessApi.Tools38 ExcelApi.Tools39 OutlookApi.Tools40 PowerPointApi.Tools
1 Attributes
2 DeveloperToolbox
3 DeveloperToolbox.Utils.Animation
4 OfficeApi.Enums
5 NetOffice1
6 DeveloperToolbox.ToolboxControls.RegistryEditor3
7 DeveloperToolbox.Utils.Animation.Colors1
8 OfficeApi.Native72
9 CollectionsGeneric1
10 DeveloperToolbox.ToolboxControls.ProjectWizard.Controls24111
11 Tools3
12 ADODBApi2047
13 DAOApi14910
14 DeveloperToolbox.ToolboxControls.ProjectWizard6117
15 MSComctlLibApi20112
16 OfficeApi248866172
17 OfficeApi.Extensions.TrayMenuUtils43
18 OWC10Api8545783
19 OfficeApi.Tools34314131
20 OutlookApi111204215
21 VBIDEApi167101
22 AccessApi7628361673232
23 ExcelApi1593135261872
24 OfficeApi.Tools.Contribution111
25 OutlookApi.GlobalHelperModules1369
26 PowerPointApi18188421602
27 WordApi1211518132513
28 AccessApi.GlobalHelperModules33310127
29 AccessApi.Tools.Contribution111
30 ExcelApi.GlobalHelperModules3217
31 ExcelApi.Tools.Contribution111
32 OutlookApi.Tools.Contribution111
33 PowerPointApi.GlobalHelperModules5314117
34 PowerPointApi.Tools.Contribution111
35 WordApi.GlobalHelperModules5313142
36 WordApi.Tools43311344
37 AccessApi.Tools121103411
38 ExcelApi.Tools131113421
39 OutlookApi.Tools121103431
40 PowerPointApi.Tools121103411
Uses a module listed above itPart of a loopThe module itself
1 Attributes2 DeveloperToolbox3 DeveloperToolbox.Utils.Animation4 OfficeApi.Enums5 NetOffice6 DeveloperToolbox.ToolboxControls.RegistryEditor7 DeveloperToolbox.Utils.Animation.Colors8 OfficeApi.Native9 CollectionsGeneric10 DeveloperToolbox.ToolboxControls.ProjectWizard.Controls11 Tools12 ADODBApi13 DAOApi14 DeveloperToolbox.ToolboxControls.ProjectWizard15 MSComctlLibApi16 OfficeApi17 OfficeApi.Extensions.TrayMenuUtils18 OWC10Api19 OfficeApi.Tools20 OutlookApi21 VBIDEApi22 AccessApi23 ExcelApi24 OfficeApi.Tools.Contribution25 OutlookApi.GlobalHelperModules26 PowerPointApi27 WordApi28 AccessApi.GlobalHelperModules29 AccessApi.Tools.Contribution30 ExcelApi.GlobalHelperModules31 ExcelApi.Tools.Contribution32 OutlookApi.Tools.Contribution33 PowerPointApi.GlobalHelperModules34 PowerPointApi.Tools.Contribution35 WordApi.GlobalHelperModules36 WordApi.Tools37 AccessApi.Tools38 ExcelApi.Tools39 OutlookApi.Tools40 PowerPointApi.ToolsAttributes1DeveloperToolbox2DeveloperToolbox.Utils.Animation3OfficeApi.Enums4NetOffice5DeveloperToolbox.ToolboxControls.RegistryEditor6DeveloperToolbox.Utils.Animation.Colors7OfficeApi.Native8CollectionsGeneric9DeveloperToolbox.ToolboxControls.ProjectWizard.Controls10Tools11ADODBApi12DAOApi13DeveloperToolbox.ToolboxControls.ProjectWizard14MSComctlLibApi15OfficeApi16OfficeApi.Extensions.TrayMenuUtils17OWC10Api18OfficeApi.Tools19OutlookApi20VBIDEApi21AccessApi22ExcelApi23OfficeApi.Tools.Contribution24OutlookApi.GlobalHelperModules25PowerPointApi26WordApi27AccessApi.GlobalHelperModules28AccessApi.Tools.Contribution29ExcelApi.GlobalHelperModules30ExcelApi.Tools.Contribution31OutlookApi.Tools.Contribution32PowerPointApi.GlobalHelperModules33PowerPointApi.Tools.Contribution34WordApi.GlobalHelperModules35WordApi.Tools36AccessApi.Tools37ExcelApi.Tools38OutlookApi.Tools39PowerPointApi.Tools40131721241113204714910611720112248866172438545783343141311112042151671017628361673232159313526187211113691818842160212115181325133331012711132171111115314117111531314243311344121103411131113421121103431121103411+113 more modules (most-connected shown)

At a glance — Code Health · 63.7 · Adequate · gated by D18 ·

At a glance — Architecture · 71.4 · Adequate · gated by AX2 ·

At a glance — Maturity · 59.6 · Adequate · gated by M2 ·

At a glance — Readiness · 66.9 · Adequate · gated by D13 ·

At a glance — Security · 33.0 · Weak · gated by D28, D29, D36, C1 ·

At a glance — Performance · 100.0 · Exemplary ·

Security & Compliance — OWASP Top-10 mapping

Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).

OWASP categoryFindingsSeverity
A07:2025 — Authentication Failures211High / Critical
A05:2025 — Injection51High / Critical
A03:2025 — Software Supply Chain Failures5Medium

Roadmap

Top priorities: Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.); Resolve the 106 High secret finding(s) in Secrets (history) — start with REDACTED (2), REDACTED (2), REDACTED; Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.

Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.

Do thisHelpsEffortDimension
Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).+13.9 ptsMediumData Protection
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with NOBuildTools.ReferenceAnalyzer.csproj.+2.4 ptsLowADR Quality
Resolve the 1 Build failed finding(s) in Solution Shape.+1.9 ptsLowSolution Shape
Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (7), REDACTED.+1.8 ptsLowStatic Analysis (SAST)
Resolve the 106 High secret finding(s) in Secrets (history) — start with REDACTED (2), REDACTED (2), REDACTED.+7.1 ptsHighSecrets (history)
Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED.+1.4 ptsLowStatic Analysis (SAST)
Resolve the 4 EmptyCatchBlock finding(s) in Explicit Debt — start with Program.cs (2), TweetPane.cs, HotKey.cs.+1.3 ptsLowExplicit Debt
Resolve the 4 NoWarnInCsproj finding(s) in Explicit Debt — start with ClientApplication.csproj (3), NetOffice.Tests.csproj.+1.3 ptsLowExplicit Debt

File quality

Per-file score 0–10 — a quality signature. Of 1033 files carrying findings, judged against the Production bar: 0% slop · 41% mixed · 59% near-clean.

FileScoreBandWorst signal
REDACTED1.4SlopExplicit Debt: WriteOnlyPrivateField
Source/NetOffice/Running/ChildWindowBatchEnumerator.cs3.0SlopExplicit Debt: WriteOnlyPrivateField
Source/Word/Tools/Contribution/ApplicationUtils.cs3.8SlopExplicit Debt: WriteOnlyPrivateField
REDACTED4.2MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.4MixedSecret Scanning: Leaked secret: REDACTED
REDACTED4.4MixedSecret Scanning: Leaked secret: REDACTED
REDACTED4.4MixedSecret Scanning: Leaked secret: REDACTED
REDACTED4.4MixedSecret Scanning: Leaked secret: REDACTED
REDACTED4.4MixedSecret Scanning: Leaked secret: REDACTED
REDACTED4.4MixedSecret Scanning: Leaked secret: REDACTED
REDACTED4.4MixedSecret Scanning: Leaked secret: REDACTED
REDACTED4.4MixedSecret Scanning: Leaked secret: REDACTED
REDACTED4.4MixedSecret Scanning: Leaked secret: REDACTED
REDACTED4.4MixedSecret Scanning: Leaked secret: REDACTED
REDACTED4.4MixedSecret Scanning: Leaked secret: REDACTED
REDACTED4.4MixedSecret Scanning: Leaked secret: REDACTED
REDACTED4.4MixedSecret Scanning: Leaked secret: REDACTED
REDACTED4.4MixedSecret Scanning: Leaked secret: REDACTED
REDACTED4.4MixedSecret Scanning: Leaked secret: REDACTED
REDACTED4.4MixedSecret Scanning: Leaked secret: REDACTED

How the grades work

Every finding carries one of four grades. Three say how serious it is. The fourth says this survey could not settle it — and it is a grade, not a gap.

Critical — 278

A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.

Serious — 2333

Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.

Minor — 160

Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.

Could not be resolved — 13

Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.

Methodology & how to trust this report

This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 57 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.

Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.

What we checked — 57 dimensions across the health lenses
D4D5D6D10D13D14D15D16D17D18D19D20D21D24D26D27D28D29D30D35D36D37D43D44AX10AX2AX3AX4AX5AX6AX8C1C4GD1IC1M1M2M3M4P1P3P4P6PF1PF3X12X13X16X18X20X26X27X28X29X3X30X5

Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.

How to trust any code-health report — three questions
  1. Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 2758 of 2771 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
  2. Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
  3. Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

This report answers yes to all three. That's the bar to hold any assessment to.

Tools & methods

The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Canine Code Analyzer duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivySecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3✓ deterministic

Every finding is locatable in findings.md. Run 01a1e6f4-a9fc-75f6-b41e-71affd22a820.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.

  • D1 Cyclomatic Complexity — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Cyclomatic Complexity couldn't be assessed within its 5-minute budget on a solution this large — not included in this run.
  • D2 Cognitive Complexity — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Cognitive Complexity couldn't be assessed within its 5-minute budget on a solution this large — not included in this run.
  • D3 God Classes — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. God Classes couldn't be assessed within its 5-minute budget on a solution this large — not included in this run.
  • D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the test suite could not be built/run in-image (commonly external-service dependencies — a database, a broker — we won't provision). To have it measured, make the suite runnable without them. For context only, test code is ≈ 1% of production LoC (15,335 test / 1,242,095 production) — a rough proxy, NOT a coverage measurement, so it is excluded from the score. You can widen what we reach: optional: make the suite runnable without a database, broker or other service we do not provision, and real coverage is measured on the next scan.
  • D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 77 test(s) behind this row are the ones the C# collector could read, and this repository also carries at least 61 test source file(s) (.vb) that it cannot: it parses C# syntax and matches C# test attributes, so a vitest/jest/JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
  • D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability not scored — the test tier(s) ran but surfaced none of this repository's 77 test method(s) to the runner, so flakiness couldn't be exercised. This is an analysis-environment limitation, not a finding about the tests.
  • D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
  • D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Msbuild failed when processing the file 'Toolbox/Toolbox/NetOffice.DeveloperToolbox.csproj' with message: Could not find rule set file "AllRules.ruleset".
  • D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
  • D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
  • D23 Boundary Type-Coupling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Large codebase (1,242,095 production LoC in the .NET projects) with no declared bounded contexts — cross-boundary type coupling is unassessed Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D30 Dependency Vulnerabilities — measured, with a gap in what it reached — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. `dotnet list package --vulnerable` could not read this solution's dependency graph — it reported an error for at least one project and returned no package data at all (typically a packages.config / non-PackageReference project, which the command cannot read). An unreadable dependency graph is not a clean one; migrate the project(s) to PackageReference to enable this scan. 1 of 2 declared ecosystem(s) (nuget packages.config) WERE scanned and every vulnerability they reported is included in this result; nuget was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that nuget is free of known-vulnerable dependencies.
  • D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `Source/ADODB/DispatchInterfaces/_Record.cs`, `Source/ADODB/DispatchInterfaces/_Record_Deprecated.cs` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
  • D34 Knowledge Freshness — git history too condensed for a reliable signal — The history looks squashed or freshly imported, so per-file ownership reflects those commits rather than real maintenance. This dimension is reported as a low-confidence advisory and is not scored.
  • AX2 Stateful singletons — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 2496 further occurrence(s) are not listed individually; the score already reflects all 2536.
  • ED5 Idempotency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Idempotency could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: ArgumentException: Syntax node is not within syntax tree.
  • IC1 Incompleteness & stubs — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 2880 further occurrence(s) are not listed individually; the score already reflects all 2920.
  • M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
  • P10 Library API & versioning — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Library API & versioning could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: ArgumentException: SyntaxTree is not part of the compilation (Parameter 'syntaxTree').
  • P11 BDD / executable specs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. BDD / executable specs could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: ArgumentException: SyntaxTree is not part of the compilation (Parameter 'syntaxTree').
  • P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
  • P7 Outbound HTTP resilience — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Outbound HTTP resilience could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: ArgumentException: SyntaxTree is not part of the compilation (Parameter 'syntaxTree').
  • P8 Schema migrations — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Schema migrations could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: ArgumentException: SyntaxTree is not part of the compilation (Parameter 'syntaxTree').
  • X18 Disposal-pattern correctness — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 71 further occurrence(s) are not listed individually; the score already reflects all 111.
  • X3 Exception handling — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 15 further occurrence(s) are not listed individually; the score already reflects all 55.
  • X5 Nullable reference types — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 40 further occurrence(s) are not listed individually; the score already reflects all 80.

Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.

Limitations & what we did not check

We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.

Per-dimension blind spots

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
  • D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
  • D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
  • D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
  • D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
  • M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

Dimensions

D4 · Code Duplication5.8 / 10Adequate✓ Tool-verified

What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.

Maturity: Documented → Verified → Prevented · effective 5.8 / 10 · rule-coverage 100% · ceiling Verified

1137 duplicated block group(s) detected. 10.4 % of the production lines (129,671 of 1,242,095) are in a reported copy. A further 683 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 84 of the 1820 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.

Edited copy of a member (3 corresponding lines) · ×305Source/DAO/DispatchInterfaces/Workspace.cs:364
Duplicated block (5 lines × 2) · ×131Source/Excel/Events/AppEvents.cs:686
Duplicated block (53 lines × 2) · ×66Source/Excel/DispatchInterfaces/Action.cs:53
Duplicated block (53 lines × 3) · ×53Source/Excel/DispatchInterfaces/AddIns.cs:56
Duplicated block (11 lines × 2) · ×49Source/NetOffice/Invoker.cs:997

+ 373 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 305 Edited copy of a member (3 corresponding lines) finding(s) in Code Duplication — start with CanvasShapes.cs (36), Shapes.cs (29), Range.cs (16). — One of this dimension's main actionable groups (305 warning-level).
  2. Resolve the 131 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with DiagramNodeChildren.cs (4), AppEvents.cs (3), ISpreadsheetEventSink.cs (3). — One of this dimension's main actionable groups (131 warning-level).
  3. Resolve the 66 Duplicated block (53 lines × 2) finding(s) in Code Duplication — start with Action.cs, Actions.cs, AutoFilter.cs. — One of this dimension's main actionable groups (66 warning-level).

Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.

D5 · Coupling9.5 / 10Stronggated by 5 serious findings✓ Tool-verified

What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.

Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.

Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.

Maturity: Documented → Verified → Prevented · effective 9.5 / 10 · rule-coverage 100% · ceiling Prevented

82 projects, 0 dependency cycle(s), 1 unstable depended-on project(s).

Off the main sequence: NetOffice · ×4Source/NetOffice/NetOffice.csproj:1
Unstable project AccessApiSource/Access/AccessApi.csproj:1

What to do

  1. Resolve the 4 Off the main sequence finding(s) in Coupling — start with NetOffice.csproj, OfficeApi.csproj, MSDATASRCApi.csproj. — One of this dimension's main actionable groups (4 warning-level).
  2. Resolve the 1 Unstable project AccessApi finding(s) in Coupling — start with AccessApi.csproj. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.

D6 · Cohesion (LCOM4)7.5 / 10Strong✓ Tool-verified

What it measures: Whether a class's methods are focused on a single responsibility.

Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.

Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.

Maturity: Documented → Verified → Prevented · effective 7.5 / 10 · rule-coverage 100% · ceiling Verified

66 of 318 classes have LCOM4 above 3.

Low cohesion: RegistryEditorControl (LCOM4 11) · ×66Toolbox/Toolbox/ToolboxControls/RegistryEditor/RegistryEditorControl.cs:17

What to do

  1. Resolve the 66 Low cohesion finding(s) in Cohesion (LCOM4) — start with CategoryCollection.cs (3), Adjustments.cs (3), Panes.cs (2). — One of this dimension's main actionable groups (66 warning-level).

Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.

D10 · Test Quality10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the tests truly assert behaviour rather than just running the code.

Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 77 tests. Measured on the C# suite only — at least 61 test source file(s) (.vb) went unread, so its test quality is unmeasured and is not in these counts.

✓ On the Gold path — maintain.

Detailed fixes: d10_recommendation.md.

D13 · Secret Scanning0.0 / 10Critical✓ Tool-verified

What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.

Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Prevented

104 secret(s) detected.

REDACTED

What to do

  1. Resolve the 104 Leaked secret finding(s) in Secret Scanning — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (104 issue-level).

Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.

D14 · License Compliance10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether the licenses of third-party packages are compatible with your policy.

Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 161 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 8 direct `PackageReference`(s), and 148 further package(s) were reached beyond them by closing the graph over the committed `packages.lock.json` and nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots10.0 / 10Exemplary✓ Tool-verified

What it measures: Files that change often and are also complex — the riskiest hotspots.

Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

D16 · Bus Factor10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether knowledge is concentrated in too few people (the "bus factor").

Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

3 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is Source/Word/DispatchInterfaces/_Document.cs. Counted over 2766 of the 4678 production source files in this repository: 1678 are under the ~2,400-byte size floor this dimension measures over, and the remaining 234 have no attributable history left to measure.

Off-boarding risk: anonymized user #1

✓ On the Gold path — maintain.

Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.

D17 · Explicit Debt7.5 / 10Adequategated by 28 critical findings✓ Tool-verified

What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.

Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.

Maturity: Documented → Verified → Prevented · effective 7.5 / 10 · rule-coverage 100% · ceiling Prevented

3239 deducted debt markers + unmeasured dead symbols across 1242095 LoC in the .NET projects (1.2/KLoC) → score 7.5. Dead code not measured: the solution did not load cleanly, so the reference search was skipped.

WriteOnlyPrivateField · ×20REDACTED:42
EmptyCatchBlock · ×4Examples/AddinProjectHelper/Program.cs:31
NoWarnInCsproj · ×4Source/ClientApplication/ClientApplication.csproj:10
IneffectivePragmaPair · ×193Source/ADODB/Classes/Command.cs:10
CommentedOutCode · ×8RegAddin/RegAddinTest/Program.cs:16

+ 5 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 20 WriteOnlyPrivateField finding(s) in Explicit Debt — start with Addin.cs (5), CommonUtils.cs (5), ApplicationUtils.cs (3). — One of this dimension's main actionable groups (20 issue-level).
  2. Resolve the 4 EmptyCatchBlock finding(s) in Explicit Debt — start with Program.cs (2), TweetPane.cs, HotKey.cs. — One of this dimension's main actionable groups (4 issue-level).
  3. Resolve the 4 NoWarnInCsproj finding(s) in Explicit Debt — start with ClientApplication.csproj (3), NetOffice.Tests.csproj. — One of this dimension's main actionable groups (4 issue-level).

Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.

D18 · Solution Shape3.0 / 10Weak✓ Tool-verified

What it measures: Whether the solution is laid out in a sensible, conventional structure.

Method: Solution structure: project count, decomposition, shell-project detection, build success (confirmed failures cap the score); traced to actual .sln files and binaries. Deterministic.

Maturity: Documented → Verified → Prevented · effective 3.0 / 10 · rule-coverage 100% · ceiling Documented

82 projects, 5031 source files, 1244040 hand-written lines of code (1242095 production / 1945 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), plus 22127 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 81 inter-project edges (build failed). Measured across 21 solutions loaded as one workspace: `Source/NetOffice.sln`, `Examples/Examples.sln`, `Toolbox/NetOffice.DeveloperToolbox.sln`, `RegAddin/RegAddin.sln`, `Tutorials/Tutorials.sln`, `Examples/Other/Excel Addin - Google Translation/Google Translation.sln`, `Examples/Other/Outlook Addin - Use Twitter/Outlook Addin - Use Twitter.sln`, `Examples/Word/NetOffice COMAddin Examples/NetOffice Word Addin Examples.sln`, `Examples/Excel/NetOffice COMAddin Examples/NetOffice Excel Addin Examples.sln`, `Examples/Outlook/NetOffice COMAddin Examples/NetOffice Outlook Addin Examples.sln`, `Examples/Access/NetOffice COMAddin Examples/NetOffice Access Addin Examples.sln`, `Examples/PowerPoint/NetOffice COMAddin Examples/NetOffice PowerPoint Addin Examples.sln`, `Examples/Excel/IExtensibility COMAddin Examples/IExtensibility Excel Addin Examples.sln`, `Examples/Outlook/IExtensibility COMAddin Examples/IExtensibility Outlook Addin Examples.sln`, `Examples/Access/IExtensibility COMAddin Examples/IExtensibility Access Addin Examples.sln`, `Examples/PowerPoint/IExtensibility COMAddin Examples/IExtensibility PPoint Addin Examples.sln`, `Examples/Word/IExtensibility COMAddin Examples/IExtensibility Word Addin Examples.sln`, `Examples/Other/Word Addin - Search Wikipedia/Search Wikipedia.sln`, `Examples/Other/IExtensibility2 Examples/SuperAddin.sln`, `Examples/Other/COMAddin Examples/SuperAddin.sln`, `BuildTools/NOBuildTools.sln`.

Build failed

What to do

  1. Resolve the 1 Build failed finding(s) in Solution Shape. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d18_recommendation.md · top locations in Appendix A, every location in findings.md.

D19 · Documentation Quality5.0 / 10Adequate✓ Tool-verified

What it measures: Whether the project's documentation is clear, complete, and useful.

Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.

Maturity: Documented → Verified → Prevented · effective 5.0 / 10 · rule-coverage 100% · ceiling Documented

1 of 2 documentation facets pass in full; short on: F2 example. 11 document(s) read across 25 unit(s).

Documentation: no build, run or usage example · ×10README.md:1

What to do

  1. Resolve the 10 Documentation finding(s) in Documentation Quality — start with README.md (10). — One of this dimension's main actionable groups (10 recommendation-level).

Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.

D20 · ADR Quality0.0 / 10Critical✓ Tool-verified

What it measures: Whether architecture decisions are recorded well (context, decision, consequences).

Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

No architecture decision records were found.

No ADRs foundBuildTools/ReferenceAnalyzer/NOBuildTools.ReferenceAnalyzer.csproj:9

What to do

  1. Resolve the 1 No ADRs found finding(s) in ADR Quality — start with NOBuildTools.ReferenceAnalyzer.csproj. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.

D21 · Naming Consistency8.3 / 10Strong✓ Tool-verified

What it measures: Whether names — types, methods, variables — are clear and consistent.

Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.

Maturity: Documented → Verified → Prevented · effective 8.3 / 10 · rule-coverage 100% · ceiling Verified

11 naming inconsistencies among 636 declarations measured against a convention their peers follow.

`acSpreadsheetTypeExcel12Xml` spells `Xml` where 55 names in the project spell it `XML`Source/Access/Enums/AcSpreadSheetType.cs:102
`xlConnectionTypeTEXT` spells `TEXT` where 301 names in the project spell it `Text`Source/Excel/Enums/XlConnectionType.cs:39
`xlConnectionTypeWEB` spells `WEB` where 23 names in the project spell it `Web`Source/Excel/Enums/XlConnectionType.cs:46
`xlConnectionTypeMODEL` spells `MODEL` where 40 names in the project spell it `Model`Source/Excel/Enums/XlConnectionType.cs:60
`xlWK1ALL` spells `ALL` where 114 names in the project spell it `All`Source/Excel/Enums/XlFileFormat.cs:221

+ 6 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 1 `acSpreadsheetTypeExcel12Xml` spells `Xml` where 55 names in the project… finding(s) in Naming Consistency — start with AcSpreadSheetType.cs. — One of this dimension's main actionable groups (1 recommendation-level).
  2. Resolve the 1 `xlConnectionTypeTEXT` spells `TEXT` where 301 names in the project… finding(s) in Naming Consistency — start with XlConnectionType.cs. — One of this dimension's main actionable groups (1 recommendation-level).
  3. Resolve the 1 `xlConnectionTypeWEB` spells `WEB` where 23 names in the project spell… finding(s) in Naming Consistency — start with XlConnectionType.cs. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.

D24 · Comment Value2.0 1.8 / 10Critical✓ Tool-verified

What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).

Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.

Maturity: Documented → Verified → Prevented · effective 1.8 / 10 · rule-coverage 92% · ceiling Documented

20 of 250 judged comments only repeat the code they sit on (8.0 %). 40 comment(s) in another language or script were not judged.

redundant comment · ×20REDACTED:5
doc comments repeat the names · ×20Source/ADODB/Classes/Command.cs:35

What to do

  1. Resolve the 20 redundant comment finding(s) in Comment Value — start with REDACTED (14), COMObject.cs (2), Form1.cs. — One of this dimension's main actionable groups (20 recommendation-level).

Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.

D26 · Project Cohesion7.3 / 10Strong✓ Tool-verified

What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.

Method: Project size overshoot penalties (LoC / public-type count / namespace count, 2-of-3 flag) weighted by log magnitude. Exhaustive across projects, deterministic.

Maturity: Documented → Verified → Prevented · effective 7.3 / 10 · rule-coverage 100% · ceiling Documented

11 of 82 projects flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion · ×11Source/Excel/ExcelApi.csproj:1
Split NetOfficeSource/NetOffice/NetOffice.csproj:1

What to do

  1. Resolve the 11 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with ExcelApi.csproj, WordApi.csproj, AccessApi.csproj. — One of this dimension's main actionable groups (11 recommendation-level).
  2. Resolve the 1 Split NetOffice finding(s) in Project Cohesion — start with NetOffice.csproj. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.

D27 · Navigability9.9 / 10Exemplary✓ Tool-verified

What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.

Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.

Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.

Maturity: Documented → Verified → Prevented · effective 9.9 / 10 · rule-coverage 100% · ceiling Documented

95 % of calls cross a namespace and 1 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: large — vertical-slice locality expected.

Pass-through layerSource/NetOffice/Dynamics/COMDynamicMetaObject.cs:13

✓ On the Gold path — maintain.

Detailed fixes: d27_recommendation.md · top locations in Appendix A, every location in findings.md.

D28 · Secrets (history)0.0 / 10Critical✓ Tool-verified

What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.

Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

106 finding(s): 0 critical, 106 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.

REDACTED
REDACTED

What to do

  1. Resolve the 106 High secret finding(s) in Secrets (history) — start with REDACTED (2), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (106 issue-level).
  2. Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.

D29 · Static Analysis (SAST)0.3 / 10Critical✓ Tool-verified

What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.

Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.

Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).

Maturity: Documented → Verified → Prevented · effective 0.3 / 10 · rule-coverage 100% · ceiling Documented

51 finding(s): 0 critical, 35 high, 16 medium, 0 low. 20 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 2 file(s) — `Source/ADODB/DispatchInterfaces/_Record.cs` (line 229, line 319, line 405), `Source/ADODB/DispatchInterfaces/_Record_Deprecated.cs` (line 229, line 319, line 405) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

+ 2 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (7), REDACTED. — One of this dimension's main actionable groups (8 issue-level).
  2. Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
  3. No action in Static Analysis (SAST) — all 20 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (20 issue-level, 0 of them charged here).

Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.

D30 · Dependency Vulnerabilities10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.

Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (nuget packages.config). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (nuget packages.config), and the findings above are real and complete for them. nuget was not scanned (nuget: `dotnet list package --vulnerable` could not read this solution's dependency graph — it reported an error for at least one project and returned no package data at all (typically a packages.config / non-PackageReference project, which the command cannot read). An unreadable dependency graph is not a clean one; migrate the project(s) to PackageReference to enable this scan), so this is not the whole dependency surface and the result is reported at reduced confidence.

✓ On the Gold path — maintain.

Detailed fixes: d30_recommendation.md.

D35 · Change Coupling10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.

Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.

Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

D36 · Supply-chain Provenance & Signing2.5 / 10Weak✓ Tool-verified

What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.

Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.

Maturity: Documented → Verified → Prevented · effective 2.5 / 10 · rule-coverage 100% · ceiling Documented

1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.

D37 · Vulnerability-disclosure Policy10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.

Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.

✓ On the Gold path — maintain.

Detailed fixes: d37_recommendation.md.

D43 · Malicious Dependencies10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.

Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No dependency in any ecosystem this repository declares is published as malicious.

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

D44 · Platform End-of-Life10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.

Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 117 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

R = React/JS · M = Maturity · P = Readiness.

AX10 · Code composition10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does.

Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.

Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.

AX2 · Stateful singletons1.0 / 10Critical✓ Tool-verified

Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.

Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.

  • `Core` keeps one instance of itself in the static `_default`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_initalized, _wrapperTypeCache, _proxyTypeCache; e.g. `_initalized` at line 470). — Source/NetOffice/Core.cs:82
  • `Settings` keeps one instance of itself in the static `_default`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_enableProxyManagement, _enableKnownReferenceInspection, _enableAutoDisposeEventArguments, _exceptionMessageBehavior, _exceptionDefaultMessage, _exceptionDiagnosticsMessage; e.g. `_enableProxyManagement` at line 116). — Source/NetOffice/Settings.cs:11
  • `DebugConsole` keeps one instance of itself in the static `_default`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_name, _messageList, EnableSharedOutput; e.g. `_name` at line 288). — Source/NetOffice/Trace/DebugConsole.cs:13
  • `RichTextDialog` is not registered, but `DialogUtilsEx` creates it and keeps it in the static `_openNonModalDialogs`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_timeoutMode; e.g. `_timeoutMode` at line 200). — Source/Office.Extensions/Dialogs/RichTextDialog.cs:12
  • `wnd` keeps one instance of itself in the static `def`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (hotkeys; e.g. `hotkeys` at line 124). — Toolbox/Toolbox/ToolboxControls/ApplicationObserver/HotKey.cs:96
  • `TwitterTimer` is not registered, but `TwitterPane` creates it and keeps it in the static `Client`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_enabled, Timer, _intervalSeconds, _consumerKey, _consumerSecret, _accessToken; e.g. `_enabled` at line 71). — Examples/Other/Outlook Addin - Use Twitter/Outlook Addin - Use Twitter/Twitter/TwitterTimer.cs:20
  • `CurrentAppDomain` is not registered, but the singleton `Core` creates it and keeps it in `CoreDomain`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (_assemblyVersion; e.g. `_assemblyVersion` at line 64). — Source/NetOffice/Loader/CurrentAppDomain.cs:11
  • `RetryMessageFilter` is not registered, but the singleton `Settings` creates it and keeps it in `_messageFilter`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (_retryMode, _logMode, _messageFilter; e.g. `_retryMode` at line 90). — Source/NetOffice/Filtering/RetryMessageFilter.cs:11
  • `PerformanceTrace` is not registered, but the singleton `Settings` creates it and keeps it in `_performanceTrace`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (_enabled; e.g. `_enabled` at line 169). — Source/NetOffice/Trace/PerformanceTrace.cs:12
  • `Application` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 108). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/Excel/Classes/Application.cs:68
  • `Chart` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 74). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/Excel/Classes/Chart.cs:33
  • `OLEObject` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 63). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/Excel/Classes/OLEObject.cs:22
  • `QueryTable` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 62). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/Excel/Classes/QueryTable.cs:22
  • `Workbook` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 101). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/Excel/Classes/Workbook.cs:61
  • `Worksheet` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 78). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/Excel/Classes/Worksheet.cs:38
  • `AboveAverage` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 41). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/Excel/DispatchInterfaces/AboveAverage.cs:13
  • `Action` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 41). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/Excel/DispatchInterfaces/Action.cs:13
  • `Actions` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 44). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/Excel/DispatchInterfaces/Actions.cs:16
  • `AddIn` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 41). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/Excel/DispatchInterfaces/AddIn.cs:13
  • `AddIns` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 44). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/Excel/DispatchInterfaces/AddIns.cs:16
  • `AddIns2` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 44). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/Excel/DispatchInterfaces/AddIns2.cs:16
  • `Adjustments` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 45). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/Excel/DispatchInterfaces/Adjustments.cs:16
  • `AllowEditRange` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 41). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/Excel/DispatchInterfaces/AllowEditRange.cs:13
  • `AllowEditRanges` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 44). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/Excel/DispatchInterfaces/AllowEditRanges.cs:16
  • `Arc` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 168). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/Excel/DispatchInterfaces/Arc.cs:140
  • `Arcs` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 171). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/Excel/DispatchInterfaces/Arcs.cs:143
  • `Areas` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 44). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/Excel/DispatchInterfaces/Areas.cs:16
  • `AutoCorrect` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 159). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/Excel/DispatchInterfaces/AutoCorrect.cs:131
  • `AutoFilter` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 41). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/Excel/DispatchInterfaces/AutoFilter.cs:13
  • `AutoRecover` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 41). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/Excel/DispatchInterfaces/AutoRecover.cs:13
  • `Axes` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 44). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/Excel/DispatchInterfaces/Axes.cs:16
  • `Axis` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 41). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/Excel/DispatchInterfaces/Axis.cs:13
  • `AxisTitle` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 173). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/Excel/DispatchInterfaces/AxisTitle.cs:145
  • `Border` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 41). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/Excel/DispatchInterfaces/Border.cs:13
  • `Borders` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 44). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/Excel/DispatchInterfaces/Borders.cs:16
  • `Button` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 168). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/Excel/DispatchInterfaces/Button.cs:140
  • `Buttons` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 171). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/Excel/DispatchInterfaces/Buttons.cs:143
  • `CalculatedFields` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 44). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/Excel/DispatchInterfaces/CalculatedFields.cs:16
  • `CalculatedItems` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 44). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/Excel/DispatchInterfaces/CalculatedItems.cs:16
  • `CalculatedMember` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 41). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/Excel/DispatchInterfaces/CalculatedMember.cs:13

What to do

  • Keep singletons stateless or back their state with thread-safe types (Concurrent*/Immutable*); otherwise concurrent callers race.
  • A `static` field is one slot for the whole process, however its type is created: back it with a thread-safe type (ConcurrentDictionary, Interlocked), take a lock around every write, or move it into a registered singleton that does.
AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).

Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.

  • The namespaces NetOffice ↔ NetOffice.Availability ↔ NetOffice.Loader depend on each other. The lightest dependency in the cycle is NetOffice.Availability → NetOffice (NetOffice.Availability.SupportedEntityFinder → NetOffice.Core, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — Source/NetOffice/Availability/SupportedEntityFinder.cs:13
  • The namespaces NetOffice.OfficeApi ↔ NetOffice.OfficeApi.Native depend on each other. The lightest dependency in the cycle is NetOffice.OfficeApi → NetOffice.OfficeApi.Native (NetOffice.OfficeApi.IRibbonUI → NetOffice.OfficeApi.Native.IRibbonUI, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — Source/Office/NativeCaller/IRibbonUI.cs:13
  • The namespaces NetOffice.Tools ↔ NetOffice.Tools.Native depend on each other. The lightest dependency in the cycle is NetOffice.Tools → NetOffice.Tools.Native (NetOffice.Tools.ICOMAddin → NetOffice.Tools.Native.IDTExtensibility2, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — Source/NetOffice/Tools/ICOMAddin.cs:11
  • The namespaces NetOffice.OfficeApi.Tools ↔ NetOffice.OfficeApi.Tools.Contribution ↔ NetOffice.OfficeApi.Tools.Informations depend on each other. The lightest dependency in the cycle is NetOffice.OfficeApi.Tools → NetOffice.OfficeApi.Tools.Contribution (NetOffice.OfficeApi.Tools.COMAddin → NetOffice.OfficeApi.Tools.Contribution.CommonUtils, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — Source/Office/Tools/COMAddin.cs:20
  • The namespaces NetOffice.DeveloperToolbox.ToolboxControls.ProjectWizard ↔ NetOffice.DeveloperToolbox.ToolboxControls.ProjectWizard.Controls depend on each other. The lightest dependency in the cycle is NetOffice.DeveloperToolbox.ToolboxControls.ProjectWizard.Controls → NetOffice.DeveloperToolbox.ToolboxControls.ProjectWizard (NetOffice.DeveloperToolbox.ToolboxControls.ProjectWizard.Controls.ProjectControl → NetOffice.DeveloperToolbox.ToolboxControls.ProjectWizard.ProjectType, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — Toolbox/Toolbox/ToolboxControls/ProjectWizard/Controls/ProjectControl.cs:18

What to do

  • Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.
AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.

Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.

AX5 · Architecture & structure10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.

Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.

AX6 · Interface segregation9.9 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').

Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.

  • `IToolboxControl` declares 17 members: `Host`, `ControlName`, `ControlCaption`, `Icon`, `SupportsHelpContent`, `SupportsInfoMessage`, `InfoMessageKind`, `InfoMessage`, `InitializeControl`, `Activate`, `Deactivated`, `LoadComplete`, `LoadConfiguration`, `SaveConfiguration`, `GetHelpText`, `KeyDown`, `Release`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — Toolbox/Toolbox/IToolboxControl.cs:33

What to do

  • Split fat interfaces into focused role-interfaces so clients depend only on what they use.
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.

Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.

C1 · Data Protection0.0 / 10Critical✓ Tool-verified

Other · Security — Whether sensitive data is encrypted at rest and in transit and keys are vaulted.

Method: Roslyn plus filesystem scan: encryption presence (EF ColumnEncryption, key-vault references, HTTPS enforcement) and key-derivation KDF detection. Deterministic.

  • No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.

What to do

  • Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
  • Enforce HTTPS (UseHttpsRedirection / RequireHttpsMetadata) so data in transit is always encrypted.
C4 · Data Retention7.5 / 10Strong✓ Tool-verified

Other · Security — Whether data has a defined lifetime — retention periods, TTLs, cleanup jobs (storage limitation).

Method: Roslyn scan: retention/TTL configuration presence in schema; CascadeDelete detected but not scored as retention control. Deterministic, gated by PII presence.

  • A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a scheduled purge / cleanup job (PurgeOlderThan / CleanupJob).

What to do

  • Complete the data-lifecycle story: an expiry limit (a declared maximum age for the stored data — a retention-age setting, or a store-level TTL where your storage offers one), a scheduled purge/cleanup job that enforces it, and a documented retention period covering the personal data.
GD1 · Unfinished & placeholder code10.0 / 10Exemplary✓ Tool-verified

Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.

Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.

  • A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. (×7) — Source/Office/Tools/Informations/DiagnosticPairCollection.cs:98, Toolbox/Toolbox/ToolboxControls/About/AboutControl.cs:123, Toolbox/Toolbox/ToolboxControls/ProjectWizard/Controls/FinishControl.cs:104, …

What to do

  • Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
IC1 · Incompleteness & stubs6.9 / 10Adequate✓ Tool-verified

Other · Code Health — Unfinished work detected by code SHAPE, not keywords: members that only throw a "not implemented" exception, methods that take inputs and return a constant, async methods that never await, dead `if (false)` / `#if false` branches, and skeleton types most of whose members are holes. A real, objective slice of technical debt.

Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.

  • `AnalyzeInteropConnectClass` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — RegAddin/RegAddin/Metrics/AddinMetrics.cs:279
  • The branch `if (null == dispatcher)` throws `IDispatchNotImplementedException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported. (×3) — Source/NetOffice/CoreExtensions/CoreFactoryExtensions.cs:117, Source/NetOffice/CoreExtensions/CoreFactoryExtensions.cs:156, Source/NetOffice/CoreExtensions/CoreFactoryExtensions.cs:197
  • `GetListName` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. (×3) — Source/Office/Tools/Informations/DiagnosticPairCollection.cs:98, Toolbox/Toolbox/ToolboxControls/ProxyView/RotEntryCollection.cs:131, Toolbox/Toolbox/ToolboxControls/ProxyView/WindowEntryCollection.cs:136
  • `GetHelpText` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. (×2) — Toolbox/Toolbox/ToolboxControls/About/AboutControl.cs:123, Toolbox/Toolbox/ToolboxControls/Welcome/WelcomeControl.cs:194
  • `SettingsDocument` is a shipped property whose accessors only throw NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — Toolbox/Toolbox/ToolboxControls/ProjectWizard/Controls/FinishControl.cs:104
  • `GetSettingsSummary` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — Toolbox/Toolbox/ToolboxControls/ProjectWizard/Controls/FinishControl.cs:109
  • The `if` and its `else` contain the same 1 statement, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body. — Toolbox/Toolbox/ToolboxControls/ProjectWizard/Controls/ProjectControl.cs:199
  • The first 1 statement of the `if` and of the `else` are identical, so it runs on both paths regardless of the condition. Lift it above the `if` — leaving it duplicated inside makes the branches read as though they handled this differently. (×3) — Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsSingleAddinConverterCS.cs:139, Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsSingleAddinConverterVB.cs:167, Toolbox/Toolbox/ToolboxControls/Welcome/WelcomeControl.cs:239
  • `EnableDesignView` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — Toolbox/Toolbox/ToolboxControls/RegistryEditor/RegistryEditorControl.cs:232
  • `SetLanguage` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — Toolbox/Toolbox/ToolboxControls/Welcome/WelcomeControl.cs:189
  • The first 2 statements of the `if` and of the `else` are identical, so they run on both paths regardless of the condition. Lift them above the `if` — leaving them duplicated inside makes the branches read as though they handled this differently. — Toolbox/Toolbox/ToolboxControls/Welcome/WelcomeControl.cs:219
  • The first 3 statements of the `if` and of the `else` are identical, so they run on both paths regardless of the condition. Lift them above the `if` — leaving them duplicated inside makes the branches read as though they handled this differently. — Toolbox/Toolbox/Utils/Registry/UtilsRegistryEntry.cs:81
  • A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×15) — RegAddin/RegAddin/CommandLineValidator.cs:256, RegAddin/RegAddinTest/Program.cs:17, RegAddin/RegAddinTest/Program.cs:19, …
  • A `#pragma warning disable` with no error codes silences every warning for the rest of the file — hidden debt. Suppress specific codes with a justification instead. (×6) — Source/ADODB/Classes/Command.cs:10, Source/ADODB/Classes/Command.cs:23, Source/ADODB/Classes/Connection.cs:10, …

What to do

  • Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
  • Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
M1 · Documentation (README)6.9 / 10Adequate✓ Tool-verified

Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.

Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.

What to do

  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation0.0 / 10Critical✓ Tool-verified

Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.

Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.

  • No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
  • No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.

What to do

  • Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
  • Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.

Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.

M4 · Documentation accuracy10.0 / 10Exemplary○ Nothing flagged

Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.

Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.

P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether an automated pipeline builds and tests every change.

Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.

P3 · Security & performance tooling4.0 / 10Weak✓ Tool-verified

Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).

Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.

  • No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 4 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:5
  • `.github/dependabot.yml` schedules updates, but no `package-ecosystem` entry covers `nuget`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — .github/dependabot.yml:2

What to do

  • Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
  • Dependabot is configured but does not watch `nuget` — add that `package-ecosystem` entry to .github/dependabot.yml so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback8.0 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.

Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.

What to do

  • Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
P6 · Release Hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.

Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.

PF1 · Benchmark discipline10.0 / 10Exemplary✓ Tool-verified

Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.

Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.

PF3 · Async & latency hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.

X12 · Unreachable branch8.0 / 10Strong✓ Tool-verified

Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.

Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.

  • `regLocation == 2` can never be true where it stands: the guard on line 103 (`regLocation < 0 || regLocation > 2`) left this block when it was true; the enclosing `if` on line 105 (`0 == regLocation`) holds. No value of `regLocation` satisfies all of that, so the true arm of this conditional expression never runs. Reorder the tests, drop the dead branch, or fix the bound that was meant. — RegAddin/RegAddin/Common/AddinRegAnalyzer.cs:106
  • `case PossibleAddin.No:` can never be true where it stands: the guard on line 97 (`possible == PossibleAddin.No`) left this block when it was true. No value of `possible` satisfies all of that, so this case label never runs. Reorder the tests, drop the dead branch, or fix the bound that was meant. — RegAddin/RegAddin/Metrics/AddinMetrics.cs:108

What to do

  • Each finding names the span that makes the branch dead and the span it is dead because of. Confirm from the two, then delete the dead arm or fix the predicate that was meant to be reachable.
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.

Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.

X16 · Unfloored truncation loop10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.

Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.

X18 · Disposal-pattern correctness7.3 / 10Strong✓ Tool-verified

Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.

Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.

  • `utils` is a `CommonUtils`, which implements `IDisposable`, and it is created here (line 22). Every use of it in `Run` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var utils = …;`), which releases it at the end of the scope on every path including a throw. — Source/ClientApplication/RunExcel01.cs:22
  • `Application` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_appEvents_SinkHelper` itself (line 81), which makes that instance its own. But `_appEvents_SinkHelper` is named in none of the methods the disposal search covered: `Dispose` (line 220), `Dispose` (line 231) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_appEvents_SinkHelper?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — Source/Excel/Classes/Application.cs:81
  • `key` is a `RegistryKey`, which implements `IDisposable`, and it is created here (line 77). Every use of it in `CreateValue` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var key = …;`), which releases it at the end of the scope on every path including a throw. — Source/NetOffice/Tools/CodebaseAttribute.cs:77
  • `key` is a `RegistryKey`, which implements `IDisposable`, and it is created here (line 52). Every use of it in `CreateKeys` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var key = …;`), which releases it at the end of the scope on every path including a throw. — Source/NetOffice/Tools/ProgrammableAttribute.cs:52
  • `key` is a `RegistryKey`, which implements `IDisposable`, and it is created here (line 57). Every use of it in `CreateKeys` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var key = …;`), which releases it at the end of the scope on every path including a throw. — Source/NetOffice/Tools/ProgrammableAttribute.cs:57
  • `Application` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_applicationEvents2_SinkHelper` itself (line 69), which makes that instance its own. But `_applicationEvents2_SinkHelper` is named in none of the methods the disposal search covered: `Dispose` (line 210), `Dispose` (line 221) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_applicationEvents2_SinkHelper?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — Source/Word/Classes/Application.cs:69
  • `Application` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_applicationEvents3_SinkHelper` itself (line 70), which makes that instance its own. But `_applicationEvents3_SinkHelper` is named in none of the methods the disposal search covered: `Dispose` (line 210), `Dispose` (line 221) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_applicationEvents3_SinkHelper?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — Source/Word/Classes/Application.cs:70
  • `Application` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_applicationEvents4_SinkHelper` itself (line 71), which makes that instance its own. But `_applicationEvents4_SinkHelper` is named in none of the methods the disposal search covered: `Dispose` (line 210), `Dispose` (line 221) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_applicationEvents4_SinkHelper?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — Source/Word/Classes/Application.cs:71
  • `a` is a `COMObject`, which implements `IDisposable`, and it is created here (line 198). Every use of it in `Equal` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var a = …;`), which releases it at the end of the scope on every path including a throw. — Source/Word/Tools/Contribution/ApplicationUtils.cs:198
  • `Application` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_applicationEvents_SinkHelper` itself (line 53), which makes that instance its own. But `_applicationEvents_SinkHelper` is named in none of the methods the disposal search covered: `Dispose` (line 186), `Dispose` (line 197) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_applicationEvents_SinkHelper?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — Source/Outlook/Classes/Application.cs:53
  • `Application` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_applicationEvents_10_SinkHelper` itself (line 54), which makes that instance its own. But `_applicationEvents_10_SinkHelper` is named in none of the methods the disposal search covered: `Dispose` (line 186), `Dispose` (line 197) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_applicationEvents_10_SinkHelper?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — Source/Outlook/Classes/Application.cs:54
  • `Application` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_applicationEvents_11_SinkHelper` itself (line 55), which makes that instance its own. But `_applicationEvents_11_SinkHelper` is named in none of the methods the disposal search covered: `Dispose` (line 186), `Dispose` (line 197) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_applicationEvents_11_SinkHelper?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — Source/Outlook/Classes/Application.cs:55
  • `Application` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_eApplication_SinkHelper` itself (line 67), which makes that instance its own. But `_eApplication_SinkHelper` is named in none of the methods the disposal search covered: `Dispose` (line 207), `Dispose` (line 218) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_eApplication_SinkHelper?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — Source/PowerPoint/Classes/Application.cs:67
  • `dlg` is a `RichTextDialog`, which implements `IDisposable`, and it is created here (line 606). Every use of it in `ShowRegister` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var dlg = …;`), which releases it at the end of the scope on every path including a throw. — Source/Office.Extensions/Dialogs/DialogUtilsEx.cs:606
  • `dlg` is a `RichTextDialog`, which implements `IDisposable`, and it is created here (line 643). Every use of it in `ShowUnregister` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var dlg = …;`), which releases it at the end of the scope on every path including a throw. — Source/Office.Extensions/Dialogs/DialogUtilsEx.cs:643
  • `form` is a `ErrorForm`, which implements `IDisposable`, and it is created here (line 49). Every use of it in `Show` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var form = …;`), which releases it at the end of the scope on every path including a throw. — Examples/ExampleBase/ErrorForm.cs:49
  • `form` is a `ErrorForm`, which implements `IDisposable`, and it is created here (line 61). Every use of it in `Show` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var form = …;`), which releases it at the end of the scope on every path including a throw. — Examples/ExampleBase/ErrorForm.cs:61
  • `dialog` is a `FinishForm`, which implements `IDisposable`, and it is created here (line 64). Every use of it in `ShowFinishDialog` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var dialog = …;`), which releases it at the end of the scope on every path including a throw. — Examples/ExampleBase/ExampleForm.cs:64
  • `dialog` is a `OptionsForm`, which implements `IDisposable`, and it is created here (line 166). Every use of it in `OptionButton_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var dialog = …;`), which releases it at the end of the scope on every path including a throw. — Examples/ExampleBase/ExampleForm.cs:166
  • `utils` is a `CommonUtils`, which implements `IDisposable`, and it is created here (line 26). Every use of it in `RunExample` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var utils = …;`), which releases it at the end of the scope on every path including a throw. (×2) — Examples/Access/Automation/Examples/Example01.cs:26, REDACTED:26
  • `newDatabase` is a `Database`, which implements `IDisposable`, and it is created here (line 36). Every use of it in `RunExample` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var newDatabase = …;`), which releases it at the end of the scope on every path including a throw. (×2) — Examples/Access/Automation/Examples/Example01.cs:36, REDACTED:36
  • `oleCreateCommand` is a `OleDbCommand`, which implements `IDisposable`, and it is created here (line 44). Every use of it in `RunExample` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var oleCreateCommand = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:44
  • `oleInsertCommand` is a `OleDbCommand`, which implements `IDisposable`, and it is created here (line 51). Every use of it in `RunExample` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var oleInsertCommand = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:51
  • `utils` is a `CommonUtils`, which implements `IDisposable`, and it is created here (line 27). Every use of it in `RunExample` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var utils = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:27
  • `newDatabase` is a `Database`, which implements `IDisposable`, and it is created here (line 37). Every use of it in `RunExample` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var newDatabase = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:37
  • `oleCreateCommand` is a `OleDbCommand`, which implements `IDisposable`, and it is created here (line 45). Every use of it in `RunExample` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var oleCreateCommand = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:45
  • `oleInsertCommand` is a `OleDbCommand`, which implements `IDisposable`, and it is created here (line 52). Every use of it in `RunExample` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var oleInsertCommand = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:52
  • `accessApplication` is a `Application`, which implements `IDisposable`, and it is created here (line 68). Every use of it in `ShowDatabaseInfo` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var accessApplication = …;`), which releases it at the end of the scope on every path including a throw. — Examples/Access/Automation/Examples/Example04.cs:68
  • `database` is a `Database`, which implements `IDisposable`, and it is created here (line 71). Every use of it in `ShowDatabaseInfo` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var database = …;`), which releases it at the end of the scope on every path including a throw. — Examples/Access/Automation/Examples/Example04.cs:71
  • `ofd` is a `OpenFileDialog`, which implements `IDisposable`, and it is created here (line 96). Every use of it in `buttonSelectDatabase_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var ofd = …;`), which releases it at the end of the scope on every path including a throw. — Examples/Access/Automation/Examples/Example04.cs:96
  • `utils` is a `CommonUtils`, which implements `IDisposable`, and it is created here (line 90). Every use of it in `buttonStartExample_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var utils = …;`), which releases it at the end of the scope on every path including a throw. — Examples/Access/Automation/Examples/Example05.cs:90
  • `utils` is a `CommonUtils`, which implements `IDisposable`, and it is created here (line 23). Every use of it in `RunExample` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var utils = …;`), which releases it at the end of the scope on every path including a throw. — Examples/Excel/Automation/Examples/Example01.cs:23
  • `utils` is a `CommonUtils`, which implements `IDisposable`, and it is created here (line 22). Every use of it in `RunExample` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var utils = …;`), which releases it at the end of the scope on every path including a throw. (×3) — Examples/Excel/Automation/Examples/Example02.cs:22, Examples/Excel/Automation/Examples/Example03.cs:22, Examples/Excel/Automation/Examples/Example04.cs:22
  • `utils` is a `CommonUtils`, which implements `IDisposable`, and it is created here (line 21). Every use of it in `RunExample` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var utils = …;`), which releases it at the end of the scope on every path including a throw. — Examples/Excel/Automation/Examples/Example05.cs:21
  • `utils` is a `CommonUtils`, which implements `IDisposable`, and it is created here (line 31). Every use of it in `RunExample` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var utils = …;`), which releases it at the end of the scope on every path including a throw. — Examples/Excel/Automation/Examples/Example07.cs:31
  • `utils` is a `CommonUtils`, which implements `IDisposable`, and it is created here (line 24). Every use of it in `RunExample` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var utils = …;`), which releases it at the end of the scope on every path including a throw. — Examples/Excel/Automation/Examples/Example10.cs:24

What to do

  • Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
X20 · Mistyped argument guard5.4 / 10Adequate✓ Tool-verified

Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `ArgumentNullException` tells the caller a parameter was null when it provably was not.

Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements (or a repository exception type deriving from it) controlled by an `if` — directly or through the `using`, `lock` or `try` that wraps the throw — whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`); in the `else` branch, for a conjunct of the admitting condition that is FALSE of a non-null `p`. Range guards are read for bounds that leave nothing and for a `p > C.Count` bound whose index then reaches `C[p]`, `C.RemoveAt(p)` or a method of the same type that indexes with it. Deterministic, provable per finding. Advisory.

  • The guard on line 491 rejects `progId` and line 492 reports that rejection as `ArgumentNullException` — but the condition's own test `String.IsNullOrEmpty(progId)` is true of a value that is NOT null: it is satisfied by an EMPTY `progId`, and on that path `progId` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — Source/NetOffice/COMObject.cs:492
  • The guard on line 512 rejects `progId` and line 513 reports that rejection as `ArgumentNullException` — but the condition's own test `String.IsNullOrEmpty(progId)` is true of a value that is NOT null: it is satisfied by an EMPTY `progId`, and on that path `progId` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — Source/NetOffice/COMObject.cs:513
  • The guard on line 18 rejects `name` and line 19 reports that rejection as `ArgumentNullException` — but the condition's own test `String.IsNullOrWhiteSpace(name)` is true of a value that is NOT null: it is satisfied by an EMPTY `name`, and on that path `name` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — Source/NetOffice/Loader/DependentAssembly.cs:19
  • The guard on line 204 rejects `componentName` and line 205 reports that rejection as `ArgumentNullException` — but the condition's own test `String.IsNullOrEmpty(componentName)` is true of a value that is NOT null: it is satisfied by an EMPTY `componentName`, and on that path `componentName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — Source/NetOffice/Running/RunningObjectTable.cs:205
  • The guard on line 206 rejects `className` and line 207 reports that rejection as `ArgumentNullException` — but the condition's own test `String.IsNullOrEmpty(className)` is true of a value that is NOT null: it is satisfied by an EMPTY `className`, and on that path `className` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — Source/NetOffice/Running/RunningObjectTable.cs:207
  • The guard on line 104 rejects `resourcePath` and line 105 reports that rejection as `ArgumentNullException` — but the condition's own test `String.IsNullOrEmpty(resourcePath)` is true of a value that is NOT null: it is satisfied by an EMPTY `resourcePath`, and on that path `resourcePath` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — Source/NetOffice/Tools/CustomUIAttribute.cs:105
  • The guard on line 106 rejects `assemblyNamespace` and line 107 reports that rejection as `ArgumentNullException` — but the condition's own test `String.IsNullOrEmpty(assemblyNamespace)` is true of a value that is NOT null: it is satisfied by an EMPTY `assemblyNamespace`, and on that path `assemblyNamespace` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — Source/NetOffice/Tools/CustomUIAttribute.cs:107
  • The guard on line 31 rejects `name` and line 32 reports that rejection as `ArgumentNullException` — but the condition's own test `String.IsNullOrWhiteSpace(name)` is true of a value that is NOT null: it is satisfied by an EMPTY `name`, and on that path `name` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — Source/NetOffice/Tools/Native/Bridge/CdeclHandle.cs:32
  • The guard on line 96 rejects `name` and line 97 reports that rejection as `ArgumentNullException` — but the condition's own test `String.IsNullOrWhiteSpace(name)` is true of a value that is NOT null: it is satisfied by an EMPTY `name`, and on that path `name` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — Source/NetOffice/Tools/Native/Bridge/CdeclHandle.cs:97
  • The guard on line 133 rejects `fullFileName` and line 134 reports that rejection as `ArgumentNullException` — but the condition's own test `String.IsNullOrWhiteSpace(fullFileName)` is true of a value that is NOT null: it is satisfied by an EMPTY `fullFileName`, and on that path `fullFileName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — Source/NetOffice/Tools/Native/Bridge/CdeclHandle.cs:134
  • The guard on line 192 rejects `fileName` and line 193 reports that rejection as `ArgumentNullException` — but the condition's own test `String.IsNullOrWhiteSpace(fileName)` is true of a value that is NOT null: it is satisfied by an EMPTY `fileName`, and on that path `fileName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — Source/NetOffice/Tools/Native/Bridge/CdeclHandle.cs:193
  • The guard on line 184 rejects `componentName` and line 185 reports that rejection as `ArgumentNullException` — but the condition's own test `String.IsNullOrWhiteSpace(componentName)` is true of a value that is NOT null: it is satisfied by an EMPTY `componentName`, and on that path `componentName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — Source/NetOffice/Trace/PerformanceTrace.cs:185
  • The guard on line 212 rejects `componentName` and line 213 reports that rejection as `ArgumentNullException` — but the condition's own test `String.IsNullOrWhiteSpace(componentName)` is true of a value that is NOT null: it is satisfied by an EMPTY `componentName`, and on that path `componentName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — Source/NetOffice/Trace/PerformanceTrace.cs:213
  • The guard on line 214 rejects `entityName` and line 215 reports that rejection as `ArgumentNullException` — but the condition's own test `String.IsNullOrWhiteSpace(entityName)` is true of a value that is NOT null: it is satisfied by an EMPTY `entityName`, and on that path `entityName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — Source/NetOffice/Trace/PerformanceTrace.cs:215
  • The guard on line 243 rejects `componentName` and line 244 reports that rejection as `ArgumentNullException` — but the condition's own test `String.IsNullOrWhiteSpace(componentName)` is true of a value that is NOT null: it is satisfied by an EMPTY `componentName`, and on that path `componentName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — Source/NetOffice/Trace/PerformanceTrace.cs:244
  • The guard on line 245 rejects `entityName` and line 246 reports that rejection as `ArgumentNullException` — but the condition's own test `String.IsNullOrWhiteSpace(entityName)` is true of a value that is NOT null: it is satisfied by an EMPTY `entityName`, and on that path `entityName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — Source/NetOffice/Trace/PerformanceTrace.cs:246
  • The guard on line 247 rejects `methodName` and line 248 reports that rejection as `ArgumentNullException` — but the condition's own test `String.IsNullOrWhiteSpace(methodName)` is true of a value that is NOT null: it is satisfied by an EMPTY `methodName`, and on that path `methodName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — Source/NetOffice/Trace/PerformanceTrace.cs:248
  • The guard on line 113 rejects `resourcePath` and line 114 reports that rejection as `ArgumentNullException` — but the condition's own test `String.IsNullOrEmpty(resourcePath)` is true of a value that is NOT null: it is satisfied by an EMPTY `resourcePath`, and on that path `resourcePath` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — Source/Outlook/Tools/OlCustomUIAttribute.cs:114
  • The guard on line 115 rejects `assemblyNamespace` and line 116 reports that rejection as `ArgumentNullException` — but the condition's own test `String.IsNullOrEmpty(assemblyNamespace)` is true of a value that is NOT null: it is satisfied by an EMPTY `assemblyNamespace`, and on that path `assemblyNamespace` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — Source/Outlook/Tools/OlCustomUIAttribute.cs:116
  • The guard on line 300 rejects `assemblyFullPath` and line 301 reports that rejection as `ArgumentNullException` — but the condition's own test `String.IsNullOrWhiteSpace(assemblyFullPath)` is true of a value that is NOT null: it is satisfied by an EMPTY `assemblyFullPath`, and on that path `assemblyFullPath` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — Toolbox/Toolbox/Program.cs:301

What to do

  • Each finding names the throw and the test in its own condition that is true of a NON-null value. Confirm from the two, then throw the exception that describes what was actually wrong: `ArgumentException` for a value that arrived empty, or the .NET 8 helpers that spell the whole guard in one line and pick the type for you — `ArgumentException.ThrowIfNullOrEmpty(s)` / `ThrowIfNullOrWhiteSpace(s)` for strings, `ArgumentNullException.ThrowIfNull(x)` followed by `ArgumentOutOfRangeException.ThrowIfZero(x.Count)` for a collection. Splitting the two conditions is usually clearer than picking one exception for both: they are different failures and the caller may want to handle them differently.
X26 · Unsynchronised callback handoff10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.

Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.

X27 · Collection changed while being enumerated8.0 / 10Strong✓ Tool-verified

Other · Code Health — Whether a `foreach` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is enumerating invalidates the enumerator it is holding, so the next `MoveNext` throws `InvalidOperationException` and the remaining items are never seen.

Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.

  • The loop walks `_pointList`, and line 239 calls `point.RemoveEventBinding(…)`, which reaches `_pointList.Remove(this)` in `SinkHelper.RemoveEventBinding` — a structural change to that same `List` while the loop's enumerator is live. The next `MoveNext` throws `InvalidOperationException: Collection was modified; enumeration operation may not execute`, so every pass that reaches this call ends the loop by exception instead of by running out of items, and the remaining items are never seen. — Source/NetOffice/SinkHelper.cs:238

What to do

  • Each finding names the two spans that cannot both stand — the `foreach` source, and the call inside the body that structurally changes that same collection. Confirm from those two, then pick one: enumerate a snapshot (`foreach (var x in c.ToList())`), collect what needs changing and apply it after the loop, or — where the loop was only ever meant to act on the first match — `break` immediately after the mutation, which is the one shape that is already safe.
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.

Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.

X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.

Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.

X3 · Exception handling6.4 / 10Adequate✓ Tool-verified

Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.

Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.

  • `throw exception;` resets the exception's stack trace to this line, hiding where it really came from. Use a bare `throw;` to preserve the original stack. (×3) — Source/NetOffice/COMObject.cs:1355, Source/NetOffice/Core.cs:1291, Toolbox/Toolbox/ToolboxControls/OfficeUI/OfficeUIControl.cs:185
  • `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. (×31) — Source/NetOffice/COMProxyShare.cs:335, Source/NetOffice/Contribution/CollectionsGeneric/DisposableSequence.cs:98, Source/NetOffice/Contribution/CollectionsGeneric/DisposableSequence.cs:124, …
  • An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×3) — Examples/AddinProjectHelper/Program.cs:31, Examples/AddinRemovalTool/Program.cs:31, Toolbox/Toolbox/ToolboxControls/ApplicationObserver/HotKey.cs:194
  • `catch (System.ComponentModel.Win32Exception)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. — Toolbox/Toolbox/ToolboxControls/ApplicationObserver/OfficeProcessKiller.cs:294
  • `catch (NotSupportedException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. — Toolbox/Toolbox/ToolboxControls/ApplicationObserver/OfficeProcessKiller.cs:295
  • `catch (InvalidOperationException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. — Toolbox/Toolbox/ToolboxControls/ApplicationObserver/OfficeProcessKiller.cs:296

What to do

  • Rethrow loses stack trace (`throw ex;`)
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.

Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.

X5 · Nullable reference types10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether nullable reference types are enabled and not undermined by heavy `!` suppression.

Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.

  • This method contradicts itself about `sheet`: line 25 assigns it with `as Excel.Worksheet`, which hands back null rather than throwing when the value is not a `Excel.Worksheet`, but line 26 then dereferences it directly as `sheet.Cells` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `sheet` once before the first use and handle the null case, or cast with `(Excel.Worksheet)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Source/ClientApplication/RunExcel01.cs:26
  • This method contradicts itself about `shareProvider`: line 750 assigns it with `as ICOMProxyShareProvider`, which hands back null rather than throwing when the value is not a `ICOMProxyShareProvider`, but line 751 then dereferences it directly as `shareProvider.SetProxyShare` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `shareProvider` once before the first use and handle the null case, or cast with `(ICOMProxyShareProvider)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Source/NetOffice/COMObject.cs:751
  • This method contradicts itself about `shareProvider`: line 1266 assigns it with `as ICOMProxyShareProvider`, which hands back null rather than throwing when the value is not a `ICOMProxyShareProvider`, but line 1267 then dereferences it directly as `shareProvider.SetProxyShare` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `shareProvider` once before the first use and handle the null case, or cast with `(ICOMProxyShareProvider)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Source/NetOffice/COMObject.cs:1267
  • This method contradicts itself about `childHandles`: line 226 assigns it with `as List<IntPtr>`, which hands back null rather than throwing when the value is not a `List<IntPtr>`, but line 227 then dereferences it directly as `childHandles.Add` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `childHandles` once before the first use and handle the null case, or cast with `(List<IntPtr>)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Source/NetOffice/Running/ChildWindowBatchEnumerator.cs:227
  • This method contradicts itself about `childHandles`: line 165 assigns it with `as List<IntPtr>`, which hands back null rather than throwing when the value is not a `List<IntPtr>`, but line 166 then dereferences it directly as `childHandles.Add` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `childHandles` once before the first use and handle the null case, or cast with `(List<IntPtr>)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Source/NetOffice/Running/ChildWindowEnumerator.cs:166
  • This method contradicts itself about `childHandles`: line 171 assigns it with `as List<IntPtr>`, which hands back null rather than throwing when the value is not a `List<IntPtr>`, but line 172 then dereferences it directly as `childHandles.Add` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `childHandles` once before the first use and handle the null case, or cast with `(List<IntPtr>)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Source/NetOffice/Running/ChildWindowEnumerator.cs:172
  • This method contradicts itself about `attribute`: line 135 assigns it with `as CustomUIAttribute`, which hands back null rather than throwing when the value is not a `CustomUIAttribute`, but line 136 then dereferences it directly as `attribute.RibbonID` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `attribute` once before the first use and handle the null case, or cast with `(CustomUIAttribute)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Source/NetOffice/Tools/AttributeReflector.cs:136
  • This method contradicts itself about `toolStripItem`: line 944 assigns it with `as ToolStripItem`, which hands back null rather than throwing when the value is not a `ToolStripItem`, but line 945 then dereferences it directly as `toolStripItem.Tag` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `toolStripItem` once before the first use and handle the null case, or cast with `(ToolStripItem)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Source/Office.Extensions/TrayMenuUtils/TrayMenu.cs:945
  • This method contradicts itself about `toolStripItem`: line 958 assigns it with `as ToolStripMenuItem`, which hands back null rather than throwing when the value is not a `ToolStripMenuItem`, but line 959 then dereferences it directly as `toolStripItem.Checked` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `toolStripItem` once before the first use and handle the null case, or cast with `(ToolStripMenuItem)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Source/Office.Extensions/TrayMenuUtils/TrayMenu.cs:959
  • This method contradicts itself about `toolStripItem`: line 971 assigns it with `as ToolStripMenuItem`, which hands back null rather than throwing when the value is not a `ToolStripMenuItem`, but line 972 then dereferences it directly as `toolStripItem.Tag` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `toolStripItem` once before the first use and handle the null case, or cast with `(ToolStripMenuItem)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Source/Office.Extensions/TrayMenuUtils/TrayMenu.cs:972
  • This method contradicts itself about `toolStripItem`: line 985 assigns it with `as ToolStripTextBox`, which hands back null rather than throwing when the value is not a `ToolStripTextBox`, but line 986 then dereferences it directly as `toolStripItem.Tag` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `toolStripItem` once before the first use and handle the null case, or cast with `(ToolStripTextBox)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Source/Office.Extensions/TrayMenuUtils/TrayMenu.cs:986
  • This method contradicts itself about `toolStripItem`: line 999 assigns it with `as ToolStripComboBox`, which hands back null rather than throwing when the value is not a `ToolStripComboBox`, but line 1000 then dereferences it directly as `toolStripItem.Tag` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `toolStripItem` once before the first use and handle the null case, or cast with `(ToolStripComboBox)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Source/Office.Extensions/TrayMenuUtils/TrayMenu.cs:1000
  • This method contradicts itself about `toolStripItem`: line 1013 assigns it with `as ToolStripComboBox`, which hands back null rather than throwing when the value is not a `ToolStripComboBox`, but line 1014 then dereferences it directly as `toolStripItem.Tag` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `toolStripItem` once before the first use and handle the null case, or cast with `(ToolStripComboBox)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Source/Office.Extensions/TrayMenuUtils/TrayMenu.cs:1014
  • This method contradicts itself about `toolStripItem`: line 1027 assigns it with `as ToolStripControlHost`, which hands back null rather than throwing when the value is not a `ToolStripControlHost`, but line 1028 then dereferences it directly as `toolStripItem.Tag` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `toolStripItem` once before the first use and handle the null case, or cast with `(ToolStripControlHost)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Source/Office.Extensions/TrayMenuUtils/TrayMenu.cs:1028
  • This method contradicts itself about `toolStripItem`: line 1041 assigns it with `as ToolStripControlHost`, which hands back null rather than throwing when the value is not a `ToolStripControlHost`, but line 1042 then dereferences it directly as `toolStripItem.Tag` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `toolStripItem` once before the first use and handle the null case, or cast with `(ToolStripControlHost)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Source/Office.Extensions/TrayMenuUtils/TrayMenu.cs:1042
  • This method contradicts itself about `toolStripItem`: line 1055 assigns it with `as ToolStripControlHost`, which hands back null rather than throwing when the value is not a `ToolStripControlHost`, but line 1056 then dereferences it directly as `toolStripItem.Tag` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `toolStripItem` once before the first use and handle the null case, or cast with `(ToolStripControlHost)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Source/Office.Extensions/TrayMenuUtils/TrayMenu.cs:1056
  • This method contradicts itself about `button`: line 477 assigns it with `as RadioButton`, which hands back null rather than throwing when the value is not a `RadioButton`, but line 478 then dereferences it directly as `button.Checked` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `button` once before the first use and handle the null case, or cast with `(RadioButton)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Source/Office.Extensions/TrayMenuUtils/TrayMenuMonitorItemControl.cs:478
  • This method contradicts itself about `args`: line 586 assigns it with `as MouseEventArgs`, which hands back null rather than throwing when the value is not a `MouseEventArgs`, but line 587 then dereferences it directly as `args.Button` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `args` once before the first use and handle the null case, or cast with `(MouseEventArgs)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Source/Office.Extensions/TrayUtils.cs:587
  • This method contradicts itself about `label`: line 182 assigns it with `as LinkLabel`, which hands back null rather than throwing when the value is not a `LinkLabel`, but line 183 then dereferences it directly as `label.Tag` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `label` once before the first use and handle the null case, or cast with `(LinkLabel)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Examples/ExampleBase/ExampleForm.cs:183
  • This method contradicts itself about `mailItem`: line 85 assigns it with `as Outlook.MailItem`, which hands back null rather than throwing when the value is not a `Outlook.MailItem`, but line 86 then dereferences it directly as `mailItem.CloseEvent` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `mailItem` once before the first use and handle the null case, or cast with `(Outlook.MailItem)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Examples/Outlook/Automation/Examples/Example06.cs:86
  • This method contradicts itself about `mailItem`: line 68 assigns it with `as Outlook.MailItem`, which hands back null rather than throwing when the value is not a `Outlook.MailItem`, but line 71 then dereferences it directly as `mailItem.Recipients` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `mailItem` once before the first use and handle the null case, or cast with `(Outlook.MailItem)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Examples/Outlook/Automation/Examples/Example03.cs:71
  • This method contradicts itself about `newTask`: line 20 assigns it with `as Outlook.TaskItem`, which hands back null rather than throwing when the value is not a `Outlook.TaskItem`, but line 23 then dereferences it directly as `newTask.Subject` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `newTask` once before the first use and handle the null case, or cast with `(Outlook.TaskItem)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Examples/Outlook/Automation/Examples/Example02.cs:23
  • This method contradicts itself about `entry`: line 96 assigns it with `as AddinEntry`, which hands back null rather than throwing when the value is not a `AddinEntry`, but line 97 then dereferences it directly as `entry.Delete` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `entry` once before the first use and handle the null case, or cast with `(AddinEntry)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Examples/AddinRemovalTool/Form1.cs:97
  • This method contradicts itself about `attrib`: line 52 assigns it with `as RessourceTableAttribute`, which hands back null rather than throwing when the value is not a `RessourceTableAttribute`, but line 53 then dereferences it directly as `attrib.Address` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `attrib` once before the first use and handle the null case, or cast with `(RessourceTableAttribute)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Toolbox/Toolbox/RessourceTableAttribute.cs:53
  • This method contradicts itself about `control`: line 154 assigns it with `as Control`, which hands back null rather than throwing when the value is not a `Control`, but line 155 then dereferences it directly as `control.Tag` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `control` once before the first use and handle the null case, or cast with `(Control)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Toolbox/Toolbox/ToolboxControls/About/AboutControl.cs:155
  • This method contradicts itself about `label`: line 182 assigns it with `as LinkLabel`, which hands back null rather than throwing when the value is not a `LinkLabel`, but line 183 then dereferences it directly as `label.Text` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `label` once before the first use and handle the null case, or cast with `(LinkLabel)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Toolbox/Toolbox/ToolboxControls/About/AboutControl.cs:183
  • This method contradicts itself about `label`: line 207 assigns it with `as LinkLabel`, which hands back null rather than throwing when the value is not a `LinkLabel`, but line 208 then dereferences it directly as `label.Tag` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `label` once before the first use and handle the null case, or cast with `(LinkLabel)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Toolbox/Toolbox/ToolboxControls/About/AboutControl.cs:208
  • This method contradicts itself about `blockArray`: line 187 assigns it with `as DataBlock[]`, which hands back null rather than throwing when the value is not a `DataBlock[]`, but line 190 then dereferences it directly with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `blockArray` once before the first use and handle the null case, or cast with `(DataBlock[])` so the failure is reported where it happens — rather than leaving the two readings side by side. — Toolbox/Toolbox/Controls/Hex/DataMap.cs:190
  • This method contradicts itself about `root`: line 188 assigns it with `as XmlNode`, which hands back null rather than throwing when the value is not a `XmlNode`, but line 191 then dereferences it directly as `root.Attributes` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `root` once before the first use and handle the null case, or cast with `(XmlNode)` so the failure is reported where it happens — rather than leaving the two readings side by side. — REDACTED:191
  • This method contradicts itself about `winControl`: line 337 assigns it with `as Control`, which hands back null rather than throwing when the value is not a `Control`, but line 338 then dereferences it directly as `winControl.Visible` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `winControl` once before the first use and handle the null case, or cast with `(Control)` so the failure is reported where it happens — rather than leaving the two readings side by side. — REDACTED:338
  • This method contradicts itself about `versions`: line 138 assigns it with `as CustomAttributeArgument[]`, which hands back null rather than throwing when the value is not a `CustomAttributeArgument[]`, but line 139 then dereferences it directly as `versions.Length` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `versions` once before the first use and handle the null case, or cast with `(CustomAttributeArgument[])` so the failure is reported where it happens — rather than leaving the two readings side by side. — Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/NetOfficeSupportTable.cs:139
  • This method contradicts itself about `versions`: line 203 assigns it with `as CustomAttributeArgument[]`, which hands back null rather than throwing when the value is not a `CustomAttributeArgument[]`, but line 204 then dereferences it directly as `versions.Length` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `versions` once before the first use and handle the null case, or cast with `(CustomAttributeArgument[])` so the failure is reported where it happens — rather than leaving the two readings side by side. — Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/NetOfficeSupportTable.cs:204
  • This method contradicts itself about `versions`: line 333 assigns it with `as CustomAttributeArgument[]`, which hands back null rather than throwing when the value is not a `CustomAttributeArgument[]`, but line 334 then dereferences it directly as `versions.Length` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `versions` once before the first use and handle the null case, or cast with `(CustomAttributeArgument[])` so the failure is reported where it happens — rather than leaving the two readings side by side. — Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/NetOfficeSupportTable.cs:334
  • This method contradicts itself about `versions`: line 354 assigns it with `as CustomAttributeArgument[]`, which hands back null rather than throwing when the value is not a `CustomAttributeArgument[]`, but line 355 then dereferences it directly as `versions.Length` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `versions` once before the first use and handle the null case, or cast with `(CustomAttributeArgument[])` so the failure is reported where it happens — rather than leaving the two readings side by side. — Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/NetOfficeSupportTable.cs:355
  • This method contradicts itself about `versions`: line 381 assigns it with `as CustomAttributeArgument[]`, which hands back null rather than throwing when the value is not a `CustomAttributeArgument[]`, but line 382 then dereferences it directly as `versions.Length` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `versions` once before the first use and handle the null case, or cast with `(CustomAttributeArgument[])` so the failure is reported where it happens — rather than leaving the two readings side by side. — Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/NetOfficeSupportTable.cs:382
  • This method contradicts itself about `commandBar`: line 298 assigns it with `as OfficeApi.CommandBar`, which hands back null rather than throwing when the value is not a `OfficeApi.CommandBar`, but line 299 then dereferences it directly as `commandBar.Controls` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `commandBar` once before the first use and handle the null case, or cast with `(OfficeApi.CommandBar)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Toolbox/Toolbox/ToolboxControls/OfficeUI/OfficeUIControl.cs:299
  • This method contradicts itself about `commandBar`: line 329 assigns it with `as OfficeApi.CommandBar`, which hands back null rather than throwing when the value is not a `OfficeApi.CommandBar`, but line 330 then dereferences it directly as `commandBar.Reset` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `commandBar` once before the first use and handle the null case, or cast with `(OfficeApi.CommandBar)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Toolbox/Toolbox/ToolboxControls/OfficeUI/OfficeUIControl.cs:330
  • This method contradicts itself about `control`: line 334 assigns it with `as OfficeApi.CommandBarControl`, which hands back null rather than throwing when the value is not a `OfficeApi.CommandBarControl`, but line 335 then dereferences it directly as `control.Reset` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `control` once before the first use and handle the null case, or cast with `(OfficeApi.CommandBarControl)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Toolbox/Toolbox/ToolboxControls/OfficeUI/OfficeUIControl.cs:335
  • This method contradicts itself about `commandBar`: line 357 assigns it with `as OfficeApi.CommandBar`, which hands back null rather than throwing when the value is not a `OfficeApi.CommandBar`, but line 358 then dereferences it directly as `commandBar.Delete` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `commandBar` once before the first use and handle the null case, or cast with `(OfficeApi.CommandBar)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Toolbox/Toolbox/ToolboxControls/OfficeUI/OfficeUIControl.cs:358
  • This method contradicts itself about `control`: line 363 assigns it with `as OfficeApi.CommandBarControl`, which hands back null rather than throwing when the value is not a `OfficeApi.CommandBarControl`, but line 364 then dereferences it directly as `control.Delete` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `control` once before the first use and handle the null case, or cast with `(OfficeApi.CommandBarControl)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Toolbox/Toolbox/ToolboxControls/OfficeUI/OfficeUIControl.cs:364

What to do

  • Where a method uses `?.` on a symbol and then dereferences it directly, settle the question once: test it before the first use and handle null, or drop the `?.`.

Reference — by lens

The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.

LensScoreRatingImpact
Code Health63.7Adequate — gated by D18Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture71.4Adequate — gated by AX2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity59.6Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness66.9Adequate — gated by D13Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security33.0Weak — gated by D28, D29, D36, C1Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance100.0ExemplaryStrongest area.
Unscored — 4 check(s) recorded observations but carry no score

These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.

  • P12 CI test-gate honesty — 2 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
  • X10 Duplicated predicate — 16 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X6 Hand-rolled structured-format parsing — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 35 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for

These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.

  • C3 Audit Trail — Repo shows no audit-logging mechanism (IAuditable, an immutable audit log, an EF SaveChanges interceptor) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
  • C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 55 check(s) not relevant to this codebase

These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.

  • AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
  • AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
  • AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
  • AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
  • AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
  • AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
  • AX1 Captive dependencies — no DI registrations detected
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
  • D1 Cyclomatic Complexity — Cyclomatic Complexity not included (time budget)
  • D11 Test Reliability — Test runner surfaced no tests
  • D12 Dependency Hygiene — Dependency hygiene not measured
  • D2 Cognitive Complexity — Cognitive Complexity not included (time budget)
  • D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
  • D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
  • D25 ADR Conformance — no ADRs to check
  • D3 God Classes — God Classes not included (time budget)
  • D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
  • D32 Data Compliance (PII/GDPR) — 2 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • D34 Knowledge Freshness — history too condensed to judge knowledge freshness
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
  • D8 Code Coverage — Coverage not measured
  • DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
  • ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
  • ED5 Idempotency — Idempotency could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • P10 Library API & versioning — Library API & versioning could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
  • P11 BDD / executable specs — BDD / executable specs could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
  • P2 Observability — This repo is a library, not a deployed service — it has no process to operate, so production observability (structured logging, tracing/metrics, health checks) is N/A. A library may log via an injected ILogger, but the absence of operational telemetry is not a defect here. If it grows a host (web API, worker), the dimension reactivates.
  • P7 Outbound HTTP resilience — Outbound HTTP resilience could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
  • P8 Schema migrations — Schema migrations could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
  • P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
  • PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
  • SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X2 Cancellation propagation — no async method does work a token could cancel
  • X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X32 Type resolved by simple name across every loaded assembly — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X4 Structured logging — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.

Critical — 278 finding(s)
D28 · Secrets (history) · High secret · ×106
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 81 more in this group — see findings.md.
D13 · Secret Scanning · Leaked secret · ×104
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 79 more in this group — see findings.md.
D17 · Explicit Debt · WriteOnlyPrivateField · ×20
  • WriteOnlyPrivateField REDACTED:42 — private string _visioTypesRelative — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField REDACTED:43 — private string _visioEnumsRelative — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField Examples/Access/IExtensibility COMAddin Examples/TaskPane/Addin.cs:23 — private SampleControl _sampleControl — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField Examples/Excel/IExtensibility COMAddin Examples/TaskPane/Addin.cs:23 — private SampleControl _sampleControl — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField Examples/Outlook/IExtensibility COMAddin Examples/TaskPane/Addin.cs:25 — private SampleControl _sampleControl — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField Examples/PowerPoint/IExtensibility COMAddin Examples/TaskPane/Addin.cs:23 — private SampleControl _sampleControl — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField Examples/Word/IExtensibility COMAddin Examples/TaskPane/Addin.cs:23 — private SampleControl _sampleControl — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField Source/Access/Tools/Contribution/CommonUtils.cs:14 — private AccessApi.Application _ownerApplication — assigned 2 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField Source/Excel/Tools/Contribution/CommonUtils.cs:13 — private ExcelApi.Application _ownerApplication — assigned 2 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField Source/NetOffice/Running/ChildWindowBatchEnumerator.cs:73 — private ChildWindowBatchEnumerator _currentInstance — assigned 3 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField Source/NetOffice/Running/ChildWindowEnumerator.cs:31 — private ChildWindowEnumerator _currentInstance — assigned 3 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField Source/Office.Extensions/TrayMenuUtils/TrayMenuMonitorItem.cs:31 — private Action _disableHighlight — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField Source/Office/Tools/Contribution/ColorUtils.cs:13 — private CommonUtils _owner — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField Source/Office/Tools/Contribution/ImageUtils.cs:41 — private CommonUtils _owner — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField Source/Word/Tools/Contribution/ApplicationUtils.cs:39 — private CommonUtils _owner — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField Source/Outlook/Tools/Contribution/CommonUtils.cs:18 — private OutlookApi.Application _ownerApplication — assigned 2 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField Source/PowerPoint/Tools/Contribution/ApplicationUtils.cs:55 — private Guid _unknown — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField Source/Word/Tools/Contribution/ApplicationUtils.cs:37 — private Guid _unknown — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField Source/PowerPoint/Tools/Contribution/CommonUtils.cs:13 — private PowerPointApi.Application _ownerApplication — assigned 2 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField Source/Word/Tools/Contribution/CommonUtils.cs:13 — private WordApi.Application _ownerApplication — assigned 2 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AX3 · Project dependency cycles · Namespace dependency cycle · ×5
  • Namespace dependency cycle Source/NetOffice/Availability/SupportedEntityFinder.cs:13 — The namespaces NetOffice ↔ NetOffice.Availability ↔ NetOffice.Loader depend on each other. The lightest dependency in the cycle is NetOffice.Availability → NetOffice (NetOffice.Availability.SupportedEntityFinder → NetOffice.Core, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
  • Namespace dependency cycle Source/Office/NativeCaller/IRibbonUI.cs:13 — The namespaces NetOffice.OfficeApi ↔ NetOffice.OfficeApi.Native depend on each other. The lightest dependency in the cycle is NetOffice.OfficeApi → NetOffice.OfficeApi.Native (NetOffice.OfficeApi.IRibbonUI → NetOffice.OfficeApi.Native.IRibbonUI, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
  • Namespace dependency cycle Source/NetOffice/Tools/ICOMAddin.cs:11 — The namespaces NetOffice.Tools ↔ NetOffice.Tools.Native depend on each other. The lightest dependency in the cycle is NetOffice.Tools → NetOffice.Tools.Native (NetOffice.Tools.ICOMAddin → NetOffice.Tools.Native.IDTExtensibility2, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
  • Namespace dependency cycle Source/Office/Tools/COMAddin.cs:20 — The namespaces NetOffice.OfficeApi.Tools ↔ NetOffice.OfficeApi.Tools.Contribution ↔ NetOffice.OfficeApi.Tools.Informations depend on each other. The lightest dependency in the cycle is NetOffice.OfficeApi.Tools → NetOffice.OfficeApi.Tools.Contribution (NetOffice.OfficeApi.Tools.COMAddin → NetOffice.OfficeApi.Tools.Contribution.CommonUtils, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
  • Namespace dependency cycle Toolbox/Toolbox/ToolboxControls/ProjectWizard/Controls/ProjectControl.cs:18 — The namespaces NetOffice.DeveloperToolbox.ToolboxControls.ProjectWizard ↔ NetOffice.DeveloperToolbox.ToolboxControls.ProjectWizard.Controls depend on each other. The lightest dependency in the cycle is NetOffice.DeveloperToolbox.ToolboxControls.ProjectWizard.Controls → NetOffice.DeveloperToolbox.ToolboxControls.ProjectWizard (NetOffice.DeveloperToolbox.ToolboxControls.ProjectWizard.Controls.ProjectControl → NetOffice.DeveloperToolbox.ToolboxControls.ProjectWizard.ProjectType, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
D17 · Explicit Debt · EmptyCatchBlock · ×4
  • EmptyCatchBlock Examples/AddinProjectHelper/Program.cs:31 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock Examples/AddinRemovalTool/Program.cs:31 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock Examples/Other/Outlook Addin - Use Twitter/Outlook Addin - Use Twitter/UserControls/TweetPane.cs:103 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock Toolbox/Toolbox/ToolboxControls/ApplicationObserver/HotKey.cs:194 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
D17 · Explicit Debt · NoWarnInCsproj · ×4
  • NoWarnInCsproj Source/ClientApplication/ClientApplication.csproj:10 — 1701 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj Source/ClientApplication/ClientApplication.csproj:10 — 1702 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj Source/ClientApplication/ClientApplication.csproj:10 — 1519 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj Source/NetOffice.Tests/NetOffice.Tests.csproj:11 — CS0067 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
Serious — 2333 finding(s)
D4 · Code Duplication · Edited copy of a member (3 corresponding lines) · ×305
  • Edited copy of a member (3 corresponding lines) Source/DAO/DispatchInterfaces/Workspace.cs:364 — Source/DAO/DispatchInterfaces/Workspace.cs:364-366 | Source/DAO/DispatchInterfaces/_DBEngine.cs:373-375 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) Source/DAO/DispatchInterfaces/Workspace.cs:514 — Source/DAO/DispatchInterfaces/Workspace.cs:514-516 | Source/DAO/DispatchInterfaces/_DBEngine.cs:565-567 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) Source/Excel/DispatchInterfaces/Arcs.cs:958 — Source/Excel/DispatchInterfaces/Arcs.cs:958-960 | Source/Excel/Interfaces/IArcs.cs:957-959 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) Source/Excel/DispatchInterfaces/Buttons.cs:1024 — Source/Excel/DispatchInterfaces/Buttons.cs:1024-1026 | Source/Excel/Interfaces/IButtons.cs:1023-1025 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) Source/Excel/DispatchInterfaces/CalculatedMembers.cs:200 — Source/Excel/DispatchInterfaces/CalculatedMembers.cs:200-202 | Source/Excel/Interfaces/ICalculatedMembers.cs:194-196 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) Source/Excel/DispatchInterfaces/CalculatedMembers.cs:291 — Source/Excel/DispatchInterfaces/CalculatedMembers.cs:291-293 | Source/Excel/Interfaces/ICalculatedMembers.cs:280-282 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) Source/Excel/DispatchInterfaces/CalculatedMembers.cs:379 — Source/Excel/DispatchInterfaces/CalculatedMembers.cs:379-381 | Source/Excel/Interfaces/ICalculatedMembers.cs:364-366 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) Source/Excel/DispatchInterfaces/ChartObjects.cs:651 — Source/Excel/DispatchInterfaces/ChartObjects.cs:651-653 | Source/Excel/Interfaces/IChartObjects.cs:626-628 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) Source/Excel/DispatchInterfaces/Charts.cs:808 — Source/Excel/DispatchInterfaces/Charts.cs:808-810 | Source/Excel/Interfaces/ICharts.cs:779-781 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) Source/Excel/DispatchInterfaces/CheckBoxes.cs:901 — Source/Excel/DispatchInterfaces/CheckBoxes.cs:901-903 | Source/Excel/Interfaces/ICheckBoxes.cs:900-902 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) Source/Excel/DispatchInterfaces/Connections.cs:267 — Source/Excel/DispatchInterfaces/Connections.cs:267-269 | Source/Excel/Interfaces/IConnections.cs:259-261 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) Source/Excel/DispatchInterfaces/Connections.cs:324 — Source/Excel/DispatchInterfaces/Connections.cs:324-326 | Source/Excel/Interfaces/IConnections.cs:316-318 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) Source/Excel/DispatchInterfaces/DropDowns.cs:1020 — Source/Excel/DispatchInterfaces/DropDowns.cs:1020-1022 | Source/Excel/Interfaces/IDropDowns.cs:1019-1021 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) Source/Excel/DispatchInterfaces/EditBoxes.cs:851 — Source/Excel/DispatchInterfaces/EditBoxes.cs:851-853 | Source/Excel/Interfaces/IEditBoxes.cs:850-852 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) Source/Excel/DispatchInterfaces/FormatConditions.cs:200 — Source/Excel/DispatchInterfaces/FormatConditions.cs:200-202 | Source/Excel/Interfaces/IFormatConditions.cs:194-196 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) Source/Excel/DispatchInterfaces/GroupBoxes.cs:823 — Source/Excel/DispatchInterfaces/GroupBoxes.cs:823-825 | Source/Excel/Interfaces/IGroupBoxes.cs:823-825 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) Source/Excel/DispatchInterfaces/Labels.cs:816 — Source/Excel/DispatchInterfaces/Labels.cs:816-818 | Source/Excel/Interfaces/ILabels.cs:816-818 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) Source/Excel/DispatchInterfaces/Lines.cs:586 — Source/Excel/DispatchInterfaces/Lines.cs:586-588 | Source/Excel/Interfaces/ILines.cs:586-588 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) Source/Excel/DispatchInterfaces/ListBoxes.cs:899 — Source/Excel/DispatchInterfaces/ListBoxes.cs:899-901 | Source/Excel/Interfaces/IListBoxes.cs:899-901 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) Source/Excel/DispatchInterfaces/ListObjects.cs:282 — Source/Excel/DispatchInterfaces/ListObjects.cs:282-284 | Source/Excel/Interfaces/IListObjects.cs:270-272 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) Source/Excel/DispatchInterfaces/ListObjects.cs:362 — Source/Excel/DispatchInterfaces/ListObjects.cs:362-364 | Source/Excel/Interfaces/IListObjects.cs:350-352 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) Source/Excel/DispatchInterfaces/MenuItems.cs:249 — Source/Excel/DispatchInterfaces/MenuItems.cs:249-251 | Source/Excel/Interfaces/IMenuItems.cs:249-251 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) Source/Excel/DispatchInterfaces/Names.cs:257 — Source/Excel/DispatchInterfaces/Names.cs:257-259 | Source/Excel/Interfaces/INames.cs:246-248 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) Source/Excel/DispatchInterfaces/OLEObjects.cs:804 — Source/Excel/DispatchInterfaces/OLEObjects.cs:804-806 | Source/Excel/Interfaces/IOLEObjects.cs:766-768 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) Source/Excel/DispatchInterfaces/OptionButtons.cs:913 — Source/Excel/DispatchInterfaces/OptionButtons.cs:913-915 | Source/Excel/Interfaces/IOptionButtons.cs:913-915 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • + 280 more in this group — see findings.md.
D17 · Explicit Debt · IneffectivePragmaPair · ×193
  • IneffectivePragmaPair Source/ADODB/Classes/Command.cs:10 — #pragma disable is restored on the very next line — the pair suppresses nothing; delete it.
  • IneffectivePragmaPair Source/ADODB/Classes/Parameter.cs:10 — #pragma disable is restored on the very next line — the pair suppresses nothing; delete it.
  • IneffectivePragmaPair Source/ADODB/Classes/Record.cs:10 — #pragma disable is restored on the very next line — the pair suppresses nothing; delete it.
  • IneffectivePragmaPair Source/ADODB/Classes/Stream.cs:10 — #pragma disable is restored on the very next line — the pair suppresses nothing; delete it.
  • IneffectivePragmaPair Source/Access/Classes/AccessField.cs:10 — #pragma disable is restored on the very next line — the pair suppresses nothing; delete it.
  • IneffectivePragmaPair Source/Access/Classes/AdditionalData.cs:10 — #pragma disable is restored on the very next line — the pair suppresses nothing; delete it.
  • IneffectivePragmaPair Source/Access/Classes/AllDataAccessPages.cs:10 — #pragma disable is restored on the very next line — the pair suppresses nothing; delete it.
  • IneffectivePragmaPair Source/Access/Classes/AllDatabaseDiagrams.cs:10 — #pragma disable is restored on the very next line — the pair suppresses nothing; delete it.
  • IneffectivePragmaPair Source/Access/Classes/AllForms.cs:10 — #pragma disable is restored on the very next line — the pair suppresses nothing; delete it.
  • IneffectivePragmaPair Source/Access/Classes/AllFunctions.cs:10 — #pragma disable is restored on the very next line — the pair suppresses nothing; delete it.
  • IneffectivePragmaPair Source/Access/Classes/AllMacros.cs:10 — #pragma disable is restored on the very next line — the pair suppresses nothing; delete it.
  • IneffectivePragmaPair Source/Access/Classes/AllModules.cs:10 — #pragma disable is restored on the very next line — the pair suppresses nothing; delete it.
  • IneffectivePragmaPair Source/Access/Classes/AllQueries.cs:10 — #pragma disable is restored on the very next line — the pair suppresses nothing; delete it.
  • IneffectivePragmaPair Source/Access/Classes/AllReports.cs:10 — #pragma disable is restored on the very next line — the pair suppresses nothing; delete it.
  • IneffectivePragmaPair Source/Access/Classes/AllStoredProcedures.cs:10 — #pragma disable is restored on the very next line — the pair suppresses nothing; delete it.
  • IneffectivePragmaPair Source/Access/Classes/AllTables.cs:10 — #pragma disable is restored on the very next line — the pair suppresses nothing; delete it.
  • IneffectivePragmaPair Source/Access/Classes/AllViews.cs:10 — #pragma disable is restored on the very next line — the pair suppresses nothing; delete it.
  • IneffectivePragmaPair Source/Access/Classes/Application.cs:11 — #pragma disable is restored on the very next line — the pair suppresses nothing; delete it.
  • IneffectivePragmaPair Source/Access/Classes/AutoCorrect.cs:10 — #pragma disable is restored on the very next line — the pair suppresses nothing; delete it.
  • IneffectivePragmaPair Source/Access/Classes/CodeData.cs:10 — #pragma disable is restored on the very next line — the pair suppresses nothing; delete it.
  • IneffectivePragmaPair Source/Access/Classes/CodeProject.cs:10 — #pragma disable is restored on the very next line — the pair suppresses nothing; delete it.
  • IneffectivePragmaPair Source/Access/Classes/Control.cs:10 — #pragma disable is restored on the very next line — the pair suppresses nothing; delete it.
  • IneffectivePragmaPair Source/Access/Classes/CurrentData.cs:10 — #pragma disable is restored on the very next line — the pair suppresses nothing; delete it.
  • IneffectivePragmaPair Source/Access/Classes/CurrentProject.cs:10 — #pragma disable is restored on the very next line — the pair suppresses nothing; delete it.
  • IneffectivePragmaPair Source/Access/Classes/DataAccessPage.cs:10 — #pragma disable is restored on the very next line — the pair suppresses nothing; delete it.
  • + 168 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×131
  • Duplicated block (5 lines × 2) Source/Excel/Events/AppEvents.cs:686 — Source/Excel/Events/AppEvents.cs:686-690 | Source/Excel/Events/AppEvents.cs:702-706 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (5 lines × 2) Source/PowerPoint/Events/EApplication.cs:349 — Source/PowerPoint/Events/EApplication.cs:349-353 | Source/PowerPoint/Events/EApplication.cs:365-369 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (5 lines × 2) Source/OWC10/Events/ISpreadsheetEventSink.cs:438 — Source/OWC10/Events/ISpreadsheetEventSink.cs:438-442 | Source/OWC10/Events/ISpreadsheetEventSink.cs:454-458 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (5 lines × 2) Source/OWC10/Events/ISpreadsheetEventSink.cs:660 — Source/OWC10/Events/ISpreadsheetEventSink.cs:660-664 | Source/OWC10/Events/ISpreadsheetEventSink.cs:690-694 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (5 lines × 2) Source/MSComctlLib/Events/DImageComboEvents.cs:159 — Source/MSComctlLib/Events/DImageComboEvents.cs:159-163 | Source/MSComctlLib/Events/DImageComboEvents.cs:175-179 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (5 lines × 2) Source/ADODB/Events/RecordsetEvents.cs:222 — Source/ADODB/Events/RecordsetEvents.cs:222-226 | Source/ADODB/Events/RecordsetEvents.cs:261-265 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (5 lines × 2) Source/Outlook/Events/ExplorerEvents.cs:42 — Source/Outlook/Events/ExplorerEvents.cs:42-46 | Source/Outlook/Events/InspectorEvents.cs:23-27 — before extracting anything, compare `Source/Outlook/Events/ExplorerEvents.cs` and `Source/Outlook/Events/InspectorEvents.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 34 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 2) Source/Access/Events/DispAttachmentEvents.cs:42 — Source/Access/Events/DispAttachmentEvents.cs:42-46 | Source/Access/Events/DispTextBoxEvents.cs:28-32 — before extracting anything, compare `Source/Access/Events/DispAttachmentEvents.cs` and `Source/Access/Events/DispTextBoxEvents.cs` as WHOLE FILES: this scan already matched 36 separate duplicated blocks between them, totalling at least 314 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 2) Source/Access/Events/DispNavigationControlEvents.cs:28 — Source/Access/Events/DispNavigationControlEvents.cs:28-32 | Source/Access/Events/DispWebBrowserControlEvents.cs:47-51 — before extracting anything, compare `Source/Access/Events/DispNavigationControlEvents.cs` and `Source/Access/Events/DispWebBrowserControlEvents.cs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 266 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 2) Source/Excel/Events/DocEvents.cs:69 — Source/Excel/Events/DocEvents.cs:69-73 | Source/Excel/Events/DocEvents.cs:77-81 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (5 lines × 2) Source/Outlook/Events/ExplorerEvents.cs:19 — Source/Outlook/Events/ExplorerEvents.cs:19-23 | Source/Outlook/Events/InspectorEvents.cs:19-23 — before extracting anything, compare `Source/Outlook/Events/ExplorerEvents.cs` and `Source/Outlook/Events/InspectorEvents.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 34 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 2) Source/Outlook/Events/ExplorerEvents_10.cs:19 — Source/Outlook/Events/ExplorerEvents_10.cs:19-23 | Source/Outlook/Events/InspectorEvents_10.cs:19-23 — before extracting anything, compare `Source/Outlook/Events/ExplorerEvents_10.cs` and `Source/Outlook/Events/InspectorEvents_10.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 130 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 2) Source/Access/Events/DispCommandButtonEvents.cs:19 — Source/Access/Events/DispCommandButtonEvents.cs:19-23 | Source/Access/Events/DispOptionButtonEvents.cs:19-23 — before extracting anything, compare `Source/Access/Events/DispCommandButtonEvents.cs` and `Source/Access/Events/DispOptionButtonEvents.cs` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 217 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 2) Source/ADODB/Events/ConnectionEvents.cs:249 — Source/ADODB/Events/ConnectionEvents.cs:249-253 | Source/ADODB/Events/ConnectionEvents.cs:292-296 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/ADODB/Events/ConnectionEvents.cs:249` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (5 lines × 2) Source/Office/Tools/COMAddin.cs:1090 — Source/Office/Tools/COMAddin.cs:1090-1094 | Source/Office/Tools/COMAddin.cs:1113-1117 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (5 lines × 2) Source/Access/Events/_FormEvents2.cs:19 — Source/Access/Events/_FormEvents2.cs:19-23 | Source/Access/Events/_ReportEvents2.cs:55-59 — before extracting anything, compare `Source/Access/Events/_FormEvents2.cs` and `Source/Access/Events/_ReportEvents2.cs` as WHOLE FILES: this scan already matched 45 separate duplicated blocks between them, totalling at least 418 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 2) Source/OWC10/Events/ISpreadsheetEventSink.cs:557 — Source/OWC10/Events/ISpreadsheetEventSink.cs:557-561 | Source/OWC10/Events/ISpreadsheetEventSink.cs:575-579 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (5 lines × 2) Source/MSComctlLib/Events/DImageComboEvents.cs:19 — Source/MSComctlLib/Events/DImageComboEvents.cs:19-23 | Source/MSComctlLib/Events/IToolbarEvents.cs:24-28 — before extracting anything, compare `Source/MSComctlLib/Events/DImageComboEvents.cs` and `Source/MSComctlLib/Events/IToolbarEvents.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 171 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Source/MSComctlLib/Events/DImageComboEvents.cs:24` calls `MethodImpl`, `DispId`, `Dropdown` and `Source/MSComctlLib/Events/IToolbarEvents.cs:29` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 2) Source/Excel/Events/AppEvents.cs:67 — Source/Excel/Events/AppEvents.cs:67-71 | Source/Excel/Events/AppEvents.cs:72-76 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (5 lines × 2) Source/Excel/Events/AppEvents.cs:261 — Source/Excel/Events/AppEvents.cs:261-265 | Source/Excel/Events/AppEvents.cs:266-270 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (5 lines × 2) Source/Excel/Events/WorkbookEvents.cs:63 — Source/Excel/Events/WorkbookEvents.cs:63-67 | Source/Excel/Events/WorkbookEvents.cs:68-72 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (5 lines × 2) Source/Word/Events/ApplicationEvents4.cs:215 — Source/Word/Events/ApplicationEvents4.cs:215-219 | Source/Word/Events/ApplicationEvents4.cs:220-224 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (5 lines × 2) Source/Outlook/Events/ApplicationEvents_10.cs:19 — Source/Outlook/Events/ApplicationEvents_10.cs:19-23 | Source/Outlook/Events/ItemEvents_10.cs:99-103 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (5 lines × 2) Source/Outlook/Events/OutlookBarPaneEvents.cs:19 — Source/Outlook/Events/OutlookBarPaneEvents.cs:19-23 | Source/Outlook/Events/OutlookBarShortcutsEvents.cs:29-33 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (5 lines × 2) Source/Outlook/Events/ReminderCollectionEvents.cs:27 — Source/Outlook/Events/ReminderCollectionEvents.cs:27-31 | Source/Outlook/Events/ReminderCollectionEvents.cs:32-36 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • + 106 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (53 lines × 2) · ×66
  • Duplicated block (53 lines × 2) Source/Excel/DispatchInterfaces/Action.cs:53 — Source/Excel/DispatchInterfaces/Action.cs:53-105 | Source/Outlook/DispatchInterfaces/Action.cs:53-105 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (53 lines × 2) Source/Excel/DispatchInterfaces/Actions.cs:56 — Source/Excel/DispatchInterfaces/Actions.cs:56-108 | Source/Outlook/DispatchInterfaces/Actions.cs:56-108 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (53 lines × 2) Source/Excel/DispatchInterfaces/AutoFilter.cs:53 — Source/Excel/DispatchInterfaces/AutoFilter.cs:53-105 | Source/OWC10/DispatchInterfaces/AutoFilter.cs:52-104 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (53 lines × 2) Source/Excel/DispatchInterfaces/Characters.cs:53 — Source/Excel/DispatchInterfaces/Characters.cs:53-105 | Source/Word/DispatchInterfaces/Characters.cs:56-108 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (53 lines × 2) Source/DAO/DispatchInterfaces/Connections.cs:52 — Source/DAO/DispatchInterfaces/Connections.cs:52-104 | Source/Excel/DispatchInterfaces/Connections.cs:56-108 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (53 lines × 2) Source/Excel/DispatchInterfaces/CustomProperties.cs:56 — Source/Excel/DispatchInterfaces/CustomProperties.cs:56-108 | Source/Word/DispatchInterfaces/CustomProperties.cs:56-108 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (53 lines × 2) Source/Excel/DispatchInterfaces/CustomProperty.cs:53 — Source/Excel/DispatchInterfaces/CustomProperty.cs:53-105 | Source/Word/DispatchInterfaces/CustomProperty.cs:53-105 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (53 lines × 2) Source/Excel/DispatchInterfaces/Dialog.cs:53 — Source/Excel/DispatchInterfaces/Dialog.cs:53-105 | Source/Word/DispatchInterfaces/Dialog.cs:53-105 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (53 lines × 2) Source/Excel/DispatchInterfaces/Dialogs.cs:56 — Source/Excel/DispatchInterfaces/Dialogs.cs:56-108 | Source/Word/DispatchInterfaces/Dialogs.cs:56-108 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (53 lines × 2) Source/Excel/DispatchInterfaces/DropDown.cs:252 — Source/Excel/DispatchInterfaces/DropDown.cs:252-304 | Source/Word/DispatchInterfaces/DropDown.cs:53-105 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (53 lines × 2) Source/Excel/DispatchInterfaces/Filter.cs:53 — Source/Excel/DispatchInterfaces/Filter.cs:53-105 | Source/OWC10/DispatchInterfaces/Filter.cs:52-104 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (53 lines × 2) Source/Excel/DispatchInterfaces/Filters.cs:56 — Source/Excel/DispatchInterfaces/Filters.cs:56-108 | Source/OWC10/DispatchInterfaces/Filters.cs:55-107 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (53 lines × 2) Source/Access/DispatchInterfaces/FormatConditions.cs:56 — Source/Access/DispatchInterfaces/FormatConditions.cs:56-108 | Source/Excel/DispatchInterfaces/FormatConditions.cs:56-108 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (53 lines × 2) Source/Excel/DispatchInterfaces/Lines.cs:55 — Source/Excel/DispatchInterfaces/Lines.cs:55-107 | Source/Word/DispatchInterfaces/Lines.cs:56-108 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (53 lines × 2) Source/Excel/DispatchInterfaces/Mailer.cs:53 — Source/Excel/DispatchInterfaces/Mailer.cs:53-105 | Source/Word/DispatchInterfaces/Mailer.cs:52-104 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (53 lines × 2) Source/Access/DispatchInterfaces/Module.cs:54 — Source/Access/DispatchInterfaces/Module.cs:54-106 | Source/Excel/DispatchInterfaces/Module.cs:52-104 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (53 lines × 2) Source/Access/DispatchInterfaces/Modules.cs:56 — Source/Access/DispatchInterfaces/Modules.cs:56-108 | Source/Excel/DispatchInterfaces/Modules.cs:55-107 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (53 lines × 2) Source/Excel/DispatchInterfaces/Name.cs:150 — Source/Excel/DispatchInterfaces/Name.cs:150-202 | Source/OWC10/DispatchInterfaces/Name.cs:148-200 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (53 lines × 2) Source/Excel/DispatchInterfaces/Names.cs:56 — Source/Excel/DispatchInterfaces/Names.cs:56-108 | Source/OWC10/DispatchInterfaces/Names.cs:55-107 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (53 lines × 2) Source/Excel/DispatchInterfaces/PivotAxis.cs:53 — Source/Excel/DispatchInterfaces/PivotAxis.cs:53-105 | Source/OWC10/DispatchInterfaces/PivotAxis.cs:52-104 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (53 lines × 2) Source/Excel/DispatchInterfaces/PivotCell.cs:53 — Source/Excel/DispatchInterfaces/PivotCell.cs:53-105 | Source/OWC10/DispatchInterfaces/PivotCell.cs:52-104 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (53 lines × 2) Source/Excel/DispatchInterfaces/PivotField.cs:270 — Source/Excel/DispatchInterfaces/PivotField.cs:270-322 | Source/OWC10/DispatchInterfaces/PivotField.cs:52-104 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (53 lines × 2) Source/Excel/DispatchInterfaces/PivotFields.cs:56 — Source/Excel/DispatchInterfaces/PivotFields.cs:56-108 | Source/OWC10/DispatchInterfaces/PivotFields.cs:55-107 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (53 lines × 2) Source/Excel/DispatchInterfaces/Protection.cs:53 — Source/Excel/DispatchInterfaces/Protection.cs:53-105 | Source/OWC10/DispatchInterfaces/Protection.cs:52-104 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (53 lines × 2) Source/Excel/DispatchInterfaces/PublishObject.cs:53 — Source/Excel/DispatchInterfaces/PublishObject.cs:53-105 | Source/PowerPoint/DispatchInterfaces/PublishObject.cs:53-105 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • + 41 more in this group — see findings.md.
D6 · Cohesion (LCOM4) · Low cohesion · ×66
  • Low cohesion: RegistryEditorControl (LCOM4 11) Toolbox/Toolbox/ToolboxControls/RegistryEditor/RegistryEditorControl.cs:17 — RegistryEditorControl's methods fall into 11 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 11 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: MainForm (LCOM4 5) REDACTED:16 — MainForm's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: CategoryCollection (LCOM4 4) Source/Excel/DispatchInterfaces/CategoryCollection.cs:17 — CategoryCollection's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: ModelTableNames (LCOM4 4) Source/Excel/DispatchInterfaces/ModelTableNames.cs:16 — ModelTableNames's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: Panes (LCOM4 4) Source/Excel/DispatchInterfaces/Panes.cs:16 — Panes's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: ICategoryCollection (LCOM4 4) Source/Excel/Interfaces/ICategoryCollection.cs:15 — ICategoryCollection's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: IPanes (LCOM4 4) Source/Excel/Interfaces/IPanes.cs:15 — IPanes's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: ChChartFields (LCOM4 4) Source/OWC10/DispatchInterfaces/ChChartFields.cs:15 — ChChartFields's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: ChDataLabels (LCOM4 4) Source/OWC10/DispatchInterfaces/ChDataLabels.cs:15 — ChDataLabels's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: ChErrorBarsCollection (LCOM4 4) Source/OWC10/DispatchInterfaces/ChErrorBarsCollection.cs:15 — ChErrorBarsCollection's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: ChSegments (LCOM4 4) Source/OWC10/DispatchInterfaces/ChSegments.cs:15 — ChSegments's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: FieldListDragDataList (LCOM4 4) Source/OWC10/DispatchInterfaces/FieldListDragDataList.cs:15 — FieldListDragDataList's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: Headings (LCOM4 4) Source/OWC10/DispatchInterfaces/Headings.cs:15 — Headings's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: Adjustments (LCOM4 4) Source/Office/DispatchInterfaces/Adjustments.cs:15 — Adjustments's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: AnswerWizardFiles (LCOM4 4) Source/Office/DispatchInterfaces/AnswerWizardFiles.cs:15 — AnswerWizardFiles's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: ODSOColumns (LCOM4 4) Source/Office/DispatchInterfaces/ODSOColumns.cs:16 — ODSOColumns's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: ODSOFilters (LCOM4 4) Source/Office/DispatchInterfaces/ODSOFilters.cs:16 — ODSOFilters's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: ServerPolicy (LCOM4 4) Source/Office/DispatchInterfaces/ServerPolicy.cs:16 — ServerPolicy's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: CategoryCollection (LCOM4 4) Source/Office/Interfaces/CategoryCollection.cs:15 — CategoryCollection's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: Actions (LCOM4 4) Source/Outlook/DispatchInterfaces/Actions.cs:16 — Actions's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: AddressLists (LCOM4 4) Source/Outlook/DispatchInterfaces/AddressLists.cs:16 — AddressLists's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: Attachments (LCOM4 4) Source/Outlook/DispatchInterfaces/Attachments.cs:16 — Attachments's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: Conflicts (LCOM4 4) Source/Outlook/DispatchInterfaces/Conflicts.cs:16 — Conflicts's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: Exceptions (LCOM4 4) Source/Outlook/DispatchInterfaces/Exceptions.cs:16 — Exceptions's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: Links (LCOM4 4) Source/Outlook/DispatchInterfaces/Links.cs:15 — Links's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • + 41 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (53 lines × 3) · ×53
  • Duplicated block (53 lines × 3) Source/Excel/DispatchInterfaces/AddIns.cs:56 — Source/Excel/DispatchInterfaces/AddIns.cs:56-108 | Source/PowerPoint/DispatchInterfaces/AddIns.cs:53-105 | Source/Word/DispatchInterfaces/AddIns.cs:56-108 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (53 lines × 3) Source/Excel/DispatchInterfaces/Axis.cs:53 — Source/Excel/DispatchInterfaces/Axis.cs:53-105 | Source/PowerPoint/DispatchInterfaces/Axis.cs:53-105 | Source/Word/DispatchInterfaces/Axis.cs:53-105 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (53 lines × 3) Source/Excel/DispatchInterfaces/AxisTitle.cs:185 — Source/Excel/DispatchInterfaces/AxisTitle.cs:185-237 | Source/PowerPoint/DispatchInterfaces/AxisTitle.cs:184-236 | Source/Word/DispatchInterfaces/AxisTitle.cs:184-236 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (53 lines × 3) Source/Excel/DispatchInterfaces/Border.cs:53 — Source/Excel/DispatchInterfaces/Border.cs:53-105 | Source/OWC10/DispatchInterfaces/Border.cs:52-104 | Source/Word/DispatchInterfaces/Border.cs:53-105 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (53 lines × 3) Source/Excel/DispatchInterfaces/ChartArea.cs:53 — Source/Excel/DispatchInterfaces/ChartArea.cs:53-105 | Source/PowerPoint/DispatchInterfaces/ChartArea.cs:53-105 | Source/Word/DispatchInterfaces/ChartArea.cs:53-105 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (53 lines × 3) Source/Excel/DispatchInterfaces/ChartCategory.cs:53 — Source/Excel/DispatchInterfaces/ChartCategory.cs:53-105 | Source/PowerPoint/DispatchInterfaces/ChartCategory.cs:53-105 | Source/Word/DispatchInterfaces/ChartCategory.cs:53-105 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (53 lines × 3) Source/Excel/DispatchInterfaces/ChartFormat.cs:53 — Source/Excel/DispatchInterfaces/ChartFormat.cs:53-105 | Source/PowerPoint/DispatchInterfaces/ChartFormat.cs:53-105 | Source/Word/DispatchInterfaces/ChartFormat.cs:53-105 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (53 lines × 3) Source/Excel/DispatchInterfaces/ChartGroup.cs:53 — Source/Excel/DispatchInterfaces/ChartGroup.cs:53-105 | Source/PowerPoint/DispatchInterfaces/ChartGroup.cs:53-105 | Source/Word/DispatchInterfaces/ChartGroup.cs:53-105 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (53 lines × 3) Source/Excel/DispatchInterfaces/ChartTitle.cs:185 — Source/Excel/DispatchInterfaces/ChartTitle.cs:185-237 | Source/PowerPoint/DispatchInterfaces/ChartTitle.cs:184-236 | Source/Word/DispatchInterfaces/ChartTitle.cs:184-236 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (53 lines × 3) Source/Excel/DispatchInterfaces/Comment.cs:53 — Source/Excel/DispatchInterfaces/Comment.cs:53-105 | Source/PowerPoint/DispatchInterfaces/Comment.cs:53-105 | Source/Word/DispatchInterfaces/Comment.cs:53-105 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (53 lines × 3) Source/Excel/DispatchInterfaces/Comments.cs:56 — Source/Excel/DispatchInterfaces/Comments.cs:56-108 | Source/PowerPoint/DispatchInterfaces/Comments.cs:53-105 | Source/Word/DispatchInterfaces/Comments.cs:56-108 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (53 lines × 3) Source/Excel/DispatchInterfaces/Corners.cs:52 — Source/Excel/DispatchInterfaces/Corners.cs:52-104 | Source/PowerPoint/DispatchInterfaces/Corners.cs:52-104 | Source/Word/DispatchInterfaces/Corners.cs:52-104 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (53 lines × 3) Source/Excel/DispatchInterfaces/DataLabel.cs:185 — Source/Excel/DispatchInterfaces/DataLabel.cs:185-237 | Source/PowerPoint/DispatchInterfaces/DataLabel.cs:184-236 | Source/Word/DispatchInterfaces/DataLabel.cs:184-236 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (53 lines × 3) Source/Excel/DispatchInterfaces/DataLabels.cs:56 — Source/Excel/DispatchInterfaces/DataLabels.cs:56-108 | Source/PowerPoint/DispatchInterfaces/DataLabels.cs:56-108 | Source/Word/DispatchInterfaces/DataLabels.cs:56-108 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (53 lines × 3) Source/Excel/DispatchInterfaces/DataTable.cs:53 — Source/Excel/DispatchInterfaces/DataTable.cs:53-105 | Source/PowerPoint/DispatchInterfaces/DataTable.cs:53-105 | Source/Word/DispatchInterfaces/DataTable.cs:53-105 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (53 lines × 3) Source/Excel/DispatchInterfaces/Diagram.cs:52 — Source/Excel/DispatchInterfaces/Diagram.cs:52-104 | Source/PowerPoint/DispatchInterfaces/Diagram.cs:52-104 | Source/Word/DispatchInterfaces/Diagram.cs:52-104 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (53 lines × 3) Source/Excel/DispatchInterfaces/DisplayUnitLabel.cs:185 — Source/Excel/DispatchInterfaces/DisplayUnitLabel.cs:185-237 | Source/PowerPoint/DispatchInterfaces/DisplayUnitLabel.cs:184-236 | Source/Word/DispatchInterfaces/DisplayUnitLabel.cs:184-236 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (53 lines × 3) Source/Excel/DispatchInterfaces/DownBars.cs:53 — Source/Excel/DispatchInterfaces/DownBars.cs:53-105 | Source/PowerPoint/DispatchInterfaces/DownBars.cs:52-104 | Source/Word/DispatchInterfaces/DownBars.cs:53-105 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (53 lines × 3) Source/Excel/DispatchInterfaces/DropLines.cs:53 — Source/Excel/DispatchInterfaces/DropLines.cs:53-105 | Source/PowerPoint/DispatchInterfaces/DropLines.cs:52-104 | Source/Word/DispatchInterfaces/DropLines.cs:53-105 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (53 lines × 3) Source/ADODB/DispatchInterfaces/Error.cs:52 — Source/ADODB/DispatchInterfaces/Error.cs:52-104 | Source/DAO/DispatchInterfaces/Error.cs:52-104 | Source/Excel/DispatchInterfaces/Error.cs:53-105 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (53 lines × 3) Source/Excel/DispatchInterfaces/ErrorBars.cs:53 — Source/Excel/DispatchInterfaces/ErrorBars.cs:53-105 | Source/PowerPoint/DispatchInterfaces/ErrorBars.cs:52-104 | Source/Word/DispatchInterfaces/ErrorBars.cs:53-105 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (53 lines × 3) Source/ADODB/DispatchInterfaces/Errors.cs:52 — Source/ADODB/DispatchInterfaces/Errors.cs:52-104 | Source/DAO/DispatchInterfaces/Errors.cs:52-104 | Source/Excel/DispatchInterfaces/Errors.cs:53-105 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (53 lines × 3) Source/Excel/DispatchInterfaces/Floor.cs:53 — Source/Excel/DispatchInterfaces/Floor.cs:53-105 | Source/PowerPoint/DispatchInterfaces/Floor.cs:53-105 | Source/Word/DispatchInterfaces/Floor.cs:53-105 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (53 lines × 3) Source/Excel/DispatchInterfaces/Gridlines.cs:53 — Source/Excel/DispatchInterfaces/Gridlines.cs:53-105 | Source/PowerPoint/DispatchInterfaces/Gridlines.cs:53-105 | Source/Word/DispatchInterfaces/Gridlines.cs:53-105 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (53 lines × 3) Source/Excel/DispatchInterfaces/HeaderFooter.cs:53 — Source/Excel/DispatchInterfaces/HeaderFooter.cs:53-105 | Source/PowerPoint/DispatchInterfaces/HeaderFooter.cs:53-105 | Source/Word/DispatchInterfaces/HeaderFooter.cs:53-105 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • + 28 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×49
  • Duplicated block (11 lines × 2) Source/NetOffice/Invoker.cs:997 — Source/NetOffice/Invoker.cs:997-1007 | Source/NetOffice/Invoker.cs:1035-1045 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/NetOffice/Invoker.cs:997` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) Toolbox/Toolbox/ToolboxControls/About/AboutControl.cs:185 — Toolbox/Toolbox/ToolboxControls/About/AboutControl.cs:185-195 | Toolbox/Toolbox/ToolboxControls/About/AboutControl.cs:210-220 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Toolbox/Toolbox/ToolboxControls/About/AboutControl.cs:185` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) RegAddin/RegAddin/Common/AddinRegAnalyzer.cs:49 — RegAddin/RegAddin/Common/AddinRegAnalyzer.cs:49-59 | RegAddin/RegAddin/Common/AddinRegAnalyzer.cs:94-104 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (11 lines × 2) Source/Excel/Events/AppEvents.cs:403 — Source/Excel/Events/AppEvents.cs:403-413 | Source/Excel/Events/WorkbookEvents.cs:489-499 — before extracting anything, compare `Source/Excel/Events/AppEvents.cs` and `Source/Excel/Events/WorkbookEvents.cs` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 377 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 2) Source/Excel/Events/AppEvents.cs:417 — Source/Excel/Events/AppEvents.cs:417-427 | Source/Excel/Events/WorkbookEvents.cs:503-513 — before extracting anything, compare `Source/Excel/Events/AppEvents.cs` and `Source/Excel/Events/WorkbookEvents.cs` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 377 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 2) Source/Excel/Events/AppEvents.cs:431 — Source/Excel/Events/AppEvents.cs:431-441 | Source/Excel/Events/WorkbookEvents.cs:517-527 — before extracting anything, compare `Source/Excel/Events/AppEvents.cs` and `Source/Excel/Events/WorkbookEvents.cs` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 377 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 2) Source/Excel/Events/AppEvents.cs:1051 — Source/Excel/Events/AppEvents.cs:1051-1061 | Source/Excel/Events/WorkbookEvents.cs:843-853 — before extracting anything, compare `Source/Excel/Events/AppEvents.cs` and `Source/Excel/Events/WorkbookEvents.cs` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 377 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 2) Source/Excel/Events/AppEvents.cs:1098 — Source/Excel/Events/AppEvents.cs:1098-1108 | Source/Excel/Events/WorkbookEvents.cs:887-897 — before extracting anything, compare `Source/Excel/Events/AppEvents.cs` and `Source/Excel/Events/WorkbookEvents.cs` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 377 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 2) Source/Excel/Events/WorkbookEvents.cs:607 — Source/Excel/Events/WorkbookEvents.cs:607-617 | Source/Word/Events/DocumentEvents2.cs:154-164 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 2) Source/VBIDE/Events/_dispReferencesEvents.cs:57 — Source/VBIDE/Events/_dispReferencesEvents.cs:57-67 | Source/VBIDE/Events/_dispReferences_Events.cs:57-67 — before extracting anything, compare `Source/VBIDE/Events/_dispReferencesEvents.cs` and `Source/VBIDE/Events/_dispReferences_Events.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 2) Source/VBIDE/Events/_dispReferencesEvents.cs:71 — Source/VBIDE/Events/_dispReferencesEvents.cs:71-81 | Source/VBIDE/Events/_dispReferences_Events.cs:71-81 — before extracting anything, compare `Source/VBIDE/Events/_dispReferencesEvents.cs` and `Source/VBIDE/Events/_dispReferences_Events.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 2) Source/NetOffice/Core.cs:855 — Source/NetOffice/Core.cs:855-865 | Source/NetOffice/Core.cs:907-917 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (11 lines × 2) Source/NetOffice/Utils.cs:267 — Source/NetOffice/Utils.cs:267-277 | Source/NetOffice/Utils.cs:293-303 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/NetOffice/Utils.cs:267` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) Source/Word/Events/ApplicationEvents3.cs:375 — Source/Word/Events/ApplicationEvents3.cs:375-385 | Source/Word/Events/ApplicationEvents4.cs:448-458 — before extracting anything, compare `Source/Word/Events/ApplicationEvents3.cs` and `Source/Word/Events/ApplicationEvents4.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 469 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 2) Source/Word/Events/ApplicationEvents3.cs:389 — Source/Word/Events/ApplicationEvents3.cs:389-399 | Source/Word/Events/ApplicationEvents4.cs:462-472 — before extracting anything, compare `Source/Word/Events/ApplicationEvents3.cs` and `Source/Word/Events/ApplicationEvents4.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 469 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 2) Source/Word/Events/ApplicationEvents3.cs:419 — Source/Word/Events/ApplicationEvents3.cs:419-429 | Source/Word/Events/ApplicationEvents4.cs:492-502 — before extracting anything, compare `Source/Word/Events/ApplicationEvents3.cs` and `Source/Word/Events/ApplicationEvents4.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 469 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 2) Source/Word/Events/ApplicationEvents3.cs:471 — Source/Word/Events/ApplicationEvents3.cs:471-481 | Source/Word/Events/ApplicationEvents4.cs:544-554 — before extracting anything, compare `Source/Word/Events/ApplicationEvents3.cs` and `Source/Word/Events/ApplicationEvents4.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 469 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 2) Source/Word/Events/ApplicationEvents3.cs:502 — Source/Word/Events/ApplicationEvents3.cs:502-512 | Source/Word/Events/ApplicationEvents4.cs:575-585 — before extracting anything, compare `Source/Word/Events/ApplicationEvents3.cs` and `Source/Word/Events/ApplicationEvents4.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 469 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 2) Source/Outlook/Events/ApplicationEvents_10.cs:166 — Source/Outlook/Events/ApplicationEvents_10.cs:166-176 | Source/Outlook/Events/ApplicationEvents_11.cs:223-233 — before extracting anything, compare `Source/Outlook/Events/ApplicationEvents_10.cs` and `Source/Outlook/Events/ApplicationEvents_11.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 122 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 2) Source/Outlook/Events/ApplicationEvents_10.cs:180 — Source/Outlook/Events/ApplicationEvents_10.cs:180-190 | Source/Outlook/Events/ApplicationEvents_11.cs:237-247 — before extracting anything, compare `Source/Outlook/Events/ApplicationEvents_10.cs` and `Source/Outlook/Events/ApplicationEvents_11.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 122 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 2) Source/Outlook/Events/ItemEvents.cs:311 — Source/Outlook/Events/ItemEvents.cs:311-321 | Source/Outlook/Events/ItemEvents_10.cs:368-378 — before extracting anything, compare `Source/Outlook/Events/ItemEvents.cs` and `Source/Outlook/Events/ItemEvents_10.cs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 292 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 2) Source/Outlook/Events/ItemEvents.cs:325 — Source/Outlook/Events/ItemEvents.cs:325-335 | Source/Outlook/Events/ItemEvents_10.cs:382-392 — before extracting anything, compare `Source/Outlook/Events/ItemEvents.cs` and `Source/Outlook/Events/ItemEvents_10.cs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 292 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 2) Source/Outlook/Events/ItemsEvents.cs:61 — Source/Outlook/Events/ItemsEvents.cs:61-71 | Source/Outlook/Events/ResultsEvents.cs:61-71 — before extracting anything, compare `Source/Outlook/Events/ItemsEvents.cs` and `Source/Outlook/Events/ResultsEvents.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 2) Source/Outlook/Events/ItemsEvents.cs:75 — Source/Outlook/Events/ItemsEvents.cs:75-85 | Source/Outlook/Events/ResultsEvents.cs:75-85 — before extracting anything, compare `Source/Outlook/Events/ItemsEvents.cs` and `Source/Outlook/Events/ResultsEvents.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 2) Source/Access/Events/DispPageHdrFtrInReportEvents.cs:19 — Source/Access/Events/DispPageHdrFtrInReportEvents.cs:19-29 | Source/Access/Events/DispSectionInReportEvents.cs:19-29 — before extracting anything, compare `Source/Access/Events/DispPageHdrFtrInReportEvents.cs` and `Source/Access/Events/DispSectionInReportEvents.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 179 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • + 24 more in this group — see findings.md.
X5 · Nullable reference types · Symbol treated as nullable, then dereferenced unguarded · ×40
  • Symbol treated as nullable, then dereferenced unguarded Source/ClientApplication/RunExcel01.cs:26 — This method contradicts itself about `sheet`: line 25 assigns it with `as Excel.Worksheet`, which hands back null rather than throwing when the value is not a `Excel.Worksheet`, but line 26 then dereferences it directly as `sheet.Cells` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `sheet` once before the first use and handle the null case, or cast with `(Excel.Worksheet)` so the failure is reported where it happens — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded Source/NetOffice/COMObject.cs:751 — This method contradicts itself about `shareProvider`: line 750 assigns it with `as ICOMProxyShareProvider`, which hands back null rather than throwing when the value is not a `ICOMProxyShareProvider`, but line 751 then dereferences it directly as `shareProvider.SetProxyShare` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `shareProvider` once before the first use and handle the null case, or cast with `(ICOMProxyShareProvider)` so the failure is reported where it happens — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded Source/NetOffice/COMObject.cs:1267 — This method contradicts itself about `shareProvider`: line 1266 assigns it with `as ICOMProxyShareProvider`, which hands back null rather than throwing when the value is not a `ICOMProxyShareProvider`, but line 1267 then dereferences it directly as `shareProvider.SetProxyShare` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `shareProvider` once before the first use and handle the null case, or cast with `(ICOMProxyShareProvider)` so the failure is reported where it happens — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded Source/NetOffice/Running/ChildWindowBatchEnumerator.cs:227 — This method contradicts itself about `childHandles`: line 226 assigns it with `as List<IntPtr>`, which hands back null rather than throwing when the value is not a `List<IntPtr>`, but line 227 then dereferences it directly as `childHandles.Add` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `childHandles` once before the first use and handle the null case, or cast with `(List<IntPtr>)` so the failure is reported where it happens — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded Source/NetOffice/Running/ChildWindowEnumerator.cs:166 — This method contradicts itself about `childHandles`: line 165 assigns it with `as List<IntPtr>`, which hands back null rather than throwing when the value is not a `List<IntPtr>`, but line 166 then dereferences it directly as `childHandles.Add` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `childHandles` once before the first use and handle the null case, or cast with `(List<IntPtr>)` so the failure is reported where it happens — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded Source/NetOffice/Running/ChildWindowEnumerator.cs:172 — This method contradicts itself about `childHandles`: line 171 assigns it with `as List<IntPtr>`, which hands back null rather than throwing when the value is not a `List<IntPtr>`, but line 172 then dereferences it directly as `childHandles.Add` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `childHandles` once before the first use and handle the null case, or cast with `(List<IntPtr>)` so the failure is reported where it happens — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded Source/NetOffice/Tools/AttributeReflector.cs:136 — This method contradicts itself about `attribute`: line 135 assigns it with `as CustomUIAttribute`, which hands back null rather than throwing when the value is not a `CustomUIAttribute`, but line 136 then dereferences it directly as `attribute.RibbonID` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `attribute` once before the first use and handle the null case, or cast with `(CustomUIAttribute)` so the failure is reported where it happens — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded Source/Office.Extensions/TrayMenuUtils/TrayMenu.cs:945 — This method contradicts itself about `toolStripItem`: line 944 assigns it with `as ToolStripItem`, which hands back null rather than throwing when the value is not a `ToolStripItem`, but line 945 then dereferences it directly as `toolStripItem.Tag` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `toolStripItem` once before the first use and handle the null case, or cast with `(ToolStripItem)` so the failure is reported where it happens — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded Source/Office.Extensions/TrayMenuUtils/TrayMenu.cs:959 — This method contradicts itself about `toolStripItem`: line 958 assigns it with `as ToolStripMenuItem`, which hands back null rather than throwing when the value is not a `ToolStripMenuItem`, but line 959 then dereferences it directly as `toolStripItem.Checked` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `toolStripItem` once before the first use and handle the null case, or cast with `(ToolStripMenuItem)` so the failure is reported where it happens — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded Source/Office.Extensions/TrayMenuUtils/TrayMenu.cs:972 — This method contradicts itself about `toolStripItem`: line 971 assigns it with `as ToolStripMenuItem`, which hands back null rather than throwing when the value is not a `ToolStripMenuItem`, but line 972 then dereferences it directly as `toolStripItem.Tag` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `toolStripItem` once before the first use and handle the null case, or cast with `(ToolStripMenuItem)` so the failure is reported where it happens — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded Source/Office.Extensions/TrayMenuUtils/TrayMenu.cs:986 — This method contradicts itself about `toolStripItem`: line 985 assigns it with `as ToolStripTextBox`, which hands back null rather than throwing when the value is not a `ToolStripTextBox`, but line 986 then dereferences it directly as `toolStripItem.Tag` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `toolStripItem` once before the first use and handle the null case, or cast with `(ToolStripTextBox)` so the failure is reported where it happens — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded Source/Office.Extensions/TrayMenuUtils/TrayMenu.cs:1000 — This method contradicts itself about `toolStripItem`: line 999 assigns it with `as ToolStripComboBox`, which hands back null rather than throwing when the value is not a `ToolStripComboBox`, but line 1000 then dereferences it directly as `toolStripItem.Tag` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `toolStripItem` once before the first use and handle the null case, or cast with `(ToolStripComboBox)` so the failure is reported where it happens — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded Source/Office.Extensions/TrayMenuUtils/TrayMenu.cs:1014 — This method contradicts itself about `toolStripItem`: line 1013 assigns it with `as ToolStripComboBox`, which hands back null rather than throwing when the value is not a `ToolStripComboBox`, but line 1014 then dereferences it directly as `toolStripItem.Tag` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `toolStripItem` once before the first use and handle the null case, or cast with `(ToolStripComboBox)` so the failure is reported where it happens — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded Source/Office.Extensions/TrayMenuUtils/TrayMenu.cs:1028 — This method contradicts itself about `toolStripItem`: line 1027 assigns it with `as ToolStripControlHost`, which hands back null rather than throwing when the value is not a `ToolStripControlHost`, but line 1028 then dereferences it directly as `toolStripItem.Tag` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `toolStripItem` once before the first use and handle the null case, or cast with `(ToolStripControlHost)` so the failure is reported where it happens — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded Source/Office.Extensions/TrayMenuUtils/TrayMenu.cs:1042 — This method contradicts itself about `toolStripItem`: line 1041 assigns it with `as ToolStripControlHost`, which hands back null rather than throwing when the value is not a `ToolStripControlHost`, but line 1042 then dereferences it directly as `toolStripItem.Tag` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `toolStripItem` once before the first use and handle the null case, or cast with `(ToolStripControlHost)` so the failure is reported where it happens — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded Source/Office.Extensions/TrayMenuUtils/TrayMenu.cs:1056 — This method contradicts itself about `toolStripItem`: line 1055 assigns it with `as ToolStripControlHost`, which hands back null rather than throwing when the value is not a `ToolStripControlHost`, but line 1056 then dereferences it directly as `toolStripItem.Tag` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `toolStripItem` once before the first use and handle the null case, or cast with `(ToolStripControlHost)` so the failure is reported where it happens — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded Source/Office.Extensions/TrayMenuUtils/TrayMenuMonitorItemControl.cs:478 — This method contradicts itself about `button`: line 477 assigns it with `as RadioButton`, which hands back null rather than throwing when the value is not a `RadioButton`, but line 478 then dereferences it directly as `button.Checked` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `button` once before the first use and handle the null case, or cast with `(RadioButton)` so the failure is reported where it happens — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded Source/Office.Extensions/TrayUtils.cs:587 — This method contradicts itself about `args`: line 586 assigns it with `as MouseEventArgs`, which hands back null rather than throwing when the value is not a `MouseEventArgs`, but line 587 then dereferences it directly as `args.Button` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `args` once before the first use and handle the null case, or cast with `(MouseEventArgs)` so the failure is reported where it happens — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded Examples/ExampleBase/ExampleForm.cs:183 — This method contradicts itself about `label`: line 182 assigns it with `as LinkLabel`, which hands back null rather than throwing when the value is not a `LinkLabel`, but line 183 then dereferences it directly as `label.Tag` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `label` once before the first use and handle the null case, or cast with `(LinkLabel)` so the failure is reported where it happens — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded Examples/Outlook/Automation/Examples/Example06.cs:86 — This method contradicts itself about `mailItem`: line 85 assigns it with `as Outlook.MailItem`, which hands back null rather than throwing when the value is not a `Outlook.MailItem`, but line 86 then dereferences it directly as `mailItem.CloseEvent` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `mailItem` once before the first use and handle the null case, or cast with `(Outlook.MailItem)` so the failure is reported where it happens — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded Examples/Outlook/Automation/Examples/Example03.cs:71 — This method contradicts itself about `mailItem`: line 68 assigns it with `as Outlook.MailItem`, which hands back null rather than throwing when the value is not a `Outlook.MailItem`, but line 71 then dereferences it directly as `mailItem.Recipients` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `mailItem` once before the first use and handle the null case, or cast with `(Outlook.MailItem)` so the failure is reported where it happens — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded Examples/Outlook/Automation/Examples/Example02.cs:23 — This method contradicts itself about `newTask`: line 20 assigns it with `as Outlook.TaskItem`, which hands back null rather than throwing when the value is not a `Outlook.TaskItem`, but line 23 then dereferences it directly as `newTask.Subject` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `newTask` once before the first use and handle the null case, or cast with `(Outlook.TaskItem)` so the failure is reported where it happens — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded Examples/AddinRemovalTool/Form1.cs:97 — This method contradicts itself about `entry`: line 96 assigns it with `as AddinEntry`, which hands back null rather than throwing when the value is not a `AddinEntry`, but line 97 then dereferences it directly as `entry.Delete` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `entry` once before the first use and handle the null case, or cast with `(AddinEntry)` so the failure is reported where it happens — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded Toolbox/Toolbox/RessourceTableAttribute.cs:53 — This method contradicts itself about `attrib`: line 52 assigns it with `as RessourceTableAttribute`, which hands back null rather than throwing when the value is not a `RessourceTableAttribute`, but line 53 then dereferences it directly as `attrib.Address` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `attrib` once before the first use and handle the null case, or cast with `(RessourceTableAttribute)` so the failure is reported where it happens — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded Toolbox/Toolbox/ToolboxControls/About/AboutControl.cs:155 — This method contradicts itself about `control`: line 154 assigns it with `as Control`, which hands back null rather than throwing when the value is not a `Control`, but line 155 then dereferences it directly as `control.Tag` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `control` once before the first use and handle the null case, or cast with `(Control)` so the failure is reported where it happens — rather than leaving the two readings side by side.
  • + 15 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (53 lines × 4) · ×38
  • Duplicated block (53 lines × 4) Source/Excel/DispatchInterfaces/AddIn.cs:53 — Source/Excel/DispatchInterfaces/AddIn.cs:53-105 | Source/PowerPoint/DispatchInterfaces/AddIn.cs:53-105 | Source/VBIDE/DispatchInterfaces/AddIn.cs:52-104 | Source/Word/DispatchInterfaces/AddIn.cs:53-105 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
  • Duplicated block (53 lines × 4) Source/Excel/DispatchInterfaces/Adjustments.cs:57 — Source/Excel/DispatchInterfaces/Adjustments.cs:57-109 | Source/Office/DispatchInterfaces/Adjustments.cs:56-108 | Source/PowerPoint/DispatchInterfaces/Adjustments.cs:56-108 | Source/Word/DispatchInterfaces/Adjustments.cs:56-108 — before extracting anything, compare `Source/Excel/DispatchInterfaces/Adjustments.cs` and `Source/Office/DispatchInterfaces/Adjustments.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 66 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (53 lines × 4) Source/Excel/DispatchInterfaces/Axes.cs:56 — Source/Excel/DispatchInterfaces/Axes.cs:56-108 | Source/Office/DispatchInterfaces/Axes.cs:55-107 | Source/PowerPoint/DispatchInterfaces/Axes.cs:56-108 | Source/Word/DispatchInterfaces/Axes.cs:56-108 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
  • Duplicated block (53 lines × 4) Source/Excel/DispatchInterfaces/Borders.cs:56 — Source/Excel/DispatchInterfaces/Borders.cs:56-108 | Source/OWC10/DispatchInterfaces/Borders.cs:55-107 | Source/PowerPoint/DispatchInterfaces/Borders.cs:53-105 | Source/Word/DispatchInterfaces/Borders.cs:56-108 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
  • Duplicated block (53 lines × 4) Source/Excel/DispatchInterfaces/CalloutFormat.cs:54 — Source/Excel/DispatchInterfaces/CalloutFormat.cs:54-106 | Source/Office/DispatchInterfaces/CalloutFormat.cs:53-105 | Source/PowerPoint/DispatchInterfaces/CalloutFormat.cs:53-105 | Source/Word/DispatchInterfaces/CalloutFormat.cs:53-105 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
  • Duplicated block (53 lines × 4) Source/Excel/DispatchInterfaces/CategoryCollection.cs:57 — Source/Excel/DispatchInterfaces/CategoryCollection.cs:57-109 | Source/Office/Interfaces/CategoryCollection.cs:55-107 | Source/PowerPoint/DispatchInterfaces/CategoryCollection.cs:56-108 | Source/Word/DispatchInterfaces/CategoryCollection.cs:56-108 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
  • Duplicated block (53 lines × 4) Source/Excel/DispatchInterfaces/ChartColorFormat.cs:52 — Source/Excel/DispatchInterfaces/ChartColorFormat.cs:52-104 | Source/Office/Interfaces/ChartColorFormat.cs:52-104 | Source/PowerPoint/DispatchInterfaces/ChartColorFormat.cs:52-104 | Source/Word/DispatchInterfaces/ChartColorFormat.cs:53-105 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
  • Duplicated block (53 lines × 4) Source/Excel/DispatchInterfaces/ChartFillFormat.cs:52 — Source/Excel/DispatchInterfaces/ChartFillFormat.cs:52-104 | Source/Office/DispatchInterfaces/ChartFillFormat.cs:52-104 | Source/PowerPoint/DispatchInterfaces/ChartFillFormat.cs:52-104 | Source/Word/DispatchInterfaces/ChartFillFormat.cs:52-104 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
  • Duplicated block (53 lines × 4) Source/Excel/DispatchInterfaces/ChartGroups.cs:56 — Source/Excel/DispatchInterfaces/ChartGroups.cs:56-108 | Source/Office/DispatchInterfaces/ChartGroups.cs:55-107 | Source/PowerPoint/DispatchInterfaces/ChartGroups.cs:56-108 | Source/Word/DispatchInterfaces/ChartGroups.cs:56-108 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
  • Duplicated block (53 lines × 4) Source/Excel/DispatchInterfaces/ColorFormat.cs:54 — Source/Excel/DispatchInterfaces/ColorFormat.cs:54-106 | Source/Office/DispatchInterfaces/ColorFormat.cs:53-105 | Source/PowerPoint/DispatchInterfaces/ColorFormat.cs:53-105 | Source/Word/DispatchInterfaces/ColorFormat.cs:53-105 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
  • Duplicated block (53 lines × 4) Source/Excel/DispatchInterfaces/ConnectorFormat.cs:53 — Source/Excel/DispatchInterfaces/ConnectorFormat.cs:53-105 | Source/Office/DispatchInterfaces/ConnectorFormat.cs:52-104 | Source/PowerPoint/DispatchInterfaces/ConnectorFormat.cs:53-105 | Source/Word/DispatchInterfaces/ConnectorFormat.cs:53-105 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
  • Duplicated block (53 lines × 4) Source/Excel/DispatchInterfaces/DiagramNode.cs:53 — Source/Excel/DispatchInterfaces/DiagramNode.cs:53-105 | Source/Office/DispatchInterfaces/DiagramNode.cs:53-105 | Source/PowerPoint/DispatchInterfaces/DiagramNode.cs:52-104 | Source/Word/DispatchInterfaces/DiagramNode.cs:53-105 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
  • Duplicated block (53 lines × 4) Source/Excel/DispatchInterfaces/DiagramNodeChildren.cs:56 — Source/Excel/DispatchInterfaces/DiagramNodeChildren.cs:56-108 | Source/Office/DispatchInterfaces/DiagramNodeChildren.cs:56-108 | Source/PowerPoint/DispatchInterfaces/DiagramNodeChildren.cs:55-107 | Source/Word/DispatchInterfaces/DiagramNodeChildren.cs:55-107 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
  • Duplicated block (53 lines × 4) Source/Excel/DispatchInterfaces/DiagramNodes.cs:56 — Source/Excel/DispatchInterfaces/DiagramNodes.cs:56-108 | Source/Office/DispatchInterfaces/DiagramNodes.cs:56-108 | Source/PowerPoint/DispatchInterfaces/DiagramNodes.cs:55-107 | Source/Word/DispatchInterfaces/DiagramNodes.cs:55-107 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
  • Duplicated block (53 lines × 4) Source/Excel/DispatchInterfaces/FillFormat.cs:54 — Source/Excel/DispatchInterfaces/FillFormat.cs:54-106 | Source/Office/DispatchInterfaces/FillFormat.cs:53-105 | Source/PowerPoint/DispatchInterfaces/FillFormat.cs:53-105 | Source/Word/DispatchInterfaces/FillFormat.cs:53-105 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
  • Duplicated block (53 lines × 4) Source/Excel/DispatchInterfaces/FreeformBuilder.cs:53 — Source/Excel/DispatchInterfaces/FreeformBuilder.cs:53-105 | Source/Office/DispatchInterfaces/FreeformBuilder.cs:52-104 | Source/PowerPoint/DispatchInterfaces/FreeformBuilder.cs:53-105 | Source/Word/DispatchInterfaces/FreeformBuilder.cs:53-105 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
  • Duplicated block (53 lines × 4) Source/Excel/DispatchInterfaces/FullSeriesCollection.cs:56 — Source/Excel/DispatchInterfaces/FullSeriesCollection.cs:56-108 | Source/Office/Interfaces/FullSeriesCollection.cs:55-107 | Source/PowerPoint/DispatchInterfaces/FullSeriesCollection.cs:56-108 | Source/Word/DispatchInterfaces/FullSeriesCollection.cs:56-108 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
  • Duplicated block (53 lines × 4) Source/Excel/DispatchInterfaces/GroupShapes.cs:56 — Source/Excel/DispatchInterfaces/GroupShapes.cs:56-108 | Source/Office/DispatchInterfaces/GroupShapes.cs:55-107 | Source/PowerPoint/DispatchInterfaces/GroupShapes.cs:56-108 | Source/Word/DispatchInterfaces/GroupShapes.cs:56-108 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
  • Duplicated block (53 lines × 4) Source/Excel/DispatchInterfaces/Interior.cs:53 — Source/Excel/DispatchInterfaces/Interior.cs:53-105 | Source/OWC10/DispatchInterfaces/Interior.cs:52-104 | Source/PowerPoint/DispatchInterfaces/Interior.cs:53-105 | Source/Word/DispatchInterfaces/Interior.cs:53-105 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
  • Duplicated block (53 lines × 4) Source/Excel/DispatchInterfaces/LegendEntries.cs:56 — Source/Excel/DispatchInterfaces/LegendEntries.cs:56-108 | Source/Office/Interfaces/LegendEntries.cs:55-107 | Source/PowerPoint/DispatchInterfaces/LegendEntries.cs:56-108 | Source/Word/DispatchInterfaces/LegendEntries.cs:56-108 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
  • Duplicated block (53 lines × 4) Source/Excel/DispatchInterfaces/LegendEntry.cs:53 — Source/Excel/DispatchInterfaces/LegendEntry.cs:53-105 | Source/Office/Interfaces/LegendEntry.cs:52-104 | Source/PowerPoint/DispatchInterfaces/LegendEntry.cs:53-105 | Source/Word/DispatchInterfaces/LegendEntry.cs:53-105 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
  • Duplicated block (53 lines × 4) Source/Excel/DispatchInterfaces/LineFormat.cs:54 — Source/Excel/DispatchInterfaces/LineFormat.cs:54-106 | Source/Office/DispatchInterfaces/LineFormat.cs:53-105 | Source/PowerPoint/DispatchInterfaces/LineFormat.cs:53-105 | Source/Word/DispatchInterfaces/LineFormat.cs:53-105 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
  • Duplicated block (53 lines × 4) Source/Access/DispatchInterfaces/Pages.cs:56 — Source/Access/DispatchInterfaces/Pages.cs:56-108 | Source/Excel/DispatchInterfaces/Pages.cs:56-108 | Source/Outlook/DispatchInterfaces/Pages.cs:56-108 | Source/Word/DispatchInterfaces/Pages.cs:56-108 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
  • Duplicated block (53 lines × 4) Source/Excel/DispatchInterfaces/Pane.cs:53 — Source/Excel/DispatchInterfaces/Pane.cs:53-105 | Source/OWC10/DispatchInterfaces/Pane.cs:52-104 | Source/PowerPoint/DispatchInterfaces/Pane.cs:53-105 | Source/Word/DispatchInterfaces/Pane.cs:53-105 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
  • Duplicated block (53 lines × 4) Source/Excel/DispatchInterfaces/PictureFormat.cs:54 — Source/Excel/DispatchInterfaces/PictureFormat.cs:54-106 | Source/Office/DispatchInterfaces/PictureFormat.cs:53-105 | Source/PowerPoint/DispatchInterfaces/PictureFormat.cs:53-105 | Source/Word/DispatchInterfaces/PictureFormat.cs:53-105 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
  • + 13 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (724 lines × 2) · ×36
  • Duplicated block (724 lines × 2) Source/Excel/DispatchInterfaces/WorksheetFunction.And.cs:54 — Source/Excel/DispatchInterfaces/WorksheetFunction.And.cs:54-777 | Source/Excel/Interfaces/IWorksheetFunction.And.cs:54-777 — before extracting anything, compare `Source/Excel/DispatchInterfaces/WorksheetFunction.And.cs` and `Source/Excel/Interfaces/IWorksheetFunction.And.cs` as WHOLE FILES: 99% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (724 lines × 2) Source/Excel/DispatchInterfaces/WorksheetFunction.AveDev.cs:54 — Source/Excel/DispatchInterfaces/WorksheetFunction.AveDev.cs:54-777 | Source/Excel/Interfaces/IWorksheetFunction.AveDev.cs:54-777 — before extracting anything, compare `Source/Excel/DispatchInterfaces/WorksheetFunction.AveDev.cs` and `Source/Excel/Interfaces/IWorksheetFunction.AveDev.cs` as WHOLE FILES: 99% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (724 lines × 2) Source/Excel/DispatchInterfaces/WorksheetFunction.Average.cs:54 — Source/Excel/DispatchInterfaces/WorksheetFunction.Average.cs:54-777 | Source/Excel/Interfaces/IWorksheetFunction.Average.cs:54-777 — before extracting anything, compare `Source/Excel/DispatchInterfaces/WorksheetFunction.Average.cs` and `Source/Excel/Interfaces/IWorksheetFunction.Average.cs` as WHOLE FILES: 99% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (724 lines × 2) Source/Excel/DispatchInterfaces/WorksheetFunction.Count.cs:54 — Source/Excel/DispatchInterfaces/WorksheetFunction.Count.cs:54-777 | Source/Excel/Interfaces/IWorksheetFunction.Count.cs:54-777 — before extracting anything, compare `Source/Excel/DispatchInterfaces/WorksheetFunction.Count.cs` and `Source/Excel/Interfaces/IWorksheetFunction.Count.cs` as WHOLE FILES: 99% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (724 lines × 2) Source/Excel/DispatchInterfaces/WorksheetFunction.CountA.cs:54 — Source/Excel/DispatchInterfaces/WorksheetFunction.CountA.cs:54-777 | Source/Excel/Interfaces/IWorksheetFunction.CountA.cs:54-777 — before extracting anything, compare `Source/Excel/DispatchInterfaces/WorksheetFunction.CountA.cs` and `Source/Excel/Interfaces/IWorksheetFunction.CountA.cs` as WHOLE FILES: 99% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (724 lines × 2) Source/Excel/DispatchInterfaces/WorksheetFunction.DevSq.cs:54 — Source/Excel/DispatchInterfaces/WorksheetFunction.DevSq.cs:54-777 | Source/Excel/Interfaces/IWorksheetFunction.DevSq.cs:54-777 — before extracting anything, compare `Source/Excel/DispatchInterfaces/WorksheetFunction.DevSq.cs` and `Source/Excel/Interfaces/IWorksheetFunction.DevSq.cs` as WHOLE FILES: 99% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (724 lines × 2) Source/Excel/DispatchInterfaces/WorksheetFunction.Gcd.cs:54 — Source/Excel/DispatchInterfaces/WorksheetFunction.Gcd.cs:54-777 | Source/Excel/Interfaces/IWorksheetFunction.Gcd.cs:54-777 — before extracting anything, compare `Source/Excel/DispatchInterfaces/WorksheetFunction.Gcd.cs` and `Source/Excel/Interfaces/IWorksheetFunction.Gcd.cs` as WHOLE FILES: 99% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (724 lines × 2) Source/Excel/DispatchInterfaces/WorksheetFunction.GeoMean.cs:54 — Source/Excel/DispatchInterfaces/WorksheetFunction.GeoMean.cs:54-777 | Source/Excel/Interfaces/IWorksheetFunction.GeoMean.cs:54-777 — before extracting anything, compare `Source/Excel/DispatchInterfaces/WorksheetFunction.GeoMean.cs` and `Source/Excel/Interfaces/IWorksheetFunction.GeoMean.cs` as WHOLE FILES: 99% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (724 lines × 2) Source/Excel/DispatchInterfaces/WorksheetFunction.HarMean.cs:54 — Source/Excel/DispatchInterfaces/WorksheetFunction.HarMean.cs:54-777 | Source/Excel/Interfaces/IWorksheetFunction.HarMean.cs:54-777 — before extracting anything, compare `Source/Excel/DispatchInterfaces/WorksheetFunction.HarMean.cs` and `Source/Excel/Interfaces/IWorksheetFunction.HarMean.cs` as WHOLE FILES: 99% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (724 lines × 2) Source/Excel/DispatchInterfaces/WorksheetFunction.ImProduct.cs:54 — Source/Excel/DispatchInterfaces/WorksheetFunction.ImProduct.cs:54-777 | Source/Excel/Interfaces/IWorksheetFunction.ImProduct.cs:54-777 — before extracting anything, compare `Source/Excel/DispatchInterfaces/WorksheetFunction.ImProduct.cs` and `Source/Excel/Interfaces/IWorksheetFunction.ImProduct.cs` as WHOLE FILES: 99% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (724 lines × 2) Source/Excel/DispatchInterfaces/WorksheetFunction.ImSum.cs:54 — Source/Excel/DispatchInterfaces/WorksheetFunction.ImSum.cs:54-777 | Source/Excel/Interfaces/IWorksheetFunction.ImSum.cs:54-777 — before extracting anything, compare `Source/Excel/DispatchInterfaces/WorksheetFunction.ImSum.cs` and `Source/Excel/Interfaces/IWorksheetFunction.ImSum.cs` as WHOLE FILES: 99% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (724 lines × 2) Source/Excel/DispatchInterfaces/WorksheetFunction.Kurt.cs:54 — Source/Excel/DispatchInterfaces/WorksheetFunction.Kurt.cs:54-777 | Source/Excel/Interfaces/IWorksheetFunction.Kurt.cs:54-777 — before extracting anything, compare `Source/Excel/DispatchInterfaces/WorksheetFunction.Kurt.cs` and `Source/Excel/Interfaces/IWorksheetFunction.Kurt.cs` as WHOLE FILES: 99% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (724 lines × 2) Source/Excel/DispatchInterfaces/WorksheetFunction.Lcm.cs:54 — Source/Excel/DispatchInterfaces/WorksheetFunction.Lcm.cs:54-777 | Source/Excel/Interfaces/IWorksheetFunction.Lcm.cs:54-777 — before extracting anything, compare `Source/Excel/DispatchInterfaces/WorksheetFunction.Lcm.cs` and `Source/Excel/Interfaces/IWorksheetFunction.Lcm.cs` as WHOLE FILES: 99% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (724 lines × 2) Source/Excel/DispatchInterfaces/WorksheetFunction.Max.cs:54 — Source/Excel/DispatchInterfaces/WorksheetFunction.Max.cs:54-777 | Source/Excel/Interfaces/IWorksheetFunction.Max.cs:54-777 — before extracting anything, compare `Source/Excel/DispatchInterfaces/WorksheetFunction.Max.cs` and `Source/Excel/Interfaces/IWorksheetFunction.Max.cs` as WHOLE FILES: 99% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (724 lines × 2) Source/Excel/DispatchInterfaces/WorksheetFunction.Median.cs:54 — Source/Excel/DispatchInterfaces/WorksheetFunction.Median.cs:54-777 | Source/Excel/Interfaces/IWorksheetFunction.Median.cs:54-777 — before extracting anything, compare `Source/Excel/DispatchInterfaces/WorksheetFunction.Median.cs` and `Source/Excel/Interfaces/IWorksheetFunction.Median.cs` as WHOLE FILES: 99% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (724 lines × 2) Source/Excel/DispatchInterfaces/WorksheetFunction.Min.cs:54 — Source/Excel/DispatchInterfaces/WorksheetFunction.Min.cs:54-777 | Source/Excel/Interfaces/IWorksheetFunction.Min.cs:54-777 — before extracting anything, compare `Source/Excel/DispatchInterfaces/WorksheetFunction.Min.cs` and `Source/Excel/Interfaces/IWorksheetFunction.Min.cs` as WHOLE FILES: 99% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (724 lines × 2) Source/Excel/DispatchInterfaces/WorksheetFunction.Mode.cs:54 — Source/Excel/DispatchInterfaces/WorksheetFunction.Mode.cs:54-777 | Source/Excel/Interfaces/IWorksheetFunction.Mode.cs:54-777 — before extracting anything, compare `Source/Excel/DispatchInterfaces/WorksheetFunction.Mode.cs` and `Source/Excel/Interfaces/IWorksheetFunction.Mode.cs` as WHOLE FILES: 99% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (724 lines × 2) Source/Excel/DispatchInterfaces/WorksheetFunction.Mode_Mult.cs:54 — Source/Excel/DispatchInterfaces/WorksheetFunction.Mode_Mult.cs:54-777 | Source/Excel/Interfaces/IWorksheetFunction.Mode_Mult.cs:54-777 — before extracting anything, compare `Source/Excel/DispatchInterfaces/WorksheetFunction.Mode_Mult.cs` and `Source/Excel/Interfaces/IWorksheetFunction.Mode_Mult.cs` as WHOLE FILES: 99% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (724 lines × 2) Source/Excel/DispatchInterfaces/WorksheetFunction.Mode_Sngl.cs:54 — Source/Excel/DispatchInterfaces/WorksheetFunction.Mode_Sngl.cs:54-777 | Source/Excel/Interfaces/IWorksheetFunction.Mode_Sngl.cs:54-777 — before extracting anything, compare `Source/Excel/DispatchInterfaces/WorksheetFunction.Mode_Sngl.cs` and `Source/Excel/Interfaces/IWorksheetFunction.Mode_Sngl.cs` as WHOLE FILES: 99% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (724 lines × 2) Source/Excel/DispatchInterfaces/WorksheetFunction.MultiNomial.cs:54 — Source/Excel/DispatchInterfaces/WorksheetFunction.MultiNomial.cs:54-777 | Source/Excel/Interfaces/IWorksheetFunction.MultiNomial.cs:54-777 — before extracting anything, compare `Source/Excel/DispatchInterfaces/WorksheetFunction.MultiNomial.cs` and `Source/Excel/Interfaces/IWorksheetFunction.MultiNomial.cs` as WHOLE FILES: 99% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (724 lines × 2) Source/Excel/DispatchInterfaces/WorksheetFunction.Or.cs:54 — Source/Excel/DispatchInterfaces/WorksheetFunction.Or.cs:54-777 | Source/Excel/Interfaces/IWorksheetFunction.Or.cs:54-777 — before extracting anything, compare `Source/Excel/DispatchInterfaces/WorksheetFunction.Or.cs` and `Source/Excel/Interfaces/IWorksheetFunction.Or.cs` as WHOLE FILES: 99% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (724 lines × 2) Source/Excel/DispatchInterfaces/WorksheetFunction.Product.cs:54 — Source/Excel/DispatchInterfaces/WorksheetFunction.Product.cs:54-777 | Source/Excel/Interfaces/IWorksheetFunction.Product.cs:54-777 — before extracting anything, compare `Source/Excel/DispatchInterfaces/WorksheetFunction.Product.cs` and `Source/Excel/Interfaces/IWorksheetFunction.Product.cs` as WHOLE FILES: 99% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (724 lines × 2) Source/Excel/DispatchInterfaces/WorksheetFunction.Skew.cs:54 — Source/Excel/DispatchInterfaces/WorksheetFunction.Skew.cs:54-777 | Source/Excel/Interfaces/IWorksheetFunction.Skew.cs:54-777 — before extracting anything, compare `Source/Excel/DispatchInterfaces/WorksheetFunction.Skew.cs` and `Source/Excel/Interfaces/IWorksheetFunction.Skew.cs` as WHOLE FILES: 99% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (724 lines × 2) Source/Excel/DispatchInterfaces/WorksheetFunction.Skew_p.cs:54 — Source/Excel/DispatchInterfaces/WorksheetFunction.Skew_p.cs:54-777 | Source/Excel/Interfaces/IWorksheetFunction.Skew_p.cs:54-777 — before extracting anything, compare `Source/Excel/DispatchInterfaces/WorksheetFunction.Skew_p.cs` and `Source/Excel/Interfaces/IWorksheetFunction.Skew_p.cs` as WHOLE FILES: 99% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (724 lines × 2) Source/Excel/DispatchInterfaces/WorksheetFunction.StDev.cs:54 — Source/Excel/DispatchInterfaces/WorksheetFunction.StDev.cs:54-777 | Source/Excel/Interfaces/IWorksheetFunction.StDev.cs:54-777 — before extracting anything, compare `Source/Excel/DispatchInterfaces/WorksheetFunction.StDev.cs` and `Source/Excel/Interfaces/IWorksheetFunction.StDev.cs` as WHOLE FILES: 99% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • + 11 more in this group — see findings.md.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×34
  • Swallowed exception (caught, then discarded) Source/NetOffice/COMProxyShare.cs:335 — `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
  • Swallowed exception (caught, then discarded) Source/NetOffice/Contribution/CollectionsGeneric/DisposableSequence.cs:98 — `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
  • Swallowed exception (caught, then discarded) Source/NetOffice/Contribution/CollectionsGeneric/DisposableSequence.cs:124 — `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
  • Swallowed exception (caught, then discarded) Source/NetOffice/Contribution/CollectionsGeneric/DisposableSequence.cs:136 — `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
  • Swallowed exception (caught, then discarded) Source/NetOffice/Contribution/CollectionsGeneric/DisposableSequence.cs:247 — `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
  • Swallowed exception (caught, then discarded) Source/NetOffice/Contribution/CollectionsGeneric/DisposableSequence.cs:259 — `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
  • Swallowed exception (caught, then discarded) Source/NetOffice/Contribution/CollectionsGeneric/DisposableSequence.cs:283 — `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
  • Swallowed exception (caught, then discarded) Source/NetOffice/Contribution/CollectionsGeneric/DisposableSequence.cs:295 — `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
  • Swallowed exception (caught, then discarded) Source/NetOffice/Contribution/Controls/InstanceMonitor.cs:326 — `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
  • Swallowed exception (caught, then discarded) Source/NetOffice/Diagnostics/SelfDiagnostics.cs:161 — `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
  • Swallowed exception (caught, then discarded) Source/NetOffice/Running/RunningObjectTable.cs:47 — `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
  • Swallowed exception (caught, then discarded) Source/NetOffice/Running/RunningObjectTable.cs:74 — `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
  • Swallowed exception (caught, then discarded) Source/NetOffice/Running/RunningWindowTable.Nested.cs:177 — `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
  • Swallowed exception (caught, then discarded) Source/NetOffice/Running/RunningWindowTable.Nested.cs:200 — `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
  • Swallowed exception (caught, then discarded) Source/Office.Extensions/Dialogs/AboutDialog.cs:75 — `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
  • Swallowed exception (caught, then discarded) Source/Office.Extensions/Dialogs/RichTextDialog.cs:210 — `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
  • Swallowed exception (caught, then discarded) Source/Office.Extensions/TrayMenuUtils/TrayMenu.cs:542 — `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
  • Swallowed exception (caught, then discarded) Source/Office.Extensions/TrayMenuUtils/TrayMenu.cs:565 — `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
  • Swallowed exception (caught, then discarded) Source/Office.Extensions/TrayMenuUtils/TrayMenu.cs:588 — `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
  • Swallowed exception (caught, then discarded) Source/Office.Extensions/TrayMenuUtils/TrayMenu.cs:626 — `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
  • Swallowed exception (caught, then discarded) Source/Office.Extensions/TrayMenuUtils/TrayMenu.cs:647 — `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
  • Swallowed exception (caught, then discarded) Source/Office.Extensions/TrayMenuUtils/TrayMenu.cs:668 — `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
  • Swallowed exception (caught, then discarded) Source/Office.Extensions/TrayMenuUtils/TrayMenuMonitorItemControl.cs:463 — `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
  • Swallowed exception (caught, then discarded) Toolbox/Toolbox/Controls/Custom/InviteControl.cs:45 — `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
  • Swallowed exception (caught, then discarded) Toolbox/Toolbox/Controls/Custom/InviteControl.cs:57 — `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
  • + 9 more in this group — see findings.md.
X18 · Disposal-pattern correctness · Disposable created and abandoned in the method that made it · ×32
  • Disposable created and abandoned in the method that made it Source/ClientApplication/RunExcel01.cs:22 — `utils` is a `CommonUtils`, which implements `IDisposable`, and it is created here (line 22). Every use of it in `Run` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var utils = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it Source/NetOffice/Tools/CodebaseAttribute.cs:77 — `key` is a `RegistryKey`, which implements `IDisposable`, and it is created here (line 77). Every use of it in `CreateValue` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var key = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it Source/NetOffice/Tools/ProgrammableAttribute.cs:52 — `key` is a `RegistryKey`, which implements `IDisposable`, and it is created here (line 52). Every use of it in `CreateKeys` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var key = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it Source/NetOffice/Tools/ProgrammableAttribute.cs:57 — `key` is a `RegistryKey`, which implements `IDisposable`, and it is created here (line 57). Every use of it in `CreateKeys` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var key = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it Source/Word/Tools/Contribution/ApplicationUtils.cs:198 — `a` is a `COMObject`, which implements `IDisposable`, and it is created here (line 198). Every use of it in `Equal` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var a = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it Source/Office.Extensions/Dialogs/DialogUtilsEx.cs:606 — `dlg` is a `RichTextDialog`, which implements `IDisposable`, and it is created here (line 606). Every use of it in `ShowRegister` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var dlg = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it Source/Office.Extensions/Dialogs/DialogUtilsEx.cs:643 — `dlg` is a `RichTextDialog`, which implements `IDisposable`, and it is created here (line 643). Every use of it in `ShowUnregister` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var dlg = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it Examples/ExampleBase/ErrorForm.cs:49 — `form` is a `ErrorForm`, which implements `IDisposable`, and it is created here (line 49). Every use of it in `Show` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var form = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it Examples/ExampleBase/ErrorForm.cs:61 — `form` is a `ErrorForm`, which implements `IDisposable`, and it is created here (line 61). Every use of it in `Show` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var form = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it Examples/ExampleBase/ExampleForm.cs:64 — `dialog` is a `FinishForm`, which implements `IDisposable`, and it is created here (line 64). Every use of it in `ShowFinishDialog` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var dialog = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it Examples/ExampleBase/ExampleForm.cs:166 — `dialog` is a `OptionsForm`, which implements `IDisposable`, and it is created here (line 166). Every use of it in `OptionButton_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var dialog = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it Examples/Access/Automation/Examples/Example01.cs:26 — `utils` is a `CommonUtils`, which implements `IDisposable`, and it is created here (line 26). Every use of it in `RunExample` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var utils = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it Examples/Access/Automation/Examples/Example01.cs:36 — `newDatabase` is a `Database`, which implements `IDisposable`, and it is created here (line 36). Every use of it in `RunExample` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var newDatabase = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it REDACTED:26 — `utils` is a `CommonUtils`, which implements `IDisposable`, and it is created here (line 26). Every use of it in `RunExample` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var utils = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it REDACTED:36 — `newDatabase` is a `Database`, which implements `IDisposable`, and it is created here (line 36). Every use of it in `RunExample` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var newDatabase = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it REDACTED:44 — `oleCreateCommand` is a `OleDbCommand`, which implements `IDisposable`, and it is created here (line 44). Every use of it in `RunExample` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var oleCreateCommand = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it REDACTED:51 — `oleInsertCommand` is a `OleDbCommand`, which implements `IDisposable`, and it is created here (line 51). Every use of it in `RunExample` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var oleInsertCommand = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it REDACTED:27 — `utils` is a `CommonUtils`, which implements `IDisposable`, and it is created here (line 27). Every use of it in `RunExample` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var utils = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it REDACTED:37 — `newDatabase` is a `Database`, which implements `IDisposable`, and it is created here (line 37). Every use of it in `RunExample` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var newDatabase = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it REDACTED:45 — `oleCreateCommand` is a `OleDbCommand`, which implements `IDisposable`, and it is created here (line 45). Every use of it in `RunExample` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var oleCreateCommand = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it REDACTED:52 — `oleInsertCommand` is a `OleDbCommand`, which implements `IDisposable`, and it is created here (line 52). Every use of it in `RunExample` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var oleInsertCommand = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it Examples/Access/Automation/Examples/Example04.cs:68 — `accessApplication` is a `Application`, which implements `IDisposable`, and it is created here (line 68). Every use of it in `ShowDatabaseInfo` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var accessApplication = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it Examples/Access/Automation/Examples/Example04.cs:71 — `database` is a `Database`, which implements `IDisposable`, and it is created here (line 71). Every use of it in `ShowDatabaseInfo` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var database = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it Examples/Access/Automation/Examples/Example04.cs:96 — `ofd` is a `OpenFileDialog`, which implements `IDisposable`, and it is created here (line 96). Every use of it in `buttonSelectDatabase_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var ofd = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it Examples/Access/Automation/Examples/Example05.cs:90 — `utils` is a `CommonUtils`, which implements `IDisposable`, and it is created here (line 90). Every use of it in `buttonStartExample_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var utils = …;`), which releases it at the end of the scope on every path including a throw.
  • + 7 more in this group — see findings.md.
AX2 · Stateful singletons · Process-global static state · ×31
  • Process-global static state: Application Source/Excel/Classes/Application.cs:68 — `Application` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 108). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: Chart Source/Excel/Classes/Chart.cs:33 — `Chart` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 74). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: OLEObject Source/Excel/Classes/OLEObject.cs:22 — `OLEObject` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 63). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: QueryTable Source/Excel/Classes/QueryTable.cs:22 — `QueryTable` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 62). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: Workbook Source/Excel/Classes/Workbook.cs:61 — `Workbook` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 101). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: Worksheet Source/Excel/Classes/Worksheet.cs:38 — `Worksheet` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 78). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: AboveAverage Source/Excel/DispatchInterfaces/AboveAverage.cs:13 — `AboveAverage` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 41). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: Action Source/Excel/DispatchInterfaces/Action.cs:13 — `Action` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 41). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: Actions Source/Excel/DispatchInterfaces/Actions.cs:16 — `Actions` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 44). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: AddIn Source/Excel/DispatchInterfaces/AddIn.cs:13 — `AddIn` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 41). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: AddIns Source/Excel/DispatchInterfaces/AddIns.cs:16 — `AddIns` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 44). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: AddIns2 Source/Excel/DispatchInterfaces/AddIns2.cs:16 — `AddIns2` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 44). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: Adjustments Source/Excel/DispatchInterfaces/Adjustments.cs:16 — `Adjustments` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 45). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: AllowEditRange Source/Excel/DispatchInterfaces/AllowEditRange.cs:13 — `AllowEditRange` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 41). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: AllowEditRanges Source/Excel/DispatchInterfaces/AllowEditRanges.cs:16 — `AllowEditRanges` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 44). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: Arc Source/Excel/DispatchInterfaces/Arc.cs:140 — `Arc` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 168). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: Arcs Source/Excel/DispatchInterfaces/Arcs.cs:143 — `Arcs` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 171). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: Areas Source/Excel/DispatchInterfaces/Areas.cs:16 — `Areas` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 44). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: AutoCorrect Source/Excel/DispatchInterfaces/AutoCorrect.cs:131 — `AutoCorrect` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 159). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: AutoFilter Source/Excel/DispatchInterfaces/AutoFilter.cs:13 — `AutoFilter` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 41). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: AutoRecover Source/Excel/DispatchInterfaces/AutoRecover.cs:13 — `AutoRecover` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 41). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: Axes Source/Excel/DispatchInterfaces/Axes.cs:16 — `Axes` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 44). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: Axis Source/Excel/DispatchInterfaces/Axis.cs:13 — `Axis` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 41). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: AxisTitle Source/Excel/DispatchInterfaces/AxisTitle.cs:145 — `AxisTitle` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 173). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: Border Source/Excel/DispatchInterfaces/Border.cs:13 — `Border` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_type; e.g. `_type` at line 41). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • + 6 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×31
  • Duplicated block (8 lines × 2) Source/Excel/Events/DocEvents.cs:283 — Source/Excel/Events/DocEvents.cs:283-290 | Source/Excel/Events/DocEvents.cs:304-311 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (8 lines × 2) Source/MSComctlLib/Events/ITreeViewEvents.cs:192 — Source/MSComctlLib/Events/ITreeViewEvents.cs:192-199 | Source/MSComctlLib/Events/ListViewEvents.cs:187-194 — before extracting anything, compare `Source/MSComctlLib/Events/ITreeViewEvents.cs` and `Source/MSComctlLib/Events/ListViewEvents.cs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 319 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Source/MSComctlLib/Events/ITreeViewEvents.cs:192` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) Source/Analyzers/NetOffice.Analyzers/EventValidateRaiseConsistencyAnalyzer.cs:158 — Source/Analyzers/NetOffice.Analyzers/EventValidateRaiseConsistencyAnalyzer.cs:158-165 | Source/Analyzers/NetOffice.Analyzers/EventValidateRaiseConsistencyAnalyzer.cs:174-181 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 2) Source/Outlook/Events/ApplicationEvents_10.cs:48 — Source/Outlook/Events/ApplicationEvents_10.cs:48-55 | Source/Outlook/Events/ApplicationEvents_11.cs:48-55 — before extracting anything, compare `Source/Outlook/Events/ApplicationEvents_10.cs` and `Source/Outlook/Events/ApplicationEvents_11.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 122 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (8 lines × 2) Source/Outlook/Events/ItemsEvents.cs:20 — Source/Outlook/Events/ItemsEvents.cs:20-27 | Source/Outlook/Events/ResultsEvents.cs:20-27 — before extracting anything, compare `Source/Outlook/Events/ItemsEvents.cs` and `Source/Outlook/Events/ResultsEvents.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (8 lines × 2) Source/Access/Events/DispNavigationControlEvents.cs:21 — Source/Access/Events/DispNavigationControlEvents.cs:21-28 | Source/Access/Events/DispWebBrowserControlEvents.cs:26-33 — before extracting anything, compare `Source/Access/Events/DispNavigationControlEvents.cs` and `Source/Access/Events/DispWebBrowserControlEvents.cs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 266 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (8 lines × 2) Toolbox/Toolbox/Controls/Hex/HexBox.cs:1988 — Toolbox/Toolbox/Controls/Hex/HexBox.cs:1988-1995 | Toolbox/Toolbox/Controls/Hex/HexBox.cs:2171-2178 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (8 lines × 2) Source/Excel/Events/AppEvents.cs:25 — Source/Excel/Events/AppEvents.cs:25-32 | Source/Excel/Events/WorkbookEvents.cs:76-83 — before extracting anything, compare `Source/Excel/Events/AppEvents.cs` and `Source/Excel/Events/WorkbookEvents.cs` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 377 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Source/Excel/Events/WorkbookEvents.cs:84` calls `SinkArgument` and `Source/Excel/Events/AppEvents.cs:33` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (8 lines × 2) Source/Access/Events/_PageHdrFtrInReportEvents.cs:19 — Source/Access/Events/_PageHdrFtrInReportEvents.cs:19-26 | Source/Access/Events/_SectionInReportEvents.cs:19-26 — before extracting anything, compare `Source/Access/Events/_PageHdrFtrInReportEvents.cs` and `Source/Access/Events/_SectionInReportEvents.cs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 162 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (8 lines × 2) Source/Office.Extensions/TrayMenuUtils/TrayMenuMonitorItem.cs:107 — Source/Office.Extensions/TrayMenuUtils/TrayMenuMonitorItem.cs:107-114 | Source/Office.Extensions/TrayMenuUtils/TrayMenuMonitorItem.cs:135-142 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (8 lines × 2) Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/WindowsFormsConverterCS.cs:58 — Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/WindowsFormsConverterCS.cs:58-65 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/WindowsFormsConverterVB.cs:61-68 — before extracting anything, compare `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/WindowsFormsConverterCS.cs` and `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/WindowsFormsConverterVB.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 33 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (8 lines × 2) RegAddin/RegAddin/Common/AddinRegAnalyzer.cs:65 — RegAddin/RegAddin/Common/AddinRegAnalyzer.cs:65-72 | RegAddin/RegAddin/Common/AddinRegAnalyzer.cs:113-120 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `RegAddin/RegAddin/Common/AddinRegAnalyzer.cs:65` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) Source/NetOffice/Running/ChildWindowBatchEnumerator.cs:15 — Source/NetOffice/Running/ChildWindowBatchEnumerator.cs:15-22 | Source/NetOffice/Running/ChildWindowEnumerator.cs:15-22 — before extracting anything, compare `Source/NetOffice/Running/ChildWindowBatchEnumerator.cs` and `Source/NetOffice/Running/ChildWindowEnumerator.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 2) Source/OWC10/DispatchInterfaces/ChChart.cs:877 — Source/OWC10/DispatchInterfaces/ChChart.cs:877-884 | Source/OWC10/DispatchInterfaces/ChSeries.cs:599-606 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (8 lines × 2) Toolbox/Toolbox/Controls/Hex/HexBox.cs:2318 — Toolbox/Toolbox/Controls/Hex/HexBox.cs:2318-2325 | Toolbox/Toolbox/Controls/Hex/HexBox.cs:2376-2383 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Toolbox/Toolbox/Controls/Hex/HexBox.cs:2384` calls `GetType` and `Toolbox/Toolbox/Controls/Hex/HexBox.cs:2327` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (8 lines × 2) Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/ReportControl.cs:486 — Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/ReportControl.cs:486-493 | Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/ReportControl.cs:514-521 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (8 lines × 2) Source/Excel/Events/AppEvents.cs:234 — Source/Excel/Events/AppEvents.cs:234-241 | Source/Excel/Events/WorkbookEvents.cs:206-213 — before extracting anything, compare `Source/Excel/Events/AppEvents.cs` and `Source/Excel/Events/WorkbookEvents.cs` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 377 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Source/Excel/Events/WorkbookEvents.cs:213` calls `SinkArgument` and `Source/Excel/Events/AppEvents.cs:241` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (8 lines × 2) Source/NetOffice/Contribution/Controls/InstanceMonitor.cs:202 — Source/NetOffice/Contribution/Controls/InstanceMonitor.cs:202-209 | Source/Office.Extensions/TrayMenuUtils/TrayMenuMonitorItemControl.cs:261-268 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Source/NetOffice/Contribution/Controls/InstanceMonitor.cs:202` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (8 lines × 2) RegAddin/RegAddin/Register/RegisterOperationHost.cs:144 — RegAddin/RegAddin/Register/RegisterOperationHost.cs:144-151 | RegAddin/RegAddin/Register/RegisterOperationHost.cs:154-161 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (8 lines × 2) Source/Excel/Events/ChartEvents.cs:306 — Source/Excel/Events/ChartEvents.cs:306-313 | Source/Excel/Events/DocEvents.cs:208-215 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (8 lines × 2) Source/Word/Events/DocumentEvents.cs:59 — Source/Word/Events/DocumentEvents.cs:59-66 | Source/Word/Events/DocumentEvents2.cs:121-128 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (8 lines × 2) Source/Outlook/Events/ApplicationEvents_10.cs:194 — Source/Outlook/Events/ApplicationEvents_10.cs:194-201 | Source/Outlook/Events/ApplicationEvents_11.cs:251-258 — before extracting anything, compare `Source/Outlook/Events/ApplicationEvents_10.cs` and `Source/Outlook/Events/ApplicationEvents_11.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 122 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (8 lines × 2) Source/Outlook/Events/ExplorerEvents.cs:93 — Source/Outlook/Events/ExplorerEvents.cs:93-100 | Source/Outlook/Events/ExplorerEvents_10.cs:142-149 — before extracting anything, compare `Source/Outlook/Events/ExplorerEvents.cs` and `Source/Outlook/Events/ExplorerEvents_10.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 100 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (8 lines × 2) Source/Outlook/Events/ExplorerEvents.cs:121 — Source/Outlook/Events/ExplorerEvents.cs:121-128 | Source/Outlook/Events/ExplorerEvents_10.cs:170-177 — before extracting anything, compare `Source/Outlook/Events/ExplorerEvents.cs` and `Source/Outlook/Events/ExplorerEvents_10.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 100 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (8 lines × 2) Source/Outlook/Events/ExplorerEvents_10.cs:341 — Source/Outlook/Events/ExplorerEvents_10.cs:341-348 | Source/Outlook/Events/InspectorEvents_10.cs:196-203 — before extracting anything, compare `Source/Outlook/Events/ExplorerEvents_10.cs` and `Source/Outlook/Events/InspectorEvents_10.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 130 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • + 6 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×31
  • Duplicated block (6 lines × 2) Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/ReportControl.cs:237 — Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/ReportControl.cs:237-242 | Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/ReportControl.cs:258-263 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/ReportControl.cs:237` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (6 lines × 2) Source/Access/Events/DispBoundObjectFrameEvents.cs:19 — Source/Access/Events/DispBoundObjectFrameEvents.cs:19-24 | Source/Access/Events/DispObjectFrameEvents.cs:19-24 — before extracting anything, compare `Source/Access/Events/DispBoundObjectFrameEvents.cs` and `Source/Access/Events/DispObjectFrameEvents.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 183 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Source/Access/Events/DispObjectFrameEvents.cs:25` calls `MethodImpl`, `DispId`, `Enter` and `Source/Access/Events/DispBoundObjectFrameEvents.cs:25` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (6 lines × 2) Source/Access/Events/_FormEvents.cs:59 — Source/Access/Events/_FormEvents.cs:59-64 | Source/Access/Events/_ReportEvents.cs:19-24 — before extracting anything, compare `Source/Access/Events/_FormEvents.cs` and `Source/Access/Events/_ReportEvents.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 89 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (6 lines × 2) Source/Access/Events/_FormEvents2.cs:61 — Source/Access/Events/_FormEvents2.cs:61-66 | Source/Access/Events/_ReportEvents2.cs:19-24 — before extracting anything, compare `Source/Access/Events/_FormEvents2.cs` and `Source/Access/Events/_ReportEvents2.cs` as WHOLE FILES: this scan already matched 45 separate duplicated blocks between them, totalling at least 418 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (6 lines × 2) RegAddin/RegAddin/Common/AddinClassInformations.cs:31 — RegAddin/RegAddin/Common/AddinClassInformations.cs:31-36 | RegAddin/RegAddin/Common/AddinClassInformations.cs:67-72 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (6 lines × 2) Source/Office/Tools/COMAddin.cs:1037 — Source/Office/Tools/COMAddin.cs:1037-1042 | Source/Office/Tools/COMAddin.cs:1060-1065 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/Office/Tools/COMAddin.cs:1037` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) Source/NetOffice/Contribution/Controls/InstanceMonitor.cs:248 — Source/NetOffice/Contribution/Controls/InstanceMonitor.cs:248-253 | Source/Office.Extensions/TrayMenuUtils/TrayMenuMonitorItemControl.cs:298-303 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Source/NetOffice/Contribution/Controls/InstanceMonitor.cs:248` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) Source/ADODB/Events/ConnectionEvents.cs:140 — Source/ADODB/Events/ConnectionEvents.cs:140-145 | Source/ADODB/Events/ConnectionEvents.cs:225-230 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/ADODB/Events/ConnectionEvents.cs:140` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Source/ADODB/Events/ConnectionEvents.cs:232` calls `CreateEventArgumentObjectFromComProxy` and `Source/ADODB/Events/ConnectionEvents.cs:147` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (6 lines × 2) BuildTools/SearchAndReplace/SearchAndReplaceManager.cs:45 — BuildTools/SearchAndReplace/SearchAndReplaceManager.cs:45-50 | BuildTools/SearchAndReplace/SearchAndReplaceManager.cs:61-66 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `BuildTools/SearchAndReplace/SearchAndReplaceManager.cs:45` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) Source/Excel/Events/AppEvents.cs:142 — Source/Excel/Events/AppEvents.cs:142-147 | Source/Excel/Events/AppEvents.cs:148-153 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (6 lines × 2) Source/Excel/Events/AppEvents.cs:300 — Source/Excel/Events/AppEvents.cs:300-305 | Source/Excel/Events/WorkbookEvents.cs:242-247 — before extracting anything, compare `Source/Excel/Events/AppEvents.cs` and `Source/Excel/Events/WorkbookEvents.cs` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 377 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (6 lines × 2) Source/Excel/Events/AppEvents.cs:778 — Source/Excel/Events/AppEvents.cs:778-783 | Source/Excel/Events/WorkbookEvents.cs:666-671 — before extracting anything, compare `Source/Excel/Events/AppEvents.cs` and `Source/Excel/Events/WorkbookEvents.cs` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 377 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (6 lines × 2) Source/Excel/Events/DocEvents.cs:22 — Source/Excel/Events/DocEvents.cs:22-27 | Source/Excel/Events/DocEvents.cs:28-33 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (6 lines × 2) Source/Excel/Events/WorkbookEvents.cs:138 — Source/Excel/Events/WorkbookEvents.cs:138-143 | Source/Word/Events/DocumentEvents2.cs:31-36 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (6 lines × 2) Source/Office/Tools/COMAddin.cs:1039 — Source/Office/Tools/COMAddin.cs:1039-1044 | Source/Office/Tools/COMAddin.cs:1090-1096 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (6 lines × 2) Source/Office/Tools/COMAddin.cs:1062 — Source/Office/Tools/COMAddin.cs:1062-1067 | Source/Office/Tools/COMAddin.cs:1113-1119 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (6 lines × 2) Source/Word/Events/DocumentEvents2.cs:70 — Source/Word/Events/DocumentEvents2.cs:70-75 | Source/Word/Events/DocumentEvents2.cs:76-81 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (6 lines × 2) Source/Outlook/Events/ExplorerEvents.cs:37 — Source/Outlook/Events/ExplorerEvents.cs:37-42 | Source/Outlook/Events/ExplorerEvents_10.cs:37-42 — before extracting anything, compare `Source/Outlook/Events/ExplorerEvents.cs` and `Source/Outlook/Events/ExplorerEvents_10.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 100 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (6 lines × 2) Source/PowerPoint/Events/EApplication.cs:59 — Source/PowerPoint/Events/EApplication.cs:59-64 | Source/PowerPoint/Events/EApplication.cs:65-70 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (6 lines × 2) Source/Access/Events/_FormEvents.cs:188 — Source/Access/Events/_FormEvents.cs:188-193 | Source/Access/Events/_FormEvents.cs:199-204 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (6 lines × 2) Source/Access/Events/_FormEvents.cs:225 — Source/Access/Events/_FormEvents.cs:225-230 | Source/Access/Events/_FormEvents2.cs:200-205 — before extracting anything, compare `Source/Access/Events/_FormEvents.cs` and `Source/Access/Events/_FormEvents2.cs` as WHOLE FILES: this scan already matched 72 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (6 lines × 2) Source/ADODB/Events/ConnectionEvents.cs:51 — Source/ADODB/Events/ConnectionEvents.cs:51-56 | Source/ADODB/Events/ConnectionEvents.cs:61-66 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (6 lines × 2) Source/Office.Extensions/TrayMenuUtils/TrayMenu.cs:301 — Source/Office.Extensions/TrayMenuUtils/TrayMenu.cs:301-306 | Source/Office.Extensions/TrayMenuUtils/TrayMenu.cs:334-339 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/Office.Extensions/TrayMenuUtils/TrayMenu.cs:301` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) Source/NetOffice/Diagnostics/SelfDiagnostics.cs:76 — Source/NetOffice/Diagnostics/SelfDiagnostics.cs:76-81 | Source/Office/Tools/Informations/AssemblyInfo.cs:85-90 — before extracting anything, compare `Source/NetOffice/Diagnostics/SelfDiagnostics.cs` and `Source/Office/Tools/Informations/AssemblyInfo.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 33 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (6 lines × 2) Source/NetOffice/Diagnostics/SelfDiagnostics.cs:91 — Source/NetOffice/Diagnostics/SelfDiagnostics.cs:91-96 | Source/Office/Tools/Informations/AssemblyInfo.cs:100-105 — before extracting anything, compare `Source/NetOffice/Diagnostics/SelfDiagnostics.cs` and `Source/Office/Tools/Informations/AssemblyInfo.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 33 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • + 6 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×30
  • Duplicated block (12 lines × 2) Source/Excel/Events/AppEvents.cs:285 — Source/Excel/Events/AppEvents.cs:285-296 | Source/Excel/Events/WorkbookEvents.cs:228-239 — before extracting anything, compare `Source/Excel/Events/AppEvents.cs` and `Source/Excel/Events/WorkbookEvents.cs` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 377 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (12 lines × 2) Source/ADODB/Events/RecordsetEvents.cs:51 — Source/ADODB/Events/RecordsetEvents.cs:51-62 | Source/ADODB/Events/RecordsetEvents.cs:66-77 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (12 lines × 2) Source/NetOffice/Events/CoClassEventReflector.cs:46 — Source/NetOffice/Events/CoClassEventReflector.cs:46-57 | Source/NetOffice/Events/CoClassEventReflector.cs:100-111 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/NetOffice/Events/CoClassEventReflector.cs:46` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) Source/NetOffice/SinkHelper.cs:159 — Source/NetOffice/SinkHelper.cs:159-170 | Source/NetOffice/SinkHelper.cs:199-210 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (12 lines × 2) Source/MSComctlLib/Events/ITreeViewEvents.cs:19 — Source/MSComctlLib/Events/ITreeViewEvents.cs:19-30 | Source/MSComctlLib/Events/ListViewEvents.cs:19-30 — before extracting anything, compare `Source/MSComctlLib/Events/ITreeViewEvents.cs` and `Source/MSComctlLib/Events/ListViewEvents.cs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 319 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (12 lines × 2) Source/NetOffice/Extensions/EnumerableExtensions.cs:28 — Source/NetOffice/Extensions/EnumerableExtensions.cs:28-39 | Source/NetOffice/Extensions/EnumerableExtensions.cs:108-119 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/NetOffice/Extensions/EnumerableExtensions.cs:28` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (12 lines × 2) Source/NetOffice/Utils.cs:213 — Source/NetOffice/Utils.cs:213-224 | Source/NetOffice/Utils.cs:240-251 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/NetOffice/Utils.cs:213` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) Source/Outlook/Events/ExplorerEvents_10.cs:231 — Source/Outlook/Events/ExplorerEvents_10.cs:231-242 | Source/Outlook/Events/InspectorEvents_10.cs:121-132 — before extracting anything, compare `Source/Outlook/Events/ExplorerEvents_10.cs` and `Source/Outlook/Events/InspectorEvents_10.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 130 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (12 lines × 2) Source/Outlook/Events/ExplorerEvents_10.cs:246 — Source/Outlook/Events/ExplorerEvents_10.cs:246-257 | Source/Outlook/Events/InspectorEvents_10.cs:136-147 — before extracting anything, compare `Source/Outlook/Events/ExplorerEvents_10.cs` and `Source/Outlook/Events/InspectorEvents_10.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 130 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (12 lines × 2) Source/Outlook/Events/ExplorerEvents_10.cs:261 — Source/Outlook/Events/ExplorerEvents_10.cs:261-272 | Source/Outlook/Events/InspectorEvents_10.cs:151-162 — before extracting anything, compare `Source/Outlook/Events/ExplorerEvents_10.cs` and `Source/Outlook/Events/InspectorEvents_10.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 130 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (12 lines × 2) Source/Outlook/Events/ExplorerEvents_10.cs:276 — Source/Outlook/Events/ExplorerEvents_10.cs:276-287 | Source/Outlook/Events/InspectorEvents_10.cs:166-177 — before extracting anything, compare `Source/Outlook/Events/ExplorerEvents_10.cs` and `Source/Outlook/Events/InspectorEvents_10.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 130 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (12 lines × 2) Source/Outlook/Events/ItemEvents.cs:127 — Source/Outlook/Events/ItemEvents.cs:127-138 | Source/Outlook/Events/ItemEvents_10.cs:184-195 — before extracting anything, compare `Source/Outlook/Events/ItemEvents.cs` and `Source/Outlook/Events/ItemEvents_10.cs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 292 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (12 lines × 2) Source/Outlook/Events/ItemEvents.cs:192 — Source/Outlook/Events/ItemEvents.cs:192-203 | Source/Outlook/Events/ItemEvents_10.cs:249-260 — before extracting anything, compare `Source/Outlook/Events/ItemEvents.cs` and `Source/Outlook/Events/ItemEvents_10.cs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 292 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (12 lines × 2) Source/Outlook/Events/ItemEvents.cs:266 — Source/Outlook/Events/ItemEvents.cs:266-277 | Source/Outlook/Events/ItemEvents_10.cs:323-334 — before extracting anything, compare `Source/Outlook/Events/ItemEvents.cs` and `Source/Outlook/Events/ItemEvents_10.cs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 292 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (12 lines × 2) Source/Outlook/Events/ItemEvents.cs:281 — Source/Outlook/Events/ItemEvents.cs:281-292 | Source/Outlook/Events/ItemEvents_10.cs:338-349 — before extracting anything, compare `Source/Outlook/Events/ItemEvents.cs` and `Source/Outlook/Events/ItemEvents_10.cs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 292 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (12 lines × 2) Source/Outlook/Events/ItemEvents.cs:296 — Source/Outlook/Events/ItemEvents.cs:296-307 | Source/Outlook/Events/ItemEvents_10.cs:353-364 — before extracting anything, compare `Source/Outlook/Events/ItemEvents.cs` and `Source/Outlook/Events/ItemEvents_10.cs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 292 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (12 lines × 2) Source/Access/DispatchInterfaces/_Label.cs:1778 — Source/Access/DispatchInterfaces/_Label.cs:1778-1789 | Source/Access/DispatchInterfaces/_Line.cs:675-686 — before extracting anything, compare `Source/Access/DispatchInterfaces/_Label.cs` and `Source/Access/DispatchInterfaces/_Line.cs` as WHOLE FILES: 88% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (12 lines × 2) Source/Access/Events/_FormEvents.cs:360 — Source/Access/Events/_FormEvents.cs:360-371 | Source/Access/Events/_FormEvents2.cs:335-346 — before extracting anything, compare `Source/Access/Events/_FormEvents.cs` and `Source/Access/Events/_FormEvents2.cs` as WHOLE FILES: this scan already matched 72 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (12 lines × 2) Source/Access/Events/_FormEvents.cs:411 — Source/Access/Events/_FormEvents.cs:411-422 | Source/Access/Events/_FormEvents2.cs:387-398 — before extracting anything, compare `Source/Access/Events/_FormEvents.cs` and `Source/Access/Events/_FormEvents2.cs` as WHOLE FILES: this scan already matched 72 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (12 lines × 2) Source/Access/Events/_FormEvents.cs:443 — Source/Access/Events/_FormEvents.cs:443-454 | Source/Access/Events/_FormEvents2.cs:419-430 — before extracting anything, compare `Source/Access/Events/_FormEvents.cs` and `Source/Access/Events/_FormEvents2.cs` as WHOLE FILES: this scan already matched 72 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (12 lines × 2) Source/Access/Events/_FormEvents.cs:783 — Source/Access/Events/_FormEvents.cs:783-794 | Source/Access/Events/_FormEvents2.cs:760-771 — before extracting anything, compare `Source/Access/Events/_FormEvents.cs` and `Source/Access/Events/_FormEvents2.cs` as WHOLE FILES: this scan already matched 72 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (12 lines × 2) Source/Access/Events/_FormEvents.cs:798 — Source/Access/Events/_FormEvents.cs:798-809 | Source/Access/Events/_FormEvents2.cs:775-786 — before extracting anything, compare `Source/Access/Events/_FormEvents.cs` and `Source/Access/Events/_FormEvents2.cs` as WHOLE FILES: this scan already matched 72 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (12 lines × 2) Source/Access/Events/_FormEvents.cs:813 — Source/Access/Events/_FormEvents.cs:813-824 | Source/Access/Events/_FormEvents2.cs:790-801 — before extracting anything, compare `Source/Access/Events/_FormEvents.cs` and `Source/Access/Events/_FormEvents2.cs` as WHOLE FILES: this scan already matched 72 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (12 lines × 2) Source/Access/Events/_ReportEvents.cs:144 — Source/Access/Events/_ReportEvents.cs:144-155 | Source/Access/Events/_ReportEvents2.cs:241-252 — before extracting anything, compare `Source/Access/Events/_ReportEvents.cs` and `Source/Access/Events/_ReportEvents2.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 83 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (12 lines × 2) Source/MSComctlLib/Events/ITreeViewEvents.cs:171 — Source/MSComctlLib/Events/ITreeViewEvents.cs:171-182 | Source/MSComctlLib/Events/ListViewEvents.cs:166-177 — before extracting anything, compare `Source/MSComctlLib/Events/ITreeViewEvents.cs` and `Source/MSComctlLib/Events/ListViewEvents.cs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 319 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • + 5 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (27–30 lines × 2) · ×22
  • Duplicated block (27–30 lines × 2) Source/Excel/Classes/Workbook.cs:120 — Source/Excel/Classes/Workbook.cs:120-149 | Source/OWC10/DispatchInterfaces/Workbook.cs:182-208 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (27–30 lines × 2) Source/Excel/Classes/Worksheet.cs:97 — Source/Excel/Classes/Worksheet.cs:97-126 | Source/OWC10/DispatchInterfaces/Worksheet.cs:67-93 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (27–30 lines × 2) Source/Excel/DispatchInterfaces/Button.cs:195 — Source/Excel/DispatchInterfaces/Button.cs:195-221 | Source/MSComctlLib/Classes/Button.cs:75-104 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (27–30 lines × 2) Source/Excel/DispatchInterfaces/Buttons.cs:198 — Source/Excel/DispatchInterfaces/Buttons.cs:198-224 | Source/MSComctlLib/Classes/Buttons.cs:75-104 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (27–30 lines × 2) Source/Access/Classes/FormatCondition.cs:76 — Source/Access/Classes/FormatCondition.cs:76-105 | Source/Excel/DispatchInterfaces/FormatCondition.cs:68-94 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (27–30 lines × 2) Source/Access/Classes/Label.cs:85 — Source/Access/Classes/Label.cs:85-114 | Source/Excel/DispatchInterfaces/Label.cs:195-221 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (27–30 lines × 2) Source/Access/Classes/ListBox.cs:94 — Source/Access/Classes/ListBox.cs:94-123 | Source/Excel/DispatchInterfaces/ListBox.cs:218-244 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (27–30 lines × 2) Source/Access/Classes/OptionButton.cs:94 — Source/Access/Classes/OptionButton.cs:94-123 | Source/Excel/DispatchInterfaces/OptionButton.cs:194-220 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (27–30 lines × 2) Source/Excel/DispatchInterfaces/PivotTable.cs:309 — Source/Excel/DispatchInterfaces/PivotTable.cs:309-335 | Source/OWC10/Classes/PivotTable.cs:107-136 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (27–30 lines × 2) Source/Excel/DispatchInterfaces/Tab.cs:68 — Source/Excel/DispatchInterfaces/Tab.cs:68-94 | Source/MSComctlLib/Classes/Tab.cs:75-104 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (27–30 lines × 2) Source/Access/Classes/TextBox.cs:97 — Source/Access/Classes/TextBox.cs:97-126 | Source/Excel/DispatchInterfaces/TextBox.cs:194-220 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (27–30 lines × 2) Source/Excel/DispatchInterfaces/Toolbar.cs:67 — Source/Excel/DispatchInterfaces/Toolbar.cs:67-93 | Source/MSComctlLib/Classes/Toolbar.cs:93-122 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (27–30 lines × 2) Source/DAO/DispatchInterfaces/Document.cs:67 — Source/DAO/DispatchInterfaces/Document.cs:67-93 | Source/Word/Classes/Document.cs:94-123 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (27–30 lines × 2) Source/PowerPoint/DispatchInterfaces/ParagraphFormat.cs:68 — Source/PowerPoint/DispatchInterfaces/ParagraphFormat.cs:68-94 | Source/Word/Classes/ParagraphFormat.cs:76-105 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (27–30 lines × 2) Source/Outlook/Classes/Categories.cs:76 — Source/Outlook/Classes/Categories.cs:76-105 | Source/Word/DispatchInterfaces/Categories.cs:71-97 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (27–30 lines × 2) Source/Outlook/Classes/Category.cs:76 — Source/Outlook/Classes/Category.cs:76-105 | Source/Word/DispatchInterfaces/Category.cs:68-94 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (27–30 lines × 2) Source/DAO/Classes/Index.cs:75 — Source/DAO/Classes/Index.cs:75-104 | Source/Word/DispatchInterfaces/Index.cs:68-94 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (27–30 lines × 2) Source/Access/Classes/Attachment.cs:96 — Source/Access/Classes/Attachment.cs:96-125 | Source/Outlook/DispatchInterfaces/Attachment.cs:68-94 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (27–30 lines × 2) Source/Access/Classes/GroupLevel.cs:76 — Source/Access/Classes/GroupLevel.cs:76-105 | Source/OWC10/DispatchInterfaces/GroupLevel.cs:67-93 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (27–30 lines × 2) Source/Access/DispatchInterfaces/Controls.cs:71 — Source/Access/DispatchInterfaces/Controls.cs:71-97 | Source/MSComctlLib/Classes/Controls.cs:75-104 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (27–30 lines × 2) Source/ADODB/Classes/Connection.cs:87 — Source/ADODB/Classes/Connection.cs:87-116 | Source/DAO/DispatchInterfaces/Connection.cs:67-93 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (27–30 lines × 2) Source/ADODB/Classes/Recordset.cs:90 — Source/ADODB/Classes/Recordset.cs:90-119 | Source/DAO/DispatchInterfaces/Recordset.cs:67-93 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×22
  • Duplicated block (13 lines × 2) Source/NetOffice/Invoker.cs:172 — Source/NetOffice/Invoker.cs:172-184 | Source/NetOffice/Invoker.cs:981-993 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/NetOffice/Invoker.cs:172` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) Source/Access/Events/_FormEvents.cs:73 — Source/Access/Events/_FormEvents.cs:73-85 | Source/Access/Events/_ReportEvents.cs:24-36 — before extracting anything, compare `Source/Access/Events/_FormEvents.cs` and `Source/Access/Events/_ReportEvents.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 89 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (13 lines × 2) Source/Access/Events/_FormEvents.cs:243 — Source/Access/Events/_FormEvents.cs:243-255 | Source/Access/Events/_FormEvents2.cs:218-230 — before extracting anything, compare `Source/Access/Events/_FormEvents.cs` and `Source/Access/Events/_FormEvents2.cs` as WHOLE FILES: this scan already matched 72 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (13 lines × 2) Source/Access/Events/_FormEvents2.cs:75 — Source/Access/Events/_FormEvents2.cs:75-87 | Source/Access/Events/_ReportEvents2.cs:24-36 — before extracting anything, compare `Source/Access/Events/_FormEvents2.cs` and `Source/Access/Events/_ReportEvents2.cs` as WHOLE FILES: this scan already matched 45 separate duplicated blocks between them, totalling at least 418 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (13 lines × 2) Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsMultiAddinConverterCS.cs:89 — Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsMultiAddinConverterCS.cs:89-101 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsSingleAddinConverterCS.cs:89-101 — before extracting anything, compare `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsMultiAddinConverterCS.cs` and `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsSingleAddinConverterCS.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 112 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (13 lines × 2) Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsMultiAddinConverterCS.cs:132 — Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsMultiAddinConverterCS.cs:132-144 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsSingleAddinConverterCS.cs:117-129 — before extracting anything, compare `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsMultiAddinConverterCS.cs` and `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsSingleAddinConverterCS.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 112 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsMultiAddinConverterCS.cs:132` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (13 lines × 2) Source/Excel/Events/AppEvents.cs:349 — Source/Excel/Events/AppEvents.cs:349-361 | Source/Excel/Events/WorkbookEvents.cs:435-447 — before extracting anything, compare `Source/Excel/Events/AppEvents.cs` and `Source/Excel/Events/WorkbookEvents.cs` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 377 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (13 lines × 2) Source/Excel/Events/AppEvents.cs:648 — Source/Excel/Events/AppEvents.cs:648-660 | Source/Excel/Events/WorkbookEvents.cs:547-559 — before extracting anything, compare `Source/Excel/Events/AppEvents.cs` and `Source/Excel/Events/WorkbookEvents.cs` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 377 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (13 lines × 2) Source/Excel/Events/AppEvents.cs:664 — Source/Excel/Events/AppEvents.cs:664-676 | Source/Excel/Events/WorkbookEvents.cs:563-575 — before extracting anything, compare `Source/Excel/Events/AppEvents.cs` and `Source/Excel/Events/WorkbookEvents.cs` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 377 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (13 lines × 2) Source/Excel/Events/AppEvents.cs:1065 — Source/Excel/Events/AppEvents.cs:1065-1077 | Source/Excel/Events/WorkbookEvents.cs:857-869 — before extracting anything, compare `Source/Excel/Events/AppEvents.cs` and `Source/Excel/Events/WorkbookEvents.cs` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 377 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (13 lines × 2) Source/NetOffice/COMObject.cs:255 — Source/NetOffice/COMObject.cs:255-267 | Source/NetOffice/COMObject.cs:337-349 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/NetOffice/COMObject.cs:255` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) Source/Word/Events/ApplicationEvents3.cs:403 — Source/Word/Events/ApplicationEvents3.cs:403-415 | Source/Word/Events/ApplicationEvents4.cs:476-488 — before extracting anything, compare `Source/Word/Events/ApplicationEvents3.cs` and `Source/Word/Events/ApplicationEvents4.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 469 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (13 lines × 2) Source/Word/Events/ApplicationEvents3.cs:537 — Source/Word/Events/ApplicationEvents3.cs:537-549 | Source/Word/Events/ApplicationEvents4.cs:610-622 — before extracting anything, compare `Source/Word/Events/ApplicationEvents3.cs` and `Source/Word/Events/ApplicationEvents4.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 469 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (13 lines × 2) Source/Access/Events/_FormEvents.cs:995 — Source/Access/Events/_FormEvents.cs:995-1007 | Source/Access/Events/_FormEvents2.cs:874-886 — before extracting anything, compare `Source/Access/Events/_FormEvents.cs` and `Source/Access/Events/_FormEvents2.cs` as WHOLE FILES: this scan already matched 72 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (13 lines × 2) Source/Access/Events/_FormEvents.cs:1068 — Source/Access/Events/_FormEvents.cs:1068-1080 | Source/Access/Events/_FormEvents2.cs:947-959 — before extracting anything, compare `Source/Access/Events/_FormEvents.cs` and `Source/Access/Events/_FormEvents2.cs` as WHOLE FILES: this scan already matched 72 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (13 lines × 2) Source/Access/Events/_FormEvents.cs:1102 — Source/Access/Events/_FormEvents.cs:1102-1114 | Source/Access/Events/_FormEvents2.cs:981-993 — before extracting anything, compare `Source/Access/Events/_FormEvents.cs` and `Source/Access/Events/_FormEvents2.cs` as WHOLE FILES: this scan already matched 72 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (13 lines × 2) Source/OWC10/Events/IChartEvents.cs:229 — Source/OWC10/Events/IChartEvents.cs:229-241 | Source/OWC10/Events/IPivotControlEvents.cs:490-502 — before extracting anything, compare `Source/OWC10/Events/IChartEvents.cs` and `Source/OWC10/Events/IPivotControlEvents.cs` as WHOLE FILES: this scan already matched 39 separate duplicated blocks between them, totalling at least 404 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (13 lines × 2) Source/OWC10/Events/IChartEvents.cs:245 — Source/OWC10/Events/IChartEvents.cs:245-257 | Source/OWC10/Events/IPivotControlEvents.cs:506-518 — before extracting anything, compare `Source/OWC10/Events/IChartEvents.cs` and `Source/OWC10/Events/IPivotControlEvents.cs` as WHOLE FILES: this scan already matched 39 separate duplicated blocks between them, totalling at least 404 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (13 lines × 2) Source/OWC10/Events/IChartEvents.cs:414 — Source/OWC10/Events/IChartEvents.cs:414-426 | Source/OWC10/Events/IPivotControlEvents.cs:654-666 — before extracting anything, compare `Source/OWC10/Events/IChartEvents.cs` and `Source/OWC10/Events/IPivotControlEvents.cs` as WHOLE FILES: this scan already matched 39 separate duplicated blocks between them, totalling at least 404 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (13 lines × 2) Source/OWC10/Events/IPivotControlEvents.cs:474 — Source/OWC10/Events/IPivotControlEvents.cs:474-486 | Source/OWC10/Events/ISpreadsheetEventSink.cs:374-386 — before extracting anything, compare `Source/OWC10/Events/IPivotControlEvents.cs` and `Source/OWC10/Events/ISpreadsheetEventSink.cs` as WHOLE FILES: this scan already matched 36 separate duplicated blocks between them, totalling at least 344 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (13 lines × 2) Toolbox/Toolbox/ToolboxControls/ProjectWizard/Controls/GuiControl.cs:263 — Toolbox/Toolbox/ToolboxControls/ProjectWizard/Controls/GuiControl.cs:263-275 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/Controls/GuiControl.cs:279-291 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (13 lines × 2) BuildTools/VersionUpdater/Form1.cs:371 — BuildTools/VersionUpdater/Form1.cs:371-383 | BuildTools/VersionUpdater/Form1.cs:388-400 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `BuildTools/VersionUpdater/Form1.cs:371` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (8 lines × 3) · ×21
  • Duplicated block (8 lines × 3) Source/NetOffice/Invoker.cs:326 — Source/NetOffice/Invoker.cs:326-333 | Source/NetOffice/Invoker.cs:622-629 | Source/NetOffice/Invoker.cs:808-815 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/NetOffice/Invoker.cs:326` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (8 lines × 3) Source/NetOffice/Invoker.cs:427 — Source/NetOffice/Invoker.cs:427-434 | Source/NetOffice/Invoker.cs:723-730 | Source/NetOffice/Invoker.cs:958-965 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/NetOffice/Invoker.cs:427` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (8 lines × 3) Source/Outlook/Events/ApplicationEvents.cs:30 — Source/Outlook/Events/ApplicationEvents.cs:30-37 | Source/Outlook/Events/ApplicationEvents_10.cs:30-37 | Source/Outlook/Events/ApplicationEvents_11.cs:30-37 — before extracting anything, compare `Source/Outlook/Events/ApplicationEvents.cs` and `Source/Outlook/Events/ApplicationEvents_10.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 82 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (8 lines × 3) Source/Excel/DispatchInterfaces/XmlMap.cs:472 — Source/Excel/DispatchInterfaces/XmlMap.cs:472-479 | Source/Excel/Interfaces/IWorkbookQuery.cs:301-308 | Source/Excel/Interfaces/IXmlMap.cs:447-454 — before extracting anything, compare `Source/Excel/DispatchInterfaces/XmlMap.cs` and `Source/Excel/Interfaces/IXmlMap.cs` as WHOLE FILES: 91% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (8 lines × 3) Source/MSComctlLib/Events/DImageComboEvents.cs:27 — Source/MSComctlLib/Events/DImageComboEvents.cs:27-34 | Source/MSComctlLib/Events/ISliderEvents.cs:19-26 | Source/MSComctlLib/Events/ITabStripEvents.cs:19-26 — before extracting anything, compare `Source/MSComctlLib/Events/DImageComboEvents.cs` and `Source/MSComctlLib/Events/ISliderEvents.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 192 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (8 lines × 3) Source/Excel/Events/AppEvents.cs:751 — Source/Excel/Events/AppEvents.cs:751-758 | Source/Excel/Events/AppEvents.cs:771-778 | Source/Excel/Events/AppEvents.cs:792-799 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (8 lines × 3) Source/Excel/Events/AppEvents.cs:914 — Source/Excel/Events/AppEvents.cs:914-921 | Source/Excel/Events/DocEvents.cs:283-290 | Source/Excel/Events/DocEvents.cs:304-311 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Excel/Events/AppEvents.cs:913` calls `CreateEventArgumentObjectFromComProxy` and `Source/Excel/Events/DocEvents.cs:281` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (8 lines × 3) Source/NetOffice/Invoker.cs:472 — Source/NetOffice/Invoker.cs:472-482 | Source/NetOffice/Invoker.cs:504-511 | Source/NetOffice/Invoker.cs:579-589 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/NetOffice/Invoker.cs:472` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (8 lines × 3) Source/Excel/DispatchInterfaces/ModelTableNames.cs:235 — Source/Excel/DispatchInterfaces/ModelTableNames.cs:235-242 | Source/Excel/Interfaces/IModelTableNames.cs:228-235 | Source/Office/DispatchInterfaces/AnswerWizardFiles.cs:224-231 — before extracting anything, compare `Source/Excel/DispatchInterfaces/ModelTableNames.cs` and `Source/Excel/Interfaces/IModelTableNames.cs` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (8 lines × 3) Source/Excel/Events/WorkbookEvents.cs:277 — Source/Excel/Events/WorkbookEvents.cs:277-284 | Source/Word/Events/DocumentEvents.cs:70-77 | Source/Word/Events/DocumentEvents2.cs:132-139 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (8 lines × 3) Source/Word/Events/ApplicationEvents2.cs:139 — Source/Word/Events/ApplicationEvents2.cs:139-146 | Source/Word/Events/ApplicationEvents3.cs:204-211 | Source/Word/Events/ApplicationEvents4.cs:277-284 — before extracting anything, compare `Source/Word/Events/ApplicationEvents2.cs` and `Source/Word/Events/ApplicationEvents3.cs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 270 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (8 lines × 3) Source/Outlook/Events/ApplicationEvents.cs:92 — Source/Outlook/Events/ApplicationEvents.cs:92-99 | Source/Outlook/Events/ApplicationEvents_10.cs:106-113 | Source/Outlook/Events/ApplicationEvents_11.cs:163-170 — before extracting anything, compare `Source/Outlook/Events/ApplicationEvents.cs` and `Source/Outlook/Events/ApplicationEvents_10.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 82 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (8 lines × 3) Source/Access/Events/_FormEvents.cs:338 — Source/Access/Events/_FormEvents.cs:338-345 | Source/Access/Events/_FormEvents2.cs:313-320 | Source/Access/Events/_ReportEvents2.cs:278-285 — before extracting anything, compare `Source/Access/Events/_FormEvents.cs` and `Source/Access/Events/_FormEvents2.cs` as WHOLE FILES: this scan already matched 72 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (8 lines × 3) Source/Access/Events/_FormEvents.cs:349 — Source/Access/Events/_FormEvents.cs:349-356 | Source/Access/Events/_FormEvents2.cs:324-331 | Source/Access/Events/_ReportEvents2.cs:267-274 — before extracting anything, compare `Source/Access/Events/_FormEvents.cs` and `Source/Access/Events/_FormEvents2.cs` as WHOLE FILES: this scan already matched 72 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (8 lines × 3) Source/Access/Events/_FormEvents.cs:708 — Source/Access/Events/_FormEvents.cs:708-715 | Source/Access/Events/_FormEvents2.cs:684-692 | Source/Access/Events/_ReportEvents2.cs:474-482 — before extracting anything, compare `Source/Access/Events/_FormEvents.cs` and `Source/Access/Events/_FormEvents2.cs` as WHOLE FILES: this scan already matched 72 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (8 lines × 3) Source/Access/Events/_FormEvents.cs:927 — Source/Access/Events/_FormEvents.cs:927-934 | Source/Access/Events/_FormEvents2.cs:805-812 | Source/OWC10/Events/IPivotControlEvents.cs:290-297 — before extracting anything, compare `Source/Access/Events/_FormEvents.cs` and `Source/Access/Events/_FormEvents2.cs` as WHOLE FILES: this scan already matched 72 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (8 lines × 3) Source/Access/Events/_FormEvents.cs:938 — Source/Access/Events/_FormEvents.cs:938-945 | Source/Access/Events/_FormEvents2.cs:816-823 | Source/OWC10/Events/IPivotControlEvents.cs:301-308 — before extracting anything, compare `Source/Access/Events/_FormEvents.cs` and `Source/Access/Events/_FormEvents2.cs` as WHOLE FILES: this scan already matched 72 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (8 lines × 3) Source/Access/Events/_FormEvents.cs:962 — Source/Access/Events/_FormEvents.cs:962-969 | Source/Access/Events/_FormEvents2.cs:841-848 | Source/OWC10/Events/IPivotControlEvents.cs:279-286 — before extracting anything, compare `Source/Access/Events/_FormEvents.cs` and `Source/Access/Events/_FormEvents2.cs` as WHOLE FILES: this scan already matched 72 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (8 lines × 3) Source/Access/Events/_FormEvents.cs:973 — Source/Access/Events/_FormEvents.cs:973-980 | Source/Access/Events/_FormEvents2.cs:852-859 | Source/OWC10/Events/IPivotControlEvents.cs:268-275 — before extracting anything, compare `Source/Access/Events/_FormEvents.cs` and `Source/Access/Events/_FormEvents2.cs` as WHOLE FILES: this scan already matched 72 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (8 lines × 3) Source/Access/Events/_FormEvents.cs:1057 — Source/Access/Events/_FormEvents.cs:1057-1064 | Source/Access/Events/_FormEvents2.cs:936-943 | Source/OWC10/Events/IChartEvents.cs:196-203 — before extracting anything, compare `Source/Access/Events/_FormEvents.cs` and `Source/Access/Events/_FormEvents2.cs` as WHOLE FILES: this scan already matched 72 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (8 lines × 3) Examples/Outlook/Automation/FormMain.cs:18 — Examples/Outlook/Automation/FormMain.cs:18-25 | Examples/PowerPoint/Automation/FormMain.cs:18-25 | Examples/Word/Automation/FormMain.cs:26-33 — before extracting anything, compare `Examples/Outlook/Automation/FormMain.cs` and `Examples/PowerPoint/Automation/FormMain.cs` as WHOLE FILES: 88% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×21
  • Duplicated block (7 lines × 2) Source/NetOffice/Extensions/EnumerableExtensions.cs:74 — Source/NetOffice/Extensions/EnumerableExtensions.cs:74-80 | Source/NetOffice/Extensions/EnumerableExtensions.cs:152-158 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (7 lines × 2) Source/Access/Events/_FormEvents.cs:143 — Source/Access/Events/_FormEvents.cs:143-149 | Source/Access/Events/_ReportEvents.cs:36-42 — before extracting anything, compare `Source/Access/Events/_FormEvents.cs` and `Source/Access/Events/_ReportEvents.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 89 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (7 lines × 2) Source/Access/Events/_FormEvents2.cs:145 — Source/Access/Events/_FormEvents2.cs:145-151 | Source/Access/Events/_ReportEvents2.cs:36-42 — before extracting anything, compare `Source/Access/Events/_FormEvents2.cs` and `Source/Access/Events/_ReportEvents2.cs` as WHOLE FILES: this scan already matched 45 separate duplicated blocks between them, totalling at least 418 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (7 lines × 2) Source/Excel/Events/AppEvents.cs:523 — Source/Excel/Events/AppEvents.cs:523-529 | Source/Excel/Events/AppEvents.cs:1022-1028 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/Excel/Events/AppEvents.cs:523` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (7 lines × 2) Source/Excel/Events/AppEvents.cs:887 — Source/Excel/Events/AppEvents.cs:887-893 | Source/Excel/Events/AppEvents.cs:910-916 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/Excel/Events/AppEvents.cs:887` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (7 lines × 2) RegAddin/RegAddin/Common/AddinRegAnalyzer.cs:41 — RegAddin/RegAddin/Common/AddinRegAnalyzer.cs:41-47 | RegAddin/RegAddin/Common/AddinRegAnalyzer.cs:86-92 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) Source/Office/Interfaces/IConverterApplicationPreferences.cs:172 — Source/Office/Interfaces/IConverterApplicationPreferences.cs:172-178 | Source/Office/Interfaces/IConverterPreferences.cs:140-146 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (7 lines × 2) Source/Access/DispatchInterfaces/Module.cs:292 — Source/Access/DispatchInterfaces/Module.cs:292-298 | Source/VBIDE/DispatchInterfaces/_CodeModule.cs:277-283 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (7 lines × 2) Source/Excel/Events/AppEvents.cs:77 — Source/Excel/Events/AppEvents.cs:77-83 | Source/Excel/Events/AppEvents.cs:90-96 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (7 lines × 2) Source/Excel/Events/AppEvents.cs:163 — Source/Excel/Events/AppEvents.cs:163-169 | Source/Excel/Events/WorkbookEvents.cs:143-149 — before extracting anything, compare `Source/Excel/Events/AppEvents.cs` and `Source/Excel/Events/WorkbookEvents.cs` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 377 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (7 lines × 2) Source/Excel/Events/AppEvents.cs:758 — Source/Excel/Events/AppEvents.cs:758-764 | Source/Excel/Events/WorkbookEvents.cs:648-654 — before extracting anything, compare `Source/Excel/Events/AppEvents.cs` and `Source/Excel/Events/WorkbookEvents.cs` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 377 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (7 lines × 2) Source/Excel/Events/AppEvents.cs:799 — Source/Excel/Events/AppEvents.cs:799-805 | Source/Excel/Events/WorkbookEvents.cs:685-691 — before extracting anything, compare `Source/Excel/Events/AppEvents.cs` and `Source/Excel/Events/WorkbookEvents.cs` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 377 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (7 lines × 2) Source/Excel/Events/WorkbookEvents.cs:156 — Source/Excel/Events/WorkbookEvents.cs:156-162 | Source/Excel/Events/WorkbookEvents.cs:163-169 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (7 lines × 2) Source/Office/DispatchInterfaces/IBlogExtensibility.cs:171 — Source/Office/DispatchInterfaces/IBlogExtensibility.cs:171-177 | Source/Office/DispatchInterfaces/IBlogExtensibility.cs:195-201 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/Office/DispatchInterfaces/IBlogExtensibility.cs:171` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) Source/Outlook/Events/ExplorerEvents.cs:27 — Source/Outlook/Events/ExplorerEvents.cs:27-33 | Source/Outlook/Events/ExplorerEvents_10.cs:27-33 — before extracting anything, compare `Source/Outlook/Events/ExplorerEvents.cs` and `Source/Outlook/Events/ExplorerEvents_10.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 100 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (7 lines × 2) Source/Access/Events/DispComboBoxEvents.cs:32 — Source/Access/Events/DispComboBoxEvents.cs:32-38 | Source/Access/Events/_ComboBoxEvents.cs:32-38 — before extracting anything, compare `Source/Access/Events/DispComboBoxEvents.cs` and `Source/Access/Events/_ComboBoxEvents.cs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 263 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (7 lines × 2) Source/OWC10/Events/ISpreadsheetEventSink.cs:119 — Source/OWC10/Events/ISpreadsheetEventSink.cs:119-125 | Source/OWC10/Events/ISpreadsheetEventSink.cs:126-132 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (7 lines × 2) Source/OWC10/Events/ISpreadsheetEventSink.cs:167 — Source/OWC10/Events/ISpreadsheetEventSink.cs:167-173 | Source/OWC10/Events/ISpreadsheetEventSink.cs:178-184 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (7 lines × 2) RegAddin/RegAddin/Commands.cs:221 — RegAddin/RegAddin/Commands.cs:221-227 | RegAddin/RegAddin/Commands.cs:228-234 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (7 lines × 2) Source/ADODB/Events/ConnectionEvents.cs:200 — Source/ADODB/Events/ConnectionEvents.cs:200-206 | Source/ADODB/Events/ConnectionEvents.cs:229-235 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Source/ADODB/Events/ConnectionEvents.cs:206` calls `SetValue` and `Source/ADODB/Events/ConnectionEvents.cs:235` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (7 lines × 2) Examples/Excel/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:194 — Examples/Excel/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:194-200 | Examples/PowerPoint/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:187-193 — before extracting anything, compare `Examples/Excel/IExtensibility COMAddin Examples/ClassicUI/Addin.cs` and `Examples/PowerPoint/IExtensibility COMAddin Examples/ClassicUI/Addin.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 91 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Examples/Excel/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:194` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
X20 · Mistyped argument guard · Argument guard throws the exception its own condition disproves · ×20
  • Argument guard throws the exception its own condition disproves Source/NetOffice/COMObject.cs:492 — The guard on line 491 rejects `progId` and line 492 reports that rejection as `ArgumentNullException` — but the condition's own test `String.IsNullOrEmpty(progId)` is true of a value that is NOT null: it is satisfied by an EMPTY `progId`, and on that path `progId` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves Source/NetOffice/COMObject.cs:513 — The guard on line 512 rejects `progId` and line 513 reports that rejection as `ArgumentNullException` — but the condition's own test `String.IsNullOrEmpty(progId)` is true of a value that is NOT null: it is satisfied by an EMPTY `progId`, and on that path `progId` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves Source/NetOffice/Loader/DependentAssembly.cs:19 — The guard on line 18 rejects `name` and line 19 reports that rejection as `ArgumentNullException` — but the condition's own test `String.IsNullOrWhiteSpace(name)` is true of a value that is NOT null: it is satisfied by an EMPTY `name`, and on that path `name` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves Source/NetOffice/Running/RunningObjectTable.cs:205 — The guard on line 204 rejects `componentName` and line 205 reports that rejection as `ArgumentNullException` — but the condition's own test `String.IsNullOrEmpty(componentName)` is true of a value that is NOT null: it is satisfied by an EMPTY `componentName`, and on that path `componentName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves Source/NetOffice/Running/RunningObjectTable.cs:207 — The guard on line 206 rejects `className` and line 207 reports that rejection as `ArgumentNullException` — but the condition's own test `String.IsNullOrEmpty(className)` is true of a value that is NOT null: it is satisfied by an EMPTY `className`, and on that path `className` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves Source/NetOffice/Tools/CustomUIAttribute.cs:105 — The guard on line 104 rejects `resourcePath` and line 105 reports that rejection as `ArgumentNullException` — but the condition's own test `String.IsNullOrEmpty(resourcePath)` is true of a value that is NOT null: it is satisfied by an EMPTY `resourcePath`, and on that path `resourcePath` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves Source/NetOffice/Tools/CustomUIAttribute.cs:107 — The guard on line 106 rejects `assemblyNamespace` and line 107 reports that rejection as `ArgumentNullException` — but the condition's own test `String.IsNullOrEmpty(assemblyNamespace)` is true of a value that is NOT null: it is satisfied by an EMPTY `assemblyNamespace`, and on that path `assemblyNamespace` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves Source/NetOffice/Tools/Native/Bridge/CdeclHandle.cs:32 — The guard on line 31 rejects `name` and line 32 reports that rejection as `ArgumentNullException` — but the condition's own test `String.IsNullOrWhiteSpace(name)` is true of a value that is NOT null: it is satisfied by an EMPTY `name`, and on that path `name` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves Source/NetOffice/Tools/Native/Bridge/CdeclHandle.cs:97 — The guard on line 96 rejects `name` and line 97 reports that rejection as `ArgumentNullException` — but the condition's own test `String.IsNullOrWhiteSpace(name)` is true of a value that is NOT null: it is satisfied by an EMPTY `name`, and on that path `name` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves Source/NetOffice/Tools/Native/Bridge/CdeclHandle.cs:134 — The guard on line 133 rejects `fullFileName` and line 134 reports that rejection as `ArgumentNullException` — but the condition's own test `String.IsNullOrWhiteSpace(fullFileName)` is true of a value that is NOT null: it is satisfied by an EMPTY `fullFileName`, and on that path `fullFileName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves Source/NetOffice/Tools/Native/Bridge/CdeclHandle.cs:193 — The guard on line 192 rejects `fileName` and line 193 reports that rejection as `ArgumentNullException` — but the condition's own test `String.IsNullOrWhiteSpace(fileName)` is true of a value that is NOT null: it is satisfied by an EMPTY `fileName`, and on that path `fileName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves Source/NetOffice/Trace/PerformanceTrace.cs:185 — The guard on line 184 rejects `componentName` and line 185 reports that rejection as `ArgumentNullException` — but the condition's own test `String.IsNullOrWhiteSpace(componentName)` is true of a value that is NOT null: it is satisfied by an EMPTY `componentName`, and on that path `componentName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves Source/NetOffice/Trace/PerformanceTrace.cs:213 — The guard on line 212 rejects `componentName` and line 213 reports that rejection as `ArgumentNullException` — but the condition's own test `String.IsNullOrWhiteSpace(componentName)` is true of a value that is NOT null: it is satisfied by an EMPTY `componentName`, and on that path `componentName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves Source/NetOffice/Trace/PerformanceTrace.cs:215 — The guard on line 214 rejects `entityName` and line 215 reports that rejection as `ArgumentNullException` — but the condition's own test `String.IsNullOrWhiteSpace(entityName)` is true of a value that is NOT null: it is satisfied by an EMPTY `entityName`, and on that path `entityName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves Source/NetOffice/Trace/PerformanceTrace.cs:244 — The guard on line 243 rejects `componentName` and line 244 reports that rejection as `ArgumentNullException` — but the condition's own test `String.IsNullOrWhiteSpace(componentName)` is true of a value that is NOT null: it is satisfied by an EMPTY `componentName`, and on that path `componentName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves Source/NetOffice/Trace/PerformanceTrace.cs:246 — The guard on line 245 rejects `entityName` and line 246 reports that rejection as `ArgumentNullException` — but the condition's own test `String.IsNullOrWhiteSpace(entityName)` is true of a value that is NOT null: it is satisfied by an EMPTY `entityName`, and on that path `entityName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves Source/NetOffice/Trace/PerformanceTrace.cs:248 — The guard on line 247 rejects `methodName` and line 248 reports that rejection as `ArgumentNullException` — but the condition's own test `String.IsNullOrWhiteSpace(methodName)` is true of a value that is NOT null: it is satisfied by an EMPTY `methodName`, and on that path `methodName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves Source/Outlook/Tools/OlCustomUIAttribute.cs:114 — The guard on line 113 rejects `resourcePath` and line 114 reports that rejection as `ArgumentNullException` — but the condition's own test `String.IsNullOrEmpty(resourcePath)` is true of a value that is NOT null: it is satisfied by an EMPTY `resourcePath`, and on that path `resourcePath` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves Source/Outlook/Tools/OlCustomUIAttribute.cs:116 — The guard on line 115 rejects `assemblyNamespace` and line 116 reports that rejection as `ArgumentNullException` — but the condition's own test `String.IsNullOrEmpty(assemblyNamespace)` is true of a value that is NOT null: it is satisfied by an EMPTY `assemblyNamespace`, and on that path `assemblyNamespace` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves Toolbox/Toolbox/Program.cs:301 — The guard on line 300 rejects `assemblyFullPath` and line 301 reports that rejection as `ArgumentNullException` — but the condition's own test `String.IsNullOrWhiteSpace(assemblyFullPath)` is true of a value that is NOT null: it is satisfied by an EMPTY `assemblyFullPath`, and on that path `assemblyFullPath` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
D4 · Code Duplication · Duplicated block (6 lines × 3) · ×18
  • Duplicated block (6 lines × 3) Source/Excel/Events/ChartEvents.cs:20 — Source/Excel/Events/ChartEvents.cs:20-25 | Source/Excel/Events/DocEvents.cs:37-42 | Source/Excel/Events/WorkbookEvents.cs:24-29 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
  • Duplicated block (6 lines × 3) Source/Excel/Events/ChartEvents.cs:48 — Source/Excel/Events/ChartEvents.cs:48-53 | Source/OWC10/Events/IChartEvents.cs:77-82 | Source/OWC10/Events/IPivotControlEvents.cs:63-68 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (6 lines × 3) Source/Excel/Events/DocEvents.cs:280 — Source/Excel/Events/DocEvents.cs:280-285 | Source/Excel/Events/DocEvents.cs:301-306 | Source/Excel/Events/DocEvents.cs:322-327 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/Excel/Events/DocEvents.cs:280` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (6 lines × 3) Source/Access/Events/_BoundObjectFrameEvents.cs:19 — Source/Access/Events/_BoundObjectFrameEvents.cs:19-24 | Source/Access/Events/_CustomControlEvents.cs:19-24 | Source/Access/Events/_ObjectFrameEvents.cs:19-24 — before extracting anything, compare `Source/Access/Events/_BoundObjectFrameEvents.cs` and `Source/Access/Events/_CustomControlEvents.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 69 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Source/Access/Events/_ObjectFrameEvents.cs:25` calls `MethodImpl`, `DispId`, `Enter` and `Source/Access/Events/_BoundObjectFrameEvents.cs:25` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (6 lines × 3) RegAddin/RegAddin/Common/AddinRegAnalyzer.cs:67 — RegAddin/RegAddin/Common/AddinRegAnalyzer.cs:67-72 | RegAddin/RegAddin/Common/AddinRegAnalyzer.cs:115-120 | RegAddin/RegAddin/RegFile/RegFileOperationHost.cs:297-302 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `RegAddin/RegAddin/Common/AddinRegAnalyzer.cs:67` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 3) Source/OWC10/Events/IChartEvents.cs:318 — Source/OWC10/Events/IChartEvents.cs:318-323 | Source/OWC10/Events/IPivotControlEvents.cs:579-584 | Source/OWC10/Events/ISpreadsheetEventSink.cs:290-295 — before extracting anything, compare `Source/OWC10/Events/IChartEvents.cs` and `Source/OWC10/Events/IPivotControlEvents.cs` as WHOLE FILES: this scan already matched 39 separate duplicated blocks between them, totalling at least 404 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Source/OWC10/Events/IChartEvents.cs:318` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 3) Source/Excel/Events/AppEvents.cs:41 — Source/Excel/Events/AppEvents.cs:41-46 | Source/Excel/Events/WorkbookEvents.cs:45-50 | Source/Excel/Events/WorkbookEvents.cs:93-98 — before extracting anything, compare `Source/Excel/Events/AppEvents.cs` and `Source/Excel/Events/WorkbookEvents.cs` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 377 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (6 lines × 3) Source/Excel/Events/AppEvents.cs:112 — Source/Excel/Events/AppEvents.cs:112-117 | Source/Excel/Events/AppEvents.cs:118-123 | Source/Excel/Events/AppEvents.cs:124-129 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (6 lines × 3) Source/Word/Events/ApplicationEvents3.cs:34 — Source/Word/Events/ApplicationEvents3.cs:34-39 | Source/Word/Events/ApplicationEvents3.cs:40-45 | Source/Word/Events/ApplicationEvents3.cs:116-121 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (6 lines × 3) Source/Word/Events/ApplicationEvents3.cs:58 — Source/Word/Events/ApplicationEvents3.cs:58-63 | Source/Word/Events/ApplicationEvents3.cs:64-69 | Source/Word/Events/ApplicationEvents3.cs:146-151 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (6 lines × 3) Source/Word/Events/ApplicationEvents3.cs:53 — Source/Word/Events/ApplicationEvents3.cs:53-58 | Source/Word/Events/ApplicationEvents3.cs:87-92 | Source/Word/Events/ApplicationEvents3.cs:122-127 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (6 lines × 3) Source/PowerPoint/Events/EApplication.cs:31 — Source/PowerPoint/Events/EApplication.cs:31-36 | Source/Word/Events/ApplicationEvents3.cs:84-89 | Source/Word/Events/ApplicationEvents4.cs:84-89 — before extracting anything, compare `Source/Word/Events/ApplicationEvents3.cs` and `Source/Word/Events/ApplicationEvents4.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 469 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (6 lines × 3) Source/Word/Events/ApplicationEvents4.cs:34 — Source/Word/Events/ApplicationEvents4.cs:34-39 | Source/Word/Events/ApplicationEvents4.cs:40-45 | Source/Word/Events/ApplicationEvents4.cs:116-121 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (6 lines × 3) Source/Word/Events/ApplicationEvents4.cs:58 — Source/Word/Events/ApplicationEvents4.cs:58-63 | Source/Word/Events/ApplicationEvents4.cs:64-69 | Source/Word/Events/ApplicationEvents4.cs:146-151 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (6 lines × 3) Source/Word/Events/ApplicationEvents4.cs:53 — Source/Word/Events/ApplicationEvents4.cs:53-58 | Source/Word/Events/ApplicationEvents4.cs:87-92 | Source/Word/Events/ApplicationEvents4.cs:122-127 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (6 lines × 3) Source/Access/Events/DispPageHdrFtrInReportEvents.cs:27 — Source/Access/Events/DispPageHdrFtrInReportEvents.cs:27-32 | Source/Access/Events/DispSectionInReportEvents.cs:27-32 | Source/Access/Events/_PageHdrFtrInReportEvents.cs:27-32 — before extracting anything, compare `Source/Access/Events/DispPageHdrFtrInReportEvents.cs` and `Source/Access/Events/DispSectionInReportEvents.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 179 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Source/Access/Events/DispSectionInReportEvents.cs:32` calls `MethodImpl`, `DispId`, `Retreat` and `Source/Access/Events/DispPageHdrFtrInReportEvents.cs:32` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (6 lines × 3) Source/Access/Events/_FormEvents.cs:68 — Source/Access/Events/_FormEvents.cs:68-73 | Source/Access/Events/_FormEvents2.cs:70-75 | Source/Access/Events/_ReportEvents2.cs:63-68 — before extracting anything, compare `Source/Access/Events/_FormEvents.cs` and `Source/Access/Events/_FormEvents2.cs` as WHOLE FILES: this scan already matched 72 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (6 lines × 3) RegAddin/RegAddin/Commands.cs:212 — RegAddin/RegAddin/Commands.cs:212-217 | RegAddin/RegAddin/Commands.cs:220-225 | RegAddin/RegAddin/Commands.cs:227-232 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `RegAddin/RegAddin/Commands.cs:217` calls `Add`, `CommandSyntax` and `RegAddin/RegAddin/Commands.cs:225` does not — after which the two agree again for 5 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×17
  • Members sharing a duplicated core (4 members, 50+ identical tokens) Source/Excel/Events/AppEvents.cs:926 — Source/Excel/Events/AppEvents.cs:926-937 | Source/Excel/Events/AppEvents.cs:976-987 | Source/Excel/Events/AppEvents.cs:990-1001 | Source/Excel/Events/AppEvents.cs:1004-1015 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) Source/Excel/Events/DocEvents.cs:246 — Source/Excel/Events/DocEvents.cs:246-257 | Source/Excel/Events/DocEvents.cs:336-347 | Source/Excel/Events/WorkbookEvents.cs:578-589 | Source/Excel/Events/WorkbookEvents.cs:592-603 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) Source/Access/Tools/COMAddin.cs:438 — Source/Access/Tools/COMAddin.cs:438-453 | Source/Excel/Tools/COMAddin.cs:437-452 | Source/PowerPoint/Tools/COMAddin.cs:439-454 | Source/Word/Tools/COMAddin.cs:440-455 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) Source/Excel/Tools/RealtimeDataServer.cs:385 — Source/Excel/Tools/RealtimeDataServer.cs:385-413 | Source/Excel/Tools/RealtimeDataServer.cs:416-444 | Source/NetOffice/Tools/COMAddinRegisterHandler.cs:161-197 | Source/NetOffice/Tools/COMAddinUnRegisterHandler.cs:102-138 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) Source/Office/Tools/COMAddin.cs:1036 — Source/Office/Tools/COMAddin.cs:1036-1051 | Source/Office/Tools/COMAddin.cs:1059-1074 | Source/Office/Tools/COMAddin.cs:1084-1097 | Source/Office/Tools/COMAddin.cs:1107-1120 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) Source/VBIDE/Events/_dispReferencesEvents.cs:56 — Source/VBIDE/Events/_dispReferencesEvents.cs:56-67 | Source/VBIDE/Events/_dispReferencesEvents.cs:70-81 | Source/VBIDE/Events/_dispReferences_Events.cs:56-67 | Source/VBIDE/Events/_dispReferences_Events.cs:70-81 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) Source/NetOffice/Extensions/EnumerableExtensions.cs:184 — Source/NetOffice/Extensions/EnumerableExtensions.cs:184-217 | Source/NetOffice/Extensions/EnumerableExtensions.cs:231-266 | Source/NetOffice/Extensions/EnumerableExtensions.cs:278-311 | Source/NetOffice/Extensions/EnumerableExtensions.cs:324-359 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) Source/NetOffice/Utils.cs:205 — Source/NetOffice/Utils.cs:205-224 | Source/NetOffice/Utils.cs:232-251 | Source/NetOffice/Utils.cs:259-277 | Source/NetOffice/Utils.cs:285-303 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) Source/Word/Events/ApplicationEvents4.cs:728 — Source/Word/Events/ApplicationEvents4.cs:728-739 | Source/Word/Events/ApplicationEvents4.cs:778-789 | Source/Word/Events/ApplicationEvents4.cs:792-803 | Source/Word/Events/ApplicationEvents4.cs:806-817 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) Source/Outlook/Events/ApplicationEvents_10.cs:165 — Source/Outlook/Events/ApplicationEvents_10.cs:165-176 | Source/Outlook/Events/ApplicationEvents_10.cs:179-190 | Source/Outlook/Events/ApplicationEvents_11.cs:222-233 | Source/Outlook/Events/ApplicationEvents_11.cs:236-247 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) Source/Access/Events/DispPageHdrFtrInReportEvents.cs:95 — Source/Access/Events/DispPageHdrFtrInReportEvents.cs:95-109 | Source/Access/Events/DispSectionInReportEvents.cs:99-113 | Source/Access/Events/_PageHdrFtrInReportEvents.cs:91-105 | Source/Access/Events/_SectionInReportEvents.cs:99-113 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) Source/Access/Events/DispPageHdrFtrInReportEvents.cs:112 — Source/Access/Events/DispPageHdrFtrInReportEvents.cs:112-126 | Source/Access/Events/DispSectionInReportEvents.cs:116-130 | Source/Access/Events/_PageHdrFtrInReportEvents.cs:108-122 | Source/Access/Events/_SectionInReportEvents.cs:116-130 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) Source/Access/Events/_FormEvents.cs:457 — Source/Access/Events/_FormEvents.cs:457-469 | Source/Access/Events/_FormEvents2.cs:433-445 | Source/Access/Events/_ReportEvents.cs:78-90 | Source/Access/Events/_ReportEvents2.cs:175-187 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) Source/Access/Events/_FormEvents.cs:691 — Source/Access/Events/_FormEvents.cs:691-705 | Source/Access/Events/_FormEvents2.cs:667-681 | Source/Access/Events/_ReportEvents.cs:126-140 | Source/Access/Events/_ReportEvents2.cs:223-237 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) Source/Access/Events/_FormEvents.cs:1067 — Source/Access/Events/_FormEvents.cs:1067-1080 | Source/Access/Events/_FormEvents.cs:1101-1114 | Source/Access/Events/_FormEvents2.cs:946-959 | Source/Access/Events/_FormEvents2.cs:980-993 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) Source/MSComctlLib/Events/ITreeViewEvents.cs:202 — Source/MSComctlLib/Events/ITreeViewEvents.cs:202-213 | Source/MSComctlLib/Events/ITreeViewEvents.cs:216-227 | Source/MSComctlLib/Events/ITreeViewEvents.cs:230-241 | Source/MSComctlLib/Events/ITreeViewEvents.cs:374-385 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) Examples/Excel/Automation/Examples/Example01.cs:17 — Examples/Excel/Automation/Examples/Example01.cs:17-51 | Examples/Excel/Automation/Examples/Example02.cs:16-98 | Examples/Excel/Automation/Examples/Example04.cs:16-56 | Examples/Excel/Automation/Examples/Example10.cs:18-62 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Edited copy of a member (12 corresponding lines) · ×17
  • Edited copy of a member (12 corresponding lines) Source/Office/Tools/Informations/AssemblyInfo.cs:187 — Source/Office/Tools/Informations/AssemblyInfo.cs:187-199 | Source/Office/Tools/Informations/EnvironmentInfo.cs:124-135 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) Source/OWC10/DispatchInterfaces/IDataSourceControl.cs:1124 — Source/OWC10/DispatchInterfaces/IDataSourceControl.cs:1124-1136 | Source/OWC10/Interfaces/FieldListHierarchySite.cs:187-198 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) Source/NetOffice/Contribution/Controls/InstanceMonitor.cs:202 — Source/NetOffice/Contribution/Controls/InstanceMonitor.cs:202-213 | Source/Office.Extensions/TrayMenuUtils/TrayMenuMonitorItemControl.cs:261-272 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) Source/Access/Events/_References_Events.cs:56 — Source/Access/Events/_References_Events.cs:56-67 | Source/Access/Events/_References_Events.cs:70-81 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) Source/NetOffice/Tools/CodebaseAttribute.cs:90 — Source/NetOffice/Tools/CodebaseAttribute.cs:90-101 | Source/NetOffice/Tools/CodebaseAttribute.cs:111-122 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) Source/MSComctlLib/Events/IStatusBarEvents.cs:132 — Source/MSComctlLib/Events/IStatusBarEvents.cs:132-143 | Source/MSComctlLib/Events/IStatusBarEvents.cs:146-157 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) Source/MSComctlLib/Events/IToolbarEvents.cs:141 — Source/MSComctlLib/Events/IToolbarEvents.cs:141-152 | Source/MSComctlLib/Events/IToolbarEvents.cs:400-411 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) Source/MSComctlLib/Events/ListViewEvents.cs:211 — Source/MSComctlLib/Events/ListViewEvents.cs:211-222 | Source/MSComctlLib/Events/ListViewEvents.cs:494-505 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) Source/Outlook/Events/NavigationGroupsEvents_12.cs:60 — Source/Outlook/Events/NavigationGroupsEvents_12.cs:60-71 | Source/Outlook/Events/NavigationGroupsEvents_12.cs:74-85 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) Source/PowerPoint/Events/EApplication.cs:444 — Source/PowerPoint/Events/EApplication.cs:444-455 | Source/PowerPoint/Events/EApplication.cs:458-469 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) Source/Outlook/Events/StoresEvents_12.cs:57 — Source/Outlook/Events/StoresEvents_12.cs:57-71 | Source/Outlook/Events/StoresEvents_12.cs:74-85 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) Source/OWC10/Events/ISpreadsheetEventSink.cs:611 — Source/OWC10/Events/ISpreadsheetEventSink.cs:611-622 | Source/OWC10/Events/ISpreadsheetEventSink.cs:719-730 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) Source/Office/Events/_CustomTaskPaneEvents.cs:56 — Source/Office/Events/_CustomTaskPaneEvents.cs:56-67 | Source/Office/Events/_CustomTaskPaneEvents.cs:70-81 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) Source/Outlook/Events/FoldersEvents.cs:60 — Source/Outlook/Events/FoldersEvents.cs:60-71 | Source/Outlook/Events/FoldersEvents.cs:74-85 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) Source/NetOffice/CoreExtensions/CoreMethodExtensions.cs:2292 — Source/NetOffice/CoreExtensions/CoreMethodExtensions.cs:2292-2304 | Source/NetOffice/CoreExtensions/CorePropertyGetExtensions.cs:1918-1929 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) Source/Word/Tools/COMAddin.cs:1003 — Source/Word/Tools/COMAddin.cs:1003-1014 | Source/Outlook/Tools/COMAddin.cs:1114-1126 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) Source/Word/Tools/COMAddin.cs:1024 — Source/Word/Tools/COMAddin.cs:1024-1035 | Source/Outlook/Tools/COMAddin.cs:1136-1147 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (27–30 lines × 3) · ×17
  • Duplicated block (27–30 lines × 3) Source/Excel/Classes/Chart.cs:93 — Source/Excel/Classes/Chart.cs:93-122 | Source/PowerPoint/DispatchInterfaces/Chart.cs:226-252 | Source/Word/DispatchInterfaces/Chart.cs:254-280 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (27–30 lines × 3) Source/Access/Classes/CheckBox.cs:94 — Source/Access/Classes/CheckBox.cs:94-123 | Source/Excel/DispatchInterfaces/CheckBox.cs:195-221 | Source/Word/DispatchInterfaces/CheckBox.cs:68-94 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (27–30 lines × 3) Source/Access/Classes/Line.cs:80 — Source/Access/Classes/Line.cs:80-109 | Source/Excel/DispatchInterfaces/Line.cs:67-93 | Source/Word/DispatchInterfaces/Line.cs:68-94 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (27–30 lines × 3) Source/Access/Classes/Page.cs:85 — Source/Access/Classes/Page.cs:85-114 | Source/Excel/DispatchInterfaces/Page.cs:68-94 | Source/Word/DispatchInterfaces/Page.cs:68-94 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (27–30 lines × 3) Source/ADODB/Classes/Parameter.cs:75 — Source/ADODB/Classes/Parameter.cs:75-104 | Source/DAO/DispatchInterfaces/Parameter.cs:67-93 | Source/Excel/DispatchInterfaces/Parameter.cs:68-94 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (27–30 lines × 3) Source/Excel/DispatchInterfaces/Range.cs:682 — Source/Excel/DispatchInterfaces/Range.cs:682-708 | Source/OWC10/Classes/Range.cs:79-108 | Source/Word/DispatchInterfaces/Range.cs:172-198 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (27–30 lines × 3) Source/Access/Classes/Rectangle.cs:85 — Source/Access/Classes/Rectangle.cs:85-114 | Source/Excel/DispatchInterfaces/Rectangle.cs:194-220 | Source/Word/DispatchInterfaces/Rectangle.cs:68-94 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (27–30 lines × 3) Source/Access/Classes/SmartTag.cs:76 — Source/Access/Classes/SmartTag.cs:76-105 | Source/Excel/DispatchInterfaces/SmartTag.cs:67-93 | Source/Word/DispatchInterfaces/SmartTag.cs:67-93 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (27–30 lines × 3) Source/Access/Classes/SmartTagAction.cs:76 — Source/Access/Classes/SmartTagAction.cs:76-105 | Source/Excel/DispatchInterfaces/SmartTagAction.cs:67-93 | Source/Word/DispatchInterfaces/SmartTagAction.cs:67-93 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (27–30 lines × 3) Source/Access/Classes/SmartTagActions.cs:76 — Source/Access/Classes/SmartTagActions.cs:76-105 | Source/Excel/DispatchInterfaces/SmartTagActions.cs:70-96 | Source/Word/DispatchInterfaces/SmartTagActions.cs:70-96 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (27–30 lines × 3) Source/Access/Classes/SmartTags.cs:76 — Source/Access/Classes/SmartTags.cs:76-105 | Source/Excel/DispatchInterfaces/SmartTags.cs:70-96 | Source/Word/DispatchInterfaces/SmartTags.cs:70-96 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (27–30 lines × 3) Source/Outlook/Classes/Column.cs:76 — Source/Outlook/Classes/Column.cs:76-105 | Source/PowerPoint/DispatchInterfaces/Column.cs:68-94 | Source/Word/DispatchInterfaces/Column.cs:68-94 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (27–30 lines × 3) Source/Outlook/Classes/Columns.cs:76 — Source/Outlook/Classes/Columns.cs:76-105 | Source/PowerPoint/DispatchInterfaces/Columns.cs:68-94 | Source/Word/DispatchInterfaces/Columns.cs:71-97 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (27–30 lines × 3) Source/ADODB/DispatchInterfaces/Field.cs:67 — Source/ADODB/DispatchInterfaces/Field.cs:67-93 | Source/DAO/Classes/Field.cs:75-104 | Source/Word/DispatchInterfaces/Field.cs:68-94 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (27–30 lines × 3) Source/Outlook/Classes/Row.cs:76 — Source/Outlook/Classes/Row.cs:76-105 | Source/PowerPoint/DispatchInterfaces/Row.cs:68-94 | Source/Word/DispatchInterfaces/Row.cs:68-94 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (27–30 lines × 3) Source/Access/Classes/Section.cs:86 — Source/Access/Classes/Section.cs:86-115 | Source/OWC10/DispatchInterfaces/Section.cs:67-93 | Source/Word/DispatchInterfaces/Section.cs:68-94 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (27–30 lines × 3) Source/Outlook/Classes/Table.cs:76 — Source/Outlook/Classes/Table.cs:76-105 | Source/PowerPoint/DispatchInterfaces/Table.cs:68-94 | Source/Word/DispatchInterfaces/Table.cs:68-94 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
D4 · Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) · ×16
  • Members sharing a duplicated core (5 members, 50+ identical tokens) Source/Excel/Events/AppEvents.cs:663 — Source/Excel/Events/AppEvents.cs:663-676 | Source/Excel/Events/AppEvents.cs:679-692 | Source/Excel/Events/AppEvents.cs:695-708 | Source/Excel/Events/WorkbookEvents.cs:562-575 | Source/Excel/Events/WorkbookEvents.cs:798-811 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) Source/NetOffice/CoreExtensions/CorePropertySetExtensions.cs:109 — Source/NetOffice/CoreExtensions/CorePropertySetExtensions.cs:109-115 | Source/NetOffice/CoreExtensions/CorePropertySetExtensions.cs:205-211 | Source/NetOffice/CoreExtensions/CorePropertySetExtensions.cs:398-404 | Source/NetOffice/CoreExtensions/CorePropertySetExtensions.cs:494-500 | Source/NetOffice/CoreExtensions/CorePropertySetExtensions.cs:687-694 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) Source/NetOffice/Running/RunningObjectTable.cs:123 — Source/NetOffice/Running/RunningObjectTable.cs:123-192 | Source/NetOffice/Running/RunningObjectTable.cs:203-278 | Source/NetOffice/Running/RunningObjectTable.cs:288-358 | Source/NetOffice/Running/RunningObjectTable.cs:368-472 | Source/NetOffice/Running/RunningObjectTable.cs:480-557 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) Source/Outlook/Events/ItemEvents.cs:310 — Source/Outlook/Events/ItemEvents.cs:310-321 | Source/Outlook/Events/ItemEvents.cs:324-335 | Source/Outlook/Events/ItemEvents_10.cs:367-378 | Source/Outlook/Events/ItemEvents_10.cs:381-392 | Source/Outlook/Events/ItemEvents_10.cs:429-440 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) Source/PowerPoint/Events/EApplication.cs:374 — Source/PowerPoint/Events/EApplication.cs:374-385 | Source/PowerPoint/Events/EApplication.cs:388-399 | Source/PowerPoint/Events/EApplication.cs:402-413 | Source/PowerPoint/Events/EApplication.cs:549-560 | Source/PowerPoint/Events/EApplication.cs:563-574 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) Source/Access/Events/_FormEvents.cs:827 — Source/Access/Events/_FormEvents.cs:827-845 | Source/Access/Events/_FormEvents.cs:848-864 | Source/Access/Events/_FormEvents.cs:867-885 | Source/Access/Events/_FormEvents.cs:888-904 | Source/Access/Events/_FormEvents.cs:907-923 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) Source/Access/Events/_FormEvents.cs:1145 — Source/Access/Events/_FormEvents.cs:1145-1158 | Source/Access/Events/_FormEvents2.cs:1024-1037 | Source/Access/Events/_ReportEvents2.cs:520-540 | Source/OWC10/Events/IChartEvents.cs:386-399 | Source/OWC10/Events/ISpreadsheetEventSink.cs:584-597 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) Source/Office.Extensions/Dialogs/DialogUtilsEx.cs:666 — Source/Office.Extensions/Dialogs/DialogUtilsEx.cs:666-706 | Source/Office.Extensions/Dialogs/DialogUtilsEx.cs:750-788 | Source/Office.Extensions/Dialogs/DialogUtilsEx.cs:864-883 | Source/Office.Extensions/Dialogs/DialogUtilsEx.cs:896-913 | Source/Office.Extensions/Dialogs/DialogUtilsEx.cs:1090-1109 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) Toolbox/Toolbox/ToolboxControls/About/AboutControl.cs:173 — Toolbox/Toolbox/ToolboxControls/About/AboutControl.cs:173-195 | Toolbox/Toolbox/ToolboxControls/About/AboutControl.cs:198-220 | Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/OfficeCompatibilityControl.cs:296-318 | Toolbox/Toolbox/ToolboxControls/OutlookSecurity/OutlookSecurityControl.cs:225-247 | Toolbox/Toolbox/ToolboxControls/Welcome/WelcomeControl.cs:292-314 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) Examples/Access/NetOffice COMAddin Examples/02 Ribbons And Panes/SamplePane.cs:76 — Examples/Access/NetOffice COMAddin Examples/02 Ribbons And Panes/SamplePane.cs:76-93 | Examples/Excel/NetOffice COMAddin Examples/02 Ribbons And Panes/SamplePane.cs:76-93 | Examples/Outlook/NetOffice COMAddin Examples/02 Ribbons And Panes/SamplePane.cs:77-94 | Examples/PowerPoint/NetOffice COMAddin Examples/02 Ribbons And Panes/SamplePane.cs:76-93 | Examples/Word/NetOffice COMAddin Examples/02 Ribbons And Panes/SamplePane.cs:76-93 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) Examples/Access/NetOffice COMAddin Examples/03 Troubleshooting and Diagnostics/Addin.cs:36 — Examples/Access/NetOffice COMAddin Examples/03 Troubleshooting and Diagnostics/Addin.cs:36-68 | Examples/Excel/NetOffice COMAddin Examples/03 Troubleshooting and Diagnostics/Addin.cs:36-68 | Examples/Outlook/NetOffice COMAddin Examples/03 Troubleshooting and Diagnostics/Addin.cs:38-70 | Examples/PowerPoint/NetOffice COMAddin Examples/03 Troubleshooting and Diagnostics/Addin.cs:36-68 | Examples/Word/NetOffice COMAddin Examples/03 Troubleshooting and Diagnostics/Addin.cs:36-68 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) Examples/Access/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:92 — Examples/Access/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:92-125 | Examples/Excel/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:149-200 | Examples/Outlook/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:146-184 | Examples/PowerPoint/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:147-193 | Examples/Word/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:197-252 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) Examples/Access/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:181 — Examples/Access/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:181-195 | Examples/Excel/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:179-193 | Examples/Other/IExtensibility2 Examples/SuperAddin/Addin.cs:196-210 | Examples/PowerPoint/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:180-194 | Examples/Word/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:178-192 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) Examples/Access/IExtensibility COMAddin Examples/TaskPane/Addin.cs:31 — Examples/Access/IExtensibility COMAddin Examples/TaskPane/Addin.cs:31-47 | Examples/Excel/IExtensibility COMAddin Examples/TaskPane/Addin.cs:31-47 | Examples/Outlook/IExtensibility COMAddin Examples/TaskPane/Addin.cs:33-49 | Examples/PowerPoint/IExtensibility COMAddin Examples/TaskPane/Addin.cs:31-47 | Examples/Word/IExtensibility COMAddin Examples/TaskPane/Addin.cs:31-47 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) REDACTED:31 — REDACTED:31-49 | REDACTED:31-49 | REDACTED:33-52 | REDACTED:33-51 | REDACTED:32-50 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) REDACTED:83 — REDACTED:83-96 | REDACTED:83-96 | REDACTED:86-99 | REDACTED:85-98 | REDACTED:84-97 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication · Edited copy of a member (15 corresponding lines) · ×15
  • Edited copy of a member (15 corresponding lines) Toolbox/Toolbox/ToolboxControls/ApplicationObserver/ApplicationObserverControl.cs:137 — Toolbox/Toolbox/ToolboxControls/ApplicationObserver/ApplicationObserverControl.cs:137-173 | Toolbox/Toolbox/ToolboxControls/ApplicationObserver/ApplicationObserverControl.cs:176-190 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) Source/Office/Events/_CustomXMLPartEvents.cs:84 — Source/Office/Events/_CustomXMLPartEvents.cs:84-101 | Source/Office/Events/_CustomXMLPartEvents.cs:104-118 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) Source/Excel/Events/AppEvents.cs:502 — Source/Excel/Events/AppEvents.cs:502-516 | Source/Excel/Events/AppEvents.cs:538-552 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) Source/PowerPoint/Events/EApplication.cs:472 — Source/PowerPoint/Events/EApplication.cs:472-486 | Source/PowerPoint/Events/EApplication.cs:577-591 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) Source/Excel/Events/AppEvents.cs:940 — Source/Excel/Events/AppEvents.cs:940-954 | Source/Word/Events/ApplicationEvents4.cs:742-756 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) REDACTED:186 — REDACTED:186-200 | REDACTED:228-244 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) Source/Office/Tools/COMAddin.cs:629 — Source/Office/Tools/COMAddin.cs:629-643 | Source/Office/Tools/CustomTaskPaneHandler.cs:179-193 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) Source/Office.Extensions/TrayMenuUtils/TrayMenuMonitorItem.cs:103 — Source/Office.Extensions/TrayMenuUtils/TrayMenuMonitorItem.cs:103-117 | Source/Office.Extensions/TrayMenuUtils/TrayMenuMonitorItem.cs:131-145 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) RegAddin/RegAddin/RegFile/RegValueConverter.cs:63 — RegAddin/RegAddin/RegFile/RegValueConverter.cs:63-91 | RegAddin/RegAddin/RegFile/RegValueConverter.cs:94-108 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) Source/MSComctlLib/Events/ITreeViewEvents.cs:185 — Source/MSComctlLib/Events/ITreeViewEvents.cs:185-199 | Source/MSComctlLib/Events/ListViewEvents.cs:180-194 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) Source/MSComctlLib/Events/ITreeViewEvents.cs:244 — Source/MSComctlLib/Events/ITreeViewEvents.cs:244-258 | Source/MSComctlLib/Events/ITreeViewEvents.cs:261-275 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) Source/Outlook/Tools/COMAddin.cs:742 — Source/Outlook/Tools/COMAddin.cs:742-756 | Source/Outlook/Tools/COMAddin.cs:789-803 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) RegAddin/RegAddin/Common/AttributeReflection.cs:13 — RegAddin/RegAddin/Common/AttributeReflection.cs:13-27 | RegAddin/RegAddin/Dispatcher/MethodUtils.cs:46-62 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) Toolbox/Toolbox/Controls/Hex/HexBox.cs:492 — Toolbox/Toolbox/Controls/Hex/HexBox.cs:492-506 | Toolbox/Toolbox/Controls/Hex/HexBox.cs:509-524 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) Source/NetOffice/Running/ChildWindowEnumerator.cs:130 — Source/NetOffice/Running/ChildWindowEnumerator.cs:130-147 | Source/Outlook/Tools/Contribution/Security/User32.cs:165-179 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×15
  • Duplicated block (10 lines × 2) Source/Excel/Events/AppEvents.cs:133 — Source/Excel/Events/AppEvents.cs:133-142 | Source/Excel/Events/WorkbookEvents.cs:117-126 — before extracting anything, compare `Source/Excel/Events/AppEvents.cs` and `Source/Excel/Events/WorkbookEvents.cs` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 377 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (10 lines × 2) Source/Access/Events/_FormEvents2.cs:66 — Source/Access/Events/_FormEvents2.cs:66-75 | Source/Access/Events/_ReportEvents2.cs:59-68 — before extracting anything, compare `Source/Access/Events/_FormEvents2.cs` and `Source/Access/Events/_ReportEvents2.cs` as WHOLE FILES: this scan already matched 45 separate duplicated blocks between them, totalling at least 418 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (10 lines × 2) Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsMultiAddinConverterVB.cs:172 — Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsMultiAddinConverterVB.cs:172-181 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsSingleAddinConverterVB.cs:156-165 — before extracting anything, compare `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsMultiAddinConverterVB.cs` and `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsSingleAddinConverterVB.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 180 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsMultiAddinConverterVB.cs:172` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (10 lines × 2) Source/Excel/Events/AppEvents.cs:894 — Source/Excel/Events/AppEvents.cs:894-903 | Source/Excel/Events/WorkbookEvents.cs:766-775 — before extracting anything, compare `Source/Excel/Events/AppEvents.cs` and `Source/Excel/Events/WorkbookEvents.cs` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 377 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Source/Excel/Events/AppEvents.cs:894` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) Source/Outlook/Events/ItemEvents.cs:20 — Source/Outlook/Events/ItemEvents.cs:20-29 | Source/Outlook/Events/ItemEvents_10.cs:20-29 — before extracting anything, compare `Source/Outlook/Events/ItemEvents.cs` and `Source/Outlook/Events/ItemEvents_10.cs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 292 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (10 lines × 2) Source/Excel/Events/DocEvents.cs:138 — Source/Excel/Events/DocEvents.cs:138-147 | Source/Excel/Events/DocEvents.cs:219-228 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (10 lines × 2) Source/Office/Native/SignatureProvider.cs:87 — Source/Office/Native/SignatureProvider.cs:87-100 | Source/Office/Native/SignatureProvider.cs:101-110 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (10 lines × 2) Source/Outlook/Events/NavigationGroupsEvents_12.cs:61 — Source/Outlook/Events/NavigationGroupsEvents_12.cs:61-70 | Source/Outlook/Events/NavigationGroupsEvents_12.cs:75-84 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (10 lines × 2) Source/PowerPoint/Events/EApplication.cs:445 — Source/PowerPoint/Events/EApplication.cs:445-454 | Source/PowerPoint/Events/EApplication.cs:459-468 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (10 lines × 2) Source/OWC10/Events/IChartEvents.cs:564 — Source/OWC10/Events/IChartEvents.cs:564-573 | Source/OWC10/Events/IChartEvents.cs:578-587 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (10 lines × 2) Source/MSComctlLib/Events/IStatusBarEvents.cs:133 — Source/MSComctlLib/Events/IStatusBarEvents.cs:133-142 | Source/MSComctlLib/Events/IStatusBarEvents.cs:147-156 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (10 lines × 2) Source/MSComctlLib/Events/IToolbarEvents.cs:142 — Source/MSComctlLib/Events/IToolbarEvents.cs:142-151 | Source/MSComctlLib/Events/IToolbarEvents.cs:401-410 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (10 lines × 2) Source/MSComctlLib/Events/ListViewEvents.cs:212 — Source/MSComctlLib/Events/ListViewEvents.cs:212-221 | Source/MSComctlLib/Events/ListViewEvents.cs:495-504 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (10 lines × 2) Source/NetOffice/Running/ChildWindowBatchEnumerator.cs:160 — Source/NetOffice/Running/ChildWindowBatchEnumerator.cs:160-169 | Source/NetOffice/Running/ChildWindowEnumerator.cs:118-127 — before extracting anything, compare `Source/NetOffice/Running/ChildWindowBatchEnumerator.cs` and `Source/NetOffice/Running/ChildWindowEnumerator.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (10 lines × 2) Source/Outlook/Events/ApplicationEvents.cs:103 — Source/Outlook/Events/ApplicationEvents.cs:103-112 | Source/Outlook/Events/ApplicationEvents_10.cs:117-126 — before extracting anything, compare `Source/Outlook/Events/ApplicationEvents.cs` and `Source/Outlook/Events/ApplicationEvents_10.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 82 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×15
  • Duplicated block (9 lines × 2) Source/Outlook/Events/ItemEvents_10.cs:110 — Source/Outlook/Events/ItemEvents_10.cs:110-118 | Source/Outlook/Events/ItemEvents_10.cs:122-130 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (9 lines × 2) Source/OWC10/Events/IChartEvents.cs:90 — Source/OWC10/Events/IChartEvents.cs:90-98 | Source/OWC10/Events/IPivotControlEvents.cs:76-84 — before extracting anything, compare `Source/OWC10/Events/IChartEvents.cs` and `Source/OWC10/Events/IPivotControlEvents.cs` as WHOLE FILES: this scan already matched 39 separate duplicated blocks between them, totalling at least 404 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (9 lines × 2) Source/OWC10/Events/IPivotControlEvents.cs:173 — Source/OWC10/Events/IPivotControlEvents.cs:173-181 | Source/OWC10/Events/ISpreadsheetEventSink.cs:80-88 — before extracting anything, compare `Source/OWC10/Events/IPivotControlEvents.cs` and `Source/OWC10/Events/ISpreadsheetEventSink.cs` as WHOLE FILES: this scan already matched 36 separate duplicated blocks between them, totalling at least 344 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (9 lines × 2) Toolbox/Toolbox/Utils/Animation/Panel/AnimatedPanel.cs:122 — Toolbox/Toolbox/Utils/Animation/Panel/AnimatedPanel.cs:122-130 | Toolbox/Toolbox/Utils/Animation/Panel/AnimatedPanel.cs:261-269 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (9 lines × 2) Source/Access/Events/_FormEvents.cs:831 — Source/Access/Events/_FormEvents.cs:831-839 | Source/Access/Events/_FormEvents.cs:871-879 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/Access/Events/_FormEvents.cs:831` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (9 lines × 2) Source/Access/Events/_References_Events.cs:57 — Source/Access/Events/_References_Events.cs:57-65 | Source/Access/Events/_References_Events.cs:71-79 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (9 lines × 2) Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsSingleAddinConverterCS.cs:123 — Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsSingleAddinConverterCS.cs:123-131 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsSingleAddinConverterVB.cs:147-155 — before extracting anything, compare `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsSingleAddinConverterCS.cs` and `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsSingleAddinConverterVB.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsSingleAddinConverterCS.cs:123` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsSingleAddinConverterVB.cs:158` calls `Replace` and `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsSingleAddinConverterCS.cs:133` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (9 lines × 2) Source/NetOffice/Diagnostics/SelfDiagnostics.cs:47 — Source/NetOffice/Diagnostics/SelfDiagnostics.cs:47-55 | Source/Office/Tools/Informations/AssemblyInfo.cs:56-64 — before extracting anything, compare `Source/NetOffice/Diagnostics/SelfDiagnostics.cs` and `Source/Office/Tools/Informations/AssemblyInfo.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 33 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (9 lines × 2) Source/VBIDE/Events/_dispReferencesEvents.cs:19 — Source/VBIDE/Events/_dispReferencesEvents.cs:19-27 | Source/VBIDE/Events/_dispReferences_Events.cs:19-27 — before extracting anything, compare `Source/VBIDE/Events/_dispReferencesEvents.cs` and `Source/VBIDE/Events/_dispReferences_Events.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (9 lines × 2) Source/ADODB/Events/RecordsetEvents.cs:160 — Source/ADODB/Events/RecordsetEvents.cs:160-168 | Source/ADODB/Events/RecordsetEvents.cs:202-210 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (9 lines × 2) Source/OWC10/Events/IPivotControlEvents.cs:634 — Source/OWC10/Events/IPivotControlEvents.cs:634-642 | Source/OWC10/Events/ISpreadsheetEventSink.cs:401-409 — before extracting anything, compare `Source/OWC10/Events/IPivotControlEvents.cs` and `Source/OWC10/Events/ISpreadsheetEventSink.cs` as WHOLE FILES: this scan already matched 36 separate duplicated blocks between them, totalling at least 344 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (9 lines × 2) Source/Excel/Events/AppEvents.cs:907 — Source/Excel/Events/AppEvents.cs:907-915 | Source/Excel/Events/WorkbookEvents.cs:779-787 — before extracting anything, compare `Source/Excel/Events/AppEvents.cs` and `Source/Excel/Events/WorkbookEvents.cs` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 377 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (9 lines × 2) Source/Outlook/Events/_ViewsEvents.cs:57 — Source/Outlook/Events/_ViewsEvents.cs:57-65 | Source/Outlook/Events/_ViewsEvents.cs:70-78 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (9 lines × 2) Source/Access/Events/_CustomControlEvents.cs:20 — Source/Access/Events/_CustomControlEvents.cs:20-28 | Source/Access/Events/_ObjectFrameEvents.cs:20-28 — before extracting anything, compare `Source/Access/Events/_CustomControlEvents.cs` and `Source/Access/Events/_ObjectFrameEvents.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Source/Access/Events/_ObjectFrameEvents.cs:29` calls `SinkArgument` and `Source/Access/Events/_CustomControlEvents.cs:29` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (9 lines × 2) Source/Word/Events/ApplicationEvents3.cs:100 — Source/Word/Events/ApplicationEvents3.cs:100-108 | Source/Word/Events/ApplicationEvents4.cs:100-108 — before extracting anything, compare `Source/Word/Events/ApplicationEvents3.cs` and `Source/Word/Events/ApplicationEvents4.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 469 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (10 lines × 3) · ×15
  • Duplicated block (10 lines × 3) Source/Word/Events/ApplicationEvents2.cs:150 — Source/Word/Events/ApplicationEvents2.cs:150-159 | Source/Word/Events/ApplicationEvents3.cs:215-224 | Source/Word/Events/ApplicationEvents4.cs:288-297 — before extracting anything, compare `Source/Word/Events/ApplicationEvents2.cs` and `Source/Word/Events/ApplicationEvents3.cs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 270 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (10 lines × 3) Source/Excel/Events/WorkbookEvents.cs:393 — Source/Excel/Events/WorkbookEvents.cs:393-402 | Source/Excel/Events/WorkbookEvents.cs:407-416 | Source/Excel/Events/WorkbookEvents.cs:421-430 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (10 lines × 3) Source/Office/Events/_CustomXMLPartsEvents.cs:62 — Source/Office/Events/_CustomXMLPartsEvents.cs:62-71 | Source/Office/Events/_CustomXMLPartsEvents.cs:76-85 | Source/Office/Events/_CustomXMLPartsEvents.cs:90-99 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (10 lines × 3) Source/PowerPoint/Events/EApplication.cs:595 — Source/PowerPoint/Events/EApplication.cs:595-604 | Source/PowerPoint/Events/EApplication.cs:645-654 | Source/PowerPoint/Events/EApplication.cs:659-668 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (10 lines × 3) Source/OWC10/Events/ISpreadsheetEventSink.cs:626 — Source/OWC10/Events/ISpreadsheetEventSink.cs:626-635 | Source/OWC10/Events/ISpreadsheetEventSink.cs:640-649 | Source/OWC10/Events/ISpreadsheetEventSink.cs:670-679 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (10 lines × 3) RegAddin/RegAddin/RegFile/RegFileOperationHost.cs:72 — RegAddin/RegAddin/RegFile/RegFileOperationHost.cs:72-82 | RegAddin/RegAddin/Register/RegisterOperationHost.cs:60-70 | RegAddin/RegAddin/Unregister/UnregisterOperationHost.cs:56-65 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `RegAddin/RegAddin/RegFile/RegFileOperationHost.cs:72` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (10 lines × 3) Source/Access/Tools/COMAddin.cs:864 — Source/Access/Tools/COMAddin.cs:864-873 | Source/Excel/Tools/COMAddin.cs:866-875 | Source/PowerPoint/Tools/COMAddin.cs:865-874 — before extracting anything, compare `Source/Access/Tools/COMAddin.cs` and `Source/Excel/Tools/COMAddin.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 284 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (10 lines × 3) Source/Access/Tools/COMAddin.cs:884 — Source/Access/Tools/COMAddin.cs:884-893 | Source/Excel/Tools/COMAddin.cs:886-895 | Source/PowerPoint/Tools/COMAddin.cs:885-894 — before extracting anything, compare `Source/Access/Tools/COMAddin.cs` and `Source/Excel/Tools/COMAddin.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 284 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (10 lines × 3) Toolbox/Toolbox/ToolboxControls/RegistryEditor/ChangeBinaryControl.cs:114 — Toolbox/Toolbox/ToolboxControls/RegistryEditor/ChangeBinaryControl.cs:114-123 | Toolbox/Toolbox/ToolboxControls/RegistryEditor/ChangeDWORDControl.cs:147-156 | Toolbox/Toolbox/ToolboxControls/RegistryEditor/ChangeStringControl.cs:116-125 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (10 lines × 3) Toolbox/Toolbox/ToolboxControls/RegistryEditor/ChangeBinaryControl.cs:127 — Toolbox/Toolbox/ToolboxControls/RegistryEditor/ChangeBinaryControl.cs:127-136 | Toolbox/Toolbox/ToolboxControls/RegistryEditor/ChangeNameControl.cs:105-114 | Toolbox/Toolbox/ToolboxControls/RegistryEditor/ChangeStringControl.cs:103-112 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (10 lines × 3) Examples/Excel/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:38 — Examples/Excel/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:38-47 | Examples/Excel/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:29-38 | Examples/Excel/IExtensibility COMAddin Examples/TaskPane/Addin.cs:55-64 — `Examples/Excel/IExtensibility COMAddin Examples/ClassicUI/Addin.cs` and `Examples/Excel/IExtensibility COMAddin Examples/RibbonUI/Addin.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 83 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (10 lines × 3) Examples/Outlook/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:36 — Examples/Outlook/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:36-45 | Examples/Outlook/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:29-38 | Examples/Outlook/IExtensibility COMAddin Examples/TaskPane/Addin.cs:57-66 — `Examples/Outlook/IExtensibility COMAddin Examples/ClassicUI/Addin.cs` and `Examples/Outlook/IExtensibility COMAddin Examples/RibbonUI/Addin.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 90 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (10 lines × 3) Examples/Access/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:36 — Examples/Access/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:36-45 | Examples/Access/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:29-38 | Examples/Access/IExtensibility COMAddin Examples/TaskPane/Addin.cs:55-64 — `Examples/Access/IExtensibility COMAddin Examples/ClassicUI/Addin.cs` and `Examples/Access/IExtensibility COMAddin Examples/RibbonUI/Addin.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 83 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (10 lines × 3) Examples/PowerPoint/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:38 — Examples/PowerPoint/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:38-47 | Examples/PowerPoint/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:29-38 | Examples/PowerPoint/IExtensibility COMAddin Examples/TaskPane/Addin.cs:55-64 — `Examples/PowerPoint/IExtensibility COMAddin Examples/ClassicUI/Addin.cs` and `Examples/PowerPoint/IExtensibility COMAddin Examples/RibbonUI/Addin.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 84 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (10 lines × 3) Examples/Word/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:39 — Examples/Word/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:39-48 | Examples/Word/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:29-38 | Examples/Word/IExtensibility COMAddin Examples/TaskPane/Addin.cs:55-64 — `Examples/Word/IExtensibility COMAddin Examples/ClassicUI/Addin.cs` and `Examples/Word/IExtensibility COMAddin Examples/RibbonUI/Addin.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 79 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) · ×14
  • Members sharing a duplicated core (6 members, 50+ identical tokens) Source/Excel/DispatchInterfaces/_Workbook.cs:4880 — Source/Excel/DispatchInterfaces/_Workbook.cs:4880-4890 | Source/Excel/DispatchInterfaces/_Workbook.cs:4901-4911 | Source/Excel/DispatchInterfaces/_Workbook.cs:4923-4933 | Source/Excel/DispatchInterfaces/_Workbook.cs:4945-4955 | Source/Excel/DispatchInterfaces/_Workbook.cs:4966-4976 | Source/Excel/DispatchInterfaces/_Workbook.cs:4988-4998 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
  • Members sharing a duplicated core (6 members, 50+ identical tokens) Source/Excel/Events/AppEvents.cs:334 — Source/Excel/Events/AppEvents.cs:334-345 | Source/Excel/Events/AppEvents.cs:460-471 | Source/Excel/Events/AppEvents.cs:474-485 | Source/Excel/Events/AppEvents.cs:488-499 | Source/Excel/Events/AppEvents.cs:571-582 | Source/Excel/Events/AppEvents.cs:585-596 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
  • Members sharing a duplicated core (6 members, 50+ identical tokens) Source/Access/Events/DispWebBrowserControlEvents.cs:456 — Source/Access/Events/DispWebBrowserControlEvents.cs:456-470 | Source/Excel/Events/ChartEvents.cs:289-302 | Source/OWC10/Events/IChartEvents.cs:228-241 | Source/OWC10/Events/IChartEvents.cs:244-257 | Source/OWC10/Events/IPivotControlEvents.cs:489-502 | Source/OWC10/Events/IPivotControlEvents.cs:505-518 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
  • Members sharing a duplicated core (6 members, 50+ identical tokens) Source/Access/Tools/COMAddin.cs:298 — Source/Access/Tools/COMAddin.cs:298-318 | Source/Excel/Tools/COMAddin.cs:298-318 | Source/Outlook/Tools/COMAddin.cs:308-328 | Source/PowerPoint/Tools/COMAddin.cs:299-319 | Source/VBIDE/Tools/COMAddin.cs:264-283 | Source/Word/Tools/COMAddin.cs:301-321 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
  • Members sharing a duplicated core (6 members, 50+ identical tokens) Source/Access/Tools/COMAddin.cs:531 — Source/Access/Tools/COMAddin.cs:531-565 | Source/Excel/Tools/COMAddin.cs:530-564 | Source/Office/Tools/COMAddin.cs:674-708 | Source/Outlook/Tools/COMAddin.cs:572-606 | Source/PowerPoint/Tools/COMAddin.cs:532-566 | Source/Word/Tools/COMAddin.cs:533-567 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
  • Members sharing a duplicated core (6 members, 50+ identical tokens) Source/Access/Tools/COMAddin.cs:568 — Source/Access/Tools/COMAddin.cs:568-602 | Source/Excel/Tools/COMAddin.cs:567-601 | Source/Office/Tools/COMAddin.cs:711-745 | Source/Outlook/Tools/COMAddin.cs:609-643 | Source/PowerPoint/Tools/COMAddin.cs:569-603 | Source/Word/Tools/COMAddin.cs:570-604 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
  • Members sharing a duplicated core (6 members, 50+ identical tokens) Source/Access/Tools/COMAddin.cs:789 — Source/Access/Tools/COMAddin.cs:789-805 | Source/Office/Tools/COMAddin.cs:939-955 | Source/Outlook/Tools/COMAddin.cs:1027-1043 | Source/PowerPoint/Tools/COMAddin.cs:790-806 | Source/VBIDE/Tools/COMAddin.cs:397-413 | Source/Word/Tools/COMAddin.cs:929-945 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
  • Members sharing a duplicated core (6 members, 50+ identical tokens) Source/Word/Events/ApplicationEvents2.cs:275 — Source/Word/Events/ApplicationEvents2.cs:275-289 | Source/Word/Events/ApplicationEvents2.cs:292-306 | Source/Word/Events/ApplicationEvents3.cs:340-354 | Source/Word/Events/ApplicationEvents3.cs:357-371 | Source/Word/Events/ApplicationEvents4.cs:413-427 | Source/Word/Events/ApplicationEvents4.cs:430-444 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
  • Members sharing a duplicated core (6 members, 50+ identical tokens) Source/Outlook/Events/ItemEvents.cs:338 — Source/Outlook/Events/ItemEvents.cs:338-352 | Source/Outlook/Events/ItemEvents_10.cs:395-409 | Source/Outlook/Events/ItemEvents_10.cs:443-457 | Source/Outlook/Events/ItemEvents_10.cs:460-474 | Source/Outlook/Events/ItemEvents_10.cs:477-491 | Source/Outlook/Events/ItemEvents_10.cs:494-508 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
  • Members sharing a duplicated core (6 members, 50+ identical tokens) Source/Access/Events/DispBoundObjectFrameEvents.cs:127 — Source/Access/Events/DispBoundObjectFrameEvents.cs:127-139 | Source/Access/Events/DispCustomControlEvents.cs:68-80 | Source/Access/Events/DispWebBrowserControlEvents.cs:159-171 | Source/Access/Events/_BoundObjectFrameEvents.cs:127-139 | Source/Access/Events/_CustomControlEvents.cs:67-79 | Source/Access/Events/_ObjectFrameEvents.cs:101-113 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
  • Members sharing a duplicated core (6 members, 50+ identical tokens) Source/Access/Events/_FormEvents.cs:994 — Source/Access/Events/_FormEvents.cs:994-1007 | Source/Access/Events/_FormEvents.cs:1010-1023 | Source/Access/Events/_FormEvents.cs:1026-1039 | Source/Access/Events/_FormEvents2.cs:873-886 | Source/Access/Events/_FormEvents2.cs:889-902 | Source/Access/Events/_FormEvents2.cs:905-918 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
  • Members sharing a duplicated core (6 members, 50+ identical tokens) Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/ReportControl.cs:187 — Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/ReportControl.cs:187-232 | Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/ReportControl.cs:235-253 | Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/ReportControl.cs:256-274 | Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/ReportControl.cs:277-295 | Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/ReportControl.cs:298-316 | Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/ReportControl.cs:319-338 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
  • Members sharing a duplicated core (6 members, 50+ identical tokens) REDACTED:52 — REDACTED:52-80 | REDACTED:52-80 | REDACTED:55-83 | REDACTED:54-82 | REDACTED:53-81 | Toolbox/Toolbox/Translator.cs:68-97 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
  • Members sharing a duplicated core (6 members, 50+ identical tokens) Examples/Outlook/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:125 — Examples/Outlook/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:125-136 | Examples/Outlook/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:154-165 | Examples/Outlook/IExtensibility COMAddin Examples/TaskPane/Addin.cs:139-154 | Examples/Word/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:134-145 | Examples/Word/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:155-166 | Examples/Word/IExtensibility COMAddin Examples/TaskPane/Addin.cs:137-152 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
D4 · Code Duplication · Duplicated block (5 lines × 4) · ×14
  • Duplicated block (5 lines × 4) Source/Excel/Events/AppEvents.cs:355 — Source/Excel/Events/AppEvents.cs:355-359 | Source/Excel/Events/AppEvents.cs:451-455 | Source/Excel/Events/WorkbookEvents.cs:441-445 | Source/Excel/Events/WorkbookEvents.cs:537-541 — before extracting anything, compare `Source/Excel/Events/AppEvents.cs` and `Source/Excel/Events/WorkbookEvents.cs` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 377 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 4) Source/Office.Extensions/Dialogs/DialogUtilsEx.cs:667 — Source/Office.Extensions/Dialogs/DialogUtilsEx.cs:667-671 | Source/Office.Extensions/Dialogs/DialogUtilsEx.cs:751-755 | Source/Office.Extensions/Dialogs/DialogUtilsEx.cs:865-869 | Source/Office.Extensions/Dialogs/DialogUtilsEx.cs:1091-1095 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (5 lines × 4) Source/Excel/Events/AppEvents.cs:731 — Source/Excel/Events/AppEvents.cs:731-735 | Source/Excel/Events/AppEvents.cs:754-758 | Source/Excel/Events/AppEvents.cs:774-778 | Source/Excel/Events/AppEvents.cs:795-799 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/Excel/Events/AppEvents.cs:731` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (5 lines × 4) Source/Excel/Events/AppEvents.cs:46 — Source/Excel/Events/AppEvents.cs:46-50 | Source/Excel/Events/AppEvents.cs:51-55 | Source/Excel/Events/WorkbookEvents.cs:98-102 | Source/Excel/Events/WorkbookEvents.cs:103-107 — before extracting anything, compare `Source/Excel/Events/AppEvents.cs` and `Source/Excel/Events/WorkbookEvents.cs` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 377 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 4) Source/Access/Events/DispPageHdrFtrInReportEvents.cs:27 — Source/Access/Events/DispPageHdrFtrInReportEvents.cs:27-31 | Source/Access/Events/DispSectionInReportEvents.cs:27-31 | Source/Access/Events/_PageHdrFtrInReportEvents.cs:27-31 | Source/Access/Events/_SectionInReportEvents.cs:27-31 — before extracting anything, compare `Source/Access/Events/DispPageHdrFtrInReportEvents.cs` and `Source/Access/Events/DispSectionInReportEvents.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 179 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Source/Access/Events/DispSectionInReportEvents.cs:32` calls `MethodImpl`, `DispId`, `Retreat` and `Source/Access/Events/DispPageHdrFtrInReportEvents.cs:32` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 4) Source/Excel/DispatchInterfaces/AddIns.cs:237 — Source/Excel/DispatchInterfaces/AddIns.cs:237-241 | Source/Excel/DispatchInterfaces/AddIns2.cs:237-241 | Source/Excel/Interfaces/IAddIns.cs:230-234 | Source/Excel/Interfaces/IAddIns2.cs:230-234 — before extracting anything, compare `Source/Excel/DispatchInterfaces/AddIns.cs` and `Source/Excel/Interfaces/IAddIns.cs` as WHOLE FILES: 88% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 4) Source/Excel/DispatchInterfaces/Adjustments.cs:192 — Source/Excel/DispatchInterfaces/Adjustments.cs:192-196 | Source/Office/DispatchInterfaces/Adjustments.cs:191-195 | Source/PowerPoint/DispatchInterfaces/Adjustments.cs:222-226 | Source/Word/DispatchInterfaces/Adjustments.cs:221-225 — before extracting anything, compare `Source/Excel/DispatchInterfaces/Adjustments.cs` and `Source/Office/DispatchInterfaces/Adjustments.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 66 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 4) Source/Excel/DispatchInterfaces/CalculatedItems.cs:250 — Source/Excel/DispatchInterfaces/CalculatedItems.cs:250-254 | Source/Excel/DispatchInterfaces/PivotItemList.cs:213-217 | Source/Excel/Interfaces/ICalculatedItems.cs:243-247 | Source/Excel/Interfaces/IPivotItemList.cs:208-212 — before extracting anything, compare `Source/Excel/DispatchInterfaces/CalculatedItems.cs` and `Source/Excel/Interfaces/ICalculatedItems.cs` as WHOLE FILES: 89% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 4) Source/Excel/DispatchInterfaces/FullSeriesCollection.cs:212 — Source/Excel/DispatchInterfaces/FullSeriesCollection.cs:212-216 | Source/Excel/DispatchInterfaces/SeriesCollection.cs:409-413 | Source/Excel/Interfaces/IFullSeriesCollection.cs:207-211 | Source/Excel/Interfaces/ISeriesCollection.cs:389-393 — before extracting anything, compare `Source/Excel/DispatchInterfaces/FullSeriesCollection.cs` and `Source/Excel/Interfaces/IFullSeriesCollection.cs` as WHOLE FILES: 87% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 4) Source/Excel/DispatchInterfaces/PivotTables.cs:268 — Source/Excel/DispatchInterfaces/PivotTables.cs:268-272 | Source/Excel/DispatchInterfaces/SlicerPivotTables.cs:235-239 | Source/Excel/Interfaces/IPivotTables.cs:259-263 | Source/Excel/Interfaces/ISlicerPivotTables.cs:228-232 — before extracting anything, compare `Source/Excel/DispatchInterfaces/PivotTables.cs` and `Source/Excel/Interfaces/IPivotTables.cs` as WHOLE FILES: 90% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 4) Source/Office/DispatchInterfaces/Adjustments.cs:174 — Source/Office/DispatchInterfaces/Adjustments.cs:174-178 | Source/Office/DispatchInterfaces/AnswerWizardFiles.cs:189-193 | Source/PowerPoint/DispatchInterfaces/Adjustments.cs:205-209 | Source/Word/DispatchInterfaces/Adjustments.cs:204-208 — before extracting anything, compare `Source/Office/DispatchInterfaces/Adjustments.cs` and `Source/PowerPoint/DispatchInterfaces/Adjustments.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 4) Source/Office/DispatchInterfaces/CanvasShapes.cs:392 — Source/Office/DispatchInterfaces/CanvasShapes.cs:392-396 | Source/Office/DispatchInterfaces/GroupShapes.cs:191-195 | Source/Office/DispatchInterfaces/ShapeRange.cs:1185-1189 | Source/Office/DispatchInterfaces/Shapes.cs:694-698 — before extracting anything, compare `Source/Office/DispatchInterfaces/GroupShapes.cs` and `Source/Office/DispatchInterfaces/ShapeRange.cs` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 4) Source/Word/DispatchInterfaces/CanvasShapes.cs:479 — Source/Word/DispatchInterfaces/CanvasShapes.cs:479-483 | Source/Word/DispatchInterfaces/GroupShapes.cs:223-227 | Source/Word/DispatchInterfaces/ShapeRange.cs:1430-1434 | Source/Word/DispatchInterfaces/Shapes.cs:1454-1458 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 4) Source/PowerPoint/DispatchInterfaces/CanvasShapes.cs:419 — Source/PowerPoint/DispatchInterfaces/CanvasShapes.cs:419-423 | Source/PowerPoint/DispatchInterfaces/GroupShapes.cs:224-228 | Source/PowerPoint/DispatchInterfaces/ShapeRange.cs:1623-1627 | Source/PowerPoint/DispatchInterfaces/Shapes.cs:1523-1527 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Edited copy of a member (9 corresponding lines) · ×13
  • Edited copy of a member (9 corresponding lines) Toolbox/Toolbox/ToolboxControls/ProjectWizard/LocalizedCaptions.cs:18 — Toolbox/Toolbox/ToolboxControls/ProjectWizard/LocalizedCaptions.cs:18-26 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/LocalizedCaptions.cs:29-37 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) Source/Access/Events/DispSectionInReportEvents.cs:133 — Source/Access/Events/DispSectionInReportEvents.cs:133-141 | Source/Access/Events/_SectionInReportEvents.cs:133-141 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) Source/Access/Events/_DummyEvents.cs:54 — Source/Access/Events/_DummyEvents.cs:54-62 | Source/OWC10/Events/ISpreadsheetEventSink.cs:420-428 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) Source/Access/Events/_FormEvents.cs:374 — Source/Access/Events/_FormEvents.cs:374-382 | Source/Access/Events/_FormEvents2.cs:349-357 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) Source/Access/Events/_ReportEvents.cs:158 — Source/Access/Events/_ReportEvents.cs:158-166 | Source/Access/Events/_ReportEvents2.cs:255-263 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) Source/Excel/Events/ChartEvents.cs:305 — Source/Excel/Events/ChartEvents.cs:305-313 | Source/Excel/Events/DocEvents.cs:207-215 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) Source/Outlook/Events/ApplicationEvents_10.cs:193 — Source/Outlook/Events/ApplicationEvents_10.cs:193-201 | Source/Outlook/Events/ApplicationEvents_11.cs:250-258 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) Source/Outlook/Events/ExplorerEvents.cs:92 — Source/Outlook/Events/ExplorerEvents.cs:92-100 | Source/Outlook/Events/ExplorerEvents_10.cs:141-149 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) Source/Outlook/Events/ExplorerEvents.cs:120 — Source/Outlook/Events/ExplorerEvents.cs:120-128 | Source/Outlook/Events/ExplorerEvents_10.cs:169-177 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) Source/Outlook/Events/ExplorerEvents_10.cs:340 — Source/Outlook/Events/ExplorerEvents_10.cs:340-348 | Source/Outlook/Events/InspectorEvents_10.cs:195-203 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) Source/Outlook/Events/ItemEvents.cs:220 — Source/Outlook/Events/ItemEvents.cs:220-228 | Source/Outlook/Events/ItemEvents_10.cs:277-285 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) Source/Outlook/Events/ItemsEvents.cs:88 — Source/Outlook/Events/ItemsEvents.cs:88-96 | Source/Outlook/Events/ResultsEvents.cs:88-96 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) Source/Word/Events/DocumentEvents.cs:58 — Source/Word/Events/DocumentEvents.cs:58-66 | Source/Word/Events/DocumentEvents2.cs:120-128 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 3+ corresponding lines) · ×13
  • Edited copies of one member (3 members, 3+ corresponding lines) Source/Word/DispatchInterfaces/Indexes.cs:362 — Source/Word/DispatchInterfaces/Indexes.cs:362-364 | Source/Word/DispatchInterfaces/TablesOfContents.cs:415-417 | Source/Word/DispatchInterfaces/TablesOfFigures.cs:458-460 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 3+ corresponding lines) Source/Word/DispatchInterfaces/Range.cs:3314 — Source/Word/DispatchInterfaces/Range.cs:3314-3316 | Source/Word/DispatchInterfaces/Selection.cs:2838-2840 | Source/Word/DispatchInterfaces/_Document.cs:4318-4320 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 3+ corresponding lines) Source/Word/DispatchInterfaces/Range.cs:4231 — Source/Word/DispatchInterfaces/Range.cs:4231-4233 | Source/Word/DispatchInterfaces/_Application.cs:3312-3314 | Source/Word/Modules/Global.cs:3265-3267 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 3+ corresponding lines) Source/DAO/DispatchInterfaces/_Index.cs:267 — Source/DAO/DispatchInterfaces/_Index.cs:267-269 | Source/DAO/DispatchInterfaces/_Relation.cs:220-222 | Source/DAO/DispatchInterfaces/_TableDef.cs:376-378 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 3+ corresponding lines) Source/Word/DispatchInterfaces/Indexes.cs:347 — Source/Word/DispatchInterfaces/Indexes.cs:347-349 | Source/Word/DispatchInterfaces/TablesOfContents.cs:400-402 | Source/Word/DispatchInterfaces/TablesOfFigures.cs:443-445 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 3+ corresponding lines) Source/Word/DispatchInterfaces/Range.cs:3364 — Source/Word/DispatchInterfaces/Range.cs:3364-3366 | Source/Word/DispatchInterfaces/Selection.cs:2888-2890 | Source/Word/DispatchInterfaces/_Document.cs:4368-4370 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 3+ corresponding lines) Source/Word/DispatchInterfaces/Indexes.cs:308 — Source/Word/DispatchInterfaces/Indexes.cs:308-310 | Source/Word/DispatchInterfaces/TablesOfContents.cs:361-363 | Source/Word/DispatchInterfaces/TablesOfFigures.cs:404-406 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 3+ corresponding lines) Source/DAO/DispatchInterfaces/_Index.cs:300 — Source/DAO/DispatchInterfaces/_Index.cs:300-302 | Source/DAO/DispatchInterfaces/_Relation.cs:253-255 | Source/DAO/DispatchInterfaces/_TableDef.cs:409-411 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 3+ corresponding lines) Source/OWC10/DispatchInterfaces/ISpreadsheet.cs:930 — Source/OWC10/DispatchInterfaces/ISpreadsheet.cs:930-932 | Source/OWC10/DispatchInterfaces/Worksheet.cs:410-412 | Source/OWC10/DispatchInterfaces/_Range.cs:989-991 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 3+ corresponding lines) Source/Office/DispatchInterfaces/IMsoChartTitle.cs:89 — Source/Office/DispatchInterfaces/IMsoChartTitle.cs:89-91 | Source/Office/Interfaces/IMsoDataLabel.cs:89-91 | Source/Office/Interfaces/IMsoDataLabels.cs:92-94 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 3+ corresponding lines) Source/Word/DispatchInterfaces/Indexes.cs:333 — Source/Word/DispatchInterfaces/Indexes.cs:333-335 | Source/Word/DispatchInterfaces/TablesOfContents.cs:386-388 | Source/Word/DispatchInterfaces/TablesOfFigures.cs:429-431 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 3+ corresponding lines) Source/Word/DispatchInterfaces/Range.cs:3350 — Source/Word/DispatchInterfaces/Range.cs:3350-3352 | Source/Word/DispatchInterfaces/Selection.cs:2874-2876 | Source/Word/DispatchInterfaces/_Document.cs:4354-4356 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 3+ corresponding lines) Source/Word/DispatchInterfaces/Row.cs:520 — Source/Word/DispatchInterfaces/Row.cs:520-522 | Source/Word/DispatchInterfaces/Rows.cs:693-695 | Source/Word/DispatchInterfaces/Table.cs:1145-1147 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (5 lines × 3) · ×13
  • Duplicated block (5 lines × 3) Source/Excel/Events/AppEvents.cs:606 — Source/Excel/Events/AppEvents.cs:606-610 | Source/Excel/Events/AppEvents.cs:622-626 | Source/Excel/Events/AppEvents.cs:638-642 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (5 lines × 3) Source/Excel/Events/AppEvents.cs:670 — Source/Excel/Events/AppEvents.cs:670-674 | Source/Excel/Events/WorkbookEvents.cs:569-573 | Source/Excel/Events/WorkbookEvents.cs:805-809 — before extracting anything, compare `Source/Excel/Events/AppEvents.cs` and `Source/Excel/Events/WorkbookEvents.cs` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 377 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 3) Source/Excel/Events/ChartEvents.cs:260 — Source/Excel/Events/ChartEvents.cs:260-264 | Source/Word/Events/ApplicationEvents3.cs:442-446 | Source/Word/Events/ApplicationEvents4.cs:515-519 — before extracting anything, compare `Source/Word/Events/ApplicationEvents3.cs` and `Source/Word/Events/ApplicationEvents4.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 469 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 3) Source/Excel/Events/ChartEvents.cs:31 — Source/Excel/Events/ChartEvents.cs:31-35 | Source/Excel/Events/ChartEvents.cs:39-43 | Source/Excel/Events/ChartEvents.cs:47-51 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (5 lines × 3) Source/Excel/Events/AppEvents.cs:28 — Source/Excel/Events/AppEvents.cs:28-32 | Source/Excel/Events/WorkbookEvents.cs:79-83 | Source/Excel/Events/WorkbookEvents.cs:114-118 — before extracting anything, compare `Source/Excel/Events/AppEvents.cs` and `Source/Excel/Events/WorkbookEvents.cs` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 377 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Source/Excel/Events/WorkbookEvents.cs:84` calls `SinkArgument` and `Source/Excel/Events/AppEvents.cs:33` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 3) Source/Excel/Events/AppEvents.cs:850 — Source/Excel/Events/AppEvents.cs:850-854 | Source/Excel/Events/DocEvents.cs:267-271 | Source/Excel/Events/WorkbookEvents.cs:722-726 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
  • Duplicated block (5 lines × 3) Source/Office/Events/_CustomXMLPartEvents.cs:75 — Source/Office/Events/_CustomXMLPartEvents.cs:75-79 | Source/Office/Events/_CustomXMLPartEvents.cs:93-97 | Source/Office/Events/_CustomXMLPartEvents.cs:111-115 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (5 lines × 3) Source/Access/Events/_FormEvents.cs:161 — Source/Access/Events/_FormEvents.cs:161-165 | Source/Access/Events/_FormEvents2.cs:163-167 | Source/Access/Events/_ReportEvents2.cs:138-142 — before extracting anything, compare `Source/Access/Events/_FormEvents.cs` and `Source/Access/Events/_FormEvents2.cs` as WHOLE FILES: this scan already matched 72 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (5 lines × 3) Source/Access/Events/_FormEvents.cs:194 — Source/Access/Events/_FormEvents.cs:194-198 | Source/Access/Events/_FormEvents.cs:205-209 | Source/Access/Events/_FormEvents.cs:210-214 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (5 lines × 3) Source/Access/Events/_FormEvents.cs:280 — Source/Access/Events/_FormEvents.cs:280-284 | Source/Access/Events/_FormEvents2.cs:255-259 | Source/OWC10/Events/IChartEvents.cs:150-154 — before extracting anything, compare `Source/Access/Events/_FormEvents.cs` and `Source/Access/Events/_FormEvents2.cs` as WHOLE FILES: this scan already matched 72 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (5 lines × 3) Source/Access/Events/_ReportEvents2.cs:142 — Source/Access/Events/_ReportEvents2.cs:142-146 | Source/OWC10/Events/IChartEvents.cs:92-96 | Source/OWC10/Events/IPivotControlEvents.cs:78-82 — before extracting anything, compare `Source/OWC10/Events/IChartEvents.cs` and `Source/OWC10/Events/IPivotControlEvents.cs` as WHOLE FILES: this scan already matched 39 separate duplicated blocks between them, totalling at least 404 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 3) Source/ADODB/Events/RecordsetEvents.cs:20 — Source/ADODB/Events/RecordsetEvents.cs:20-24 | Source/ADODB/Events/RecordsetEvents.cs:36-40 | Source/ADODB/Events/RecordsetEvents.cs:90-94 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (5 lines × 3) Source/OWC10/DispatchInterfaces/LookupSchemaRelationships.cs:168 — Source/OWC10/DispatchInterfaces/LookupSchemaRelationships.cs:168-172 | Source/OWC10/DispatchInterfaces/SchemaRelationships.cs:192-196 | Source/OWC10/DispatchInterfaces/SublistSchemaRelationships.cs:168-172 — before extracting anything, compare `Source/OWC10/DispatchInterfaces/LookupSchemaRelationships.cs` and `Source/OWC10/DispatchInterfaces/SublistSchemaRelationships.cs` as WHOLE FILES: 85% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×12
  • Duplicated block (14 lines × 2) Source/Excel/Events/AppEvents.cs:208 — Source/Excel/Events/AppEvents.cs:208-221 | Source/Excel/Events/WorkbookEvents.cs:180-193 — before extracting anything, compare `Source/Excel/Events/AppEvents.cs` and `Source/Excel/Events/WorkbookEvents.cs` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 377 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (14 lines × 2) Source/Access/Events/_FormEvents.cs:44 — Source/Access/Events/_FormEvents.cs:44-57 | Source/Access/Events/_FormEvents2.cs:46-59 — before extracting anything, compare `Source/Access/Events/_FormEvents.cs` and `Source/Access/Events/_FormEvents2.cs` as WHOLE FILES: this scan already matched 72 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (14 lines × 2) Source/Word/Events/ApplicationEvents3.cs:454 — Source/Word/Events/ApplicationEvents3.cs:454-467 | Source/Word/Events/ApplicationEvents4.cs:527-540 — before extracting anything, compare `Source/Word/Events/ApplicationEvents3.cs` and `Source/Word/Events/ApplicationEvents4.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 469 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (14 lines × 2) Source/Word/Events/ApplicationEvents3.cs:485 — Source/Word/Events/ApplicationEvents3.cs:485-498 | Source/Word/Events/ApplicationEvents4.cs:558-571 — before extracting anything, compare `Source/Word/Events/ApplicationEvents3.cs` and `Source/Word/Events/ApplicationEvents4.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 469 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (14 lines × 2) Source/Outlook/Events/ExplorerEvents.cs:104 — Source/Outlook/Events/ExplorerEvents.cs:104-117 | Source/Outlook/Events/ExplorerEvents_10.cs:153-166 — before extracting anything, compare `Source/Outlook/Events/ExplorerEvents.cs` and `Source/Outlook/Events/ExplorerEvents_10.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 100 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (14 lines × 2) Source/Outlook/Events/ExplorerEvents.cs:132 — Source/Outlook/Events/ExplorerEvents.cs:132-145 | Source/Outlook/Events/ExplorerEvents_10.cs:181-194 — before extracting anything, compare `Source/Outlook/Events/ExplorerEvents.cs` and `Source/Outlook/Events/ExplorerEvents_10.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 100 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (14 lines × 2) Source/Outlook/Events/ItemEvents.cs:175 — Source/Outlook/Events/ItemEvents.cs:175-188 | Source/Outlook/Events/ItemEvents_10.cs:232-245 — before extracting anything, compare `Source/Outlook/Events/ItemEvents.cs` and `Source/Outlook/Events/ItemEvents_10.cs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 292 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (14 lines × 2) Source/Outlook/Events/ItemEvents.cs:232 — Source/Outlook/Events/ItemEvents.cs:232-245 | Source/Outlook/Events/ItemEvents_10.cs:289-302 — before extracting anything, compare `Source/Outlook/Events/ItemEvents.cs` and `Source/Outlook/Events/ItemEvents_10.cs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 292 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (14 lines × 2) Source/Outlook/Events/ItemEvents.cs:249 — Source/Outlook/Events/ItemEvents.cs:249-262 | Source/Outlook/Events/ItemEvents_10.cs:306-319 — before extracting anything, compare `Source/Outlook/Events/ItemEvents.cs` and `Source/Outlook/Events/ItemEvents_10.cs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 292 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (14 lines × 2) Source/Outlook/Events/ItemEvents.cs:339 — Source/Outlook/Events/ItemEvents.cs:339-352 | Source/Outlook/Events/ItemEvents_10.cs:396-409 — before extracting anything, compare `Source/Outlook/Events/ItemEvents.cs` and `Source/Outlook/Events/ItemEvents_10.cs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 292 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (14 lines × 2) Source/Access/Events/DispComboBoxEvents.cs:181 — Source/Access/Events/DispComboBoxEvents.cs:181-194 | Source/Access/Events/_ComboBoxEvents.cs:179-192 — before extracting anything, compare `Source/Access/Events/DispComboBoxEvents.cs` and `Source/Access/Events/_ComboBoxEvents.cs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 263 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (14 lines × 2) Source/Access/Events/_FormEvents.cs:426 — Source/Access/Events/_FormEvents.cs:426-439 | Source/Access/Events/_FormEvents2.cs:402-415 — before extracting anything, compare `Source/Access/Events/_FormEvents.cs` and `Source/Access/Events/_FormEvents2.cs` as WHOLE FILES: this scan already matched 72 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (13 lines × 3) · ×12
  • Duplicated block (13 lines × 3) Source/Word/Events/ApplicationEvents2.cs:230 — Source/Word/Events/ApplicationEvents2.cs:230-242 | Source/Word/Events/ApplicationEvents3.cs:295-307 | Source/Word/Events/ApplicationEvents4.cs:368-380 — before extracting anything, compare `Source/Word/Events/ApplicationEvents2.cs` and `Source/Word/Events/ApplicationEvents3.cs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 270 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (13 lines × 3) Source/Word/Events/ApplicationEvents2.cs:246 — Source/Word/Events/ApplicationEvents2.cs:246-258 | Source/Word/Events/ApplicationEvents3.cs:311-323 | Source/Word/Events/ApplicationEvents4.cs:384-396 — before extracting anything, compare `Source/Word/Events/ApplicationEvents2.cs` and `Source/Word/Events/ApplicationEvents3.cs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 270 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (13 lines × 3) Source/Outlook/Events/OlkTimeZoneControlEvents.cs:146 — Source/Outlook/Events/OlkTimeZoneControlEvents.cs:146-158 | Source/Outlook/Events/OlkTimeZoneControlEvents.cs:166-178 | Source/Outlook/Events/OlkTimeZoneControlEvents.cs:186-198 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/Outlook/Events/OlkTimeZoneControlEvents.cs:146` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (13 lines × 3) Source/Access/Events/DispNavigationButtonEvents.cs:42 — Source/Access/Events/DispNavigationButtonEvents.cs:42-54 | Source/Access/Events/DispNavigationControlEvents.cs:55-67 | Source/Access/Events/DispWebBrowserControlEvents.cs:65-77 — before extracting anything, compare `Source/Access/Events/DispNavigationButtonEvents.cs` and `Source/Access/Events/DispNavigationControlEvents.cs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 226 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (13 lines × 3) Source/Access/Events/_CheckBoxInOptionEvents.cs:19 — Source/Access/Events/_CheckBoxInOptionEvents.cs:19-31 | Source/Access/Events/_OptionButtonInOptionEvents.cs:19-31 | Source/Access/Events/_ToggleButtonInOptionEvents.cs:19-31 — before extracting anything, compare `Source/Access/Events/_CheckBoxInOptionEvents.cs` and `Source/Access/Events/_OptionButtonInOptionEvents.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 177 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (13 lines × 3) Source/OWC10/Events/IChartEvents.cs:430 — Source/OWC10/Events/IChartEvents.cs:430-442 | Source/OWC10/Events/IPivotControlEvents.cs:410-422 | Source/OWC10/Events/ISpreadsheetEventSink.cs:310-322 — before extracting anything, compare `Source/OWC10/Events/IChartEvents.cs` and `Source/OWC10/Events/IPivotControlEvents.cs` as WHOLE FILES: this scan already matched 39 separate duplicated blocks between them, totalling at least 404 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (13 lines × 3) Source/OWC10/Events/IChartEvents.cs:446 — Source/OWC10/Events/IChartEvents.cs:446-458 | Source/OWC10/Events/IPivotControlEvents.cs:426-438 | Source/OWC10/Events/ISpreadsheetEventSink.cs:326-338 — before extracting anything, compare `Source/OWC10/Events/IChartEvents.cs` and `Source/OWC10/Events/IPivotControlEvents.cs` as WHOLE FILES: this scan already matched 39 separate duplicated blocks between them, totalling at least 404 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (13 lines × 3) Source/OWC10/Events/IChartEvents.cs:462 — Source/OWC10/Events/IChartEvents.cs:462-474 | Source/OWC10/Events/IPivotControlEvents.cs:458-470 | Source/OWC10/Events/ISpreadsheetEventSink.cs:358-370 — before extracting anything, compare `Source/OWC10/Events/IChartEvents.cs` and `Source/OWC10/Events/IPivotControlEvents.cs` as WHOLE FILES: this scan already matched 39 separate duplicated blocks between them, totalling at least 404 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (13 lines × 3) Source/OWC10/Events/IChartEvents.cs:478 — Source/OWC10/Events/IChartEvents.cs:478-490 | Source/OWC10/Events/IPivotControlEvents.cs:442-454 | Source/OWC10/Events/ISpreadsheetEventSink.cs:342-354 — before extracting anything, compare `Source/OWC10/Events/IChartEvents.cs` and `Source/OWC10/Events/IPivotControlEvents.cs` as WHOLE FILES: this scan already matched 39 separate duplicated blocks between them, totalling at least 404 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (13 lines × 3) BuildTools/ReferenceAnalyzer/ExceptionDisplayer.cs:20 — BuildTools/ReferenceAnalyzer/ExceptionDisplayer.cs:20-32 | BuildTools/SearchAndReplace/ExceptionDisplayer.cs:20-32 | BuildTools/VersionUpdater/ExceptionDisplayer.cs:21-33 — `BuildTools/SearchAndReplace/ExceptionDisplayer.cs` and `BuildTools/VersionUpdater/ExceptionDisplayer.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 13 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (13 lines × 3) Source/NetOffice/Invoker.cs:775 — Source/NetOffice/Invoker.cs:775-787 | Source/NetOffice/Invoker.cs:808-820 | Source/NetOffice/Invoker.cs:857-869 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/NetOffice/Invoker.cs:775` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `comObject` to `object` in one and `ICOMObject` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (13 lines × 3) Source/NetOffice/Invoker.cs:891 — Source/NetOffice/Invoker.cs:891-903 | Source/NetOffice/Invoker.cs:923-935 | Source/NetOffice/Invoker.cs:958-970 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/NetOffice/Invoker.cs:891` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (10 lines × 4) · ×12
  • Duplicated block (10 lines × 4) Source/NetOffice/Invoker.cs:1067 — Source/NetOffice/Invoker.cs:1067-1076 | Source/NetOffice/Invoker.cs:1099-1108 | Source/NetOffice/Invoker.cs:1131-1140 | Source/NetOffice/Invoker.cs:1162-1171 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/NetOffice/Invoker.cs:1067` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `value` to `object` in one and `object[]` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (10 lines × 4) Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleMultiAddinConverterCS.cs:159 — Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleMultiAddinConverterCS.cs:159-168 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleMultiAddinConverterVB.cs:166-175 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleSingleAddinConverterCS.cs:145-154 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleSingleAddinConverterVB.cs:154-163 — before extracting anything, compare `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleMultiAddinConverterCS.cs` and `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleMultiAddinConverterVB.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 85 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleMultiAddinConverterCS.cs:159` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (10 lines × 4) Source/Access/Tools/COMAddin.cs:439 — Source/Access/Tools/COMAddin.cs:439-448 | Source/Excel/Tools/COMAddin.cs:438-447 | Source/PowerPoint/Tools/COMAddin.cs:440-449 | Source/Word/Tools/COMAddin.cs:441-450 — before extracting anything, compare `Source/Access/Tools/COMAddin.cs` and `Source/Excel/Tools/COMAddin.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 284 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Source/Access/Tools/COMAddin.cs:439` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 4) Source/Excel/Tools/RealtimeDataServer.cs:386 — Source/Excel/Tools/RealtimeDataServer.cs:386-395 | Source/Excel/Tools/RealtimeDataServer.cs:417-426 | Source/NetOffice/Tools/COMAddinRegisterHandler.cs:162-171 | Source/NetOffice/Tools/COMAddinUnRegisterHandler.cs:103-112 — there are 4 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Source/Excel/Tools/RealtimeDataServer.cs:386` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (10 lines × 4) Source/Excel/Events/AppEvents.cs:927 — Source/Excel/Events/AppEvents.cs:927-936 | Source/Excel/Events/AppEvents.cs:977-986 | Source/Excel/Events/AppEvents.cs:991-1000 | Source/Excel/Events/AppEvents.cs:1005-1014 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (10 lines × 4) Source/Excel/Events/DocEvents.cs:247 — Source/Excel/Events/DocEvents.cs:247-256 | Source/Excel/Events/DocEvents.cs:337-346 | Source/Excel/Events/WorkbookEvents.cs:579-588 | Source/Excel/Events/WorkbookEvents.cs:593-602 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart.
  • Duplicated block (10 lines × 4) Source/VBIDE/Events/_dispReferencesEvents.cs:57 — Source/VBIDE/Events/_dispReferencesEvents.cs:57-66 | Source/VBIDE/Events/_dispReferencesEvents.cs:71-80 | Source/VBIDE/Events/_dispReferences_Events.cs:57-66 | Source/VBIDE/Events/_dispReferences_Events.cs:71-80 — before extracting anything, compare `Source/VBIDE/Events/_dispReferencesEvents.cs` and `Source/VBIDE/Events/_dispReferences_Events.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (10 lines × 4) Source/Word/Events/ApplicationEvents4.cs:729 — Source/Word/Events/ApplicationEvents4.cs:729-738 | Source/Word/Events/ApplicationEvents4.cs:779-788 | Source/Word/Events/ApplicationEvents4.cs:793-802 | Source/Word/Events/ApplicationEvents4.cs:807-816 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (10 lines × 4) Source/Outlook/Events/ApplicationEvents_10.cs:166 — Source/Outlook/Events/ApplicationEvents_10.cs:166-175 | Source/Outlook/Events/ApplicationEvents_10.cs:180-189 | Source/Outlook/Events/ApplicationEvents_11.cs:223-232 | Source/Outlook/Events/ApplicationEvents_11.cs:237-246 — before extracting anything, compare `Source/Outlook/Events/ApplicationEvents_10.cs` and `Source/Outlook/Events/ApplicationEvents_11.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 122 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (10 lines × 4) Source/Access/Events/_ComboBoxEvents.cs:38 — Source/Access/Events/_ComboBoxEvents.cs:38-47 | Source/Access/Events/_CommandButtonEvents.cs:23-32 | Source/Access/Events/_CustomControlEvents.cs:24-33 | Source/Access/Events/_TextBoxEvents.cs:31-40 — before extracting anything, compare `Source/Access/Events/_ComboBoxEvents.cs` and `Source/Access/Events/_CommandButtonEvents.cs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 247 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (10 lines × 4) Source/Access/Events/_FormEvents.cs:849 — Source/Access/Events/_FormEvents.cs:849-858 | Source/Access/Events/_FormEvents.cs:868-877 | Source/Access/Events/_FormEvents.cs:889-898 | Source/Access/Events/_FormEvents.cs:908-917 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (10 lines × 4) Source/MSComctlLib/Events/ITreeViewEvents.cs:203 — Source/MSComctlLib/Events/ITreeViewEvents.cs:203-212 | Source/MSComctlLib/Events/ITreeViewEvents.cs:217-226 | Source/MSComctlLib/Events/ITreeViewEvents.cs:231-240 | Source/MSComctlLib/Events/ITreeViewEvents.cs:375-384 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Edited copies of one member (3 members, 9+ corresponding lines) · ×11
  • Edited copies of one member (3 members, 9+ corresponding lines) Source/Excel/DispatchInterfaces/ModelTableNames.cs:234 — Source/Excel/DispatchInterfaces/ModelTableNames.cs:234-242 | Source/Excel/Interfaces/IModelTableNames.cs:227-235 | Source/Office/DispatchInterfaces/AnswerWizardFiles.cs:223-231 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) Source/Access/Events/_FormEvents.cs:337 — Source/Access/Events/_FormEvents.cs:337-345 | Source/Access/Events/_FormEvents2.cs:312-320 | Source/Access/Events/_ReportEvents2.cs:277-285 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) Source/Access/Events/_FormEvents.cs:348 — Source/Access/Events/_FormEvents.cs:348-356 | Source/Access/Events/_FormEvents2.cs:323-331 | Source/Access/Events/_ReportEvents2.cs:266-274 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) Source/Access/Events/_FormEvents.cs:926 — Source/Access/Events/_FormEvents.cs:926-934 | Source/Access/Events/_FormEvents2.cs:804-812 | Source/OWC10/Events/IPivotControlEvents.cs:289-297 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) Source/Access/Events/_FormEvents.cs:937 — Source/Access/Events/_FormEvents.cs:937-945 | Source/Access/Events/_FormEvents2.cs:815-823 | Source/OWC10/Events/IPivotControlEvents.cs:300-308 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) Source/Access/Events/_FormEvents.cs:961 — Source/Access/Events/_FormEvents.cs:961-969 | Source/Access/Events/_FormEvents2.cs:840-848 | Source/OWC10/Events/IPivotControlEvents.cs:278-286 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) Source/Access/Events/_FormEvents.cs:972 — Source/Access/Events/_FormEvents.cs:972-980 | Source/Access/Events/_FormEvents2.cs:851-859 | Source/OWC10/Events/IPivotControlEvents.cs:267-275 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) Source/Access/Events/_FormEvents.cs:1056 — Source/Access/Events/_FormEvents.cs:1056-1064 | Source/Access/Events/_FormEvents2.cs:935-943 | Source/OWC10/Events/IChartEvents.cs:195-203 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) Source/Excel/Events/WorkbookEvents.cs:276 — Source/Excel/Events/WorkbookEvents.cs:276-284 | Source/Word/Events/DocumentEvents.cs:69-77 | Source/Word/Events/DocumentEvents2.cs:131-139 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) Source/Outlook/Events/ApplicationEvents.cs:91 — Source/Outlook/Events/ApplicationEvents.cs:91-99 | Source/Outlook/Events/ApplicationEvents_10.cs:105-113 | Source/Outlook/Events/ApplicationEvents_11.cs:162-170 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) Source/Word/Events/ApplicationEvents2.cs:138 — Source/Word/Events/ApplicationEvents2.cs:138-146 | Source/Word/Events/ApplicationEvents3.cs:203-211 | Source/Word/Events/ApplicationEvents4.cs:276-284 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×11
  • Duplicated block (16 lines × 2) Source/Word/Tools/COMAddin.cs:1082 — Source/Word/Tools/COMAddin.cs:1082-1097 | Source/Word/Tools/DocumentInspectorBase.cs:269-284 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (16 lines × 2) Source/Access/Events/_FormEvents2.cs:152 — Source/Access/Events/_FormEvents2.cs:152-167 | Source/Access/Events/_ReportEvents2.cs:127-142 — before extracting anything, compare `Source/Access/Events/_FormEvents2.cs` and `Source/Access/Events/_ReportEvents2.cs` as WHOLE FILES: this scan already matched 45 separate duplicated blocks between them, totalling at least 418 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Access/Events/_FormEvents2.cs:148` calls `MethodImpl`, `DispId`, `Error` and `Source/Access/Events/_ReportEvents2.cs:126` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (16 lines × 2) Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/NetOfficeSupportTable.cs:323 — Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/NetOfficeSupportTable.cs:323-338 | Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/NetOfficeSupportTable.cs:344-359 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/NetOfficeSupportTable.cs:323` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (16 lines × 2) Source/Excel/Events/AppEvents.cs:365 — Source/Excel/Events/AppEvents.cs:365-380 | Source/Excel/Events/WorkbookEvents.cs:451-466 — before extracting anything, compare `Source/Excel/Events/AppEvents.cs` and `Source/Excel/Events/WorkbookEvents.cs` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 377 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (16 lines × 2) Source/Excel/Events/AppEvents.cs:384 — Source/Excel/Events/AppEvents.cs:384-399 | Source/Excel/Events/WorkbookEvents.cs:470-485 — before extracting anything, compare `Source/Excel/Events/AppEvents.cs` and `Source/Excel/Events/WorkbookEvents.cs` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 377 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (16 lines × 2) Source/Outlook/Classes/MobileItem.cs:741 — Source/Outlook/Classes/MobileItem.cs:741-756 | Source/Outlook/Classes/SharingItem.cs:768-783 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (16 lines × 2) Source/Outlook/Events/ItemEvents.cs:142 — Source/Outlook/Events/ItemEvents.cs:142-157 | Source/Outlook/Events/ItemEvents_10.cs:199-214 — before extracting anything, compare `Source/Outlook/Events/ItemEvents.cs` and `Source/Outlook/Events/ItemEvents_10.cs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 292 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (16 lines × 2) Source/Access/Classes/FormOld.cs:1477 — Source/Access/Classes/FormOld.cs:1477-1492 | Source/Access/Classes/FormOldV10.cs:1477-1492 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (16 lines × 2) Source/Access/Classes/ReportOld.cs:304 — Source/Access/Classes/ReportOld.cs:304-319 | Source/Access/Classes/ReportOldV10.cs:304-319 — before extracting anything, compare `Source/Access/Classes/ReportOld.cs` and `Source/Access/Classes/ReportOldV10.cs` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (16 lines × 2) Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/NetOfficeSupportTable.cs:85 — Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/NetOfficeSupportTable.cs:85-100 | Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/NetOfficeSupportTable.cs:113-128 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (16 lines × 2) Source/NetOffice/Tools/CustomUIAttribute.cs:104 — Source/NetOffice/Tools/CustomUIAttribute.cs:104-119 | Source/Outlook/Tools/OlCustomUIAttribute.cs:113-128 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D29 · Static Analysis (SAST) · REDACTED · ×10
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (14 lines × 3) · ×10
  • Duplicated block (14 lines × 3) Source/Word/Events/ApplicationEvents2.cs:163 — Source/Word/Events/ApplicationEvents2.cs:163-176 | Source/Word/Events/ApplicationEvents3.cs:228-241 | Source/Word/Events/ApplicationEvents4.cs:301-314 — before extracting anything, compare `Source/Word/Events/ApplicationEvents2.cs` and `Source/Word/Events/ApplicationEvents3.cs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 270 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (14 lines × 3) Source/Word/Events/ApplicationEvents2.cs:180 — Source/Word/Events/ApplicationEvents2.cs:180-193 | Source/Word/Events/ApplicationEvents3.cs:245-258 | Source/Word/Events/ApplicationEvents4.cs:318-331 — before extracting anything, compare `Source/Word/Events/ApplicationEvents2.cs` and `Source/Word/Events/ApplicationEvents3.cs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 270 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (14 lines × 3) Source/Word/Events/ApplicationEvents2.cs:276 — Source/Word/Events/ApplicationEvents2.cs:276-289 | Source/Word/Events/ApplicationEvents3.cs:341-354 | Source/Word/Events/ApplicationEvents4.cs:414-427 — before extracting anything, compare `Source/Word/Events/ApplicationEvents2.cs` and `Source/Word/Events/ApplicationEvents3.cs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 270 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (14 lines × 3) Source/Word/Events/ApplicationEvents2.cs:293 — Source/Word/Events/ApplicationEvents2.cs:293-306 | Source/Word/Events/ApplicationEvents3.cs:358-371 | Source/Word/Events/ApplicationEvents4.cs:431-444 — before extracting anything, compare `Source/Word/Events/ApplicationEvents2.cs` and `Source/Word/Events/ApplicationEvents3.cs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 270 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (14 lines × 3) Source/Outlook/Events/ApplicationEvents.cs:75 — Source/Outlook/Events/ApplicationEvents.cs:75-88 | Source/Outlook/Events/ApplicationEvents_10.cs:89-102 | Source/Outlook/Events/ApplicationEvents_11.cs:146-159 — before extracting anything, compare `Source/Outlook/Events/ApplicationEvents.cs` and `Source/Outlook/Events/ApplicationEvents_10.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 82 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (14 lines × 3) Source/Access/Events/_FormEvents.cs:719 — Source/Access/Events/_FormEvents.cs:719-732 | Source/Access/Events/_FormEvents2.cs:696-709 | Source/Access/Events/_ReportEvents2.cs:486-499 — before extracting anything, compare `Source/Access/Events/_FormEvents.cs` and `Source/Access/Events/_FormEvents2.cs` as WHOLE FILES: this scan already matched 72 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (14 lines × 3) Source/MSComctlLib/Events/ISliderEvents.cs:155 — Source/MSComctlLib/Events/ISliderEvents.cs:155-168 | Source/MSComctlLib/Events/ITabStripEvents.cs:152-165 | Source/MSComctlLib/Events/ListViewEvents.cs:226-239 — before extracting anything, compare `Source/MSComctlLib/Events/ISliderEvents.cs` and `Source/MSComctlLib/Events/ITabStripEvents.cs` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 295 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (14 lines × 3) Source/MSComctlLib/Events/ISliderEvents.cs:187 — Source/MSComctlLib/Events/ISliderEvents.cs:187-200 | Source/MSComctlLib/Events/ITabStripEvents.cs:169-182 | Source/MSComctlLib/Events/ListViewEvents.cs:243-256 — before extracting anything, compare `Source/MSComctlLib/Events/ISliderEvents.cs` and `Source/MSComctlLib/Events/ITabStripEvents.cs` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 295 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (14 lines × 3) Toolbox/Toolbox/ToolboxControls/RegistryEditor/RegistryEditorControl.cs:1298 — Toolbox/Toolbox/ToolboxControls/RegistryEditor/RegistryEditorControl.cs:1298-1311 | Toolbox/Toolbox/ToolboxControls/RegistryEditor/RegistryEditorControl.cs:1320-1333 | Toolbox/Toolbox/ToolboxControls/RegistryEditor/RegistryEditorControl.cs:1342-1355 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Toolbox/Toolbox/ToolboxControls/RegistryEditor/RegistryEditorControl.cs:1298` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 3) Examples/Excel/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:19 — Examples/Excel/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:19-32 | Examples/PowerPoint/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:19-32 | Examples/Word/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:19-32 — before extracting anything, compare `Examples/Excel/IExtensibility COMAddin Examples/ClassicUI/Addin.cs` and `Examples/PowerPoint/IExtensibility COMAddin Examples/ClassicUI/Addin.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 91 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
AX2 · Stateful singletons · Stateful shared instance · ×9
  • Stateful shared instance: Core Source/NetOffice/Core.cs:82 — `Core` keeps one instance of itself in the static `_default`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_initalized, _wrapperTypeCache, _proxyTypeCache; e.g. `_initalized` at line 470).
  • Stateful shared instance: Settings Source/NetOffice/Settings.cs:11 — `Settings` keeps one instance of itself in the static `_default`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_enableProxyManagement, _enableKnownReferenceInspection, _enableAutoDisposeEventArguments, _exceptionMessageBehavior, _exceptionDefaultMessage, _exceptionDiagnosticsMessage; e.g. `_enableProxyManagement` at line 116).
  • Stateful shared instance: DebugConsole Source/NetOffice/Trace/DebugConsole.cs:13 — `DebugConsole` keeps one instance of itself in the static `_default`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_name, _messageList, EnableSharedOutput; e.g. `_name` at line 288).
  • Stateful shared instance: RichTextDialog Source/Office.Extensions/Dialogs/RichTextDialog.cs:12 — `RichTextDialog` is not registered, but `DialogUtilsEx` creates it and keeps it in the static `_openNonModalDialogs`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_timeoutMode; e.g. `_timeoutMode` at line 200).
  • Stateful shared instance: wnd Toolbox/Toolbox/ToolboxControls/ApplicationObserver/HotKey.cs:96 — `wnd` keeps one instance of itself in the static `def`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (hotkeys; e.g. `hotkeys` at line 124).
  • Stateful shared instance: TwitterTimer Examples/Other/Outlook Addin - Use Twitter/Outlook Addin - Use Twitter/Twitter/TwitterTimer.cs:20 — `TwitterTimer` is not registered, but `TwitterPane` creates it and keeps it in the static `Client`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_enabled, Timer, _intervalSeconds, _consumerKey, _consumerSecret, _accessToken; e.g. `_enabled` at line 71).
  • Stateful shared instance: CurrentAppDomain Source/NetOffice/Loader/CurrentAppDomain.cs:11 — `CurrentAppDomain` is not registered, but the singleton `Core` creates it and keeps it in `CoreDomain`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (_assemblyVersion; e.g. `_assemblyVersion` at line 64).
  • Stateful shared instance: RetryMessageFilter Source/NetOffice/Filtering/RetryMessageFilter.cs:11 — `RetryMessageFilter` is not registered, but the singleton `Settings` creates it and keeps it in `_messageFilter`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (_retryMode, _logMode, _messageFilter; e.g. `_retryMode` at line 90).
  • Stateful shared instance: PerformanceTrace Source/NetOffice/Trace/PerformanceTrace.cs:12 — `PerformanceTrace` is not registered, but the singleton `Settings` creates it and keeps it in `_performanceTrace`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (_enabled; e.g. `_enabled` at line 169).
D4 · Code Duplication · Edited copy of a member (14 corresponding lines) · ×9
  • Edited copy of a member (14 corresponding lines) Source/Excel/Events/AppEvents.cs:711 — Source/Excel/Events/AppEvents.cs:711-724 | Source/Word/Events/ApplicationEvents4.cs:660-673 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) Source/Analyzers/NetOffice.Analyzers/EventValidateRaiseConsistencyAnalyzer.cs:156 — Source/Analyzers/NetOffice.Analyzers/EventValidateRaiseConsistencyAnalyzer.cs:156-169 | Source/Analyzers/NetOffice.Analyzers/EventValidateRaiseConsistencyAnalyzer.cs:172-185 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) Source/MSComctlLib/Events/DImageComboEvents.cs:152 — Source/MSComctlLib/Events/DImageComboEvents.cs:152-165 | Source/MSComctlLib/Events/DImageComboEvents.cs:168-181 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) Source/Office.Extensions/TrayMenuUtils/TrayMenuItems.cs:195 — Source/Office.Extensions/TrayMenuUtils/TrayMenuItems.cs:195-209 | Source/Office.Extensions/TrayMenuUtils/TrayMenuItems.cs:217-230 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) Source/Access/Classes/CheckBox.cs:570 — Source/Access/Classes/CheckBox.cs:570-583 | Source/Access/Classes/_CheckBoxInOption.cs:555-568 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) Source/Access/Classes/OptionButton.cs:570 — Source/Access/Classes/OptionButton.cs:570-583 | Source/Access/Classes/_OptionButtonInOption.cs:555-568 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) Source/Access/Classes/ToggleButton.cs:570 — Source/Access/Classes/ToggleButton.cs:570-583 | Source/Access/Classes/_ToggleButtonInOption.cs:555-568 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) Examples/Excel/NetOffice COMAddin Examples/06 Shim/Addin.cs:20 — Examples/Excel/NetOffice COMAddin Examples/06 Shim/Addin.cs:20-33 | Examples/Excel/NetOffice COMAddin Examples/06 Shim/Addin.cs:37-50 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) REDACTED:51 — REDACTED:51-65 | Examples/Other/Excel Addin - Google Translation/ServerHost/FormMain.cs:192-205 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (11 corresponding lines) · ×9
  • Edited copy of a member (11 corresponding lines) Source/Office.Extensions/TrayMenuUtils/TrayMenu.cs:300 — Source/Office.Extensions/TrayMenuUtils/TrayMenu.cs:300-310 | Source/Office.Extensions/TrayMenuUtils/TrayMenu.cs:333-343 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) Source/Outlook/Events/ApplicationEvents_10.cs:129 — Source/Outlook/Events/ApplicationEvents_10.cs:129-140 | Source/Outlook/Events/ApplicationEvents_11.cs:187-197 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) Source/Outlook/Events/AccountSelectorEvents.cs:51 — Source/Outlook/Events/AccountSelectorEvents.cs:51-61 | Source/Outlook/Events/AccountsEvents.cs:51-62 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) Source/Outlook/Events/_ViewsEvents.cs:56 — Source/Outlook/Events/_ViewsEvents.cs:56-66 | Source/Outlook/Events/_ViewsEvents.cs:69-79 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) RegAddin/RegAddin/RegFile/RegValueConverter.cs:138 — RegAddin/RegAddin/RegFile/RegValueConverter.cs:138-148 | RegAddin/RegAddin/RegFile/RegValueConverter.cs:151-162 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) Toolbox/Toolbox/ToolboxControls/ProxyView/RotEntryCollection.cs:89 — Toolbox/Toolbox/ToolboxControls/ProxyView/RotEntryCollection.cs:89-99 | Toolbox/Toolbox/ToolboxControls/ProxyView/WindowEntryCollection.cs:95-105 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) Examples/ExampleBase/ExampleForm.cs:61 — Examples/ExampleBase/ExampleForm.cs:61-71 | Tutorials/TutorialsBase/TutorialForm.cs:69-79 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) Source/Excel/Tools/COMAddin.cs:401 — Source/Excel/Tools/COMAddin.cs:401-411 | Source/VBIDE/Tools/COMAddin.cs:317-327 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) Source/Excel/Tools/COMAddin.cs:414 — Source/Excel/Tools/COMAddin.cs:414-424 | Source/VBIDE/Tools/COMAddin.cs:330-340 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (10 corresponding lines) · ×9
  • Edited copy of a member (10 corresponding lines) Toolbox/Toolbox/AssemblyInfo.cs:20 — Toolbox/Toolbox/AssemblyInfo.cs:20-29 | RegAddin/RegAddin/About.cs:14-25 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) Source/Word/DispatchInterfaces/DiagramNode.cs:390 — Source/Word/DispatchInterfaces/DiagramNode.cs:390-400 | Source/OWC10/DispatchInterfaces/IXRangeEnum.cs:184-193 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) Toolbox/Toolbox/Utils/Ressources/RessourceUtils.cs:24 — Toolbox/Toolbox/Utils/Ressources/RessourceUtils.cs:24-33 | Toolbox/Toolbox/Utils/Ressources/RessourceUtils.cs:41-50 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) Source/NetOffice/Running/ProxyInformation.cs:55 — Source/NetOffice/Running/ProxyInformation.cs:55-66 | Toolbox/Toolbox/ToolboxControls/ProxyView/Entry.cs:20-29 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) Source/NetOffice/Contribution/Controls/InstanceMonitor.cs:333 — Source/NetOffice/Contribution/Controls/InstanceMonitor.cs:333-342 | Source/Office.Extensions/TrayMenuUtils/TrayMenuMonitorItemControl.cs:433-442 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) Examples/ExampleBase/FinishForm.cs:65 — Examples/ExampleBase/FinishForm.cs:65-80 | Tutorials/TutorialsBase/FinishForm.cs:47-56 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) Toolbox/Toolbox/ToolboxControls/ApplicationObserver/ApplicationObserverControl.cs:330 — Toolbox/Toolbox/ToolboxControls/ApplicationObserver/ApplicationObserverControl.cs:330-339 | Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/ReportControl.cs:561-571 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) Toolbox/Toolbox/ToolboxControls/ApplicationObserver/ApplicationObserverControl.cs:342 — Toolbox/Toolbox/ToolboxControls/ApplicationObserver/ApplicationObserverControl.cs:342-351 | Toolbox/Toolbox/ToolboxControls/OutlookSecurity/OutlookSecurityControl.cs:250-261 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) Tutorials/TutorialsBase/AreaForm.cs:85 — Tutorials/TutorialsBase/AreaForm.cs:85-94 | Tutorials/TutorialsBase/TutorialForm.cs:82-92 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (4 corresponding lines) · ×9
  • Edited copy of a member (4 corresponding lines) Source/NetOffice/CoreExtensions/CoreMethodExtensions.cs:502 — Source/NetOffice/CoreExtensions/CoreMethodExtensions.cs:502-506 | Source/NetOffice/CoreExtensions/CorePropertyGetExtensions.cs:219-222 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) Source/NetOffice/CoreExtensions/CoreMethodExtensions.cs:1307 — Source/NetOffice/CoreExtensions/CoreMethodExtensions.cs:1307-1311 | Source/NetOffice/CoreExtensions/CorePropertyGetExtensions.cs:912-915 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) Source/Word/DispatchInterfaces/_Application.cs:2845 — Source/Word/DispatchInterfaces/_Application.cs:2845-2848 | Source/Word/Modules/Global.cs:2798-2801 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) Source/NetOffice/CoreExtensions/CoreMethodExtensions.cs:663 — Source/NetOffice/CoreExtensions/CoreMethodExtensions.cs:663-667 | Source/NetOffice/CoreExtensions/CorePropertyGetExtensions.cs:318-321 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) Source/NetOffice/CoreExtensions/CoreMethodExtensions.cs:824 — Source/NetOffice/CoreExtensions/CoreMethodExtensions.cs:824-828 | Source/NetOffice/CoreExtensions/CorePropertyGetExtensions.cs:714-717 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) Source/NetOffice/CoreExtensions/CoreMethodExtensions.cs:985 — Source/NetOffice/CoreExtensions/CoreMethodExtensions.cs:985-989 | Source/NetOffice/CoreExtensions/CorePropertyGetExtensions.cs:615-618 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) Source/NetOffice/CoreExtensions/CoreMethodExtensions.cs:1146 — Source/NetOffice/CoreExtensions/CoreMethodExtensions.cs:1146-1150 | Source/NetOffice/CoreExtensions/CorePropertyGetExtensions.cs:1111-1114 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) Source/NetOffice/CoreExtensions/CoreMethodExtensions.cs:1468 — Source/NetOffice/CoreExtensions/CoreMethodExtensions.cs:1468-1472 | Source/NetOffice/CoreExtensions/CorePropertyGetExtensions.cs:1210-1213 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) Source/NetOffice/CoreExtensions/CoreMethodExtensions.cs:2131 — Source/NetOffice/CoreExtensions/CoreMethodExtensions.cs:2131-2135 | Source/NetOffice/CoreExtensions/CorePropertyGetExtensions.cs:1819-1822 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (11 lines × 4) · ×9
  • Duplicated block (11 lines × 4) Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/NetOfficeSupportTable.cs:128 — Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/NetOfficeSupportTable.cs:128-138 | Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/NetOfficeSupportTable.cs:323-333 | Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/NetOfficeSupportTable.cs:344-354 | Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/NetOfficeSupportTable.cs:371-381 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (11 lines × 4) Source/Excel/Events/AppEvents.cs:864 — Source/Excel/Events/AppEvents.cs:864-874 | Source/Excel/Events/WorkbookEvents.cs:736-746 | Source/Excel/Events/WorkbookEvents.cs:759-769 | Source/Excel/Events/WorkbookEvents.cs:782-792 — before extracting anything, compare `Source/Excel/Events/AppEvents.cs` and `Source/Excel/Events/WorkbookEvents.cs` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 377 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Source/Excel/Events/AppEvents.cs:864` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (11 lines × 4) Source/ADODB/Events/ConnectionEvents.cs:121 — Source/ADODB/Events/ConnectionEvents.cs:121-131 | Source/ADODB/Events/ConnectionEvents.cs:159-169 | Source/ADODB/Events/ConnectionEvents.cs:177-187 | Source/ADODB/Events/ConnectionEvents.cs:273-283 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/ADODB/Events/ConnectionEvents.cs:121` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (11 lines × 4) Source/Access/Tools/COMAddin.cs:209 — Source/Access/Tools/COMAddin.cs:209-219 | Source/Outlook/Tools/COMAddin.cs:174-184 | Source/PowerPoint/Tools/COMAddin.cs:210-220 | Source/Word/Tools/COMAddin.cs:212-222 — before extracting anything, compare `Source/Access/Tools/COMAddin.cs` and `Source/Outlook/Tools/COMAddin.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 276 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 4) Source/Access/Tools/COMAddin.cs:223 — Source/Access/Tools/COMAddin.cs:223-233 | Source/Outlook/Tools/COMAddin.cs:188-198 | Source/PowerPoint/Tools/COMAddin.cs:224-234 | Source/Word/Tools/COMAddin.cs:226-236 — before extracting anything, compare `Source/Access/Tools/COMAddin.cs` and `Source/Outlook/Tools/COMAddin.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 276 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 4) Source/Access/Tools/COMAddin.cs:237 — Source/Access/Tools/COMAddin.cs:237-247 | Source/Outlook/Tools/COMAddin.cs:202-212 | Source/PowerPoint/Tools/COMAddin.cs:238-248 | Source/Word/Tools/COMAddin.cs:240-250 — before extracting anything, compare `Source/Access/Tools/COMAddin.cs` and `Source/Outlook/Tools/COMAddin.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 276 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 4) Source/Access/Tools/COMAddin.cs:251 — Source/Access/Tools/COMAddin.cs:251-261 | Source/Outlook/Tools/COMAddin.cs:216-226 | Source/PowerPoint/Tools/COMAddin.cs:252-262 | Source/Word/Tools/COMAddin.cs:254-264 — before extracting anything, compare `Source/Access/Tools/COMAddin.cs` and `Source/Outlook/Tools/COMAddin.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 276 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 4) Source/Access/Tools/COMAddin.cs:265 — Source/Access/Tools/COMAddin.cs:265-275 | Source/Outlook/Tools/COMAddin.cs:230-240 | Source/PowerPoint/Tools/COMAddin.cs:266-276 | Source/Word/Tools/COMAddin.cs:268-278 — before extracting anything, compare `Source/Access/Tools/COMAddin.cs` and `Source/Outlook/Tools/COMAddin.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 276 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 4) REDACTED:142 — REDACTED:142-152 | REDACTED:213-223 | REDACTED:154-164 | REDACTED:153-163 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 106 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (6 lines × 5) · ×9
  • Duplicated block (6 lines × 5) Source/OWC10/Events/IChartEvents.cs:281 — Source/OWC10/Events/IChartEvents.cs:281-286 | Source/OWC10/Events/IPivotControlEvents.cs:542-547 | Source/OWC10/Events/IPivotControlEvents.cs:560-565 | Source/OWC10/Events/ISpreadsheetEventSink.cs:253-258 | Source/OWC10/Events/ISpreadsheetEventSink.cs:271-276 — before extracting anything, compare `Source/OWC10/Events/IChartEvents.cs` and `Source/OWC10/Events/IPivotControlEvents.cs` as WHOLE FILES: this scan already matched 39 separate duplicated blocks between them, totalling at least 404 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (6 lines × 5) Source/Word/Events/ApplicationEvents2.cs:200 — Source/Word/Events/ApplicationEvents2.cs:200-205 | Source/Word/Events/ApplicationEvents3.cs:265-270 | Source/Word/Events/ApplicationEvents3.cs:519-524 | Source/Word/Events/ApplicationEvents4.cs:338-343 | Source/Word/Events/ApplicationEvents4.cs:592-597 — before extracting anything, compare `Source/Word/Events/ApplicationEvents2.cs` and `Source/Word/Events/ApplicationEvents3.cs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 270 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Source/Word/Events/ApplicationEvents2.cs:200` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (6 lines × 5) Source/MSComctlLib/Events/DImageComboEvents.cs:43 — Source/MSComctlLib/Events/DImageComboEvents.cs:43-48 | Source/MSComctlLib/Events/ISliderEvents.cs:29-34 | Source/MSComctlLib/Events/ITabStripEvents.cs:29-34 | Source/MSComctlLib/Events/ITreeViewEvents.cs:57-62 | Source/MSComctlLib/Events/ListViewEvents.cs:52-57 — before extracting anything, compare `Source/MSComctlLib/Events/DImageComboEvents.cs` and `Source/MSComctlLib/Events/ISliderEvents.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 192 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (6 lines × 5) Source/Excel/Events/AppEvents.cs:22 — Source/Excel/Events/AppEvents.cs:22-27 | Source/Excel/Events/AppEvents.cs:28-33 | Source/Excel/Events/AppEvents.cs:56-61 | Source/Excel/Events/WorkbookEvents.cs:73-78 | Source/Excel/Events/WorkbookEvents.cs:108-113 — before extracting anything, compare `Source/Excel/Events/AppEvents.cs` and `Source/Excel/Events/WorkbookEvents.cs` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 377 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Source/Excel/Events/WorkbookEvents.cs:117` calls `SinkArgument` and `Source/Excel/Events/AppEvents.cs:65` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (6 lines × 5) Source/Excel/Events/AppEvents.cs:355 — Source/Excel/Events/AppEvents.cs:355-360 | Source/Excel/Events/AppEvents.cs:451-456 | Source/Excel/Events/DocEvents.cs:267-272 | Source/Excel/Events/WorkbookEvents.cs:441-446 | Source/Excel/Events/WorkbookEvents.cs:537-542 — there are 5 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 5 sites; resolving a subset leaves the remainder to drift apart.
  • Duplicated block (6 lines × 5) Source/Excel/Events/AppEvents.cs:670 — Source/Excel/Events/AppEvents.cs:670-675 | Source/Excel/Events/AppEvents.cs:686-691 | Source/Excel/Events/AppEvents.cs:702-707 | Source/Excel/Events/WorkbookEvents.cs:569-574 | Source/Excel/Events/WorkbookEvents.cs:805-810 — before extracting anything, compare `Source/Excel/Events/AppEvents.cs` and `Source/Excel/Events/WorkbookEvents.cs` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 377 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (6 lines × 5) Source/ADODB/Events/ConnectionEvents.cs:19 — Source/ADODB/Events/ConnectionEvents.cs:19-24 | Source/ADODB/Events/ConnectionEvents.cs:27-32 | Source/ADODB/Events/ConnectionEvents.cs:34-39 | Source/ADODB/Events/ConnectionEvents.cs:41-46 | Source/ADODB/Events/ConnectionEvents.cs:78-83 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (6 lines × 5) Source/ADODB/Events/RecordsetEvents.cs:27 — Source/ADODB/Events/RecordsetEvents.cs:27-32 | Source/ADODB/Events/RecordsetEvents.cs:44-49 | Source/ADODB/Events/RecordsetEvents.cs:59-64 | Source/ADODB/Events/RecordsetEvents.cs:74-79 | Source/ADODB/Events/RecordsetEvents.cs:96-101 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/ADODB/Events/RecordsetEvents.cs:44` calls `SinkArgument` and `Source/ADODB/Events/RecordsetEvents.cs:59` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (6 lines × 5) Source/Access/Tools/COMAddin.cs:55 — Source/Access/Tools/COMAddin.cs:55-60 | Source/Excel/Tools/COMAddin.cs:55-60 | Source/Office/Tools/COMAddin.cs:54-59 | Source/PowerPoint/Tools/COMAddin.cs:56-61 | Source/Word/Tools/COMAddin.cs:58-63 — before extracting anything, compare `Source/Access/Tools/COMAddin.cs` and `Source/Excel/Tools/COMAddin.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 284 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D17 · Explicit Debt · CommentedOutCode · ×8
  • CommentedOutCode RegAddin/RegAddinTest/Program.cs:16 — 4 consecutive commented-code lines
  • CommentedOutCode RegAddin/RegAddinTest/Program.cs:45 — 4 consecutive commented-code lines
  • CommentedOutCode Source/NetOffice/COMObject.cs:1384 — 4 consecutive commented-code lines
  • CommentedOutCode Source/NetOffice/COMObject.cs:1403 — 4 consecutive commented-code lines
  • CommentedOutCode Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ConverterUtils.cs:48 — 4 consecutive commented-code lines
  • CommentedOutCode RegAddin/RegAddinTest/Program.cs:21 — 10 consecutive commented-code lines
  • CommentedOutCode RegAddin/RegAddinTest/Program.cs:32 — 6 consecutive commented-code lines
  • CommentedOutCode Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/Converter.cs:509 — 6 consecutive commented-code lines
D4 · Code Duplication · Edited copy of a member (7 corresponding lines) · ×8
  • Edited copy of a member (7 corresponding lines) Source/Office/DispatchInterfaces/IBlogExtensibility.cs:250 — Source/Office/DispatchInterfaces/IBlogExtensibility.cs:250-258 | Source/Office/DispatchInterfaces/IBlogExtensibility.cs:276-282 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) Source/Office/DispatchInterfaces/EncryptionProvider.cs:228 — Source/Office/DispatchInterfaces/EncryptionProvider.cs:228-234 | Source/Office/DispatchInterfaces/IBlogExtensibility.cs:151-157 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) Source/Word/Tools/DocumentInspectorAttribute.cs:74 — Source/Word/Tools/DocumentInspectorAttribute.cs:74-80 | Source/Outlook/Tools/FormRegionAttribute.cs:158-164 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) Source/Office/DispatchInterfaces/IBlogExtensibility.cs:294 — Source/Office/DispatchInterfaces/IBlogExtensibility.cs:294-300 | Source/OWC10/DispatchInterfaces/IXRangeEnum.cs:213-219 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) Toolbox/Toolbox/ToolboxControls/ProxyView/RotEntryCollection.cs:77 — Toolbox/Toolbox/ToolboxControls/ProxyView/RotEntryCollection.cs:77-86 | Toolbox/Toolbox/ToolboxControls/ProxyView/WindowEntryCollection.cs:86-92 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) Source/Word/Tools/Contribution/ApplicationUtils.cs:180 — Source/Word/Tools/Contribution/ApplicationUtils.cs:180-192 | Source/PowerPoint/Tools/Contribution/ApplicationUtils.cs:150-156 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) Source/NetOffice/Tools/AttributeReflector.cs:185 — Source/NetOffice/Tools/AttributeReflector.cs:185-191 | Source/Outlook/Tools/RequireShutdownNotificationAttribute.cs:18-24 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) RegAddin/RegAddin/Register/RegisterOperationHost.cs:87 — RegAddin/RegAddin/Register/RegisterOperationHost.cs:87-93 | RegAddin/RegAddin/Unregister/UnregisterOperationHost.cs:101-107 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 12+ corresponding lines) · ×8
  • Edited copies of one member (3 members, 12+ corresponding lines) Source/Excel/Events/WorkbookEvents.cs:392 — Source/Excel/Events/WorkbookEvents.cs:392-403 | Source/Excel/Events/WorkbookEvents.cs:406-417 | Source/Excel/Events/WorkbookEvents.cs:420-431 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 12+ corresponding lines) Source/OWC10/Events/IChartEvents.cs:547 — Source/OWC10/Events/IChartEvents.cs:547-560 | Source/OWC10/Events/IChartEvents.cs:563-574 | Source/OWC10/Events/IChartEvents.cs:577-588 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 12+ corresponding lines) Source/Office/Events/_CustomXMLPartsEvents.cs:61 — Source/Office/Events/_CustomXMLPartsEvents.cs:61-72 | Source/Office/Events/_CustomXMLPartsEvents.cs:75-86 | Source/Office/Events/_CustomXMLPartsEvents.cs:89-100 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 12+ corresponding lines) Source/Outlook/Events/OutlookBarGroupsEvents.cs:62 — Source/Outlook/Events/OutlookBarGroupsEvents.cs:62-73 | Source/Outlook/Events/OutlookBarGroupsEvents.cs:91-105 | Source/Outlook/Events/OutlookBarPaneEvents.cs:75-89 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 12+ corresponding lines) Source/Outlook/Events/OutlookBarPaneEvents.cs:58 — Source/Outlook/Events/OutlookBarPaneEvents.cs:58-72 | Source/Outlook/Events/OutlookBarShortcutsEvents.cs:62-73 | Source/Outlook/Events/OutlookBarShortcutsEvents.cs:91-105 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 12+ corresponding lines) Source/PowerPoint/Events/EApplication.cs:224 — Source/PowerPoint/Events/EApplication.cs:224-235 | Source/PowerPoint/Events/EApplication.cs:238-252 | Source/PowerPoint/Events/EApplication.cs:255-269 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 12+ corresponding lines) Source/Excel/Events/RefreshEvents.cs:71 — Source/Excel/Events/RefreshEvents.cs:71-82 | Source/Excel/Events/WorkbookEvents.cs:324-338 | Source/Outlook/Events/FormRegionEvents.cs:55-66 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 12+ corresponding lines) Examples/Excel/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:74 — Examples/Excel/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:74-85 | Examples/Outlook/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:71-82 | Examples/Word/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:71-83 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×8
  • Duplicated block (15 lines × 2) Source/Word/Tools/COMAddin.cs:1057 — Source/Word/Tools/COMAddin.cs:1057-1071 | Source/Word/Tools/DocumentInspectorBase.cs:244-258 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (15 lines × 2) Source/Access/Events/DispNavigationButtonEvents.cs:23 — Source/Access/Events/DispNavigationButtonEvents.cs:23-37 | Source/Access/Events/DispNavigationControlEvents.cs:32-46 — before extracting anything, compare `Source/Access/Events/DispNavigationButtonEvents.cs` and `Source/Access/Events/DispNavigationControlEvents.cs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 226 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (15 lines × 2) Source/Excel/Events/AppEvents.cs:843 — Source/Excel/Events/AppEvents.cs:843-857 | Source/Excel/Events/WorkbookEvents.cs:715-729 — before extracting anything, compare `Source/Excel/Events/AppEvents.cs` and `Source/Excel/Events/WorkbookEvents.cs` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 377 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (15 lines × 2) Source/Access/Events/_FormEvents.cs:1084 — Source/Access/Events/_FormEvents.cs:1084-1098 | Source/Access/Events/_FormEvents2.cs:963-977 — before extracting anything, compare `Source/Access/Events/_FormEvents.cs` and `Source/Access/Events/_FormEvents2.cs` as WHOLE FILES: this scan already matched 72 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (15 lines × 2) RegAddin/RegAddin/Register/RegisterOperationHost.cs:105 — RegAddin/RegAddin/Register/RegisterOperationHost.cs:105-119 | RegAddin/RegAddin/Unregister/UnregisterOperationHost.cs:111-125 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (15 lines × 2) Toolbox/Toolbox/ToolboxControls/RegistryEditor/RegistryEditorControl.cs:572 — Toolbox/Toolbox/ToolboxControls/RegistryEditor/RegistryEditorControl.cs:572-586 | Toolbox/Toolbox/ToolboxControls/RegistryEditor/RegistryEditorControl.cs:665-679 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (15 lines × 2) Toolbox/Toolbox/ToolboxControls/RegistryEditor/RegistryEditorControl.cs:609 — Toolbox/Toolbox/ToolboxControls/RegistryEditor/RegistryEditorControl.cs:609-623 | Toolbox/Toolbox/ToolboxControls/RegistryEditor/RegistryEditorControl.cs:657-671 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (15 lines × 2) BuildTools/VersionUpdater/Form1.cs:138 — BuildTools/VersionUpdater/Form1.cs:138-152 | BuildTools/VersionUpdater/Form1.cs:182-196 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `BuildTools/VersionUpdater/Form1.cs:138` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (7 lines × 3) · ×8
  • Duplicated block (7 lines × 3) Source/Access/Tools/COMAddin.cs:447 — Source/Access/Tools/COMAddin.cs:447-453 | Source/PowerPoint/Tools/COMAddin.cs:448-454 | Source/Word/Tools/COMAddin.cs:449-455 — before extracting anything, compare `Source/Access/Tools/COMAddin.cs` and `Source/PowerPoint/Tools/COMAddin.cs` as WHOLE FILES: this scan already matched 30 separate duplicated blocks between them, totalling at least 408 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Source/Access/Tools/COMAddin.cs:447` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 3) Source/NetOffice/CoreExtensions/CorePropertySetExtensions.cs:302 — Source/NetOffice/CoreExtensions/CorePropertySetExtensions.cs:302-308 | Source/NetOffice/CoreExtensions/CorePropertySetExtensions.cs:591-597 | Source/NetOffice/CoreExtensions/CorePropertySetExtensions.cs:785-791 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (7 lines × 3) Source/Excel/Events/AppEvents.cs:34 — Source/Excel/Events/AppEvents.cs:34-40 | Source/Excel/Events/WorkbookEvents.cs:79-85 | Source/Excel/Events/WorkbookEvents.cs:86-92 — before extracting anything, compare `Source/Excel/Events/AppEvents.cs` and `Source/Excel/Events/WorkbookEvents.cs` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 377 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Excel/Events/WorkbookEvents.cs:84` calls `SinkArgument` and `Source/Excel/Events/AppEvents.cs:32` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (7 lines × 3) Source/Outlook/Events/ApplicationEvents.cs:19 — Source/Outlook/Events/ApplicationEvents.cs:19-25 | Source/Outlook/Events/ApplicationEvents_10.cs:19-25 | Source/Outlook/Events/ApplicationEvents_11.cs:19-25 — before extracting anything, compare `Source/Outlook/Events/ApplicationEvents.cs` and `Source/Outlook/Events/ApplicationEvents_10.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 82 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (7 lines × 3) Source/Access/Events/_FormEvents.cs:153 — Source/Access/Events/_FormEvents.cs:153-159 | Source/Access/Events/_FormEvents2.cs:155-161 | Source/Access/Events/_ReportEvents2.cs:130-136 — before extracting anything, compare `Source/Access/Events/_FormEvents.cs` and `Source/Access/Events/_FormEvents2.cs` as WHOLE FILES: this scan already matched 72 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (7 lines × 3) Source/ADODB/Events/ConnectionEvents.cs:32 — Source/ADODB/Events/ConnectionEvents.cs:32-38 | Source/ADODB/Events/ConnectionEvents.cs:39-45 | Source/ADODB/Events/ConnectionEvents.cs:76-82 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (7 lines × 3) Source/Access/Tools/COMAddin.cs:832 — Source/Access/Tools/COMAddin.cs:832-838 | Source/Excel/Tools/COMAddin.cs:834-840 | Source/PowerPoint/Tools/COMAddin.cs:833-839 — before extracting anything, compare `Source/Access/Tools/COMAddin.cs` and `Source/Excel/Tools/COMAddin.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 284 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (7 lines × 3) Source/Access/Tools/COMAddin.cs:847 — Source/Access/Tools/COMAddin.cs:847-853 | Source/Excel/Tools/COMAddin.cs:849-855 | Source/PowerPoint/Tools/COMAddin.cs:848-854 — before extracting anything, compare `Source/Access/Tools/COMAddin.cs` and `Source/Excel/Tools/COMAddin.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 284 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (6 lines × 4) · ×8
  • Duplicated block (6 lines × 4) Source/Excel/Events/AppEvents.cs:371 — Source/Excel/Events/AppEvents.cs:371-376 | Source/Excel/Events/AppEvents.cs:390-395 | Source/Excel/Events/WorkbookEvents.cs:457-462 | Source/Excel/Events/WorkbookEvents.cs:476-481 — before extracting anything, compare `Source/Excel/Events/AppEvents.cs` and `Source/Excel/Events/WorkbookEvents.cs` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 377 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (6 lines × 4) Source/Access/Events/DispAttachmentEvents.cs:37 — Source/Access/Events/DispAttachmentEvents.cs:37-42 | Source/Access/Events/DispComboBoxEvents.cs:106-111 | Source/Access/Events/DispTextBoxEvents.cs:99-104 | Source/Access/Events/_FormEvents2.cs:167-172 — before extracting anything, compare `Source/Access/Events/DispAttachmentEvents.cs` and `Source/Access/Events/DispComboBoxEvents.cs` as WHOLE FILES: this scan already matched 36 separate duplicated blocks between them, totalling at least 321 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (6 lines × 4) Source/Excel/Events/ChartEvents.cs:32 — Source/Excel/Events/ChartEvents.cs:32-37 | Source/OWC10/Events/IChartEvents.cs:69-74 | Source/OWC10/Events/IPivotControlEvents.cs:55-60 | Source/OWC10/Events/ISpreadsheetEventSink.cs:114-119 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
  • Duplicated block (6 lines × 4) Source/Excel/Events/ChartEvents.cs:40 — Source/Excel/Events/ChartEvents.cs:40-45 | Source/OWC10/Events/IChartEvents.cs:85-90 | Source/OWC10/Events/IPivotControlEvents.cs:71-76 | Source/OWC10/Events/ISpreadsheetEventSink.cs:136-141 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
  • Duplicated block (6 lines × 4) Source/NetOffice/Utils.cs:213 — Source/NetOffice/Utils.cs:213-218 | Source/NetOffice/Utils.cs:240-245 | Source/NetOffice/Utils.cs:267-272 | Source/NetOffice/Utils.cs:293-298 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/NetOffice/Utils.cs:213` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Source/NetOffice/Utils.cs:219` calls `CreateObjectFromComProxy` and `Source/NetOffice/Utils.cs:273` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (6 lines × 4) Source/PowerPoint/Events/EApplication.cs:25 — Source/PowerPoint/Events/EApplication.cs:25-30 | Source/Word/Events/ApplicationEvents2.cs:78-83 | Source/Word/Events/ApplicationEvents3.cs:78-83 | Source/Word/Events/ApplicationEvents4.cs:78-83 — before extracting anything, compare `Source/Word/Events/ApplicationEvents2.cs` and `Source/Word/Events/ApplicationEvents3.cs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 270 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (6 lines × 4) Source/Access/Events/_FormEvents.cs:59 — Source/Access/Events/_FormEvents.cs:59-64 | Source/Access/Events/_FormEvents2.cs:61-66 | Source/Access/Events/_ReportEvents.cs:19-24 | Source/Access/Events/_ReportEvents2.cs:19-24 — before extracting anything, compare `Source/Access/Events/_FormEvents.cs` and `Source/Access/Events/_FormEvents2.cs` as WHOLE FILES: this scan already matched 72 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (6 lines × 4) Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ClassLibraryConverterCS.cs:64 — Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ClassLibraryConverterCS.cs:64-69 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ClassLibraryConverterVB.cs:75-80 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ConsoleConverterCS.cs:64-69 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ConsoleConverterVB.cs:74-79 — before extracting anything, compare `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ClassLibraryConverterCS.cs` and `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ConsoleConverterCS.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ClassLibraryConverterCS.cs:64` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (11 lines × 3) · ×8
  • Duplicated block (11 lines × 3) Source/Word/Events/ApplicationEvents2.cs:216 — Source/Word/Events/ApplicationEvents2.cs:216-226 | Source/Word/Events/ApplicationEvents3.cs:281-291 | Source/Word/Events/ApplicationEvents4.cs:354-364 — before extracting anything, compare `Source/Word/Events/ApplicationEvents2.cs` and `Source/Word/Events/ApplicationEvents3.cs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 270 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 3) Source/Word/Events/ApplicationEvents2.cs:262 — Source/Word/Events/ApplicationEvents2.cs:262-272 | Source/Word/Events/ApplicationEvents3.cs:327-337 | Source/Word/Events/ApplicationEvents4.cs:400-410 — before extracting anything, compare `Source/Word/Events/ApplicationEvents2.cs` and `Source/Word/Events/ApplicationEvents3.cs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 270 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 3) Source/MSComctlLib/Events/IStatusBarEvents.cs:51 — Source/MSComctlLib/Events/IStatusBarEvents.cs:51-61 | Source/MSComctlLib/Events/ITreeViewEvents.cs:84-94 | Source/MSComctlLib/Events/ListViewEvents.cs:79-89 — before extracting anything, compare `Source/MSComctlLib/Events/IStatusBarEvents.cs` and `Source/MSComctlLib/Events/ITreeViewEvents.cs` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 223 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (11 lines × 3) Source/Word/Events/DocumentEvents2.cs:234 — Source/Word/Events/DocumentEvents2.cs:234-244 | Source/Word/Events/DocumentEvents2.cs:265-275 | Source/Word/Events/DocumentEvents2.cs:282-292 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (11 lines × 3) Examples/Excel/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:64 — Examples/Excel/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:64-74 | Examples/Excel/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:42-52 | Examples/Excel/IExtensibility COMAddin Examples/TaskPane/Addin.cs:68-78 — `Examples/Excel/IExtensibility COMAddin Examples/ClassicUI/Addin.cs` and `Examples/Excel/IExtensibility COMAddin Examples/RibbonUI/Addin.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 83 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Examples/Excel/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:54` calls `OnStartupComplete` and `Examples/Excel/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:76` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (11 lines × 3) Examples/Outlook/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:49 — Examples/Outlook/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:49-59 | Examples/Outlook/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:42-52 | Examples/Outlook/IExtensibility COMAddin Examples/TaskPane/Addin.cs:70-80 — `Examples/Outlook/IExtensibility COMAddin Examples/ClassicUI/Addin.cs` and `Examples/Outlook/IExtensibility COMAddin Examples/RibbonUI/Addin.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 90 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 3) Examples/Access/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:49 — Examples/Access/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:49-59 | Examples/Access/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:42-52 | Examples/Access/IExtensibility COMAddin Examples/TaskPane/Addin.cs:68-78 — `Examples/Access/IExtensibility COMAddin Examples/ClassicUI/Addin.cs` and `Examples/Access/IExtensibility COMAddin Examples/RibbonUI/Addin.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 83 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 3) Examples/PowerPoint/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:51 — Examples/PowerPoint/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:51-61 | Examples/PowerPoint/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:42-52 | Examples/PowerPoint/IExtensibility COMAddin Examples/TaskPane/Addin.cs:68-78 — `Examples/PowerPoint/IExtensibility COMAddin Examples/ClassicUI/Addin.cs` and `Examples/PowerPoint/IExtensibility COMAddin Examples/RibbonUI/Addin.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 84 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (5 lines × 5) · ×8
  • Duplicated block (5 lines × 5) Source/Access/Events/_FormEvents.cs:831 — Source/Access/Events/_FormEvents.cs:831-835 | Source/Access/Events/_FormEvents.cs:852-856 | Source/Access/Events/_FormEvents.cs:871-875 | Source/Access/Events/_FormEvents.cs:892-896 | Source/Access/Events/_FormEvents.cs:911-915 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/Access/Events/_FormEvents.cs:831` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (5 lines × 5) Source/Access/Classes/Application.cs:164 — Source/Access/Classes/Application.cs:164-168 | Source/Excel/Classes/Application.cs:222-226 | Source/Outlook/Classes/Application.cs:188-192 | Source/PowerPoint/Classes/Application.cs:209-213 | Source/Word/Classes/Application.cs:212-216 — before extracting anything, compare `Source/Access/Classes/Application.cs` and `Source/PowerPoint/Classes/Application.cs` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 5) Source/Excel/DispatchInterfaces/Areas.cs:213 — Source/Excel/DispatchInterfaces/Areas.cs:213-217 | Source/Excel/DispatchInterfaces/Range.cs:6962-6966 | Source/Excel/DispatchInterfaces/Ranges.cs:213-217 | Source/Excel/Interfaces/IAreas.cs:208-212 | Source/Excel/Interfaces/IRanges.cs:208-212 — before extracting anything, compare `Source/Excel/DispatchInterfaces/Areas.cs` and `Source/Excel/Interfaces/IAreas.cs` as WHOLE FILES: 87% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 5) Source/Office/DispatchInterfaces/ODSOColumns.cs:171 — Source/Office/DispatchInterfaces/ODSOColumns.cs:171-175 | Source/Office/DispatchInterfaces/ODSOFilters.cs:239-243 | Source/Outlook/DispatchInterfaces/_Items.cs:398-402 | Source/Outlook/DispatchInterfaces/_Results.cs:332-336 | Source/Outlook/DispatchInterfaces/_SimpleItems.cs:214-218 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 5) Source/MSComctlLib/DispatchInterfaces/IImage.cs:169 — Source/MSComctlLib/DispatchInterfaces/IImage.cs:169-173 | Source/MSComctlLib/DispatchInterfaces/IListView.cs:712-716 | Source/MSComctlLib/DispatchInterfaces/IPanel.cs:271-275 | Source/Office/DispatchInterfaces/_CommandBarButton.cs:228-232 | Source/Outlook/DispatchInterfaces/_OlkCommandButton.cs:282-286 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 5) Source/Word/DispatchInterfaces/Characters.cs:240 — Source/Word/DispatchInterfaces/Characters.cs:240-244 | Source/Word/DispatchInterfaces/ProofreadingErrors.cs:226-230 | Source/Word/DispatchInterfaces/Sentences.cs:240-244 | Source/Word/DispatchInterfaces/StoryRanges.cs:212-216 | Source/Word/DispatchInterfaces/Words.cs:240-244 — before extracting anything, compare `Source/Word/DispatchInterfaces/Characters.cs` and `Source/Word/DispatchInterfaces/Sentences.cs` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 5) Source/Outlook/DispatchInterfaces/Links.cs:229 — Source/Outlook/DispatchInterfaces/Links.cs:229-233 | Source/Outlook/DispatchInterfaces/Pages.cs:248-252 | Source/Outlook/DispatchInterfaces/Panes.cs:215-219 | Source/Outlook/DispatchInterfaces/PropertyPages.cs:250-254 | Source/Outlook/DispatchInterfaces/Selection.cs:240-244 — before extracting anything, compare `Source/Outlook/DispatchInterfaces/Pages.cs` and `Source/Outlook/DispatchInterfaces/Panes.cs` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 5) Examples/Access/NetOffice COMAddin Examples/02 Ribbons And Panes/SamplePane.cs:69 — Examples/Access/NetOffice COMAddin Examples/02 Ribbons And Panes/SamplePane.cs:69-73 | Examples/Excel/NetOffice COMAddin Examples/02 Ribbons And Panes/SamplePane.cs:69-73 | Examples/Outlook/NetOffice COMAddin Examples/02 Ribbons And Panes/SamplePane.cs:70-74 | Examples/PowerPoint/NetOffice COMAddin Examples/02 Ribbons And Panes/SamplePane.cs:69-73 | Examples/Word/NetOffice COMAddin Examples/02 Ribbons And Panes/SamplePane.cs:69-73 — before extracting anything, compare `Examples/Access/NetOffice COMAddin Examples/02 Ribbons And Panes/SamplePane.cs` and `Examples/Excel/NetOffice COMAddin Examples/02 Ribbons And Panes/SamplePane.cs` as WHOLE FILES: 86% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
X18 · Disposal-pattern correctness · Owned disposable field is never released · ×8
  • Owned disposable field is never released Source/Excel/Classes/Application.cs:81 — `Application` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_appEvents_SinkHelper` itself (line 81), which makes that instance its own. But `_appEvents_SinkHelper` is named in none of the methods the disposal search covered: `Dispose` (line 220), `Dispose` (line 231) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_appEvents_SinkHelper?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
  • Owned disposable field is never released Source/Word/Classes/Application.cs:69 — `Application` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_applicationEvents2_SinkHelper` itself (line 69), which makes that instance its own. But `_applicationEvents2_SinkHelper` is named in none of the methods the disposal search covered: `Dispose` (line 210), `Dispose` (line 221) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_applicationEvents2_SinkHelper?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
  • Owned disposable field is never released Source/Word/Classes/Application.cs:70 — `Application` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_applicationEvents3_SinkHelper` itself (line 70), which makes that instance its own. But `_applicationEvents3_SinkHelper` is named in none of the methods the disposal search covered: `Dispose` (line 210), `Dispose` (line 221) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_applicationEvents3_SinkHelper?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
  • Owned disposable field is never released Source/Word/Classes/Application.cs:71 — `Application` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_applicationEvents4_SinkHelper` itself (line 71), which makes that instance its own. But `_applicationEvents4_SinkHelper` is named in none of the methods the disposal search covered: `Dispose` (line 210), `Dispose` (line 221) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_applicationEvents4_SinkHelper?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
  • Owned disposable field is never released Source/Outlook/Classes/Application.cs:53 — `Application` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_applicationEvents_SinkHelper` itself (line 53), which makes that instance its own. But `_applicationEvents_SinkHelper` is named in none of the methods the disposal search covered: `Dispose` (line 186), `Dispose` (line 197) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_applicationEvents_SinkHelper?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
  • Owned disposable field is never released Source/Outlook/Classes/Application.cs:54 — `Application` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_applicationEvents_10_SinkHelper` itself (line 54), which makes that instance its own. But `_applicationEvents_10_SinkHelper` is named in none of the methods the disposal search covered: `Dispose` (line 186), `Dispose` (line 197) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_applicationEvents_10_SinkHelper?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
  • Owned disposable field is never released Source/Outlook/Classes/Application.cs:55 — `Application` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_applicationEvents_11_SinkHelper` itself (line 55), which makes that instance its own. But `_applicationEvents_11_SinkHelper` is named in none of the methods the disposal search covered: `Dispose` (line 186), `Dispose` (line 197) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_applicationEvents_11_SinkHelper?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
  • Owned disposable field is never released Source/PowerPoint/Classes/Application.cs:67 — `Application` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_eApplication_SinkHelper` itself (line 67), which makes that instance its own. But `_eApplication_SinkHelper` is named in none of the methods the disposal search covered: `Dispose` (line 207), `Dispose` (line 218) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_eApplication_SinkHelper?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
D4 · Code Duplication · Edited copy of a member (13 corresponding lines) · ×7
  • Edited copy of a member (13 corresponding lines) Source/Office/DispatchInterfaces/IBlogExtensibility.cs:126 — Source/Office/DispatchInterfaces/IBlogExtensibility.cs:126-138 | Source/OWC10/DispatchInterfaces/IDataSourceControl.cs:1318-1330 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) Toolbox/Toolbox/Controls/Hex/MemoryDataBlock.cs:57 — Toolbox/Toolbox/Controls/Hex/MemoryDataBlock.cs:57-69 | Toolbox/Toolbox/Controls/Hex/MemoryDataBlock.cs:72-85 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ConverterUtils.cs:175 — Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ConverterUtils.cs:175-189 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ConverterUtils.cs:198-210 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) Toolbox/Toolbox/Utils/Animation/Panel/AnimatedPanel.cs:85 — Toolbox/Toolbox/Utils/Animation/Panel/AnimatedPanel.cs:85-97 | Toolbox/Toolbox/Utils/Animation/Panel/AnimatedPanel.cs:224-236 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) Toolbox/Toolbox/ToolboxControls/RegistryEditor/RegistryEditorControl.cs:960 — Toolbox/Toolbox/ToolboxControls/RegistryEditor/RegistryEditorControl.cs:960-972 | Toolbox/Toolbox/ToolboxControls/RegistryEditor/RegistryEditorControl.cs:1105-1117 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) Examples/Excel/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:212 — Examples/Excel/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:212-224 | Examples/Other/IExtensibility2 Examples/SuperAddin/Addin.cs:117-131 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) RegAddin/RegAddinTest/CmdLineTest03.cs:28 — RegAddin/RegAddinTest/CmdLineTest03.cs:28-40 | RegAddin/RegAddinTest/CmdLineTest03.cs:47-59 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
GD1 · Unfinished & placeholder code · Unfinished stub · ×7
  • Unfinished stub — throws NotImplementedException Source/Office/Tools/Informations/DiagnosticPairCollection.cs:98 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException Toolbox/Toolbox/ToolboxControls/About/AboutControl.cs:123 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException Toolbox/Toolbox/ToolboxControls/ProjectWizard/Controls/FinishControl.cs:104 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException Toolbox/Toolbox/ToolboxControls/ProjectWizard/Controls/FinishControl.cs:109 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException Toolbox/Toolbox/ToolboxControls/ProxyView/RotEntryCollection.cs:131 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException Toolbox/Toolbox/ToolboxControls/ProxyView/WindowEntryCollection.cs:136 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException Toolbox/Toolbox/ToolboxControls/Welcome/WelcomeControl.cs:194 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
IC1 · Incompleteness & stubs · Unfinished stub · ×7
  • Unfinished stub — throws NotImplementedException Source/Office/Tools/Informations/DiagnosticPairCollection.cs:98 — `GetListName` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException Toolbox/Toolbox/ToolboxControls/About/AboutControl.cs:123 — `GetHelpText` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException Toolbox/Toolbox/ToolboxControls/ProjectWizard/Controls/FinishControl.cs:104 — `SettingsDocument` is a shipped property whose accessors only throw NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException Toolbox/Toolbox/ToolboxControls/ProjectWizard/Controls/FinishControl.cs:109 — `GetSettingsSummary` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException Toolbox/Toolbox/ToolboxControls/ProxyView/RotEntryCollection.cs:131 — `GetListName` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException Toolbox/Toolbox/ToolboxControls/ProxyView/WindowEntryCollection.cs:136 — `GetListName` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException Toolbox/Toolbox/ToolboxControls/Welcome/WelcomeControl.cs:194 — `GetHelpText` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
D29 · Static Analysis (SAST) · REDACTED · ×6
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Edited copy of a member (23 corresponding lines) · ×6
  • Edited copy of a member (23 corresponding lines) Source/Access/Classes/CheckBox.cs:480 — Source/Access/Classes/CheckBox.cs:480-502 | Source/Access/Classes/_CheckBoxInOption.cs:465-487 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) Source/Access/Classes/OptionButton.cs:480 — Source/Access/Classes/OptionButton.cs:480-502 | Source/Access/Classes/_OptionButtonInOption.cs:465-487 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) Source/Access/Classes/ToggleButton.cs:480 — Source/Access/Classes/ToggleButton.cs:480-502 | Source/Access/Classes/_ToggleButtonInOption.cs:465-487 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) Toolbox/Toolbox/Controls/Hex/HexBox.cs:1976 — Toolbox/Toolbox/Controls/Hex/HexBox.cs:1976-1998 | Toolbox/Toolbox/Controls/Hex/HexBox.cs:2159-2181 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) Source/Excel/Tools/RealtimeDataServer.cs:330 — Source/Excel/Tools/RealtimeDataServer.cs:330-352 | Source/Excel/Tools/RealtimeDataServer.cs:360-382 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/AssemblyAnalyzer.cs:459 — Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/AssemblyAnalyzer.cs:459-490 | Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/AssemblyAnalyzer.cs:493-515 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (5 corresponding lines) · ×6
  • Edited copy of a member (5 corresponding lines) Source/OWC10/DispatchInterfaces/ViewSurface.cs:218 — Source/OWC10/DispatchInterfaces/ViewSurface.cs:218-222 | Source/MSComctlLib/DispatchInterfaces/IImageList.cs:242-246 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) RegAddin/RegAddin/CommandLineSettingsTransformer.cs:147 — RegAddin/RegAddin/CommandLineSettingsTransformer.cs:147-151 | RegAddin/RegAddin/CommandLineValidator.cs:105-112 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) Source/NetOffice/CoreExtensions/CoreMethodExtensions.cs:1797 — Source/NetOffice/CoreExtensions/CoreMethodExtensions.cs:1797-1802 | Source/NetOffice/CoreExtensions/CorePropertyGetExtensions.cs:1612-1616 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) Source/NetOffice/CoreExtensions/CoreMethodExtensions.cs:1959 — Source/NetOffice/CoreExtensions/CoreMethodExtensions.cs:1959-1964 | Source/NetOffice/CoreExtensions/CorePropertyGetExtensions.cs:1712-1716 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) BuildTools/SearchAndReplace/Form1.cs:33 — BuildTools/SearchAndReplace/Form1.cs:33-37 | BuildTools/ReferenceAnalyzer/Form1.cs:35-40 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) BuildTools/SourceUpdater/Form1.cs:88 — BuildTools/SourceUpdater/Form1.cs:88-92 | BuildTools/VersionUpdater/Form1.cs:405-409 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (27–30 lines × 4) · ×6
  • Duplicated block (27–30 lines × 4) Source/Access/Classes/AutoCorrect.cs:76 — Source/Access/Classes/AutoCorrect.cs:76-105 | Source/Excel/DispatchInterfaces/AutoCorrect.cs:186-212 | Source/PowerPoint/DispatchInterfaces/AutoCorrect.cs:68-94 | Source/Word/DispatchInterfaces/AutoCorrect.cs:68-94 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
  • Duplicated block (27–30 lines × 4) Source/Access/Classes/DefaultWebOptions.cs:75 — Source/Access/Classes/DefaultWebOptions.cs:75-104 | Source/Excel/DispatchInterfaces/DefaultWebOptions.cs:68-94 | Source/PowerPoint/DispatchInterfaces/DefaultWebOptions.cs:67-93 | Source/Word/DispatchInterfaces/DefaultWebOptions.cs:68-94 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
  • Duplicated block (27–30 lines × 4) Source/Excel/DispatchInterfaces/Font.cs:68 — Source/Excel/DispatchInterfaces/Font.cs:68-94 | Source/OWC10/DispatchInterfaces/Font.cs:67-93 | Source/PowerPoint/DispatchInterfaces/Font.cs:68-94 | Source/Word/Classes/Font.cs:76-105 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
  • Duplicated block (27–30 lines × 4) Source/Access/Classes/WebOptions.cs:75 — Source/Access/Classes/WebOptions.cs:75-104 | Source/Excel/DispatchInterfaces/WebOptions.cs:68-94 | Source/PowerPoint/DispatchInterfaces/WebOptions.cs:67-93 | Source/Word/DispatchInterfaces/WebOptions.cs:68-94 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
  • Duplicated block (27–30 lines × 4) Source/Excel/DispatchInterfaces/Windows.cs:71 — Source/Excel/DispatchInterfaces/Windows.cs:71-97 | Source/OWC10/DispatchInterfaces/Windows.cs:70-96 | Source/VBIDE/Classes/Windows.cs:75-104 | Source/Word/DispatchInterfaces/Windows.cs:71-97 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
  • Duplicated block (27–30 lines × 4) Source/ADODB/DispatchInterfaces/Properties.cs:67 — Source/ADODB/DispatchInterfaces/Properties.cs:67-93 | Source/Access/DispatchInterfaces/Properties.cs:71-97 | Source/DAO/DispatchInterfaces/Properties.cs:70-96 | Source/VBIDE/Classes/Properties.cs:75-104 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
D4 · Code Duplication · Duplicated block (21 lines × 2) · ×6
  • Duplicated block (21 lines × 2) Toolbox/Toolbox/Controls/Hex/HexBox.cs:657 — Toolbox/Toolbox/Controls/Hex/HexBox.cs:657-677 | Toolbox/Toolbox/Controls/Hex/HexBox.cs:1017-1037 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Toolbox/Toolbox/Controls/Hex/HexBox.cs:679` calls `IsHexDigit` and `Toolbox/Toolbox/Controls/Hex/HexBox.cs:1039` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (21 lines × 2) Source/Office/Tools/COMAddin.cs:545 — Source/Office/Tools/COMAddin.cs:545-565 | Source/Office/Tools/CustomTaskPaneHandler.cs:86-106 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Office/Tools/CustomTaskPaneHandler.cs:84` calls `GetType` and `Source/Office/Tools/COMAddin.cs:543` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (21 lines × 2) Source/NetOffice/Extensions/EnumerableExtensions.cs:232 — Source/NetOffice/Extensions/EnumerableExtensions.cs:232-252 | Source/NetOffice/Extensions/EnumerableExtensions.cs:325-345 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/NetOffice/Extensions/EnumerableExtensions.cs:232` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (21 lines × 2) Examples/ExampleBase/SortableBindingList.cs:119 — Examples/ExampleBase/SortableBindingList.cs:119-139 | Source/NetOffice/Contribution/CollectionsGeneric/SortableBindingList.cs:119-139 — before extracting anything, compare `Examples/ExampleBase/SortableBindingList.cs` and `Source/NetOffice/Contribution/CollectionsGeneric/SortableBindingList.cs` as WHOLE FILES: 99% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (21 lines × 2) RegAddin/RegAddin/CommandLineSettingsTransformer.cs:155 — RegAddin/RegAddin/CommandLineSettingsTransformer.cs:155-175 | RegAddin/RegAddin/CommandLineValidator.cs:279-299 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (21 lines × 2) Source/MSComctlLib/Events/ITreeViewEvents.cs:47 — Source/MSComctlLib/Events/ITreeViewEvents.cs:47-67 | Source/MSComctlLib/Events/ListViewEvents.cs:42-62 — before extracting anything, compare `Source/MSComctlLib/Events/ITreeViewEvents.cs` and `Source/MSComctlLib/Events/ListViewEvents.cs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 319 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×6
  • Duplicated block (17 lines × 2) Source/Excel/Tools/RealtimeDataServer.cs:469 — Source/Excel/Tools/RealtimeDataServer.cs:469-485 | Source/Word/Tools/DocumentInspectorBase.cs:316-332 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (17 lines × 2) Source/NetOffice/COMObject.cs:155 — Source/NetOffice/COMObject.cs:155-171 | Source/NetOffice/COMObject.cs:198-214 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/NetOffice/COMObject.cs:155` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 2) Source/NetOffice/COMObject.cs:431 — Source/NetOffice/COMObject.cs:431-447 | Source/NetOffice/COMObject.cs:465-481 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/NetOffice/COMObject.cs:431` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 2) Source/NetOffice/Contribution/Controls/InstanceMonitor.cs:467 — Source/NetOffice/Contribution/Controls/InstanceMonitor.cs:467-483 | Source/Office.Extensions/TrayMenuUtils/TrayMenuMonitorItemControl.cs:715-731 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (17 lines × 2) Toolbox/Toolbox/Forms/UriTargetForm.cs:44 — Toolbox/Toolbox/Forms/UriTargetForm.cs:44-60 | Toolbox/Toolbox/Forms/UriTargetForm.cs:64-80 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (17 lines × 2) Examples/Outlook/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:90 — Examples/Outlook/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:90-106 | Examples/Word/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:91-107 — before extracting anything, compare `Examples/Outlook/IExtensibility COMAddin Examples/RibbonUI/Addin.cs` and `Examples/Word/IExtensibility COMAddin Examples/RibbonUI/Addin.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 86 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Examples/Outlook/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:90` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Members sharing a duplicated core (8 members, 50+ identical tokens) · ×5
  • Members sharing a duplicated core (8 members, 50+ identical tokens) Source/Office/DispatchInterfaces/CommandBar.cs:498 — Source/Office/DispatchInterfaces/CommandBar.cs:498-510 | Source/Office/DispatchInterfaces/CommandBarControl.cs:562-574 | Source/Office/DispatchInterfaces/CommandBarPopup.cs:211-223 | Source/Office/DispatchInterfaces/IAccessible.cs:700-712 | Source/Office/DispatchInterfaces/_CommandBarActiveX.cs:224-236 | Source/Office/DispatchInterfaces/_CommandBarButton.cs:314-326 | Source/Office/DispatchInterfaces/_CommandBarComboBox.cs:323-335 | Source/Word/DispatchInterfaces/Window.cs:1348-1360 — These 8 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 8 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 8 times.
  • Members sharing a duplicated core (8 members, 50+ identical tokens) Source/Word/Events/ApplicationEvents2.cs:229 — Source/Word/Events/ApplicationEvents2.cs:229-242 | Source/Word/Events/ApplicationEvents2.cs:245-258 | Source/Word/Events/ApplicationEvents3.cs:294-307 | Source/Word/Events/ApplicationEvents3.cs:310-323 | Source/Word/Events/ApplicationEvents3.cs:536-549 | Source/Word/Events/ApplicationEvents4.cs:367-380 | Source/Word/Events/ApplicationEvents4.cs:383-396 | Source/Word/Events/ApplicationEvents4.cs:609-622 — These 8 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 8 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 8 times.
  • Members sharing a duplicated core (8 members, 50+ identical tokens) Source/Access/Events/DispListBoxEvents.cs:122 — Source/Access/Events/DispListBoxEvents.cs:122-134 | Source/Access/Events/DispNavigationControlEvents.cs:136-148 | Source/Access/Events/DispOptionButtonEvents.cs:131-143 | Source/Access/Events/DispOptionGroupEvents.cs:97-109 | Source/Access/Events/DispPaletteButtonEvents.cs:133-145 | Source/Access/Events/DispTextBoxEvents.cs:136-148 | Source/Access/Events/DispToggleButtonEvents.cs:133-145 | Source/Access/Events/DispWebBrowserControlEvents.cs:174-186 — These 8 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 8 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 8 times.
  • Members sharing a duplicated core (8 members, 50+ identical tokens) Source/MSComctlLib/Events/DImageComboEvents.cs:221 — Source/MSComctlLib/Events/DImageComboEvents.cs:221-235 | Source/MSComctlLib/Events/IProgressBarEvents.cs:211-225 | Source/MSComctlLib/Events/ISliderEvents.cs:307-321 | Source/MSComctlLib/Events/IStatusBarEvents.cs:264-278 | Source/MSComctlLib/Events/ITabStripEvents.cs:297-311 | Source/MSComctlLib/Events/IToolbarEvents.cs:270-284 | Source/MSComctlLib/Events/ITreeViewEvents.cs:410-424 | Source/MSComctlLib/Events/ListViewEvents.cs:378-392 — These 8 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 8 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 8 times.
  • Members sharing a duplicated core (8 members, 50+ identical tokens) Source/MSComctlLib/Events/DImageComboEvents.cs:260 — Source/MSComctlLib/Events/DImageComboEvents.cs:260-272 | Source/MSComctlLib/Events/IProgressBarEvents.cs:250-262 | Source/MSComctlLib/Events/ISliderEvents.cs:346-358 | Source/MSComctlLib/Events/IStatusBarEvents.cs:303-315 | Source/MSComctlLib/Events/ITabStripEvents.cs:336-348 | Source/MSComctlLib/Events/IToolbarEvents.cs:309-321 | Source/MSComctlLib/Events/ITreeViewEvents.cs:449-461 | Source/MSComctlLib/Events/ListViewEvents.cs:417-429 — These 8 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 8 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 8 times.
D4 · Code Duplication · Members sharing a duplicated core (7 members, 50+ identical tokens) · ×5
  • Members sharing a duplicated core (7 members, 50+ identical tokens) Source/Excel/Events/AppEvents.cs:727 — Source/Excel/Events/AppEvents.cs:727-747 | Source/Excel/Events/AppEvents.cs:750-767 | Source/Excel/Events/AppEvents.cs:770-788 | Source/Excel/Events/AppEvents.cs:791-808 | Source/Excel/Events/WorkbookEvents.cs:641-656 | Source/Excel/Events/WorkbookEvents.cs:659-675 | Source/Excel/Events/WorkbookEvents.cs:678-693 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
  • Members sharing a duplicated core (7 members, 50+ identical tokens) Source/Office/DispatchInterfaces/CommandBar.cs:523 — Source/Office/DispatchInterfaces/CommandBar.cs:523-535 | Source/Office/DispatchInterfaces/CommandBarControl.cs:587-599 | Source/Office/DispatchInterfaces/CommandBarPopup.cs:236-248 | Source/Office/DispatchInterfaces/IAccessible.cs:725-737 | Source/Office/DispatchInterfaces/_CommandBarActiveX.cs:249-261 | Source/Office/DispatchInterfaces/_CommandBarButton.cs:339-351 | Source/Office/DispatchInterfaces/_CommandBarComboBox.cs:348-360 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
  • Members sharing a duplicated core (7 members, 50+ identical tokens) Source/NetOffice/Invoker.cs:171 — Source/NetOffice/Invoker.cs:171-198 | Source/NetOffice/Invoker.cs:980-1007 | Source/NetOffice/Invoker.cs:1018-1045 | Source/NetOffice/Invoker.cs:1054-1076 | Source/NetOffice/Invoker.cs:1086-1108 | Source/NetOffice/Invoker.cs:1118-1140 | Source/NetOffice/Invoker.cs:1149-1171 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
  • Members sharing a duplicated core (7 members, 50+ identical tokens) Source/Access/Events/DispComboBoxEvents.cs:398 — Source/Access/Events/DispComboBoxEvents.cs:398-410 | Source/Access/Events/DispNavigationControlEvents.cs:374-386 | Source/Access/Events/DispTextBoxEvents.cs:374-386 | Source/Access/Events/_ComboBoxEvents.cs:396-408 | Source/Access/Events/_FormEvents.cs:767-779 | Source/Access/Events/_FormEvents2.cs:744-756 | Source/Access/Events/_TextBoxEvents.cs:371-383 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
  • Members sharing a duplicated core (7 members, 50+ identical tokens) Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/NetOfficeSupportTable.cs:84 — Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/NetOfficeSupportTable.cs:84-103 | Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/NetOfficeSupportTable.cs:112-143 | Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/NetOfficeSupportTable.cs:151-174 | Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/NetOfficeSupportTable.cs:182-208 | Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/NetOfficeSupportTable.cs:315-338 | Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/NetOfficeSupportTable.cs:341-359 | Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/NetOfficeSupportTable.cs:362-386 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
D4 · Code Duplication · Edited copy of a member (16 corresponding lines) · ×5
  • Edited copy of a member (16 corresponding lines) Source/Word/Events/ApplicationEvents4.cs:625 — Source/Word/Events/ApplicationEvents4.cs:625-643 | Source/Word/Events/DocumentEvents2.cs:183-198 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) Source/OWC10/Events/ISpreadsheetEventSink.cs:548 — Source/OWC10/Events/ISpreadsheetEventSink.cs:548-563 | Source/OWC10/Events/ISpreadsheetEventSink.cs:566-581 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) BuildTools/SearchAndReplace/Form1.cs:65 — BuildTools/SearchAndReplace/Form1.cs:65-80 | BuildTools/VersionUpdater/Form1.cs:444-459 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) Source/Office.Extensions/TrayMenuUtils/TrayMenu.cs:831 — Source/Office.Extensions/TrayMenuUtils/TrayMenu.cs:831-847 | Source/Office.Extensions/TrayMenuUtils/TrayMenu.cs:856-871 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) Source/NetOffice/Running/ProxyService.cs:101 — Source/NetOffice/Running/ProxyService.cs:101-117 | Source/NetOffice/Running/ProxyService.cs:120-135 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (18 corresponding lines) · ×5
  • Edited copy of a member (18 corresponding lines) Source/Excel/Events/AppEvents.cs:811 — Source/Excel/Events/AppEvents.cs:811-828 | Source/Word/Events/DocumentEvents2.cs:298-317 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) Source/Outlook/Tools/FormRegionAttribute.cs:175 — Source/Outlook/Tools/FormRegionAttribute.cs:175-192 | Source/Outlook/Tools/RequireShutdownNotificationAttribute.cs:33-50 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) Toolbox/Toolbox/ToolboxControls/OutlookSecurity/OutlookSecurityControl.cs:148 — Toolbox/Toolbox/ToolboxControls/OutlookSecurity/OutlookSecurityControl.cs:148-165 | Toolbox/Toolbox/ToolboxControls/RegistryEditor/RegistryEditorControl.cs:176-199 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) Toolbox/Toolbox/ToolboxControls/ProxyView/RotEntryCollection.cs:57 — Toolbox/Toolbox/ToolboxControls/ProxyView/RotEntryCollection.cs:57-74 | Toolbox/Toolbox/ToolboxControls/ProxyView/WindowEntryCollection.cs:66-83 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) Source/NetOffice/Running/RunningObjectTable.cs:37 — Source/NetOffice/Running/RunningObjectTable.cs:37-58 | Source/NetOffice/Running/RunningWindowTable.Nested.cs:167-184 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 14+ corresponding lines) · ×5
  • Edited copies of one member (3 members, 14+ corresponding lines) Source/Excel/Events/AppEvents.cs:599 — Source/Excel/Events/AppEvents.cs:599-612 | Source/Excel/Events/AppEvents.cs:615-628 | Source/Excel/Events/AppEvents.cs:631-644 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 14+ corresponding lines) Source/PowerPoint/Events/EApplication.cs:342 — Source/PowerPoint/Events/EApplication.cs:342-355 | Source/PowerPoint/Events/EApplication.cs:358-371 | Source/PowerPoint/Events/EApplication.cs:533-546 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 14+ corresponding lines) BuildTools/SearchAndReplace/SearchAndReplaceManager.cs:44 — BuildTools/SearchAndReplace/SearchAndReplaceManager.cs:44-57 | BuildTools/SearchAndReplace/SearchAndReplaceManager.cs:60-73 | BuildTools/SearchAndReplace/SearchAndReplaceManager.cs:76-89 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 14+ corresponding lines) Source/OWC10/Events/IPivotControlEvents.cs:371 — Source/OWC10/Events/IPivotControlEvents.cs:371-384 | Source/OWC10/Events/ISpreadsheetEventSink.cs:431-444 | Source/OWC10/Events/ISpreadsheetEventSink.cs:447-460 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 14+ corresponding lines) Source/NetOffice/Tools/Tweaks.cs:210 — Source/NetOffice/Tools/Tweaks.cs:210-224 | Source/NetOffice/Tools/Tweaks.cs:227-240 | Source/NetOffice/Tools/Tweaks.cs:243-256 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 6+ corresponding lines) · ×5
  • Edited copies of one member (3 members, 6+ corresponding lines) Source/DAO/Modules/Global.cs:347 — Source/DAO/Modules/Global.cs:347-352 | Source/DAO/Modules/Global.cs:558-563 | Source/DAO/Modules/Global.cs:574-579 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 6+ corresponding lines) Source/NetOffice/Diagnostics/SelfDiagnostics.cs:75 — Source/NetOffice/Diagnostics/SelfDiagnostics.cs:75-81 | Source/Office/Tools/Informations/AssemblyInfo.cs:84-90 | Toolbox/Toolbox/AssemblyInfo.cs:49-54 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 6+ corresponding lines) Source/NetOffice/Diagnostics/SelfDiagnostics.cs:90 — Source/NetOffice/Diagnostics/SelfDiagnostics.cs:90-96 | Source/Office/Tools/Informations/AssemblyInfo.cs:99-105 | Toolbox/Toolbox/AssemblyInfo.cs:63-68 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 6+ corresponding lines) Source/NetOffice/Diagnostics/SelfDiagnostics.cs:105 — Source/NetOffice/Diagnostics/SelfDiagnostics.cs:105-111 | Source/Office/Tools/Informations/AssemblyInfo.cs:114-120 | Toolbox/Toolbox/AssemblyInfo.cs:77-82 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 6+ corresponding lines) Source/NetOffice/Diagnostics/SelfDiagnostics.cs:120 — Source/NetOffice/Diagnostics/SelfDiagnostics.cs:120-126 | Source/Office/Tools/Informations/AssemblyInfo.cs:129-135 | Toolbox/Toolbox/AssemblyInfo.cs:91-96 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 9+ corresponding lines) · ×5
  • Edited copies of one member (4 members, 9+ corresponding lines) Source/Excel/DispatchInterfaces/Adjustments.cs:209 — Source/Excel/DispatchInterfaces/Adjustments.cs:209-217 | Source/Office/DispatchInterfaces/Adjustments.cs:208-216 | Source/PowerPoint/DispatchInterfaces/Adjustments.cs:239-247 | Source/Word/DispatchInterfaces/Adjustments.cs:238-246 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 9+ corresponding lines) Source/Access/Events/DispPageHdrFtrInReportEvents.cs:218 — Source/Access/Events/DispPageHdrFtrInReportEvents.cs:218-226 | Source/Access/Events/DispSectionInReportEvents.cs:233-241 | Source/Access/Events/_SectionEvents.cs:173-181 | Source/Access/Events/_SectionInReportEvents.cs:234-242 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 9+ corresponding lines) Source/Access/Events/_FormEvents.cs:472 — Source/Access/Events/_FormEvents.cs:472-480 | Source/Access/Events/_FormEvents2.cs:448-456 | Source/Access/Events/_ReportEvents2.cs:288-296 | Source/Excel/Events/ChartEvents.cs:142-150 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 9+ corresponding lines) Source/Outlook/Events/OlkComboBoxEvents.cs:289 — Source/Outlook/Events/OlkComboBoxEvents.cs:289-297 | Source/Outlook/Events/OlkDateControlEvents.cs:289-297 | Source/Outlook/Events/OlkTimeControlEvents.cs:289-297 | Source/Outlook/Events/OlkTimeZoneControlEvents.cs:289-297 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 9+ corresponding lines) Examples/Excel/Automation/FormMain.cs:16 — Examples/Excel/Automation/FormMain.cs:16-27 | Examples/Outlook/Automation/FormMain.cs:17-25 | Examples/PowerPoint/Automation/FormMain.cs:17-25 | Examples/Word/Automation/FormMain.cs:25-33 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (18 lines × 2) · ×5
  • Duplicated block (18 lines × 2) Source/Access/Events/_FormEvents.cs:171 — Source/Access/Events/_FormEvents.cs:171-188 | Source/Access/Events/_FormEvents2.cs:173-190 — before extracting anything, compare `Source/Access/Events/_FormEvents.cs` and `Source/Access/Events/_FormEvents2.cs` as WHOLE FILES: this scan already matched 72 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (18 lines × 2) Source/Excel/Tools/RealtimeDataServer.cs:448 — Source/Excel/Tools/RealtimeDataServer.cs:448-465 | Source/Word/Tools/DocumentInspectorBase.cs:295-312 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (18 lines × 2) Source/NetOffice/Utils.cs:147 — Source/NetOffice/Utils.cs:147-164 | Source/NetOffice/Utils.cs:180-197 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/NetOffice/Utils.cs:147` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 2) Source/Word/Events/ApplicationEvents3.cs:433 — Source/Word/Events/ApplicationEvents3.cs:433-450 | Source/Word/Events/ApplicationEvents4.cs:506-523 — before extracting anything, compare `Source/Word/Events/ApplicationEvents3.cs` and `Source/Word/Events/ApplicationEvents4.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 469 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (18 lines × 2) Source/Word/Events/ApplicationEvents3.cs:516 — Source/Word/Events/ApplicationEvents3.cs:516-533 | Source/Word/Events/ApplicationEvents4.cs:589-606 — before extracting anything, compare `Source/Word/Events/ApplicationEvents3.cs` and `Source/Word/Events/ApplicationEvents4.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 469 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (5 lines × 8) · ×5
  • Duplicated block (5 lines × 8) Source/Word/Events/ApplicationEvents2.cs:236 — Source/Word/Events/ApplicationEvents2.cs:236-240 | Source/Word/Events/ApplicationEvents2.cs:252-256 | Source/Word/Events/ApplicationEvents3.cs:301-305 | Source/Word/Events/ApplicationEvents3.cs:317-321 | Source/Word/Events/ApplicationEvents3.cs:543-547 | Source/Word/Events/ApplicationEvents4.cs:374-378 | Source/Word/Events/ApplicationEvents4.cs:390-394 | Source/Word/Events/ApplicationEvents4.cs:616-620 — before extracting anything, compare `Source/Word/Events/ApplicationEvents2.cs` and `Source/Word/Events/ApplicationEvents3.cs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 270 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 8) Source/OWC10/Events/IChartEvents.cs:68 — Source/OWC10/Events/IChartEvents.cs:68-72 | Source/OWC10/Events/IChartEvents.cs:76-80 | Source/OWC10/Events/IChartEvents.cs:84-88 | Source/OWC10/Events/IPivotControlEvents.cs:54-58 | Source/OWC10/Events/IPivotControlEvents.cs:62-66 | Source/OWC10/Events/IPivotControlEvents.cs:70-74 | Source/OWC10/Events/ISpreadsheetEventSink.cs:113-117 | Source/OWC10/Events/ISpreadsheetEventSink.cs:135-139 — before extracting anything, compare `Source/OWC10/Events/IChartEvents.cs` and `Source/OWC10/Events/IPivotControlEvents.cs` as WHOLE FILES: this scan already matched 39 separate duplicated blocks between them, totalling at least 404 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 8) Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleMultiAddinConverterCS.cs:111 — Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleMultiAddinConverterCS.cs:111-115 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleMultiAddinConverterVB.cs:119-123 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleSingleAddinConverterCS.cs:97-101 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleSingleAddinConverterVB.cs:107-111 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsMultiAddinConverterCS.cs:96-100 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsMultiAddinConverterVB.cs:108-112 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsSingleAddinConverterCS.cs:96-100 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsSingleAddinConverterVB.cs:108-112 — before extracting anything, compare `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleMultiAddinConverterCS.cs` and `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleMultiAddinConverterVB.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 85 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsMultiAddinConverterCS.cs:102` calls `Replace` and `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleMultiAddinConverterCS.cs:118` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 8) Source/Word/Events/ApplicationEvents2.cs:60 — Source/Word/Events/ApplicationEvents2.cs:60-64 | Source/Word/Events/ApplicationEvents2.cs:66-70 | Source/Word/Events/ApplicationEvents3.cs:60-64 | Source/Word/Events/ApplicationEvents3.cs:66-70 | Source/Word/Events/ApplicationEvents3.cs:148-152 | Source/Word/Events/ApplicationEvents4.cs:60-64 | Source/Word/Events/ApplicationEvents4.cs:66-70 | Source/Word/Events/ApplicationEvents4.cs:148-152 — before extracting anything, compare `Source/Word/Events/ApplicationEvents2.cs` and `Source/Word/Events/ApplicationEvents3.cs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 270 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 8) Source/Excel/DispatchInterfaces/ModelTableNames.cs:217 — Source/Excel/DispatchInterfaces/ModelTableNames.cs:217-221 | Source/Excel/Interfaces/IModelTableNames.cs:210-214 | Source/MSComctlLib/DispatchInterfaces/IVBDataObjectFiles.cs:209-213 | Source/Office/DispatchInterfaces/AnswerWizardFiles.cs:206-210 | Source/Office/DispatchInterfaces/FileDialogSelectedItems.cs:184-188 | Source/Office/DispatchInterfaces/FoundFiles.cs:168-172 | Source/Office/DispatchInterfaces/IFoundFiles.cs:168-172 | Source/Word/DispatchInterfaces/FontNames.cs:212-216 — before extracting anything, compare `Source/Excel/DispatchInterfaces/ModelTableNames.cs` and `Source/Excel/Interfaces/IModelTableNames.cs` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (9 lines × 3) · ×5
  • Duplicated block (9 lines × 3) Source/Access/Events/DispNavigationButtonEvents.cs:32 — Source/Access/Events/DispNavigationButtonEvents.cs:32-40 | Source/Access/Events/DispNavigationControlEvents.cs:41-49 | Source/Access/Events/DispWebBrowserControlEvents.cs:51-59 — before extracting anything, compare `Source/Access/Events/DispNavigationButtonEvents.cs` and `Source/Access/Events/DispNavigationControlEvents.cs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 226 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Source/Access/Events/DispNavigationControlEvents.cs:50` calls `MethodImpl`, `DispId`, `Click` and `Source/Access/Events/DispNavigationButtonEvents.cs:41` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (9 lines × 3) Source/Office.Extensions/Dialogs/DialogUtilsEx.cs:870 — Source/Office.Extensions/Dialogs/DialogUtilsEx.cs:870-878 | Source/Office.Extensions/Dialogs/DialogUtilsEx.cs:900-908 | Source/Office.Extensions/Dialogs/DialogUtilsEx.cs:1096-1104 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (9 lines × 3) Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/NetOfficeSupportTable.cs:88 — Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/NetOfficeSupportTable.cs:88-96 | Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/NetOfficeSupportTable.cs:116-124 | Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/NetOfficeSupportTable.cs:157-165 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (9 lines × 3) Source/OWC10/Events/IChartEvents.cs:133 — Source/OWC10/Events/IChartEvents.cs:133-141 | Source/OWC10/Events/IPivotControlEvents.cs:154-162 | Source/OWC10/Events/ISpreadsheetEventSink.cs:19-27 — before extracting anything, compare `Source/OWC10/Events/IChartEvents.cs` and `Source/OWC10/Events/IPivotControlEvents.cs` as WHOLE FILES: this scan already matched 39 separate duplicated blocks between them, totalling at least 404 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (9 lines × 3) Source/NetOffice/CoreExtensions/CoreFactoryExtensions.cs:123 — Source/NetOffice/CoreExtensions/CoreFactoryExtensions.cs:123-133 | Source/NetOffice/CoreExtensions/CoreFactoryExtensions.cs:164-174 | Source/NetOffice/Running/RunningObjectTable.cs:592-600 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Source/NetOffice/CoreExtensions/CoreFactoryExtensions.cs:135` calls `Add`, `ReleaseComObject` and `Source/NetOffice/Running/RunningObjectTable.cs:602` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (8 lines × 11) · ×5
  • Duplicated block (8 lines × 11) Source/Access/Events/DispAttachmentEvents.cs:21 — Source/Access/Events/DispAttachmentEvents.cs:21-28 | Source/Access/Events/DispBoundObjectFrameEvents.cs:26-33 | Source/Access/Events/DispCheckBoxEvents.cs:25-32 | Source/Access/Events/DispComboBoxEvents.cs:21-28 | Source/Access/Events/DispListBoxEvents.cs:21-28 | Source/Access/Events/DispOptionButtonEvents.cs:24-31 | Source/Access/Events/DispOptionGroupEvents.cs:21-28 | Source/Access/Events/DispPaletteButtonEvents.cs:25-32 | Source/Access/Events/DispTextBoxEvents.cs:21-28 | Source/Access/Events/DispToggleButtonEvents.cs:25-32 | Source/Access/Events/_FormEvents2.cs:38-45 — before extracting anything, compare `Source/Access/Events/DispAttachmentEvents.cs` and `Source/Access/Events/DispBoundObjectFrameEvents.cs` as WHOLE FILES: this scan already matched 29 separate duplicated blocks between them, totalling at least 271 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Source/Access/Events/DispAttachmentEvents.cs:29` calls `MethodImpl`, `DispId`, `Enter` and `Source/Access/Events/_FormEvents2.cs:46` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (8 lines × 11) Source/Access/Events/_BoundObjectFrameEvents.cs:39 — Source/Access/Events/_BoundObjectFrameEvents.cs:39-46 | Source/Access/Events/_CheckBoxEvents.cs:38-45 | Source/Access/Events/_ComboBoxEvents.cs:43-50 | Source/Access/Events/_CommandButtonEvents.cs:28-35 | Source/Access/Events/_CustomControlEvents.cs:29-36 | Source/Access/Events/_ListBoxEvents.cs:33-40 | Source/Access/Events/_ObjectFrameEvents.cs:30-37 | Source/Access/Events/_OptionButtonEvents.cs:38-45 | Source/Access/Events/_PaletteButtonEvents.cs:38-45 | Source/Access/Events/_TextBoxEvents.cs:36-43 | Source/Access/Events/_ToggleButtonEvents.cs:38-45 — before extracting anything, compare `Source/Access/Events/_BoundObjectFrameEvents.cs` and `Source/Access/Events/_CheckBoxEvents.cs` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 292 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Access/Events/_BoundObjectFrameEvents.cs:38` calls `SinkArgument` and `Source/Access/Events/_ComboBoxEvents.cs:42` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (8 lines × 11) Source/Access/Events/_FormEvents.cs:510 — Source/Access/Events/_FormEvents.cs:510-517 | Source/Access/Events/_FormEvents2.cs:486-493 | Source/Access/Events/_ReportEvents.cs:105-112 | Source/Access/Events/_ReportEvents2.cs:202-209 | Source/Excel/Events/ChartEvents.cs:121-128 | Source/Excel/Events/DocEvents.cs:186-193 | Source/Excel/Events/WorkbookEvents.cs:288-295 | Source/Outlook/Events/ExplorerEvents.cs:82-89 | Source/Outlook/Events/ExplorerEvents_10.cs:131-138 | Source/Outlook/Events/InspectorEvents.cs:59-66 | Source/Outlook/Events/InspectorEvents_10.cs:88-95 — before extracting anything, compare `Source/Access/Events/_FormEvents.cs` and `Source/Access/Events/_FormEvents2.cs` as WHOLE FILES: this scan already matched 72 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (8 lines × 11) Source/Access/Events/_FormEvents.cs:521 — Source/Access/Events/_FormEvents.cs:521-528 | Source/Access/Events/_FormEvents2.cs:497-504 | Source/Access/Events/_ReportEvents.cs:116-123 | Source/Access/Events/_ReportEvents2.cs:213-220 | Source/Excel/Events/ChartEvents.cs:132-139 | Source/Excel/Events/DocEvents.cs:197-204 | Source/Excel/Events/WorkbookEvents.cs:299-306 | Source/Outlook/Events/ExplorerEvents.cs:149-156 | Source/Outlook/Events/ExplorerEvents_10.cs:198-205 | Source/Outlook/Events/InspectorEvents.cs:70-77 | Source/Outlook/Events/InspectorEvents_10.cs:99-106 — before extracting anything, compare `Source/Access/Events/_FormEvents.cs` and `Source/Access/Events/_FormEvents2.cs` as WHOLE FILES: this scan already matched 72 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (8 lines × 11) Source/Access/Events/_FormEvents.cs:499 — Source/Access/Events/_FormEvents.cs:499-506 | Source/Access/Events/_FormEvents2.cs:475-482 | Source/Access/Events/_ReportEvents.cs:94-101 | Source/Access/Events/_ReportEvents2.cs:191-198 | Source/Outlook/Events/ExplorerEvents.cs:171-178 | Source/Outlook/Events/ExplorerEvents_10.cs:220-227 | Source/Outlook/Events/FormRegionEvents.cs:70-77 | Source/Outlook/Events/InspectorEvents.cs:81-88 | Source/Outlook/Events/InspectorEvents_10.cs:110-117 | Source/Word/Events/DocumentEvents.cs:81-88 | Source/Word/Events/DocumentEvents2.cs:143-150 — before extracting anything, compare `Source/Access/Events/_FormEvents.cs` and `Source/Access/Events/_FormEvents2.cs` as WHOLE FILES: this scan already matched 72 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (10 lines × 5) · ×5
  • Duplicated block (10 lines × 5) Source/Outlook/Events/ItemEvents.cs:311 — Source/Outlook/Events/ItemEvents.cs:311-320 | Source/Outlook/Events/ItemEvents.cs:325-334 | Source/Outlook/Events/ItemEvents_10.cs:368-377 | Source/Outlook/Events/ItemEvents_10.cs:382-391 | Source/Outlook/Events/ItemEvents_10.cs:430-439 — before extracting anything, compare `Source/Outlook/Events/ItemEvents.cs` and `Source/Outlook/Events/ItemEvents_10.cs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 292 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (10 lines × 5) Source/PowerPoint/Events/EApplication.cs:375 — Source/PowerPoint/Events/EApplication.cs:375-384 | Source/PowerPoint/Events/EApplication.cs:389-398 | Source/PowerPoint/Events/EApplication.cs:403-412 | Source/PowerPoint/Events/EApplication.cs:550-559 | Source/PowerPoint/Events/EApplication.cs:564-573 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (10 lines × 5) Source/Access/Tools/COMAddin.cs:403 — Source/Access/Tools/COMAddin.cs:403-412 | Source/Office/Tools/COMAddin.cs:408-417 | Source/Outlook/Tools/COMAddin.cs:436-445 | Source/PowerPoint/Tools/COMAddin.cs:404-413 | Source/Word/Tools/COMAddin.cs:405-414 — before extracting anything, compare `Source/Access/Tools/COMAddin.cs` and `Source/Office/Tools/COMAddin.cs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 287 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (10 lines × 5) Source/Access/Tools/COMAddin.cs:416 — Source/Access/Tools/COMAddin.cs:416-425 | Source/Office/Tools/COMAddin.cs:421-430 | Source/Outlook/Tools/COMAddin.cs:449-458 | Source/PowerPoint/Tools/COMAddin.cs:417-426 | Source/Word/Tools/COMAddin.cs:418-427 — before extracting anything, compare `Source/Access/Tools/COMAddin.cs` and `Source/Office/Tools/COMAddin.cs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 287 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (10 lines × 5) Examples/Access/IExtensibility COMAddin Examples/TaskPane/Addin.cs:35 — Examples/Access/IExtensibility COMAddin Examples/TaskPane/Addin.cs:35-44 | Examples/Excel/IExtensibility COMAddin Examples/TaskPane/Addin.cs:35-44 | Examples/Outlook/IExtensibility COMAddin Examples/TaskPane/Addin.cs:37-46 | Examples/PowerPoint/IExtensibility COMAddin Examples/TaskPane/Addin.cs:35-44 | Examples/Word/IExtensibility COMAddin Examples/TaskPane/Addin.cs:35-44 — before extracting anything, compare `Examples/Access/IExtensibility COMAddin Examples/TaskPane/Addin.cs` and `Examples/Excel/IExtensibility COMAddin Examples/TaskPane/Addin.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 72 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Examples/Access/IExtensibility COMAddin Examples/TaskPane/Addin.cs:35` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
IC1 · Incompleteness & stubs · Both branches open with the same statements · ×5
  • Both branches open with the same statements — the condition does not decide them Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsSingleAddinConverterCS.cs:139 — The first 1 statement of the `if` and of the `else` are identical, so it runs on both paths regardless of the condition. Lift it above the `if` — leaving it duplicated inside makes the branches read as though they handled this differently.
  • Both branches open with the same statements — the condition does not decide them Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsSingleAddinConverterVB.cs:167 — The first 1 statement of the `if` and of the `else` are identical, so it runs on both paths regardless of the condition. Lift it above the `if` — leaving it duplicated inside makes the branches read as though they handled this differently.
  • Both branches open with the same statements — the condition does not decide them Toolbox/Toolbox/ToolboxControls/Welcome/WelcomeControl.cs:219 — The first 2 statements of the `if` and of the `else` are identical, so they run on both paths regardless of the condition. Lift them above the `if` — leaving them duplicated inside makes the branches read as though they handled this differently.
  • Both branches open with the same statements — the condition does not decide them Toolbox/Toolbox/ToolboxControls/Welcome/WelcomeControl.cs:239 — The first 1 statement of the `if` and of the `else` are identical, so it runs on both paths regardless of the condition. Lift it above the `if` — leaving it duplicated inside makes the branches read as though they handled this differently.
  • Both branches open with the same statements — the condition does not decide them Toolbox/Toolbox/Utils/Registry/UtilsRegistryEntry.cs:81 — The first 3 statements of the `if` and of the `else` are identical, so they run on both paths regardless of the condition. Lift them above the `if` — leaving them duplicated inside makes the branches read as though they handled this differently.
D4 · Code Duplication · Members sharing a duplicated core (9 members, 50+ identical tokens) · ×4
  • Members sharing a duplicated core (9 members, 50+ identical tokens) Source/Outlook/Events/OlkCheckBoxEvents.cs:296 — Source/Outlook/Events/OlkCheckBoxEvents.cs:296-308 | Source/Outlook/Events/OlkComboBoxEvents.cs:311-323 | Source/Outlook/Events/OlkCommandButtonEvents.cs:281-293 | Source/Outlook/Events/OlkDateControlEvents.cs:311-323 | Source/Outlook/Events/OlkListBoxEvents.cs:296-308 | Source/Outlook/Events/OlkOptionButtonEvents.cs:296-308 | Source/Outlook/Events/OlkTextBoxEvents.cs:296-308 | Source/Outlook/Events/OlkTimeControlEvents.cs:311-323 | Source/Outlook/Events/OlkTimeZoneControlEvents.cs:311-323 — These 9 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 9 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 9 times.
  • Members sharing a duplicated core (9 members, 50+ identical tokens) Source/PowerPoint/Events/EApplication.cs:272 — Source/PowerPoint/Events/EApplication.cs:272-283 | Source/PowerPoint/Events/EApplication.cs:286-297 | Source/PowerPoint/Events/EApplication.cs:300-311 | Source/PowerPoint/Events/EApplication.cs:314-325 | Source/PowerPoint/Events/EApplication.cs:416-427 | Source/PowerPoint/Events/EApplication.cs:430-441 | Source/PowerPoint/Events/EApplication.cs:505-516 | Source/PowerPoint/Events/EApplication.cs:519-530 | Source/PowerPoint/Events/EApplication.cs:672-683 — These 9 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 9 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 9 times.
  • Members sharing a duplicated core (9 members, 50+ identical tokens) Source/Access/Events/DispAttachmentEvents.cs:187 — Source/Access/Events/DispAttachmentEvents.cs:187-199 | Source/Access/Events/DispComboBoxEvents.cs:383-395 | Source/Access/Events/DispNavigationControlEvents.cs:359-371 | Source/Access/Events/DispTextBoxEvents.cs:359-371 | Source/Access/Events/DispWebBrowserControlEvents.cs:226-238 | Source/Access/Events/_ComboBoxEvents.cs:381-393 | Source/Access/Events/_FormEvents.cs:752-764 | Source/Access/Events/_FormEvents2.cs:729-741 | Source/Access/Events/_TextBoxEvents.cs:356-368 — These 9 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 9 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 9 times.
  • Members sharing a duplicated core (9 members, 50+ identical tokens) Examples/Access/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:184 — Examples/Access/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:184-195 | Examples/Access/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:158-169 | Examples/Access/IExtensibility COMAddin Examples/TaskPane/Addin.cs:136-151 | Examples/Excel/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:127-142 | Examples/Excel/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:152-167 | Examples/Excel/IExtensibility COMAddin Examples/TaskPane/Addin.cs:136-150 | Examples/PowerPoint/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:126-137 | Examples/PowerPoint/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:157-168 | Examples/PowerPoint/IExtensibility COMAddin Examples/TaskPane/Addin.cs:137-152 — These 9 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 9 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 9 times.
D4 · Code Duplication · Edited copy of a member (21 corresponding lines) · ×4
  • Edited copy of a member (21 corresponding lines) Source/Excel/Events/AppEvents.cs:883 — Source/Excel/Events/AppEvents.cs:883-903 | Source/Excel/Events/WorkbookEvents.cs:755-775 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) Source/Access/Events/DispWebBrowserControlEvents.cs:412 — Source/Access/Events/DispWebBrowserControlEvents.cs:412-436 | Source/Access/Events/DispWebBrowserControlEvents.cs:473-493 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) Source/Outlook/Tools/Contribution/Security/Automation.cs:304 — Source/Outlook/Tools/Contribution/Security/Automation.cs:304-324 | Source/Outlook/Tools/Contribution/Security/Automation.cs:327-347 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) Source/NetOffice/Running/RunningObjectTable.cs:61 — Source/NetOffice/Running/RunningObjectTable.cs:61-85 | Source/NetOffice/Running/RunningWindowTable.Nested.cs:187-207 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (19 corresponding lines) · ×4
  • Edited copy of a member (19 corresponding lines) RegAddin/RegAddin/Common/AddinClassInformations.cs:30 — RegAddin/RegAddin/Common/AddinClassInformations.cs:30-62 | RegAddin/RegAddin/Common/AddinClassInformations.cs:66-84 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) Toolbox/Toolbox/Controls/Hex/HexBox.cs:1812 — Toolbox/Toolbox/Controls/Hex/HexBox.cs:1812-1835 | Toolbox/Toolbox/Controls/Hex/HexBox.cs:1838-1856 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) Source/Word/Tools/Contribution/ApplicationUtils.cs:155 — Source/Word/Tools/Contribution/ApplicationUtils.cs:155-177 | Source/PowerPoint/Tools/Contribution/ApplicationUtils.cs:164-182 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) REDACTED:116 — REDACTED:116-137 | REDACTED:115-133 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (27 corresponding lines) · ×4
  • Edited copy of a member (27 corresponding lines) Source/Office.Extensions/TrayMenuUtils/TrayMenuMonitorItemControl.cs:203 — Source/Office.Extensions/TrayMenuUtils/TrayMenuMonitorItemControl.cs:203-229 | Source/Office.Extensions/TrayMenuUtils/TrayMenuMonitorItemControl.cs:232-258 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) Source/NetOffice/Extensions/EnumerableExtensions.cs:62 — Source/NetOffice/Extensions/EnumerableExtensions.cs:62-95 | Source/NetOffice/Extensions/EnumerableExtensions.cs:443-469 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) Source/Word/Tools/COMAddin.cs:656 — Source/Word/Tools/COMAddin.cs:656-684 | Source/Word/Tools/COMAddin.cs:687-713 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) Source/Word/Tools/DocumentInspectorBase.cs:145 — Source/Word/Tools/DocumentInspectorBase.cs:145-173 | Source/Word/Tools/DocumentInspectorBase.cs:176-202 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (24 corresponding lines) · ×4
  • Edited copy of a member (24 corresponding lines) Source/NetOffice/Extensions/CallExtensions.cs:61 — Source/NetOffice/Extensions/CallExtensions.cs:61-84 | Source/NetOffice/Extensions/CallExtensions.cs:135-162 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) Source/NetOffice/Tools/Tweaks.cs:317 — Source/NetOffice/Tools/Tweaks.cs:317-341 | Source/NetOffice/Tools/Tweaks.cs:376-399 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) Toolbox/Toolbox/Controls/Hex/HexBox.cs:747 — Toolbox/Toolbox/Controls/Hex/HexBox.cs:747-770 | Toolbox/Toolbox/Controls/Hex/HexBox.cs:977-1000 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) Source/NetOffice/Contribution/CollectionsGeneric/DisposableSequence.cs:84 — Source/NetOffice/Contribution/CollectionsGeneric/DisposableSequence.cs:84-107 | Source/NetOffice/Contribution/CollectionsGeneric/DisposableSequence.cs:233-266 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 3+ corresponding lines) · ×4
  • Edited copies of one member (4 members, 3+ corresponding lines) Source/Excel/DispatchInterfaces/AddIns.cs:198 — Source/Excel/DispatchInterfaces/AddIns.cs:198-200 | Source/Excel/DispatchInterfaces/AddIns2.cs:198-200 | Source/Excel/Interfaces/IAddIns.cs:192-194 | Source/Excel/Interfaces/IAddIns2.cs:192-194 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 3+ corresponding lines) Source/Excel/DispatchInterfaces/Range.cs:487 — Source/Excel/DispatchInterfaces/Range.cs:487-489 | Source/Excel/DispatchInterfaces/_Application.cs:717-719 | Source/Excel/DispatchInterfaces/_Worksheet.cs:739-741 | Source/Excel/Interfaces/IRange.cs:1539-1541 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 3+ corresponding lines) Source/PowerPoint/DispatchInterfaces/AxisTitle.cs:90 — Source/PowerPoint/DispatchInterfaces/AxisTitle.cs:90-92 | Source/PowerPoint/DispatchInterfaces/ChartTitle.cs:90-92 | Source/PowerPoint/DispatchInterfaces/DataLabel.cs:90-92 | Source/PowerPoint/DispatchInterfaces/DisplayUnitLabel.cs:90-92 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 3+ corresponding lines) Source/Word/DispatchInterfaces/AxisTitle.cs:90 — Source/Word/DispatchInterfaces/AxisTitle.cs:90-92 | Source/Word/DispatchInterfaces/ChartTitle.cs:90-92 | Source/Word/DispatchInterfaces/DataLabel.cs:90-92 | Source/Word/DispatchInterfaces/DisplayUnitLabel.cs:90-92 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (64 lines × 3) · ×4
  • Duplicated block (64 lines × 3) Source/Excel/DispatchInterfaces/AxisTitle.cs:11 — Source/Excel/DispatchInterfaces/AxisTitle.cs:11-74 | Source/PowerPoint/DispatchInterfaces/AxisTitle.cs:11-74 | Source/Word/DispatchInterfaces/AxisTitle.cs:11-74 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Source/Excel/DispatchInterfaces/AxisTitle.cs:11` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (64 lines × 3) Source/Excel/DispatchInterfaces/ChartTitle.cs:11 — Source/Excel/DispatchInterfaces/ChartTitle.cs:11-74 | Source/PowerPoint/DispatchInterfaces/ChartTitle.cs:11-74 | Source/Word/DispatchInterfaces/ChartTitle.cs:11-74 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Source/Excel/DispatchInterfaces/ChartTitle.cs:11` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (64 lines × 3) Source/Excel/DispatchInterfaces/DataLabel.cs:11 — Source/Excel/DispatchInterfaces/DataLabel.cs:11-74 | Source/PowerPoint/DispatchInterfaces/DataLabel.cs:11-74 | Source/Word/DispatchInterfaces/DataLabel.cs:11-74 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Source/Excel/DispatchInterfaces/DataLabel.cs:11` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (64 lines × 3) Source/Excel/DispatchInterfaces/DisplayUnitLabel.cs:11 — Source/Excel/DispatchInterfaces/DisplayUnitLabel.cs:11-74 | Source/PowerPoint/DispatchInterfaces/DisplayUnitLabel.cs:11-74 | Source/Word/DispatchInterfaces/DisplayUnitLabel.cs:11-74 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Source/Excel/DispatchInterfaces/DisplayUnitLabel.cs:11` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (64 lines × 2) · ×4
  • Duplicated block (64 lines × 2) Source/Excel/DispatchInterfaces/Name.cs:11 — Source/Excel/DispatchInterfaces/Name.cs:11-74 | Source/OWC10/DispatchInterfaces/Name.cs:11-74 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Source/Excel/DispatchInterfaces/Name.cs:11` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (64 lines × 2) Source/Excel/DispatchInterfaces/Range.cs:14 — Source/Excel/DispatchInterfaces/Range.cs:14-77 | Source/Word/DispatchInterfaces/Range.cs:11-74 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Source/Excel/DispatchInterfaces/Range.cs:14` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (64 lines × 2) Source/Excel/DispatchInterfaces/RoutingSlip.cs:11 — Source/Excel/DispatchInterfaces/RoutingSlip.cs:11-74 | Source/Word/DispatchInterfaces/RoutingSlip.cs:11-74 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Source/Excel/DispatchInterfaces/RoutingSlip.cs:11` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (64 lines × 2) Source/PowerPoint/DispatchInterfaces/Chart.cs:11 — Source/PowerPoint/DispatchInterfaces/Chart.cs:11-74 | Source/Word/DispatchInterfaces/Chart.cs:12-75 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Source/PowerPoint/DispatchInterfaces/Chart.cs:11` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (41 lines × 2) · ×4
  • Duplicated block (41 lines × 2) Source/Access/Classes/References.cs:74 — Source/Access/Classes/References.cs:74-114 | Source/VBIDE/Classes/References.cs:73-113 — before extracting anything, compare `Source/Access/Classes/References.cs` and `Source/VBIDE/Classes/References.cs` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (41 lines × 2) Source/PowerPoint/Classes/OLEControl.cs:73 — Source/PowerPoint/Classes/OLEControl.cs:73-113 | Source/Word/Classes/OLEControl.cs:73-113 — before extracting anything, compare `Source/PowerPoint/Classes/OLEControl.cs` and `Source/Word/Classes/OLEControl.cs` as WHOLE FILES: 86% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (41 lines × 2) Source/Outlook/Events/ItemEvents.cs:57 — Source/Outlook/Events/ItemEvents.cs:57-97 | Source/Outlook/Events/ItemEvents_10.cs:57-97 — before extracting anything, compare `Source/Outlook/Events/ItemEvents.cs` and `Source/Outlook/Events/ItemEvents_10.cs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 292 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (41 lines × 2) Source/ADODB/Enums/ADCPROP_UPDATERESYNC_ENUM.cs:13 — Source/ADODB/Enums/ADCPROP_UPDATERESYNC_ENUM.cs:13-53 | Source/ADODB/Enums/CEResyncEnum.cs:13-53 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (34 lines × 2) · ×4
  • Duplicated block (34 lines × 2) Source/Outlook/Tools/COMAddin.cs:84 — Source/Outlook/Tools/COMAddin.cs:84-117 | Source/PowerPoint/Tools/COMAddin.cs:77-110 — before extracting anything, compare `Source/Outlook/Tools/COMAddin.cs` and `Source/PowerPoint/Tools/COMAddin.cs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 310 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (34 lines × 2) RegAddin/RegAddin/Dispatcher/RegisterMethod.cs:16 — RegAddin/RegAddin/Dispatcher/RegisterMethod.cs:16-49 | RegAddin/RegAddin/Dispatcher/UnRegisterMethod.cs:16-49 — before extracting anything, compare `RegAddin/RegAddin/Dispatcher/RegisterMethod.cs` and `RegAddin/RegAddin/Dispatcher/UnRegisterMethod.cs` as WHOLE FILES: 87% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (34 lines × 2) Source/OWC10/Events/IChartEvents.cs:32 — Source/OWC10/Events/IChartEvents.cs:32-65 | Source/OWC10/Events/IPivotControlEvents.cs:118-151 — before extracting anything, compare `Source/OWC10/Events/IChartEvents.cs` and `Source/OWC10/Events/IPivotControlEvents.cs` as WHOLE FILES: this scan already matched 39 separate duplicated blocks between them, totalling at least 404 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (34 lines × 2) Source/Word/Events/ApplicationEvents3.cs:113 — Source/Word/Events/ApplicationEvents3.cs:113-146 | Source/Word/Events/ApplicationEvents4.cs:113-146 — before extracting anything, compare `Source/Word/Events/ApplicationEvents3.cs` and `Source/Word/Events/ApplicationEvents4.cs` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 469 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×4
  • Duplicated block (19 lines × 2) Source/NetOffice/Extensions/EnumerableExtensions.cs:185 — Source/NetOffice/Extensions/EnumerableExtensions.cs:185-203 | Source/NetOffice/Extensions/EnumerableExtensions.cs:279-297 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/NetOffice/Extensions/EnumerableExtensions.cs:185` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (19 lines × 2) Source/Excel/Tools/RealtimeDataServer.cs:515 — Source/Excel/Tools/RealtimeDataServer.cs:515-533 | Source/Word/Tools/DocumentInspectorBase.cs:362-380 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (19 lines × 2) Source/Office.Extensions/Dialogs/DialogUtilsEx.cs:865 — Source/Office.Extensions/Dialogs/DialogUtilsEx.cs:865-883 | Source/Office.Extensions/Dialogs/DialogUtilsEx.cs:1091-1109 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (19 lines × 2) RegAddin/RegAddin/Common/AddinRegAnalyzer.cs:206 — RegAddin/RegAddin/Common/AddinRegAnalyzer.cs:206-224 | RegAddin/RegAddin/RegFile/RegFileOperationHost.cs:332-350 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (14 lines × 4) · ×4
  • Duplicated block (14 lines × 4) Source/NetOffice/Extensions/EnumerableExtensions.cs:185 — Source/NetOffice/Extensions/EnumerableExtensions.cs:185-198 | Source/NetOffice/Extensions/EnumerableExtensions.cs:232-245 | Source/NetOffice/Extensions/EnumerableExtensions.cs:279-292 | Source/NetOffice/Extensions/EnumerableExtensions.cs:325-338 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/NetOffice/Extensions/EnumerableExtensions.cs:185` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 4) Source/Access/Events/DispPageHdrFtrInReportEvents.cs:96 — Source/Access/Events/DispPageHdrFtrInReportEvents.cs:96-109 | Source/Access/Events/DispSectionInReportEvents.cs:100-113 | Source/Access/Events/_PageHdrFtrInReportEvents.cs:92-105 | Source/Access/Events/_SectionInReportEvents.cs:100-113 — before extracting anything, compare `Source/Access/Events/DispPageHdrFtrInReportEvents.cs` and `Source/Access/Events/DispSectionInReportEvents.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 179 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (14 lines × 4) Source/Access/Events/DispPageHdrFtrInReportEvents.cs:113 — Source/Access/Events/DispPageHdrFtrInReportEvents.cs:113-126 | Source/Access/Events/DispSectionInReportEvents.cs:117-130 | Source/Access/Events/_PageHdrFtrInReportEvents.cs:109-122 | Source/Access/Events/_SectionInReportEvents.cs:117-130 — before extracting anything, compare `Source/Access/Events/DispPageHdrFtrInReportEvents.cs` and `Source/Access/Events/DispSectionInReportEvents.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 179 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (14 lines × 4) Source/Access/Events/_FormEvents.cs:692 — Source/Access/Events/_FormEvents.cs:692-705 | Source/Access/Events/_FormEvents2.cs:668-681 | Source/Access/Events/_ReportEvents.cs:127-140 | Source/Access/Events/_ReportEvents2.cs:224-237 — before extracting anything, compare `Source/Access/Events/_FormEvents.cs` and `Source/Access/Events/_FormEvents2.cs` as WHOLE FILES: this scan already matched 72 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (7 lines × 5) · ×4
  • Duplicated block (7 lines × 5) Source/Access/Events/_FormEvents.cs:1152 — Source/Access/Events/_FormEvents.cs:1152-1158 | Source/Access/Events/_FormEvents2.cs:1031-1037 | Source/Access/Events/_ReportEvents2.cs:534-540 | Source/OWC10/Events/IChartEvents.cs:393-399 | Source/OWC10/Events/ISpreadsheetEventSink.cs:591-597 — before extracting anything, compare `Source/Access/Events/_FormEvents.cs` and `Source/Access/Events/_FormEvents2.cs` as WHOLE FILES: this scan already matched 72 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Source/Access/Events/_FormEvents.cs:1152` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 5) Source/Excel/Events/AppEvents.cs:891 — Source/Excel/Events/AppEvents.cs:891-897 | Source/Excel/Events/AppEvents.cs:914-920 | Source/Excel/Events/DocEvents.cs:283-289 | Source/Excel/Events/DocEvents.cs:304-310 | Source/Excel/Events/DocEvents.cs:325-331 — there are 5 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 5 sites; resolving a subset leaves the remainder to drift apart. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Excel/Events/AppEvents.cs:890` calls `CreateEventArgumentObjectFromComProxy` and `Source/Excel/Events/DocEvents.cs:323` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (7 lines × 5) Source/ADODB/Events/ConnectionEvents.cs:125 — Source/ADODB/Events/ConnectionEvents.cs:125-131 | Source/ADODB/Events/ConnectionEvents.cs:144-150 | Source/ADODB/Events/ConnectionEvents.cs:163-169 | Source/ADODB/Events/ConnectionEvents.cs:181-187 | Source/ADODB/Events/ConnectionEvents.cs:277-283 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (7 lines × 5) Source/Access/Tools/COMAddin.cs:905 — Source/Access/Tools/COMAddin.cs:905-911 | Source/Excel/Tools/COMAddin.cs:907-913 | Source/Outlook/Tools/COMAddin.cs:1159-1165 | Source/PowerPoint/Tools/COMAddin.cs:906-912 | Source/Word/Tools/COMAddin.cs:1047-1053 — before extracting anything, compare `Source/Access/Tools/COMAddin.cs` and `Source/Excel/Tools/COMAddin.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 284 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (7 lines × 4) · ×4
  • Duplicated block (7 lines × 4) Source/MSComctlLib/Events/IProgressBarEvents.cs:41 — Source/MSComctlLib/Events/IProgressBarEvents.cs:41-47 | Source/MSComctlLib/Events/IStatusBarEvents.cs:51-57 | Source/MSComctlLib/Events/ITreeViewEvents.cs:84-90 | Source/MSComctlLib/Events/ListViewEvents.cs:79-85 — before extracting anything, compare `Source/MSComctlLib/Events/IProgressBarEvents.cs` and `Source/MSComctlLib/Events/IStatusBarEvents.cs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 204 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Source/MSComctlLib/Events/IStatusBarEvents.cs:58` calls `MethodImpl`, `DispId`, `DblClick` and `Source/MSComctlLib/Events/IProgressBarEvents.cs:48` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (7 lines × 4) Source/Excel/Events/AppEvents.cs:215 — Source/Excel/Events/AppEvents.cs:215-221 | Source/Excel/Events/AppEvents.cs:224-230 | Source/Excel/Events/DocEvents.cs:69-75 | Source/Excel/Events/DocEvents.cs:77-83 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (7 lines × 4) Source/Access/Events/DispPageHdrFtrInReportEvents.cs:19 — Source/Access/Events/DispPageHdrFtrInReportEvents.cs:19-25 | Source/Access/Events/DispSectionInReportEvents.cs:19-25 | Source/Access/Events/_PageHdrFtrInReportEvents.cs:19-25 | Source/Access/Events/_SectionInReportEvents.cs:19-25 — before extracting anything, compare `Source/Access/Events/DispPageHdrFtrInReportEvents.cs` and `Source/Access/Events/DispSectionInReportEvents.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 179 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (7 lines × 4) Source/Access/Events/_FormEvents.cs:143 — Source/Access/Events/_FormEvents.cs:143-149 | Source/Access/Events/_FormEvents2.cs:145-151 | Source/Access/Events/_ReportEvents.cs:36-42 | Source/Access/Events/_ReportEvents2.cs:36-42 — before extracting anything, compare `Source/Access/Events/_FormEvents.cs` and `Source/Access/Events/_FormEvents2.cs` as WHOLE FILES: this scan already matched 72 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (713 lines × 2) · ×4
  • Duplicated block (713 lines × 2) Source/Excel/DispatchInterfaces/WorksheetFunction.Choose.cs:54 — Source/Excel/DispatchInterfaces/WorksheetFunction.Choose.cs:54-766 | Source/Excel/Interfaces/IWorksheetFunction.Choose.cs:54-766 — before extracting anything, compare `Source/Excel/DispatchInterfaces/WorksheetFunction.Choose.cs` and `Source/Excel/Interfaces/IWorksheetFunction.Choose.cs` as WHOLE FILES: 99% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (713 lines × 2) Source/Excel/DispatchInterfaces/WorksheetFunction.CountIfs.cs:54 — Source/Excel/DispatchInterfaces/WorksheetFunction.CountIfs.cs:54-766 | Source/Excel/Interfaces/IWorksheetFunction.CountIfs.cs:54-766 — before extracting anything, compare `Source/Excel/DispatchInterfaces/WorksheetFunction.CountIfs.cs` and `Source/Excel/Interfaces/IWorksheetFunction.CountIfs.cs` as WHOLE FILES: 99% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (713 lines × 2) Source/Excel/DispatchInterfaces/WorksheetFunction.Npv.cs:54 — Source/Excel/DispatchInterfaces/WorksheetFunction.Npv.cs:54-766 | Source/Excel/Interfaces/IWorksheetFunction.Npv.cs:54-766 — before extracting anything, compare `Source/Excel/DispatchInterfaces/WorksheetFunction.Npv.cs` and `Source/Excel/Interfaces/IWorksheetFunction.Npv.cs` as WHOLE FILES: 99% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (713 lines × 2) Source/Excel/DispatchInterfaces/WorksheetFunction.Subtotal.cs:54 — Source/Excel/DispatchInterfaces/WorksheetFunction.Subtotal.cs:54-766 | Source/Excel/Interfaces/IWorksheetFunction.Subtotal.cs:54-766 — before extracting anything, compare `Source/Excel/DispatchInterfaces/WorksheetFunction.Subtotal.cs` and `Source/Excel/Interfaces/IWorksheetFunction.Subtotal.cs` as WHOLE FILES: 99% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (8 lines × 4) · ×4
  • Duplicated block (8 lines × 4) Source/Excel/DispatchInterfaces/Adjustments.cs:210 — Source/Excel/DispatchInterfaces/Adjustments.cs:210-217 | Source/Office/DispatchInterfaces/Adjustments.cs:209-216 | Source/PowerPoint/DispatchInterfaces/Adjustments.cs:240-247 | Source/Word/DispatchInterfaces/Adjustments.cs:239-246 — before extracting anything, compare `Source/Excel/DispatchInterfaces/Adjustments.cs` and `Source/Office/DispatchInterfaces/Adjustments.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 66 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (8 lines × 4) Source/Access/Events/_FormEvents.cs:473 — Source/Access/Events/_FormEvents.cs:473-480 | Source/Access/Events/_FormEvents2.cs:449-456 | Source/Access/Events/_ReportEvents2.cs:289-296 | Source/Excel/Events/ChartEvents.cs:143-150 — before extracting anything, compare `Source/Access/Events/_FormEvents.cs` and `Source/Access/Events/_FormEvents2.cs` as WHOLE FILES: this scan already matched 72 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (8 lines × 4) Source/Outlook/Events/OlkComboBoxEvents.cs:290 — Source/Outlook/Events/OlkComboBoxEvents.cs:290-297 | Source/Outlook/Events/OlkDateControlEvents.cs:290-297 | Source/Outlook/Events/OlkTimeControlEvents.cs:290-297 | Source/Outlook/Events/OlkTimeZoneControlEvents.cs:290-297 — before extracting anything, compare `Source/Outlook/Events/OlkComboBoxEvents.cs` and `Source/Outlook/Events/OlkDateControlEvents.cs` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 209 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (8 lines × 4) Source/Access/Events/DispPageHdrFtrInReportEvents.cs:219 — Source/Access/Events/DispPageHdrFtrInReportEvents.cs:219-226 | Source/Access/Events/DispSectionInReportEvents.cs:234-241 | Source/Access/Events/_SectionEvents.cs:174-181 | Source/Access/Events/_SectionInReportEvents.cs:235-242 — before extracting anything, compare `Source/Access/Events/DispPageHdrFtrInReportEvents.cs` and `Source/Access/Events/DispSectionInReportEvents.cs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 179 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D5 · Coupling · Off the main sequence · ×4
  • Off the main sequence: NetOffice Source/NetOffice/NetOffice.csproj:1 — NetOffice: abstractness 0.14, instability 0.00, distance 0.86 — zone of pain — concrete and depended on by 12 project(s), so it's rigid to change.
  • Off the main sequence: OfficeApi Source/Office/OfficeApi.csproj:1 — OfficeApi: abstractness 0.06, instability 0.11, distance 0.82 — zone of pain — concrete and depended on by 7 project(s), so it's rigid to change.
  • Off the main sequence: MSDATASRCApi Source/MSDATASRC/MSDATASRCApi.csproj:1 — MSDATASRCApi: abstractness 0.00, instability 0.25, distance 0.75 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
  • Off the main sequence: ADODBApi Source/ADODB/ADODBApi.csproj:1 — ADODBApi: abstractness 0.03, instability 0.25, distance 0.72 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
D17 · Explicit Debt · TodoComment · ×3
  • TodoComment Examples/AddinRemovalTool/AddinEntry.cs:32 — // todo: fix vbe — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Source/NetOffice/Running/ChildWindowBatchEnumerator.cs:138 — // TODO: fix this for .NET Core library — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Source/NetOffice/Settings.cs:506 — // todo: handle that better by reflection — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
D17 · Explicit Debt · BareSuppressMessage · ×3
  • BareSuppressMessage Source/NetOffice.Tests/NetOffice/StringExTests.cs:14 — SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
  • BareSuppressMessage Source/NetOffice.Tests/NetOffice/StringExTests.cs:40 — SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
  • BareSuppressMessage Source/NetOffice.Tests/NetOffice/StringExTests.cs:53 — SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
D4 · Code Duplication · Near-duplicate member family (14 members, 15 shared lines) · ×3
  • Near-duplicate member family (14 members, 15 shared lines) Source/Outlook/Events/OlkBusinessCardControlEvents.cs:100 — Source/Outlook/Events/OlkBusinessCardControlEvents.cs:100-117 | Source/Outlook/Events/OlkCategoryEvents.cs:130-147 | Source/Outlook/Events/OlkCheckBoxEvents.cs:139-156 | Source/Outlook/Events/OlkComboBoxEvents.cs:143-160 | Source/Outlook/Events/OlkCommandButtonEvents.cs:135-152 | Source/Outlook/Events/OlkContactPhotoEvents.cs:130-147 | Source/Outlook/Events/OlkDateControlEvents.cs:143-160 | Source/Outlook/Events/OlkInfoBarEvents.cs:100-117 | Source/Outlook/Events/OlkLabelEvents.cs:100-117 | Source/Outlook/Events/OlkListBoxEvents.cs:139-156 | Source/Outlook/Events/OlkOptionButtonEvents.cs:139-156 | Source/Outlook/Events/OlkSenderPhotoEvents.cs:104-121 | Source/Outlook/Events/OlkTextBoxEvents.cs:139-156 | Source/Outlook/Events/OlkTimeControlEvents.cs:143-160 — These 14 members are variants of one another: a block of 15 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 14 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 14 times.
  • Near-duplicate member family (14 members, 15 shared lines) Source/Outlook/Events/OlkBusinessCardControlEvents.cs:120 — Source/Outlook/Events/OlkBusinessCardControlEvents.cs:120-137 | Source/Outlook/Events/OlkCategoryEvents.cs:150-167 | Source/Outlook/Events/OlkCheckBoxEvents.cs:159-176 | Source/Outlook/Events/OlkComboBoxEvents.cs:163-180 | Source/Outlook/Events/OlkCommandButtonEvents.cs:155-172 | Source/Outlook/Events/OlkContactPhotoEvents.cs:150-167 | Source/Outlook/Events/OlkDateControlEvents.cs:163-180 | Source/Outlook/Events/OlkInfoBarEvents.cs:120-137 | Source/Outlook/Events/OlkLabelEvents.cs:120-137 | Source/Outlook/Events/OlkListBoxEvents.cs:159-176 | Source/Outlook/Events/OlkOptionButtonEvents.cs:159-176 | Source/Outlook/Events/OlkSenderPhotoEvents.cs:124-141 | Source/Outlook/Events/OlkTextBoxEvents.cs:159-176 | Source/Outlook/Events/OlkTimeControlEvents.cs:163-180 — These 14 members are variants of one another: a block of 15 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 14 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 14 times.
  • Near-duplicate member family (14 members, 15 shared lines) Source/Outlook/Events/OlkBusinessCardControlEvents.cs:140 — Source/Outlook/Events/OlkBusinessCardControlEvents.cs:140-157 | Source/Outlook/Events/OlkCategoryEvents.cs:170-187 | Source/Outlook/Events/OlkCheckBoxEvents.cs:179-196 | Source/Outlook/Events/OlkComboBoxEvents.cs:183-200 | Source/Outlook/Events/OlkCommandButtonEvents.cs:175-192 | Source/Outlook/Events/OlkContactPhotoEvents.cs:170-187 | Source/Outlook/Events/OlkDateControlEvents.cs:183-200 | Source/Outlook/Events/OlkInfoBarEvents.cs:140-157 | Source/Outlook/Events/OlkLabelEvents.cs:140-157 | Source/Outlook/Events/OlkListBoxEvents.cs:179-196 | Source/Outlook/Events/OlkOptionButtonEvents.cs:179-196 | Source/Outlook/Events/OlkSenderPhotoEvents.cs:144-161 | Source/Outlook/Events/OlkTextBoxEvents.cs:179-196 | Source/Outlook/Events/OlkTimeControlEvents.cs:183-200 — These 14 members are variants of one another: a block of 15 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 14 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 14 times.
D4 · Code Duplication · Members sharing a duplicated core (14 members, 50+ identical tokens) · ×3
  • Members sharing a duplicated core (14 members, 50+ identical tokens) Source/NetOffice/Invoker.cs:314 — Source/NetOffice/Invoker.cs:314-338 | Source/NetOffice/Invoker.cs:348-372 | Source/NetOffice/Invoker.cs:383-404 | Source/NetOffice/Invoker.cs:415-439 | Source/NetOffice/Invoker.cs:610-634 | Source/NetOffice/Invoker.cs:644-668 | Source/NetOffice/Invoker.cs:679-700 | Source/NetOffice/Invoker.cs:711-735 | Source/NetOffice/Invoker.cs:748-787 | Source/NetOffice/Invoker.cs:796-820 | Source/NetOffice/Invoker.cs:830-869 | Source/NetOffice/Invoker.cs:879-903 | Source/NetOffice/Invoker.cs:914-935 | Source/NetOffice/Invoker.cs:946-970 — These 14 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 14 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 14 times.
  • Members sharing a duplicated core (14 members, 50+ identical tokens) Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ClassLibraryConverterCS.cs:49 — Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ClassLibraryConverterCS.cs:49-69 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ClassLibraryConverterVB.cs:56-80 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ConsoleConverterCS.cs:49-69 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ConsoleConverterVB.cs:55-79 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleMultiAddinConverterCS.cs:54-174 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleMultiAddinConverterVB.cs:60-181 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleSingleAddinConverterCS.cs:54-160 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleSingleAddinConverterVB.cs:60-169 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsMultiAddinConverterCS.cs:54-195 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsMultiAddinConverterVB.cs:60-219 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsSingleAddinConverterCS.cs:54-192 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsSingleAddinConverterVB.cs:60-216 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/WindowsFormsConverterCS.cs:55-83 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/WindowsFormsConverterVB.cs:56-84 — These 14 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 14 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 14 times.
  • Members sharing a duplicated core (14 members, 50+ identical tokens) Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ClassLibraryConverterCS.cs:80 — Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ClassLibraryConverterCS.cs:80-85 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ClassLibraryConverterVB.cs:97-108 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ConsoleConverterCS.cs:80-85 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ConsoleConverterVB.cs:96-107 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleMultiAddinConverterCS.cs:189-203 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleMultiAddinConverterVB.cs:202-224 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleSingleAddinConverterCS.cs:175-189 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleSingleAddinConverterVB.cs:190-212 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsMultiAddinConverterCS.cs:210-224 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsMultiAddinConverterVB.cs:240-262 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsSingleAddinConverterCS.cs:207-221 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsSingleAddinConverterVB.cs:237-259 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/WindowsFormsConverterCS.cs:100-111 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/WindowsFormsConverterVB.cs:102-114 — These 14 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 14 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 14 times.
D4 · Code Duplication · Edited copy of a member (26 corresponding lines) · ×3
  • Edited copy of a member (26 corresponding lines) Source/Office/Tools/COMAddin.cs:507 — Source/Office/Tools/COMAddin.cs:507-533 | Source/Office/Tools/CustomTaskPaneHandler.cs:34-59 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) BuildTools/SearchAndReplace/Form1.cs:83 — BuildTools/SearchAndReplace/Form1.cs:83-108 | BuildTools/VersionUpdater/Form1.cs:412-441 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) Tutorials/Tutorials/Tutorial02.cs:12 — Tutorials/Tutorials/Tutorial02.cs:12-51 | Tutorials/Tutorials/Tutorial09.cs:11-36 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (34 corresponding lines) · ×3
  • Edited copy of a member (34 corresponding lines) Source/NetOffice/SinkHelper.cs:158 — Source/NetOffice/SinkHelper.cs:158-191 | Source/NetOffice/SinkHelper.cs:198-231 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (34 corresponding lines) Source/NetOffice/COMObject.cs:138 — Source/NetOffice/COMObject.cs:138-171 | Source/NetOffice/COMObject.cs:180-214 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (34 corresponding lines) Toolbox/Toolbox/Controls/Hex/HexBox.cs:394 — Toolbox/Toolbox/Controls/Hex/HexBox.cs:394-427 | Toolbox/Toolbox/Controls/Hex/HexBox.cs:455-489 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 12+ corresponding lines) · ×3
  • Edited copies of one member (4 members, 12+ corresponding lines) Source/Excel/Events/DocEvents.cs:137 — Source/Excel/Events/DocEvents.cs:137-148 | Source/Excel/Events/DocEvents.cs:151-165 | Source/Excel/Events/DocEvents.cs:168-182 | Source/Excel/Events/DocEvents.cs:218-229 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 12+ corresponding lines) Source/PowerPoint/Events/EApplication.cs:594 — Source/PowerPoint/Events/EApplication.cs:594-605 | Source/PowerPoint/Events/EApplication.cs:608-622 | Source/PowerPoint/Events/EApplication.cs:644-655 | Source/PowerPoint/Events/EApplication.cs:658-669 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 12+ corresponding lines) Source/Outlook/Events/ReminderCollectionEvents.cs:90 — Source/Outlook/Events/ReminderCollectionEvents.cs:90-101 | Source/Outlook/Events/ReminderCollectionEvents.cs:104-115 | Source/Outlook/Events/ReminderCollectionEvents.cs:118-129 | Source/Outlook/Events/ReminderCollectionEvents.cs:143-154 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 8+ corresponding lines) · ×3
  • Edited copies of one member (5 members, 8+ corresponding lines) Source/Access/Tools/COMAddin.cs:831 — Source/Access/Tools/COMAddin.cs:831-838 | Source/Excel/Tools/COMAddin.cs:833-840 | Source/Outlook/Tools/COMAddin.cs:1079-1088 | Source/PowerPoint/Tools/COMAddin.cs:832-839 | Source/Word/Tools/COMAddin.cs:971-978 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 8+ corresponding lines) Source/Access/Tools/COMAddin.cs:846 — Source/Access/Tools/COMAddin.cs:846-853 | Source/Excel/Tools/COMAddin.cs:848-855 | Source/Outlook/Tools/COMAddin.cs:1096-1104 | Source/PowerPoint/Tools/COMAddin.cs:847-854 | Source/Word/Tools/COMAddin.cs:986-993 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 8+ corresponding lines) Source/Access/Tools/COMAddin.cs:904 — Source/Access/Tools/COMAddin.cs:904-911 | Source/Excel/Tools/COMAddin.cs:906-913 | Source/Outlook/Tools/COMAddin.cs:1158-1165 | Source/PowerPoint/Tools/COMAddin.cs:905-912 | Source/Word/Tools/COMAddin.cs:1046-1053 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 3+ corresponding lines) · ×3
  • Edited copies of one member (6 members, 3+ corresponding lines) Source/DAO/DispatchInterfaces/Database.cs:412 — Source/DAO/DispatchInterfaces/Database.cs:412-414 | Source/DAO/DispatchInterfaces/Document.cs:239-241 | Source/DAO/DispatchInterfaces/_Field.cs:479-481 | Source/DAO/DispatchInterfaces/_Index.cs:313-315 | Source/DAO/DispatchInterfaces/_QueryDef.cs:563-565 | Source/DAO/DispatchInterfaces/_TableDef.cs:442-444 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 3+ corresponding lines) Source/DAO/DispatchInterfaces/Database.cs:458 — Source/DAO/DispatchInterfaces/Database.cs:458-460 | Source/DAO/DispatchInterfaces/Document.cs:285-287 | Source/DAO/DispatchInterfaces/_Field.cs:525-527 | Source/DAO/DispatchInterfaces/_Index.cs:359-361 | Source/DAO/DispatchInterfaces/_QueryDef.cs:609-611 | Source/DAO/DispatchInterfaces/_TableDef.cs:488-490 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 3+ corresponding lines) Source/DAO/DispatchInterfaces/Database.cs:445 — Source/DAO/DispatchInterfaces/Database.cs:445-447 | Source/DAO/DispatchInterfaces/Document.cs:272-274 | Source/DAO/DispatchInterfaces/_Field.cs:512-514 | Source/DAO/DispatchInterfaces/_Index.cs:346-348 | Source/DAO/DispatchInterfaces/_QueryDef.cs:596-598 | Source/DAO/DispatchInterfaces/_TableDef.cs:475-477 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (31 lines × 2) · ×3
  • Duplicated block (31 lines × 2) Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsMultiAddinConverterVB.cs:87 — Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsMultiAddinConverterVB.cs:87-117 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsSingleAddinConverterVB.cs:87-117 — before extracting anything, compare `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsMultiAddinConverterVB.cs` and `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsSingleAddinConverterVB.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 180 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsMultiAddinConverterVB.cs:87` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (31 lines × 2) Source/NetOffice/Contribution/CollectionsGeneric/DisposableSequence.cs:114 — Source/NetOffice/Contribution/CollectionsGeneric/DisposableSequence.cs:114-144 | Source/NetOffice/Contribution/CollectionsGeneric/DisposableSequence.cs:273-303 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (31 lines × 2) Source/Access/Events/_FormEvents.cs:273 — Source/Access/Events/_FormEvents.cs:273-303 | Source/Access/Events/_FormEvents2.cs:248-278 — before extracting anything, compare `Source/Access/Events/_FormEvents.cs` and `Source/Access/Events/_FormEvents2.cs` as WHOLE FILES: this scan already matched 72 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (24 lines × 2) · ×3
  • Duplicated block (24 lines × 2) Source/NetOffice/Invoker.cs:315 — Source/NetOffice/Invoker.cs:315-338 | Source/NetOffice/Invoker.cs:611-634 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (24 lines × 2) Source/NetOffice/Invoker.cs:416 — Source/NetOffice/Invoker.cs:416-439 | Source/NetOffice/Invoker.cs:712-735 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (24 lines × 2) REDACTED:31 — REDACTED:31-54 | REDACTED:32-55 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (23 lines × 2) · ×3
  • Duplicated block (23 lines × 2) Source/Excel/Tools/RealtimeDataServer.cs:489 — Source/Excel/Tools/RealtimeDataServer.cs:489-511 | Source/Word/Tools/DocumentInspectorBase.cs:336-358 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (23 lines × 2) Source/NetOffice/CoreExtensions/CoreFactoryExtensions.cs:119 — Source/NetOffice/CoreExtensions/CoreFactoryExtensions.cs:119-141 | Source/NetOffice/CoreExtensions/CoreFactoryExtensions.cs:160-182 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/NetOffice/CoreExtensions/CoreFactoryExtensions.cs:119` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/NetOffice/CoreExtensions/CoreFactoryExtensions.cs:159` calls `GetTypeGuid` and `Source/NetOffice/CoreExtensions/CoreFactoryExtensions.cs:118` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (23 lines × 2) Source/PowerPoint/Tools/Contribution/ApplicationUtils.cs:125 — Source/PowerPoint/Tools/Contribution/ApplicationUtils.cs:125-147 | Source/Word/Tools/Contribution/ApplicationUtils.cs:130-152 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Source/PowerPoint/Tools/Contribution/ApplicationUtils.cs:125` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (12 lines × 3) · ×3
  • Duplicated block (12 lines × 3) Source/NetOffice/Tools/RegistryLocationAttribute.cs:125 — Source/NetOffice/Tools/RegistryLocationAttribute.cs:125-136 | Source/Outlook/Tools/FormRegionAttribute.cs:177-188 | Source/Outlook/Tools/RequireShutdownNotificationAttribute.cs:35-46 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (12 lines × 3) Source/Access/Events/_FormEvents.cs:484 — Source/Access/Events/_FormEvents.cs:484-495 | Source/Access/Events/_FormEvents2.cs:460-471 | Source/Access/Events/_ReportEvents2.cs:300-311 — before extracting anything, compare `Source/Access/Events/_FormEvents.cs` and `Source/Access/Events/_FormEvents2.cs` as WHOLE FILES: this scan already matched 72 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (12 lines × 3) Source/Access/Events/_FormEvents.cs:849 — Source/Access/Events/_FormEvents.cs:849-860 | Source/Access/Events/_FormEvents.cs:889-900 | Source/Access/Events/_FormEvents.cs:908-919 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (14 lines × 5) · ×3
  • Duplicated block (14 lines × 5) Source/Access/Tools/COMAddin.cs:792 — Source/Access/Tools/COMAddin.cs:792-805 | Source/Office/Tools/COMAddin.cs:942-955 | Source/Outlook/Tools/COMAddin.cs:1030-1043 | Source/PowerPoint/Tools/COMAddin.cs:793-806 | Source/VBIDE/Tools/COMAddin.cs:400-413 — before extracting anything, compare `Source/Access/Tools/COMAddin.cs` and `Source/Office/Tools/COMAddin.cs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 287 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Source/Access/Tools/COMAddin.cs:792` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 5) Examples/Access/NetOffice COMAddin Examples/04 Register and Unregister/Addin.cs:18 — Examples/Access/NetOffice COMAddin Examples/04 Register and Unregister/Addin.cs:18-31 | Examples/Excel/NetOffice COMAddin Examples/04 Register and Unregister/Addin.cs:18-31 | Examples/Outlook/NetOffice COMAddin Examples/04 Register and Unregister/Addin.cs:18-31 | Examples/PowerPoint/NetOffice COMAddin Examples/04 Register and Unregister/Addin.cs:18-31 | Examples/Word/NetOffice COMAddin Examples/04 Register and Unregister/Addin.cs:18-31 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Examples/Access/NetOffice COMAddin Examples/04 Register and Unregister/Addin.cs:18` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 5) Examples/Access/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:182 — Examples/Access/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:182-195 | Examples/Excel/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:180-193 | Examples/Other/IExtensibility2 Examples/SuperAddin/Addin.cs:197-210 | Examples/PowerPoint/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:181-194 | Examples/Word/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:179-192 — before extracting anything, compare `Examples/Access/IExtensibility COMAddin Examples/RibbonUI/Addin.cs` and `Examples/Excel/IExtensibility COMAddin Examples/RibbonUI/Addin.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 94 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (12 lines × 7) · ×3
  • Duplicated block (12 lines × 7) Source/Office/DispatchInterfaces/CommandBar.cs:524 — Source/Office/DispatchInterfaces/CommandBar.cs:524-535 | Source/Office/DispatchInterfaces/CommandBarControl.cs:588-599 | Source/Office/DispatchInterfaces/CommandBarPopup.cs:237-248 | Source/Office/DispatchInterfaces/IAccessible.cs:726-737 | Source/Office/DispatchInterfaces/_CommandBarActiveX.cs:250-261 | Source/Office/DispatchInterfaces/_CommandBarButton.cs:340-351 | Source/Office/DispatchInterfaces/_CommandBarComboBox.cs:349-360 — before extracting anything, compare `Source/Office/DispatchInterfaces/CommandBar.cs` and `Source/Office/DispatchInterfaces/CommandBarControl.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 32 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (12 lines × 7) Source/Access/Events/DispComboBoxEvents.cs:399 — Source/Access/Events/DispComboBoxEvents.cs:399-410 | Source/Access/Events/DispNavigationControlEvents.cs:375-386 | Source/Access/Events/DispTextBoxEvents.cs:375-386 | Source/Access/Events/_ComboBoxEvents.cs:397-408 | Source/Access/Events/_FormEvents.cs:768-779 | Source/Access/Events/_FormEvents2.cs:745-756 | Source/Access/Events/_TextBoxEvents.cs:372-383 — before extracting anything, compare `Source/Access/Events/DispComboBoxEvents.cs` and `Source/Access/Events/DispNavigationControlEvents.cs` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 225 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (12 lines × 7) Source/Office/DispatchInterfaces/CommandBar.cs:499 — Source/Office/DispatchInterfaces/CommandBar.cs:499-510 | Source/Office/DispatchInterfaces/CommandBarControl.cs:563-574 | Source/Office/DispatchInterfaces/CommandBarPopup.cs:212-223 | Source/Office/DispatchInterfaces/IAccessible.cs:701-712 | Source/Office/DispatchInterfaces/_CommandBarActiveX.cs:225-236 | Source/Office/DispatchInterfaces/_CommandBarButton.cs:315-326 | Source/Office/DispatchInterfaces/_CommandBarComboBox.cs:324-335 — before extracting anything, compare `Source/Office/DispatchInterfaces/CommandBar.cs` and `Source/Office/DispatchInterfaces/CommandBarControl.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 32 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (11 lines × 7) · ×3
  • Duplicated block (11 lines × 7) Source/NetOffice/Invoker.cs:151 — Source/NetOffice/Invoker.cs:151-161 | Source/NetOffice/Invoker.cs:217-227 | Source/NetOffice/Invoker.cs:263-273 | Source/NetOffice/Invoker.cs:295-305 | Source/NetOffice/Invoker.cs:484-494 | Source/NetOffice/Invoker.cs:513-523 | Source/NetOffice/Invoker.cs:559-569 — all 7 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/NetOffice/Invoker.cs:151` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `comObject` to `ICOMObject` in one and `object` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (11 lines × 7) Source/MSComctlLib/Events/IProgressBarEvents.cs:20 — Source/MSComctlLib/Events/IProgressBarEvents.cs:20-30 | Source/MSComctlLib/Events/ISliderEvents.cs:41-51 | Source/MSComctlLib/Events/IStatusBarEvents.cs:30-40 | Source/MSComctlLib/Events/ITabStripEvents.cs:41-51 | Source/MSComctlLib/Events/IToolbarEvents.cs:33-43 | Source/MSComctlLib/Events/ITreeViewEvents.cs:63-73 | Source/MSComctlLib/Events/ListViewEvents.cs:58-68 — before extracting anything, compare `Source/MSComctlLib/Events/IProgressBarEvents.cs` and `Source/MSComctlLib/Events/ISliderEvents.cs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 197 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (11 lines × 7) Source/Access/Tools/COMAddin.cs:741 — Source/Access/Tools/COMAddin.cs:741-751 | Source/Excel/Tools/COMAddin.cs:743-753 | Source/Office/Tools/COMAddin.cs:922-932 | Source/Outlook/Tools/COMAddin.cs:958-968 | Source/PowerPoint/Tools/COMAddin.cs:742-752 | Source/VBIDE/Tools/COMAddin.cs:437-447 | Source/Word/Tools/COMAddin.cs:881-891 — before extracting anything, compare `Source/Access/Tools/COMAddin.cs` and `Source/Excel/Tools/COMAddin.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 284 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (12 lines × 4) · ×3
  • Duplicated block (12 lines × 4) Source/Access/Events/_FormEvents.cs:458 — Source/Access/Events/_FormEvents.cs:458-469 | Source/Access/Events/_FormEvents2.cs:434-445 | Source/Access/Events/_ReportEvents.cs:79-90 | Source/Access/Events/_ReportEvents2.cs:176-187 — before extracting anything, compare `Source/Access/Events/_FormEvents.cs` and `Source/Access/Events/_FormEvents2.cs` as WHOLE FILES: this scan already matched 72 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (12 lines × 4) Source/Access/Events/_FormEvents.cs:1068 — Source/Access/Events/_FormEvents.cs:1068-1079 | Source/Access/Events/_FormEvents.cs:1102-1113 | Source/Access/Events/_FormEvents2.cs:947-958 | Source/Access/Events/_FormEvents2.cs:981-992 — before extracting anything, compare `Source/Access/Events/_FormEvents.cs` and `Source/Access/Events/_FormEvents2.cs` as WHOLE FILES: this scan already matched 72 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (12 lines × 4) Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleMultiAddinConverterCS.cs:139 — Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleMultiAddinConverterCS.cs:139-151 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleMultiAddinConverterVB.cs:147-158 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleSingleAddinConverterCS.cs:125-137 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleSingleAddinConverterVB.cs:135-146 — before extracting anything, compare `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleMultiAddinConverterCS.cs` and `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleMultiAddinConverterVB.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 85 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleMultiAddinConverterCS.cs:139` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (10 lines × 6) · ×3
  • Duplicated block (10 lines × 6) Source/Access/Tools/COMAddin.cs:790 — Source/Access/Tools/COMAddin.cs:790-799 | Source/Office/Tools/COMAddin.cs:940-949 | Source/Outlook/Tools/COMAddin.cs:1028-1037 | Source/PowerPoint/Tools/COMAddin.cs:791-800 | Source/VBIDE/Tools/COMAddin.cs:398-407 | Source/Word/Tools/COMAddin.cs:930-939 — before extracting anything, compare `Source/Access/Tools/COMAddin.cs` and `Source/Office/Tools/COMAddin.cs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 287 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (10 lines × 6) Source/Excel/Events/AppEvents.cs:335 — Source/Excel/Events/AppEvents.cs:335-344 | Source/Excel/Events/AppEvents.cs:461-470 | Source/Excel/Events/AppEvents.cs:475-484 | Source/Excel/Events/AppEvents.cs:489-498 | Source/Excel/Events/AppEvents.cs:572-581 | Source/Excel/Events/AppEvents.cs:586-595 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (10 lines × 6) Source/Access/Tools/COMAddin.cs:461 — Source/Access/Tools/COMAddin.cs:461-470 | Source/Excel/Tools/COMAddin.cs:460-469 | Source/Office/Tools/COMAddin.cs:466-475 | Source/Outlook/Tools/COMAddin.cs:502-511 | Source/PowerPoint/Tools/COMAddin.cs:462-471 | Source/Word/Tools/COMAddin.cs:463-472 — before extracting anything, compare `Source/Access/Tools/COMAddin.cs` and `Source/Excel/Tools/COMAddin.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 284 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (8 lines × 6) · ×3
  • Duplicated block (8 lines × 6) Source/Access/Tools/COMAddin.cs:299 — Source/Access/Tools/COMAddin.cs:299-306 | Source/Excel/Tools/COMAddin.cs:299-306 | Source/Outlook/Tools/COMAddin.cs:309-316 | Source/PowerPoint/Tools/COMAddin.cs:300-307 | Source/VBIDE/Tools/COMAddin.cs:265-272 | Source/Word/Tools/COMAddin.cs:302-309 — before extracting anything, compare `Source/Access/Tools/COMAddin.cs` and `Source/Excel/Tools/COMAddin.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 284 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Source/Access/Tools/COMAddin.cs:299` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 6) Source/OWC10/Events/IChartEvents.cs:518 — Source/OWC10/Events/IChartEvents.cs:518-525 | Source/OWC10/Events/IPivotControlEvents.cs:596-603 | Source/OWC10/Events/IPivotControlEvents.cs:642-649 | Source/OWC10/Events/ISpreadsheetEventSink.cs:235-242 | Source/OWC10/Events/ISpreadsheetEventSink.cs:409-416 | Source/OWC10/Events/ISpreadsheetEventSink.cs:708-715 — before extracting anything, compare `Source/OWC10/Events/IChartEvents.cs` and `Source/OWC10/Events/IPivotControlEvents.cs` as WHOLE FILES: this scan already matched 39 separate duplicated blocks between them, totalling at least 404 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (8 lines × 6) Source/Outlook/Events/ApplicationEvents.cs:129 — Source/Outlook/Events/ApplicationEvents.cs:129-136 | Source/Outlook/Events/ApplicationEvents_10.cs:144-151 | Source/Outlook/Events/ApplicationEvents_11.cs:201-208 | Source/Word/Events/ApplicationEvents2.cs:117-124 | Source/Word/Events/ApplicationEvents3.cs:182-189 | Source/Word/Events/ApplicationEvents4.cs:255-262 — before extracting anything, compare `Source/Outlook/Events/ApplicationEvents.cs` and `Source/Outlook/Events/ApplicationEvents_10.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 82 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (8 lines × 5) · ×3
  • Duplicated block (8 lines × 5) Source/NetOffice/Invoker.cs:360 — Source/NetOffice/Invoker.cs:360-367 | Source/NetOffice/Invoker.cs:656-663 | Source/NetOffice/Invoker.cs:688-695 | Source/NetOffice/Invoker.cs:891-898 | Source/NetOffice/Invoker.cs:923-930 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/NetOffice/Invoker.cs:360` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (8 lines × 5) Source/Outlook/Events/ApplicationEvents.cs:140 — Source/Outlook/Events/ApplicationEvents.cs:140-147 | Source/Outlook/Events/ApplicationEvents_10.cs:155-162 | Source/Word/Events/ApplicationEvents2.cs:128-135 | Source/Word/Events/ApplicationEvents3.cs:193-200 | Source/Word/Events/ApplicationEvents4.cs:266-273 — before extracting anything, compare `Source/Outlook/Events/ApplicationEvents.cs` and `Source/Outlook/Events/ApplicationEvents_10.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 82 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (8 lines × 5) REDACTED:100 — REDACTED:100-107 | REDACTED:100-107 | REDACTED:103-110 | REDACTED:102-109 | REDACTED:101-108 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 106 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (6 lines × 6) · ×3
  • Duplicated block (6 lines × 6) Source/NetOffice/Invoker.cs:998 — Source/NetOffice/Invoker.cs:998-1003 | Source/NetOffice/Invoker.cs:1036-1041 | Source/NetOffice/Invoker.cs:1067-1072 | Source/NetOffice/Invoker.cs:1099-1104 | Source/NetOffice/Invoker.cs:1131-1136 | Source/NetOffice/Invoker.cs:1162-1167 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/NetOffice/Invoker.cs:998` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note first that the copies are not typed on the same thing: the declarations holding them bind `value` to `object` in one and `object[]` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (6 lines × 6) Source/Access/Events/DispAttachmentEvents.cs:100 — Source/Access/Events/DispAttachmentEvents.cs:100-105 | Source/Access/Events/DispComboBoxEvents.cs:102-107 | Source/Access/Events/DispTabControlEvents.cs:65-70 | Source/Access/Events/DispTextBoxEvents.cs:95-100 | Source/Access/Events/_FormEvents2.cs:141-146 | Source/Access/Events/_ReportEvents2.cs:120-125 — before extracting anything, compare `Source/Access/Events/DispAttachmentEvents.cs` and `Source/Access/Events/DispComboBoxEvents.cs` as WHOLE FILES: this scan already matched 36 separate duplicated blocks between them, totalling at least 321 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Access/Events/DispAttachmentEvents.cs:99` calls `SinkArgument` and `Source/Access/Events/_ReportEvents2.cs:120` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (6 lines × 6) Source/Access/Events/DispBoundObjectFrameEvents.cs:19 — Source/Access/Events/DispBoundObjectFrameEvents.cs:19-24 | Source/Access/Events/DispObjectFrameEvents.cs:19-24 | Source/Access/Events/DispWebBrowserControlEvents.cs:19-24 | Source/Access/Events/_BoundObjectFrameEvents.cs:19-24 | Source/Access/Events/_CustomControlEvents.cs:19-24 | Source/Access/Events/_ObjectFrameEvents.cs:19-24 — before extracting anything, compare `Source/Access/Events/DispBoundObjectFrameEvents.cs` and `Source/Access/Events/DispObjectFrameEvents.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 183 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Source/Access/Events/DispObjectFrameEvents.cs:25` calls `MethodImpl`, `DispId`, `Enter` and `Source/Access/Events/DispBoundObjectFrameEvents.cs:25` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (9–10 lines × 2) · ×3
  • Duplicated block (9–10 lines × 2) Source/Office/Tools/COMAddin.cs:513 — Source/Office/Tools/COMAddin.cs:513-522 | Source/Office/Tools/CustomTaskPaneHandler.cs:40-48 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (9–10 lines × 2) Source/Outlook/Events/ApplicationEvents_10.cs:130 — Source/Outlook/Events/ApplicationEvents_10.cs:130-139 | Source/Outlook/Events/ApplicationEvents_11.cs:188-196 — before extracting anything, compare `Source/Outlook/Events/ApplicationEvents_10.cs` and `Source/Outlook/Events/ApplicationEvents_11.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 122 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (9–10 lines × 2) REDACTED:188 — REDACTED:188-197 | REDACTED:231-239 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:188` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `REDACTED:239` calls `SaveConfiguration` and `REDACTED:197` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (8 lines × 8) · ×3
  • Duplicated block (8 lines × 8) Source/Excel/Events/AppEvents.cs:352 — Source/Excel/Events/AppEvents.cs:352-359 | Source/Excel/Events/AppEvents.cs:368-375 | Source/Excel/Events/AppEvents.cs:387-394 | Source/Excel/Events/AppEvents.cs:448-455 | Source/Excel/Events/WorkbookEvents.cs:438-445 | Source/Excel/Events/WorkbookEvents.cs:454-461 | Source/Excel/Events/WorkbookEvents.cs:473-480 | Source/Excel/Events/WorkbookEvents.cs:534-541 — before extracting anything, compare `Source/Excel/Events/AppEvents.cs` and `Source/Excel/Events/WorkbookEvents.cs` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 377 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Source/Excel/Events/AppEvents.cs:352` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (8 lines × 8) Source/Office/DispatchInterfaces/CommandBar.cs:498 — Source/Office/DispatchInterfaces/CommandBar.cs:498-505 | Source/Office/DispatchInterfaces/CommandBarControl.cs:562-569 | Source/Office/DispatchInterfaces/CommandBarPopup.cs:211-218 | Source/Office/DispatchInterfaces/IAccessible.cs:700-707 | Source/Office/DispatchInterfaces/_CommandBarActiveX.cs:224-231 | Source/Office/DispatchInterfaces/_CommandBarButton.cs:314-321 | Source/Office/DispatchInterfaces/_CommandBarComboBox.cs:323-330 | Source/Word/DispatchInterfaces/Window.cs:1348-1355 — before extracting anything, compare `Source/Office/DispatchInterfaces/CommandBar.cs` and `Source/Office/DispatchInterfaces/CommandBarControl.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 32 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Source/Office/DispatchInterfaces/CommandBar.cs:498` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 8) Source/NetOffice/Invoker.cs:314 — Source/NetOffice/Invoker.cs:314-324 | Source/NetOffice/Invoker.cs:348-358 | Source/NetOffice/Invoker.cs:383-390 | Source/NetOffice/Invoker.cs:415-425 | Source/NetOffice/Invoker.cs:610-620 | Source/NetOffice/Invoker.cs:644-654 | Source/NetOffice/Invoker.cs:679-686 | Source/NetOffice/Invoker.cs:711-721 — all 8 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/NetOffice/Invoker.cs:314` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (7 lines × 6) · ×3
  • Duplicated block (7 lines × 6) Source/Excel/DispatchInterfaces/_Workbook.cs:4884 — Source/Excel/DispatchInterfaces/_Workbook.cs:4884-4890 | Source/Excel/DispatchInterfaces/_Workbook.cs:4905-4911 | Source/Excel/DispatchInterfaces/_Workbook.cs:4927-4933 | Source/Excel/DispatchInterfaces/_Workbook.cs:4949-4955 | Source/Excel/DispatchInterfaces/_Workbook.cs:4970-4976 | Source/Excel/DispatchInterfaces/_Workbook.cs:4992-4998 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/Excel/DispatchInterfaces/_Workbook.cs:4884` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (7 lines × 6) Source/OWC10/Events/IChartEvents.cs:46 — Source/OWC10/Events/IChartEvents.cs:46-52 | Source/OWC10/Events/IChartEvents.cs:53-59 | Source/OWC10/Events/IPivotControlEvents.cs:132-138 | Source/OWC10/Events/IPivotControlEvents.cs:139-145 | Source/OWC10/Events/ISpreadsheetEventSink.cs:25-31 | Source/OWC10/Events/ISpreadsheetEventSink.cs:38-44 — before extracting anything, compare `Source/OWC10/Events/IChartEvents.cs` and `Source/OWC10/Events/IPivotControlEvents.cs` as WHOLE FILES: this scan already matched 39 separate duplicated blocks between them, totalling at least 404 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (7 lines × 6) Source/Access/Tools/COMAddin.cs:148 — Source/Access/Tools/COMAddin.cs:148-154 | Source/Excel/Tools/COMAddin.cs:148-154 | Source/Office/Tools/COMAddin.cs:268-274 | Source/Outlook/Tools/COMAddin.cs:279-285 | Source/PowerPoint/Tools/COMAddin.cs:149-155 | Source/Word/Tools/COMAddin.cs:151-157 — before extracting anything, compare `Source/Access/Tools/COMAddin.cs` and `Source/Excel/Tools/COMAddin.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 284 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (5 lines × 6) · ×3
  • Duplicated block (5 lines × 6) Source/Excel/Events/AppEvents.cs:864 — Source/Excel/Events/AppEvents.cs:864-868 | Source/Excel/Events/AppEvents.cs:887-891 | Source/Excel/Events/AppEvents.cs:910-914 | Source/Excel/Events/WorkbookEvents.cs:736-740 | Source/Excel/Events/WorkbookEvents.cs:759-763 | Source/Excel/Events/WorkbookEvents.cs:782-786 — before extracting anything, compare `Source/Excel/Events/AppEvents.cs` and `Source/Excel/Events/WorkbookEvents.cs` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 377 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Source/Excel/Events/AppEvents.cs:864` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (5 lines × 6) Source/ADODB/Events/ConnectionEvents.cs:126 — Source/ADODB/Events/ConnectionEvents.cs:126-130 | Source/ADODB/Events/ConnectionEvents.cs:145-149 | Source/ADODB/Events/ConnectionEvents.cs:164-168 | Source/ADODB/Events/ConnectionEvents.cs:182-186 | Source/ADODB/Events/ConnectionEvents.cs:278-282 | Source/ADODB/Events/ConnectionEvents.cs:295-299 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (5 lines × 6) Source/Excel/DispatchInterfaces/GroupShapes.cs:237 — Source/Excel/DispatchInterfaces/GroupShapes.cs:237-241 | Source/Excel/DispatchInterfaces/ShapeRange.cs:1209-1213 | Source/Excel/DispatchInterfaces/Shapes.cs:904-908 | Source/Excel/Interfaces/IGroupShapes.cs:230-234 | Source/Excel/Interfaces/IShapeRange.cs:1140-1144 | Source/Excel/Interfaces/IShapes.cs:859-863 — before extracting anything, compare `Source/Excel/DispatchInterfaces/GroupShapes.cs` and `Source/Excel/Interfaces/IGroupShapes.cs` as WHOLE FILES: 88% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
IC1 · Incompleteness & stubs · Empty method body · ×3
  • Empty method body — does nothing with its inputs RegAddin/RegAddin/Metrics/AddinMetrics.cs:279 — `AnalyzeInteropConnectClass` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
  • Empty method body — does nothing with its inputs Toolbox/Toolbox/ToolboxControls/RegistryEditor/RegistryEditorControl.cs:232 — `EnableDesignView` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
  • Empty method body — does nothing with its inputs Toolbox/Toolbox/ToolboxControls/Welcome/WelcomeControl.cs:189 — `SetLanguage` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
IC1 · Incompleteness & stubs · Unfinished branch · ×3
  • Unfinished branch — throws NotImplementedException Source/NetOffice/CoreExtensions/CoreFactoryExtensions.cs:117 — The branch `if (null == dispatcher)` throws `IDispatchNotImplementedException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported.
  • Unfinished branch — throws NotImplementedException Source/NetOffice/CoreExtensions/CoreFactoryExtensions.cs:156 — The branch `if (null == dispatcher)` throws `IDispatchNotImplementedException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported.
  • Unfinished branch — throws NotImplementedException Source/NetOffice/CoreExtensions/CoreFactoryExtensions.cs:197 — The branch `if (null == dispatcher)` throws `IDispatchNotImplementedException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported.
X3 · Exception handling · Rethrow loses stack trace (`throw ex;`) · ×3
  • Rethrow loses stack trace (`throw ex;`) Source/NetOffice/COMObject.cs:1355 — `throw exception;` resets the exception's stack trace to this line, hiding where it really came from. Use a bare `throw;` to preserve the original stack.
  • Rethrow loses stack trace (`throw ex;`) Source/NetOffice/Core.cs:1291 — `throw exception;` resets the exception's stack trace to this line, hiding where it really came from. Use a bare `throw;` to preserve the original stack.
  • Rethrow loses stack trace (`throw ex;`) Toolbox/Toolbox/ToolboxControls/OfficeUI/OfficeUIControl.cs:185 — `throw exception;` resets the exception's stack trace to this line, hiding where it really came from. Use a bare `throw;` to preserve the original stack.
X3 · Exception handling · Swallowed exception (empty catch) · ×3
  • Swallowed exception (empty catch) Examples/AddinProjectHelper/Program.cs:31 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) Examples/AddinRemovalTool/Program.cs:31 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) Toolbox/Toolbox/ToolboxControls/ApplicationObserver/HotKey.cs:194 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
D17 · Explicit Debt · BarePragmaDisable · ×2
  • BarePragmaDisable Source/NetOffice/Core.cs:524 — #pragma warning disable 612, 618 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
  • BarePragmaDisable Source/Office.Extensions/Dialogs/DialogUtilsEx.cs:419 — #pragma warning disable 612, 618 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
D4 · Code Duplication · Members sharing a duplicated core (42 members, 50+ identical tokens) · ×2
  • Members sharing a duplicated core (42 members, 50+ identical tokens) Source/Access/Events/DispAttachmentEvents.cs:246 — Source/Access/Events/DispAttachmentEvents.cs:246-258 | Source/Access/Events/DispBoundObjectFrameEvents.cs:227-239 | Source/Access/Events/DispCheckBoxEvents.cs:208-220 | Source/Access/Events/DispComboBoxEvents.cs:256-268 | Source/Access/Events/DispCommandButtonEvents.cs:171-183 | Source/Access/Events/DispImageEvents.cs:90-102 | Source/Access/Events/DispLabelEvents.cs:90-102 | Source/Access/Events/DispListBoxEvents.cs:207-219 | Source/Access/Events/DispNavigationButtonEvents.cs:172-184 | Source/Access/Events/DispNavigationControlEvents.cs:232-244 | Source/Access/Events/DispObjectFrameEvents.cs:175-187 | Source/Access/Events/DispOptionButtonEvents.cs:205-217 | Source/Access/Events/DispOptionGroupEvents.cs:160-172 | Source/Access/Events/DispPageEvents.cs:90-102 | Source/Access/Events/DispPageHdrFtrInReportEvents.cs:140-152 | Source/Access/Events/DispPaletteButtonEvents.cs:207-219 | Source/Access/Events/DispRectangleEvents.cs:90-102 | Source/Access/Events/DispSectionEvents.cs:94-106 | Source/Access/Events/DispSectionInReportEvents.cs:155-167 | Source/Access/Events/DispTabControlEvents.cs:111-123 | Source/Access/Events/DispTextBoxEvents.cs:232-244 | Source/Access/Events/DispToggleButtonEvents.cs:207-219 | Source/Access/Events/DispWebBrowserControlEvents.cs:285-297 | Source/Access/Events/_BoundObjectFrameEvents.cs:227-239 | Source/Access/Events/_CheckBoxEvents.cs:207-219 | Source/Access/Events/_ComboBoxEvents.cs:254-266 | Source/Access/Events/_CommandButtonEvents.cs:171-183 | Source/Access/Events/_FormEvents.cs:564-576 | Source/Access/Events/_FormEvents2.cs:540-552 | Source/Access/Events/_ImageEvents.cs:90-102 | Source/Access/Events/_LabelEvents.cs:90-102 | Source/Access/Events/_ListBoxEvents.cs:206-218 | Source/Access/Events/_ObjectFrameEvents.cs:175-187 | Source/Access/Events/_OptionButtonEvents.cs:207-219 | Source/Access/Events/_OptionGroupEvents.cs:160-172 | Source/Access/Events/_PageEvents.cs:90-102 | Source/Access/Events/_PageHdrFtrInReportEvents.cs:136-148 | Source/Access/Events/_RectangleEvents.cs:90-102 | Source/Access/Events/_ReportEvents2.cs:347-359 | Source/Access/Events/_SectionEvents.cs:94-106 | Source/Access/Events/_SectionInReportEvents.cs:155-167 | Source/Access/Events/_ToggleButtonEvents.cs:207-219 — These 42 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 42 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 42 times.
  • Members sharing a duplicated core (42 members, 50+ identical tokens) REDACTED:67 — REDACTED:67-105 | REDACTED:108-144 | REDACTED:156-204 | REDACTED:207-233 | REDACTED:236-262 | REDACTED:265-291 | REDACTED:298-336 | REDACTED:339-375 | REDACTED:387-435 | REDACTED:438-464 | REDACTED:467-493 | REDACTED:496-522 | REDACTED:543-581 | REDACTED:584-620 | REDACTED:632-680 | REDACTED:683-709 | REDACTED:712-738 | REDACTED:741-767 | REDACTED:788-826 | REDACTED:829-865 | REDACTED:877-925 | REDACTED:928-954 | REDACTED:957-983 | REDACTED:986-1012 | REDACTED:1033-1071 | REDACTED:1074-1110 | REDACTED:1122-1170 | REDACTED:1173-1199 | REDACTED:1202-1228 | REDACTED:1231-1257 | REDACTED:1278-1316 | REDACTED:1319-1355 | REDACTED:1367-1415 | REDACTED:1418-1444 | REDACTED:1447-1473 | REDACTED:1476-1502 | REDACTED:1524-1562 | REDACTED:1565-1605 | REDACTED:1617-1665 | REDACTED:1668-1694 | REDACTED:1697-1723 | REDACTED:1726-1752 — These 42 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 42 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 42 times.
D4 · Code Duplication · Members sharing a duplicated core (30 members, 50+ identical tokens) · ×2
  • Members sharing a duplicated core (30 members, 50+ identical tokens) Source/Access/Events/DispAttachmentEvents.cs:324 — Source/Access/Events/DispAttachmentEvents.cs:324-338 | Source/Access/Events/DispBoundObjectFrameEvents.cs:305-319 | Source/Access/Events/DispCheckBoxEvents.cs:286-300 | Source/Access/Events/DispComboBoxEvents.cs:334-348 | Source/Access/Events/DispCommandButtonEvents.cs:249-263 | Source/Access/Events/DispListBoxEvents.cs:285-299 | Source/Access/Events/DispNavigationButtonEvents.cs:250-264 | Source/Access/Events/DispNavigationControlEvents.cs:310-324 | Source/Access/Events/DispOptionButtonEvents.cs:283-297 | Source/Access/Events/DispPaletteButtonEvents.cs:285-299 | Source/Access/Events/DispTabControlEvents.cs:189-203 | Source/Access/Events/DispTextBoxEvents.cs:310-324 | Source/Access/Events/DispToggleButtonEvents.cs:285-299 | Source/Access/Events/DispWebBrowserControlEvents.cs:363-377 | Source/Access/Events/_BoundObjectFrameEvents.cs:305-319 | Source/Access/Events/_CheckBoxEvents.cs:285-299 | Source/Access/Events/_CheckBoxInOptionEvents.cs:180-194 | Source/Access/Events/_ComboBoxEvents.cs:332-346 | Source/Access/Events/_CommandButtonEvents.cs:249-263 | Source/Access/Events/_FormEvents.cs:642-656 | Source/Access/Events/_FormEvents2.cs:618-632 | Source/Access/Events/_ListBoxEvents.cs:284-298 | Source/Access/Events/_OptionButtonEvents.cs:285-299 | Source/Access/Events/_OptionButtonInOptionEvents.cs:180-194 | Source/Access/Events/_PaletteButtonEvents.cs:285-299 | Source/Access/Events/_ReportEvents2.cs:425-439 | Source/Access/Events/_TabControlEvents.cs:189-203 | Source/Access/Events/_TextBoxEvents.cs:307-321 | Source/Access/Events/_ToggleButtonEvents.cs:285-299 | Source/Access/Events/_ToggleButtonInOptionEvents.cs:180-194 — These 30 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 30 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 30 times.
  • Members sharing a duplicated core (30 members, 50+ identical tokens) Source/Access/Events/DispAttachmentEvents.cs:356 — Source/Access/Events/DispAttachmentEvents.cs:356-370 | Source/Access/Events/DispBoundObjectFrameEvents.cs:337-351 | Source/Access/Events/DispCheckBoxEvents.cs:318-332 | Source/Access/Events/DispComboBoxEvents.cs:366-380 | Source/Access/Events/DispCommandButtonEvents.cs:281-295 | Source/Access/Events/DispListBoxEvents.cs:317-331 | Source/Access/Events/DispNavigationButtonEvents.cs:282-296 | Source/Access/Events/DispNavigationControlEvents.cs:342-356 | Source/Access/Events/DispOptionButtonEvents.cs:315-329 | Source/Access/Events/DispPaletteButtonEvents.cs:317-331 | Source/Access/Events/DispTabControlEvents.cs:221-235 | Source/Access/Events/DispTextBoxEvents.cs:342-356 | Source/Access/Events/DispToggleButtonEvents.cs:317-331 | Source/Access/Events/DispWebBrowserControlEvents.cs:395-409 | Source/Access/Events/_BoundObjectFrameEvents.cs:337-351 | Source/Access/Events/_CheckBoxEvents.cs:317-331 | Source/Access/Events/_CheckBoxInOptionEvents.cs:212-226 | Source/Access/Events/_ComboBoxEvents.cs:364-378 | Source/Access/Events/_CommandButtonEvents.cs:281-295 | Source/Access/Events/_FormEvents.cs:674-688 | Source/Access/Events/_FormEvents2.cs:650-664 | Source/Access/Events/_ListBoxEvents.cs:316-330 | Source/Access/Events/_OptionButtonEvents.cs:317-331 | Source/Access/Events/_OptionButtonInOptionEvents.cs:212-226 | Source/Access/Events/_PaletteButtonEvents.cs:317-331 | Source/Access/Events/_ReportEvents2.cs:457-471 | Source/Access/Events/_TabControlEvents.cs:221-235 | Source/Access/Events/_TextBoxEvents.cs:339-353 | Source/Access/Events/_ToggleButtonEvents.cs:317-331 | Source/Access/Events/_ToggleButtonInOptionEvents.cs:212-226 — These 30 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 30 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 30 times.
D4 · Code Duplication · Members sharing a duplicated core (22 members, 50+ identical tokens) · ×2
  • Members sharing a duplicated core (22 members, 50+ identical tokens) Source/Outlook/Events/OlkCategoryEvents.cs:216 — Source/Outlook/Events/OlkCategoryEvents.cs:216-230 | Source/Outlook/Events/OlkCategoryEvents.cs:248-262 | Source/Outlook/Events/OlkCheckBoxEvents.cs:225-239 | Source/Outlook/Events/OlkCheckBoxEvents.cs:257-271 | Source/Outlook/Events/OlkComboBoxEvents.cs:229-243 | Source/Outlook/Events/OlkComboBoxEvents.cs:261-275 | Source/Outlook/Events/OlkCommandButtonEvents.cs:221-235 | Source/Outlook/Events/OlkCommandButtonEvents.cs:253-267 | Source/Outlook/Events/OlkContactPhotoEvents.cs:216-230 | Source/Outlook/Events/OlkContactPhotoEvents.cs:248-262 | Source/Outlook/Events/OlkDateControlEvents.cs:229-243 | Source/Outlook/Events/OlkDateControlEvents.cs:261-275 | Source/Outlook/Events/OlkListBoxEvents.cs:225-239 | Source/Outlook/Events/OlkListBoxEvents.cs:257-271 | Source/Outlook/Events/OlkOptionButtonEvents.cs:225-239 | Source/Outlook/Events/OlkOptionButtonEvents.cs:257-271 | Source/Outlook/Events/OlkTextBoxEvents.cs:225-239 | Source/Outlook/Events/OlkTextBoxEvents.cs:257-271 | Source/Outlook/Events/OlkTimeControlEvents.cs:229-243 | Source/Outlook/Events/OlkTimeControlEvents.cs:261-275 | Source/Outlook/Events/OlkTimeZoneControlEvents.cs:229-243 | Source/Outlook/Events/OlkTimeZoneControlEvents.cs:261-275 — These 22 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 22 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 22 times.
  • Members sharing a duplicated core (22 members, 50+ identical tokens) Source/OWC10/Events/_DataSourceControlEvent.cs:156 — Source/OWC10/Events/_DataSourceControlEvent.cs:156-167 | Source/OWC10/Events/_DataSourceControlEvent.cs:170-181 | Source/OWC10/Events/_DataSourceControlEvent.cs:184-195 | Source/OWC10/Events/_DataSourceControlEvent.cs:198-209 | Source/OWC10/Events/_DataSourceControlEvent.cs:212-223 | Source/OWC10/Events/_DataSourceControlEvent.cs:226-237 | Source/OWC10/Events/_DataSourceControlEvent.cs:240-251 | Source/OWC10/Events/_DataSourceControlEvent.cs:254-265 | Source/OWC10/Events/_DataSourceControlEvent.cs:268-279 | Source/OWC10/Events/_DataSourceControlEvent.cs:282-293 | Source/OWC10/Events/_DataSourceControlEvent.cs:296-307 | Source/OWC10/Events/_DataSourceControlEvent.cs:310-321 | Source/OWC10/Events/_DataSourceControlEvent.cs:324-335 | Source/OWC10/Events/_DataSourceControlEvent.cs:338-349 | Source/OWC10/Events/_DataSourceControlEvent.cs:352-363 | Source/OWC10/Events/_DataSourceControlEvent.cs:366-377 | Source/OWC10/Events/_DataSourceControlEvent.cs:380-391 | Source/OWC10/Events/_DataSourceControlEvent.cs:394-405 | Source/OWC10/Events/_DataSourceControlEvent.cs:408-419 | Source/OWC10/Events/_DataSourceControlEvent.cs:422-433 | Source/OWC10/Events/_DataSourceControlEvent.cs:436-447 | Source/OWC10/Events/_DataSourceControlEvent.cs:450-461 — These 22 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 22 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 22 times.
D4 · Code Duplication · Members sharing a duplicated core (15 members, 50+ identical tokens) · ×2
  • Members sharing a duplicated core (15 members, 50+ identical tokens) Source/Outlook/Classes/AppointmentItem.cs:766 — Source/Outlook/Classes/AppointmentItem.cs:766-788 | Source/Outlook/Classes/ContactItem.cs:768-790 | Source/Outlook/Classes/DistListItem.cs:768-790 | Source/Outlook/Classes/DocumentItem.cs:768-790 | Source/Outlook/Classes/JournalItem.cs:768-790 | Source/Outlook/Classes/MailItem.cs:768-790 | Source/Outlook/Classes/MeetingItem.cs:768-790 | Source/Outlook/Classes/PostItem.cs:768-790 | Source/Outlook/Classes/RemoteItem.cs:768-790 | Source/Outlook/Classes/ReportItem.cs:768-790 | Source/Outlook/Classes/TaskItem.cs:768-790 | Source/Outlook/Classes/TaskRequestAcceptItem.cs:768-790 | Source/Outlook/Classes/TaskRequestDeclineItem.cs:768-790 | Source/Outlook/Classes/TaskRequestItem.cs:768-790 | Source/Outlook/Classes/TaskRequestUpdateItem.cs:768-790 — These 15 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 15 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 15 times.
  • Members sharing a duplicated core (15 members, 50+ identical tokens) Source/Access/Events/DispAttachmentEvents.cs:135 — Source/Access/Events/DispAttachmentEvents.cs:135-147 | Source/Access/Events/DispBoundObjectFrameEvents.cs:142-154 | Source/Access/Events/DispCheckBoxEvents.cs:134-146 | Source/Access/Events/DispComboBoxEvents.cs:143-155 | Source/Access/Events/_BoundObjectFrameEvents.cs:142-154 | Source/Access/Events/_CheckBoxEvents.cs:133-145 | Source/Access/Events/_ComboBoxEvents.cs:141-153 | Source/Access/Events/_FormEvents.cs:385-397 | Source/Access/Events/_FormEvents2.cs:360-372 | Source/Access/Events/_ListBoxEvents.cs:121-133 | Source/Access/Events/_OptionButtonEvents.cs:133-145 | Source/Access/Events/_OptionGroupEvents.cs:97-109 | Source/Access/Events/_PaletteButtonEvents.cs:133-145 | Source/Access/Events/_TextBoxEvents.cs:134-146 | Source/Access/Events/_ToggleButtonEvents.cs:133-145 — These 15 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 15 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 15 times.
D4 · Code Duplication · Members sharing a duplicated core (13 members, 50+ identical tokens) · ×2
  • Members sharing a duplicated core (13 members, 50+ identical tokens) Source/Word/Events/ApplicationEvents2.cs:215 — Source/Word/Events/ApplicationEvents2.cs:215-226 | Source/Word/Events/ApplicationEvents3.cs:280-291 | Source/Word/Events/ApplicationEvents3.cs:374-385 | Source/Word/Events/ApplicationEvents3.cs:388-399 | Source/Word/Events/ApplicationEvents3.cs:418-429 | Source/Word/Events/ApplicationEvents3.cs:470-481 | Source/Word/Events/ApplicationEvents3.cs:501-512 | Source/Word/Events/ApplicationEvents4.cs:353-364 | Source/Word/Events/ApplicationEvents4.cs:447-458 | Source/Word/Events/ApplicationEvents4.cs:461-472 | Source/Word/Events/ApplicationEvents4.cs:491-502 | Source/Word/Events/ApplicationEvents4.cs:543-554 | Source/Word/Events/ApplicationEvents4.cs:574-585 — These 13 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 13 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 13 times.
  • Members sharing a duplicated core (13 members, 50+ identical tokens) Source/Access/Events/DispWebBrowserControlEvents.cs:439 — Source/Access/Events/DispWebBrowserControlEvents.cs:439-453 | Source/Outlook/Events/ApplicationEvents.cs:74-88 | Source/Outlook/Events/ApplicationEvents_10.cs:88-102 | Source/Outlook/Events/ApplicationEvents_11.cs:145-159 | Source/Outlook/Events/ExplorerEvents.cs:103-117 | Source/Outlook/Events/ExplorerEvents_10.cs:152-166 | Source/Outlook/Events/ItemEvents.cs:174-188 | Source/Outlook/Events/ItemEvents.cs:231-245 | Source/Outlook/Events/ItemEvents.cs:248-262 | Source/Outlook/Events/ItemEvents_10.cs:231-245 | Source/Outlook/Events/ItemEvents_10.cs:288-302 | Source/Outlook/Events/ItemEvents_10.cs:305-319 | Source/Outlook/Events/ItemEvents_10.cs:412-426 — These 13 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 13 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 13 times.
D4 · Code Duplication · Members sharing a duplicated core (11 members, 50+ identical tokens) · ×2
  • Members sharing a duplicated core (11 members, 50+ identical tokens) Source/Excel/Events/AppEvents.cs:348 — Source/Excel/Events/AppEvents.cs:348-361 | Source/Excel/Events/AppEvents.cs:364-380 | Source/Excel/Events/AppEvents.cs:383-399 | Source/Excel/Events/AppEvents.cs:444-457 | Source/Excel/Events/AppEvents.cs:842-857 | Source/Excel/Events/DocEvents.cs:260-273 | Source/Excel/Events/WorkbookEvents.cs:434-447 | Source/Excel/Events/WorkbookEvents.cs:450-466 | Source/Excel/Events/WorkbookEvents.cs:469-485 | Source/Excel/Events/WorkbookEvents.cs:530-543 | Source/Excel/Events/WorkbookEvents.cs:714-729 — These 11 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 11 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 11 times.
  • Members sharing a duplicated core (11 members, 50+ identical tokens) Source/Outlook/Events/OlkCategoryEvents.cs:201 — Source/Outlook/Events/OlkCategoryEvents.cs:201-213 | Source/Outlook/Events/OlkCheckBoxEvents.cs:210-222 | Source/Outlook/Events/OlkComboBoxEvents.cs:214-226 | Source/Outlook/Events/OlkCommandButtonEvents.cs:206-218 | Source/Outlook/Events/OlkContactPhotoEvents.cs:201-213 | Source/Outlook/Events/OlkDateControlEvents.cs:214-226 | Source/Outlook/Events/OlkListBoxEvents.cs:210-222 | Source/Outlook/Events/OlkOptionButtonEvents.cs:210-222 | Source/Outlook/Events/OlkTextBoxEvents.cs:210-222 | Source/Outlook/Events/OlkTimeControlEvents.cs:214-226 | Source/Outlook/Events/OlkTimeZoneControlEvents.cs:214-226 — These 11 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 11 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 11 times.
D4 · Code Duplication · Members sharing a duplicated core (10 members, 50+ identical tokens) · ×2
  • Members sharing a duplicated core (10 members, 50+ identical tokens) Source/NetOffice/Invoker.cs:139 — Source/NetOffice/Invoker.cs:139-161 | Source/NetOffice/Invoker.cs:208-227 | Source/NetOffice/Invoker.cs:236-273 | Source/NetOffice/Invoker.cs:283-305 | Source/NetOffice/Invoker.cs:472-494 | Source/NetOffice/Invoker.cs:504-523 | Source/NetOffice/Invoker.cs:532-569 | Source/NetOffice/Invoker.cs:579-601 | Source/NetOffice/Invoker.cs:748-787 | Source/NetOffice/Invoker.cs:830-869 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
  • Members sharing a duplicated core (10 members, 50+ identical tokens) Source/Outlook/Events/OlkCategoryEvents.cs:233 — Source/Outlook/Events/OlkCategoryEvents.cs:233-245 | Source/Outlook/Events/OlkComboBoxEvents.cs:246-258 | Source/Outlook/Events/OlkCommandButtonEvents.cs:238-250 | Source/Outlook/Events/OlkContactPhotoEvents.cs:233-245 | Source/Outlook/Events/OlkDateControlEvents.cs:246-258 | Source/Outlook/Events/OlkListBoxEvents.cs:242-254 | Source/Outlook/Events/OlkOptionButtonEvents.cs:242-254 | Source/Outlook/Events/OlkTextBoxEvents.cs:242-254 | Source/Outlook/Events/OlkTimeControlEvents.cs:246-258 | Source/Outlook/Events/OlkTimeZoneControlEvents.cs:246-258 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
D4 · Code Duplication · Edited copy of a member (39 corresponding lines) · ×2
  • Edited copy of a member (39 corresponding lines) Toolbox/Toolbox/Utils/Animation/Panel/AnimatedPanel.cs:108 — Toolbox/Toolbox/Utils/Animation/Panel/AnimatedPanel.cs:108-146 | Toolbox/Toolbox/Utils/Animation/Panel/AnimatedPanel.cs:247-285 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (39 corresponding lines) Toolbox/Toolbox/Controls/Hex/HexBox.cs:819 — Toolbox/Toolbox/Controls/Hex/HexBox.cs:819-857 | Toolbox/Toolbox/Controls/Hex/HexBox.cs:859-899 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 20+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 20+ corresponding lines) Toolbox/Toolbox/ToolboxControls/RegistryEditor/RegistryEditorControl.cs:1292 — Toolbox/Toolbox/ToolboxControls/RegistryEditor/RegistryEditorControl.cs:1292-1311 | Toolbox/Toolbox/ToolboxControls/RegistryEditor/RegistryEditorControl.cs:1314-1333 | Toolbox/Toolbox/ToolboxControls/RegistryEditor/RegistryEditorControl.cs:1336-1355 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 20+ corresponding lines) Source/NetOffice/Utils.cs:112 — Source/NetOffice/Utils.cs:112-131 | Source/NetOffice/Utils.cs:139-164 | Source/NetOffice/Utils.cs:172-197 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (31 corresponding lines) · ×2
  • Edited copy of a member (31 corresponding lines) Source/NetOffice/CoreExtensions/CoreFactoryExtensions.cs:111 — Source/NetOffice/CoreExtensions/CoreFactoryExtensions.cs:111-141 | Source/NetOffice/CoreExtensions/CoreFactoryExtensions.cs:150-182 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (31 corresponding lines) Source/NetOffice/Contribution/Controls/InstanceMonitor.cs:287 — Source/NetOffice/Contribution/Controls/InstanceMonitor.cs:287-317 | Source/Office.Extensions/TrayMenuUtils/TrayMenuMonitorItemControl.cs:389-421 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 14+ corresponding lines) · ×2
  • Edited copies of one member (6 members, 14+ corresponding lines) Source/Outlook/Events/ApplicationEvents_11.cs:275 — Source/Outlook/Events/ApplicationEvents_11.cs:275-288 | Source/Outlook/Events/ApplicationEvents_11.cs:291-304 | Source/Outlook/Events/ApplicationEvents_11.cs:307-320 | Source/Outlook/Events/ApplicationEvents_11.cs:323-336 | Source/Outlook/Events/ApplicationEvents_11.cs:339-352 | Source/Outlook/Events/ApplicationEvents_11.cs:355-368 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 14+ corresponding lines) Source/NetOffice/Tools/Tweaks.cs:301 — Source/NetOffice/Tools/Tweaks.cs:301-314 | Source/NetOffice/Tools/Tweaks.cs:402-415 | Source/NetOffice/Tools/Tweaks.cs:418-431 | Source/NetOffice/Tools/Tweaks.cs:434-447 | Source/NetOffice/Tools/Tweaks.cs:450-463 | Source/NetOffice/Tools/Tweaks.cs:466-479 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (42 corresponding lines) · ×2
  • Edited copy of a member (42 corresponding lines) RegAddin/RegAddin/Common/AddinRegAnalyzer.cs:140 — RegAddin/RegAddin/Common/AddinRegAnalyzer.cs:140-181 | RegAddin/RegAddin/Common/Registry.cs:26-68 — These two members are one piece of code written twice and then edited apart: 42 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (42 corresponding lines) REDACTED:21 — REDACTED:21-62 | REDACTED:22-71 — These two members are one piece of code written twice and then edited apart: 42 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 17+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 17+ corresponding lines) Source/Excel/Events/AppEvents.cs:957 — Source/Excel/Events/AppEvents.cs:957-973 | Source/PowerPoint/Events/EApplication.cs:625-641 | Source/Word/Events/ApplicationEvents4.cs:759-775 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 17+ corresponding lines) Source/VBIDE/Classes/CommandBarEvents.cs:165 — Source/VBIDE/Classes/CommandBarEvents.cs:165-181 | Source/VBIDE/Classes/References.cs:188-204 | Source/VBIDE/Classes/ReferencesEvents.cs:188-204 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 22+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 22+ corresponding lines) Toolbox/Toolbox/Controls/Hex/HexBox.cs:287 — Toolbox/Toolbox/Controls/Hex/HexBox.cs:287-312 | Toolbox/Toolbox/Controls/Hex/HexBox.cs:340-364 | Toolbox/Toolbox/Controls/Hex/HexBox.cs:925-946 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 22+ corresponding lines) Toolbox/Toolbox/Controls/Hex/HexBox.cs:254 — Toolbox/Toolbox/Controls/Hex/HexBox.cs:254-279 | Toolbox/Toolbox/Controls/Hex/HexBox.cs:315-337 | Toolbox/Toolbox/Controls/Hex/HexBox.cs:901-922 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 11+ corresponding lines) · ×2
  • Edited copies of one member (4 members, 11+ corresponding lines) Source/OWC10/DispatchInterfaces/IDataSourceControl.cs:1098 — Source/OWC10/DispatchInterfaces/IDataSourceControl.cs:1098-1108 | Source/Office/DispatchInterfaces/IBlogExtensibility.cs:171-181 | Source/Office/DispatchInterfaces/IBlogExtensibility.cs:195-205 | Source/Office/DispatchInterfaces/IBlogExtensibility.cs:220-232 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 11+ corresponding lines) Toolbox/Toolbox/ToolboxControls/RegistryEditor/ChangeBinaryDialog.cs:74 — Toolbox/Toolbox/ToolboxControls/RegistryEditor/ChangeBinaryDialog.cs:74-84 | Toolbox/Toolbox/ToolboxControls/RegistryEditor/ChangeDWordDialog.cs:65-75 | Toolbox/Toolbox/ToolboxControls/RegistryEditor/ChangeNameDialog.cs:53-63 | Toolbox/Toolbox/ToolboxControls/RegistryEditor/ChangeStringDialog.cs:63-73 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 15+ corresponding lines) · ×2
  • Edited copies of one member (4 members, 15+ corresponding lines) Source/Outlook/Events/ApplicationEvents_11.cs:399 — Source/Outlook/Events/ApplicationEvents_11.cs:399-413 | Source/Outlook/Events/ExplorerEvents_10.cs:320-337 | Source/Outlook/Events/MAPIFolderEvents_12.cs:59-73 | Source/Outlook/Events/MAPIFolderEvents_12.cs:76-92 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 15+ corresponding lines) Examples/AddinRemovalTool/AddinSearcher.cs:104 — Examples/AddinRemovalTool/AddinSearcher.cs:104-121 | Examples/AddinRemovalTool/AddinSearcher.cs:124-141 | Examples/AddinRemovalTool/AddinSearcher.cs:144-158 | Examples/AddinRemovalTool/AddinSearcher.cs:161-178 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 14+ corresponding lines) · ×2
  • Edited copies of one member (4 members, 14+ corresponding lines) Source/Excel/Events/AppEvents.cs:519 — Source/Excel/Events/AppEvents.cs:519-535 | Source/Excel/Events/AppEvents.cs:1018-1031 | Source/Office/Events/_CustomXMLPartEvents.cs:68-81 | Source/Word/Events/DocumentEvents2.cs:167-180 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 14+ corresponding lines) Toolbox/Toolbox/Controls/Text/RichTextEditor.cs:81 — Toolbox/Toolbox/Controls/Text/RichTextEditor.cs:81-94 | Toolbox/Toolbox/Controls/Text/RichTextEditor.cs:97-111 | Toolbox/Toolbox/Controls/Text/RichTextEditor.cs:114-127 | Toolbox/Toolbox/Controls/Text/RichTextEditor.cs:130-143 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 12+ corresponding lines) · ×2
  • Edited copies of one member (5 members, 12+ corresponding lines) Source/OWC10/Events/ISpreadsheetEventSink.cs:625 — Source/OWC10/Events/ISpreadsheetEventSink.cs:625-636 | Source/OWC10/Events/ISpreadsheetEventSink.cs:639-650 | Source/OWC10/Events/ISpreadsheetEventSink.cs:653-666 | Source/OWC10/Events/ISpreadsheetEventSink.cs:669-680 | Source/OWC10/Events/ISpreadsheetEventSink.cs:683-696 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 12+ corresponding lines) Source/Office.Extensions/TrayUtils.cs:499 — Source/Office.Extensions/TrayUtils.cs:499-510 | Source/Office.Extensions/TrayUtils.cs:513-524 | Source/Office.Extensions/TrayUtils.cs:527-538 | Source/Office.Extensions/TrayUtils.cs:541-552 | Source/Office.Extensions/TrayUtils.cs:555-566 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 8+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 8+ corresponding lines) Source/Office/Interfaces/IConverter.cs:229 — Source/Office/Interfaces/IConverter.cs:229-236 | Source/Office/Interfaces/IConverterUICallback.cs:156-163 | Source/Office/Interfaces/IDocumentInspector.cs:168-177 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 8+ corresponding lines) Source/NetOffice/CoreExtensions/CorePropertySetExtensions.cs:301 — Source/NetOffice/CoreExtensions/CorePropertySetExtensions.cs:301-308 | Source/NetOffice/CoreExtensions/CorePropertySetExtensions.cs:590-597 | Source/NetOffice/CoreExtensions/CorePropertySetExtensions.cs:784-791 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (8 members, 8+ corresponding lines) · ×2
  • Edited copies of one member (8 members, 8+ corresponding lines) Source/OWC10/Interfaces/IOleParentUndoUnit.cs:162 — Source/OWC10/Interfaces/IOleParentUndoUnit.cs:162-169 | Source/OWC10/Interfaces/IOleUndoManager.cs:152-159 | Source/Office/Interfaces/IConverterApplicationPreferences.cs:123-130 | Source/Office/Interfaces/IConverterApplicationPreferences.cs:139-146 | Source/Office/Interfaces/IConverterApplicationPreferences.cs:171-178 | Source/Office/Interfaces/IConverterPreferences.cs:123-130 | Source/Office/Interfaces/IConverterPreferences.cs:139-146 | Source/Office/Interfaces/IConverterPreferences.cs:155-162 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
  • Edited copies of one member (8 members, 8+ corresponding lines) Source/Excel/DispatchInterfaces/XmlMap.cs:471 — Source/Excel/DispatchInterfaces/XmlMap.cs:471-479 | Source/Excel/Interfaces/IWorkbookQuery.cs:300-308 | Source/Excel/Interfaces/IXmlMap.cs:446-454 | Source/OWC10/Interfaces/IOleUndoManager.cs:233-240 | Source/OWC10/Interfaces/IOleUndoManager.cs:248-255 | Source/OWC10/Interfaces/IOleUndoUnit.cs:131-138 | Source/Office/DispatchInterfaces/IAccessible.cs:585-592 | Source/Office/Interfaces/IConverterApplicationPreferences.cs:155-162 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 9+ corresponding lines) · ×2
  • Edited copies of one member (5 members, 9+ corresponding lines) Source/OWC10/DispatchInterfaces/ChChart.cs:876 — Source/OWC10/DispatchInterfaces/ChChart.cs:876-884 | Source/OWC10/DispatchInterfaces/ChErrorBars.cs:356-364 | Source/OWC10/DispatchInterfaces/ChSeries.cs:598-606 | Source/OWC10/DispatchInterfaces/IDataSourceControl.cs:1363-1372 | Source/OWC10/DispatchInterfaces/IXRangeEnum.cs:149-157 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 9+ corresponding lines) REDACTED:99 — REDACTED:99-107 | REDACTED:99-107 | REDACTED:102-110 | REDACTED:101-109 | REDACTED:100-108 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (8 corresponding lines) · ×2
  • Edited copy of a member (8 corresponding lines) Source/NetOffice/Running/RunningWindowTable.cs:181 — Source/NetOffice/Running/RunningWindowTable.cs:181-190 | Source/NetOffice/ComTypes/ITypeInfoExtensions.cs:16-23 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) Toolbox/Toolbox/Utils/Ressources/RessourceUtils.cs:58 — Toolbox/Toolbox/Utils/Ressources/RessourceUtils.cs:58-66 | Toolbox/Toolbox/Controls/InfoLayer/InfoControl.cs:76-83 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 11+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 11+ corresponding lines) Source/Access/Events/_FormEvents.cs:948 — Source/Access/Events/_FormEvents.cs:948-958 | Source/Access/Events/_FormEvents2.cs:826-837 | Source/OWC10/Events/IChartEvents.cs:260-271 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 11+ corresponding lines) Examples/Access/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:62 — Examples/Access/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:62-74 | Examples/Outlook/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:62-72 | Examples/PowerPoint/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:64-74 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 4+ corresponding lines) · ×2
  • Edited copies of one member (4 members, 4+ corresponding lines) Source/Access/Tools/Contribution/FileUtils.cs:85 — Source/Access/Tools/Contribution/FileUtils.cs:85-88 | Source/Excel/Tools/Contribution/FileUtils.cs:81-84 | Source/PowerPoint/Tools/Contribution/FileUtils.cs:82-85 | Source/Word/Tools/Contribution/FileUtils.cs:76-79 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 4+ corresponding lines) Source/Access/Tools/Contribution/FileUtils.cs:72 — Source/Access/Tools/Contribution/FileUtils.cs:72-75 | Source/Excel/Tools/Contribution/FileUtils.cs:68-71 | Source/PowerPoint/Tools/Contribution/FileUtils.cs:69-72 | Source/Word/Tools/Contribution/FileUtils.cs:63-66 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (7 members, 9+ corresponding lines) · ×2
  • Edited copies of one member (7 members, 9+ corresponding lines) Source/Access/Events/_FormEvents.cs:983 — Source/Access/Events/_FormEvents.cs:983-991 | Source/Access/Events/_FormEvents2.cs:862-870 | Source/OWC10/Events/IChartEvents.cs:402-410 | Source/OWC10/Events/IPivotControlEvents.cs:214-222 | Source/OWC10/Events/ISpreadsheetEventSink.cs:600-608 | Source/Outlook/Events/ExplorerEvents.cs:159-167 | Source/Outlook/Events/ExplorerEvents_10.cs:208-216 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
  • Edited copies of one member (7 members, 9+ corresponding lines) Source/MSComctlLib/Events/IStatusBarEvents.cs:231 — Source/MSComctlLib/Events/IStatusBarEvents.cs:231-239 | Source/MSComctlLib/Events/IToolbarEvents.cs:237-245 | Source/MSComctlLib/Events/ITreeViewEvents.cs:363-371 | Source/MSComctlLib/Events/ListViewEvents.cs:345-353 | Source/OWC10/Events/IChartEvents.cs:206-214 | Source/OWC10/Events/IPivotControlEvents.cs:398-406 | Source/OWC10/Events/ISpreadsheetEventSink.cs:389-397 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 9+ corresponding lines) · ×2
  • Edited copies of one member (6 members, 9+ corresponding lines) Source/Outlook/Events/ApplicationEvents.cs:128 — Source/Outlook/Events/ApplicationEvents.cs:128-136 | Source/Outlook/Events/ApplicationEvents_10.cs:143-151 | Source/Outlook/Events/ApplicationEvents_11.cs:200-208 | Source/Word/Events/ApplicationEvents2.cs:116-124 | Source/Word/Events/ApplicationEvents3.cs:181-189 | Source/Word/Events/ApplicationEvents4.cs:254-262 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 9+ corresponding lines) Source/Outlook/Events/ApplicationEvents.cs:139 — Source/Outlook/Events/ApplicationEvents.cs:139-147 | Source/Outlook/Events/ApplicationEvents_10.cs:154-162 | Source/Outlook/Events/ApplicationEvents_11.cs:211-219 | Source/Word/Events/ApplicationEvents2.cs:127-135 | Source/Word/Events/ApplicationEvents3.cs:192-200 | Source/Word/Events/ApplicationEvents4.cs:265-273 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (53 lines × 5) · ×2
  • Duplicated block (53 lines × 5) Source/Excel/DispatchInterfaces/Panes.cs:56 — Source/Excel/DispatchInterfaces/Panes.cs:56-108 | Source/OWC10/DispatchInterfaces/Panes.cs:55-107 | Source/Outlook/DispatchInterfaces/Panes.cs:56-108 | Source/PowerPoint/DispatchInterfaces/Panes.cs:53-105 | Source/Word/DispatchInterfaces/Panes.cs:56-108 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times.
  • Duplicated block (53 lines × 5) Source/Access/DispatchInterfaces/_Application.cs:52 — Source/Access/DispatchInterfaces/_Application.cs:52-104 | Source/Excel/DispatchInterfaces/_Application.cs:335-387 | Source/Outlook/DispatchInterfaces/_Application.cs:52-104 | Source/PowerPoint/DispatchInterfaces/_Application.cs:52-104 | Source/Word/DispatchInterfaces/_Application.cs:52-104 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times.
D4 · Code Duplication · Duplicated block (37 lines × 2) · ×2
  • Duplicated block (37 lines × 2) Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsMultiAddinConverterVB.cs:183 — Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsMultiAddinConverterVB.cs:183-219 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsSingleAddinConverterVB.cs:180-216 — before extracting anything, compare `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsMultiAddinConverterVB.cs` and `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsSingleAddinConverterVB.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 180 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsMultiAddinConverterVB.cs:183` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (37 lines × 2) Source/NetOffice/Invoker.cs:237 — Source/NetOffice/Invoker.cs:237-273 | Source/NetOffice/Invoker.cs:533-569 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (32 lines × 5) · ×2
  • Duplicated block (32 lines × 5) Source/Access/Tools/COMAddin.cs:534 — Source/Access/Tools/COMAddin.cs:534-565 | Source/Excel/Tools/COMAddin.cs:533-564 | Source/Office/Tools/COMAddin.cs:677-708 | Source/PowerPoint/Tools/COMAddin.cs:535-566 | Source/Word/Tools/COMAddin.cs:536-567 — before extracting anything, compare `Source/Access/Tools/COMAddin.cs` and `Source/Excel/Tools/COMAddin.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 284 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Source/Access/Tools/COMAddin.cs:534` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (32 lines × 5) Source/Access/Tools/COMAddin.cs:571 — Source/Access/Tools/COMAddin.cs:571-602 | Source/Excel/Tools/COMAddin.cs:570-601 | Source/Office/Tools/COMAddin.cs:714-745 | Source/PowerPoint/Tools/COMAddin.cs:572-603 | Source/Word/Tools/COMAddin.cs:573-604 — before extracting anything, compare `Source/Access/Tools/COMAddin.cs` and `Source/Excel/Tools/COMAddin.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 284 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Source/Access/Tools/COMAddin.cs:571` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (29 lines × 2) · ×2
  • Duplicated block (29 lines × 2) Source/Office/Tools/COMAddin.cs:588 — Source/Office/Tools/COMAddin.cs:588-616 | Source/Office/Tools/CustomTaskPaneHandler.cs:131-159 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Source/Office/Tools/COMAddin.cs:588` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (29 lines × 2) Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleMultiAddinConverterVB.cs:147 — Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleMultiAddinConverterVB.cs:147-175 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleSingleAddinConverterVB.cs:135-163 — before extracting anything, compare `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleMultiAddinConverterVB.cs` and `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleSingleAddinConverterVB.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 151 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleMultiAddinConverterVB.cs:147` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (28 lines × 2) · ×2
  • Duplicated block (28 lines × 2) Source/Excel/Tools/RealtimeDataServer.cs:386 — Source/Excel/Tools/RealtimeDataServer.cs:386-413 | Source/Excel/Tools/RealtimeDataServer.cs:417-444 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (28 lines × 2) Source/Outlook/Classes/Application.cs:682 — Source/Outlook/Classes/Application.cs:682-709 | Source/Word/Classes/Application.cs:1080-1107 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (21 lines × 3) · ×2
  • Duplicated block (21 lines × 3) Source/OWC10/Events/IChartEvents.cs:108 — Source/OWC10/Events/IChartEvents.cs:108-128 | Source/OWC10/Events/IPivotControlEvents.cs:92-112 | Source/OWC10/Events/ISpreadsheetEventSink.cs:51-71 — before extracting anything, compare `Source/OWC10/Events/IChartEvents.cs` and `Source/OWC10/Events/IPivotControlEvents.cs` as WHOLE FILES: this scan already matched 39 separate duplicated blocks between them, totalling at least 404 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/OWC10/Events/IPivotControlEvents.cs:88` calls `SupportByVersion`, `MethodImpl`, `DispId` and `Source/OWC10/Events/ISpreadsheetEventSink.cs:49` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (21 lines × 3) Examples/PowerPoint/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:99 — Examples/PowerPoint/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:99-119 | Examples/PowerPoint/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:130-150 | Examples/PowerPoint/IExtensibility COMAddin Examples/TaskPane/Addin.cs:110-130 — `Examples/PowerPoint/IExtensibility COMAddin Examples/ClassicUI/Addin.cs` and `Examples/PowerPoint/IExtensibility COMAddin Examples/RibbonUI/Addin.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 84 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `Examples/PowerPoint/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:99` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (22 lines × 2) · ×2
  • Duplicated block (22 lines × 2) BuildTools/VersionUpdater/Form1.cs:112 — BuildTools/VersionUpdater/Form1.cs:112-133 | BuildTools/VersionUpdater/Form1.cs:156-177 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `BuildTools/VersionUpdater/Form1.cs:112` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (22 lines × 2) Source/Office.Extensions/Dialogs/RichTextDialog.cs:60 — Source/Office.Extensions/Dialogs/RichTextDialog.cs:60-81 | Source/Office.Extensions/Dialogs/RichTextDialog.cs:130-151 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/Office.Extensions/Dialogs/RichTextDialog.cs:60` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (20 lines × 6) · ×2
  • Duplicated block (20 lines × 6) Source/Access/Tools/COMAddin.cs:371 — Source/Access/Tools/COMAddin.cs:371-390 | Source/Excel/Tools/COMAddin.cs:370-389 | Source/Office/Tools/COMAddin.cs:376-395 | Source/Outlook/Tools/COMAddin.cs:404-423 | Source/PowerPoint/Tools/COMAddin.cs:372-391 | Source/Word/Tools/COMAddin.cs:373-392 — before extracting anything, compare `Source/Access/Tools/COMAddin.cs` and `Source/Excel/Tools/COMAddin.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 284 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Source/Access/Tools/COMAddin.cs:371` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (20 lines × 6) Examples/Access/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:158 — Examples/Access/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:158-177 | Examples/Access/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:132-151 | Examples/Access/IExtensibility COMAddin Examples/TaskPane/Addin.cs:110-129 | Examples/Excel/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:101-120 | Examples/Excel/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:126-145 | Examples/Excel/IExtensibility COMAddin Examples/TaskPane/Addin.cs:110-129 — `Examples/Access/IExtensibility COMAddin Examples/ClassicUI/Addin.cs` and `Examples/Access/IExtensibility COMAddin Examples/RibbonUI/Addin.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 83 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `Examples/Access/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:158` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (25 lines × 2) · ×2
  • Duplicated block (25 lines × 2) Source/Outlook/Events/ItemEvents.cs:26 — Source/Outlook/Events/ItemEvents.cs:26-50 | Source/Outlook/Events/ItemEvents_10.cs:26-50 — before extracting anything, compare `Source/Outlook/Events/ItemEvents.cs` and `Source/Outlook/Events/ItemEvents_10.cs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 292 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (25 lines × 2) Examples/AddinProjectHelper/Program.cs:18 — Examples/AddinProjectHelper/Program.cs:18-42 | Examples/AddinRemovalTool/Program.cs:18-42 — `Examples/AddinProjectHelper/Program.cs` and `Examples/AddinRemovalTool/Program.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 2 separate duplicated blocks between them, totalling at least 30 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (14 lines × 8) · ×2
  • Duplicated block (14 lines × 8) Source/MSComctlLib/Events/DImageComboEvents.cs:282 — Source/MSComctlLib/Events/DImageComboEvents.cs:282-295 | Source/MSComctlLib/Events/IProgressBarEvents.cs:272-285 | Source/MSComctlLib/Events/ISliderEvents.cs:368-381 | Source/MSComctlLib/Events/IStatusBarEvents.cs:325-338 | Source/MSComctlLib/Events/ITabStripEvents.cs:358-371 | Source/MSComctlLib/Events/IToolbarEvents.cs:331-344 | Source/MSComctlLib/Events/ITreeViewEvents.cs:471-484 | Source/MSComctlLib/Events/ListViewEvents.cs:439-452 — before extracting anything, compare `Source/MSComctlLib/Events/DImageComboEvents.cs` and `Source/MSComctlLib/Events/IProgressBarEvents.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 157 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Source/MSComctlLib/Events/DImageComboEvents.cs:296` calls `ToInt32` and `Source/MSComctlLib/Events/IStatusBarEvents.cs:339` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (14 lines × 8) Source/MSComctlLib/Events/DImageComboEvents.cs:222 — Source/MSComctlLib/Events/DImageComboEvents.cs:222-235 | Source/MSComctlLib/Events/IProgressBarEvents.cs:212-225 | Source/MSComctlLib/Events/ISliderEvents.cs:308-321 | Source/MSComctlLib/Events/IStatusBarEvents.cs:265-278 | Source/MSComctlLib/Events/ITabStripEvents.cs:298-311 | Source/MSComctlLib/Events/IToolbarEvents.cs:271-284 | Source/MSComctlLib/Events/ITreeViewEvents.cs:411-424 | Source/MSComctlLib/Events/ListViewEvents.cs:379-392 — before extracting anything, compare `Source/MSComctlLib/Events/DImageComboEvents.cs` and `Source/MSComctlLib/Events/IProgressBarEvents.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 157 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (20 lines × 2) · ×2
  • Duplicated block (20 lines × 2) Source/Office/DispatchInterfaces/TextRange2.cs:1148 — Source/Office/DispatchInterfaces/TextRange2.cs:1148-1167 | Source/PowerPoint/DispatchInterfaces/TextRange.cs:855-874 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (20 lines × 2) RegAddin/RegAddin/Metrics/AddinMetrics.cs:191 — RegAddin/RegAddin/Metrics/AddinMetrics.cs:191-210 | RegAddin/RegAddin/Metrics/AddinMetrics.cs:214-233 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (18 lines × 48) · ×2
  • Duplicated block (18 lines × 48) Source/Access/Events/DispAttachmentEvents.cs:283 — Source/Access/Events/DispAttachmentEvents.cs:283-300 | Source/Access/Events/DispBoundObjectFrameEvents.cs:264-281 | Source/Access/Events/DispCheckBoxEvents.cs:245-262 | Source/Access/Events/DispComboBoxEvents.cs:293-310 | Source/Access/Events/DispCommandButtonEvents.cs:208-225 | Source/Access/Events/DispImageEvents.cs:127-144 | Source/Access/Events/DispLabelEvents.cs:127-144 | Source/Access/Events/DispListBoxEvents.cs:244-261 | Source/Access/Events/DispNavigationButtonEvents.cs:209-226 | Source/Access/Events/DispNavigationControlEvents.cs:269-286 | Source/Access/Events/DispObjectFrameEvents.cs:212-229 | Source/Access/Events/DispOptionButtonEvents.cs:242-259 | Source/Access/Events/DispOptionGroupEvents.cs:197-214 | Source/Access/Events/DispPageEvents.cs:127-144 | Source/Access/Events/DispPageHdrFtrInReportEvents.cs:177-194 | Source/Access/Events/DispPaletteButtonEvents.cs:244-261 | Source/Access/Events/DispRectangleEvents.cs:127-144 | Source/Access/Events/DispSectionEvents.cs:131-148 | Source/Access/Events/DispSectionInReportEvents.cs:192-209 | Source/Access/Events/DispTabControlEvents.cs:148-165 | Source/Access/Events/DispTextBoxEvents.cs:269-286 | Source/Access/Events/DispToggleButtonEvents.cs:244-261 | Source/Access/Events/DispWebBrowserControlEvents.cs:322-339 | Source/Access/Events/_BoundObjectFrameEvents.cs:264-281 | Source/Access/Events/_CheckBoxEvents.cs:244-261 | Source/Access/Events/_CheckBoxInOptionEvents.cs:139-156 | Source/Access/Events/_ComboBoxEvents.cs:291-308 | Source/Access/Events/_CommandButtonEvents.cs:208-225 | Source/Access/Events/_FormEvents.cs:601-618 | Source/Access/Events/_FormEvents2.cs:577-594 | Source/Access/Events/_ImageEvents.cs:127-144 | Source/Access/Events/_LabelEvents.cs:127-144 | Source/Access/Events/_ListBoxEvents.cs:243-260 | Source/Access/Events/_ObjectFrameEvents.cs:212-229 | Source/Access/Events/_OptionButtonEvents.cs:244-261 | Source/Access/Events/_OptionButtonInOptionEvents.cs:139-156 | Source/Access/Events/_OptionGroupEvents.cs:197-214 | Source/Access/Events/_PageEvents.cs:127-144 | Source/Access/Events/_PageHdrFtrInReportEvents.cs:173-190 | Source/Access/Events/_PaletteButtonEvents.cs:244-261 | Source/Access/Events/_RectangleEvents.cs:127-144 | Source/Access/Events/_ReportEvents2.cs:384-401 | Source/Access/Events/_SectionEvents.cs:132-149 | Source/Access/Events/_SectionInReportEvents.cs:193-210 | Source/Access/Events/_TabControlEvents.cs:148-165 | Source/Access/Events/_TextBoxEvents.cs:266-283 | Source/Access/Events/_ToggleButtonEvents.cs:244-261 | Source/Access/Events/_ToggleButtonInOptionEvents.cs:139-156 — before extracting anything, compare `Source/Access/Events/DispAttachmentEvents.cs` and `Source/Access/Events/DispBoundObjectFrameEvents.cs` as WHOLE FILES: this scan already matched 29 separate duplicated blocks between them, totalling at least 271 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (18 lines × 48) Source/Access/Events/DispAttachmentEvents.cs:304 — Source/Access/Events/DispAttachmentEvents.cs:304-321 | Source/Access/Events/DispBoundObjectFrameEvents.cs:285-302 | Source/Access/Events/DispCheckBoxEvents.cs:266-283 | Source/Access/Events/DispComboBoxEvents.cs:314-331 | Source/Access/Events/DispCommandButtonEvents.cs:229-246 | Source/Access/Events/DispImageEvents.cs:148-165 | Source/Access/Events/DispLabelEvents.cs:148-165 | Source/Access/Events/DispListBoxEvents.cs:265-282 | Source/Access/Events/DispNavigationButtonEvents.cs:230-247 | Source/Access/Events/DispNavigationControlEvents.cs:290-307 | Source/Access/Events/DispObjectFrameEvents.cs:233-250 | Source/Access/Events/DispOptionButtonEvents.cs:263-280 | Source/Access/Events/DispOptionGroupEvents.cs:218-235 | Source/Access/Events/DispPageEvents.cs:148-165 | Source/Access/Events/DispPageHdrFtrInReportEvents.cs:198-215 | Source/Access/Events/DispPaletteButtonEvents.cs:265-282 | Source/Access/Events/DispRectangleEvents.cs:148-165 | Source/Access/Events/DispSectionEvents.cs:152-169 | Source/Access/Events/DispSectionInReportEvents.cs:213-230 | Source/Access/Events/DispTabControlEvents.cs:169-186 | Source/Access/Events/DispTextBoxEvents.cs:290-307 | Source/Access/Events/DispToggleButtonEvents.cs:265-282 | Source/Access/Events/DispWebBrowserControlEvents.cs:343-360 | Source/Access/Events/_BoundObjectFrameEvents.cs:285-302 | Source/Access/Events/_CheckBoxEvents.cs:265-282 | Source/Access/Events/_CheckBoxInOptionEvents.cs:160-177 | Source/Access/Events/_ComboBoxEvents.cs:312-329 | Source/Access/Events/_CommandButtonEvents.cs:229-246 | Source/Access/Events/_FormEvents.cs:622-639 | Source/Access/Events/_FormEvents2.cs:598-615 | Source/Access/Events/_ImageEvents.cs:148-165 | Source/Access/Events/_LabelEvents.cs:148-165 | Source/Access/Events/_ListBoxEvents.cs:264-281 | Source/Access/Events/_ObjectFrameEvents.cs:233-250 | Source/Access/Events/_OptionButtonEvents.cs:265-282 | Source/Access/Events/_OptionButtonInOptionEvents.cs:160-177 | Source/Access/Events/_OptionGroupEvents.cs:218-235 | Source/Access/Events/_PageEvents.cs:148-165 | Source/Access/Events/_PageHdrFtrInReportEvents.cs:194-211 | Source/Access/Events/_PaletteButtonEvents.cs:265-282 | Source/Access/Events/_RectangleEvents.cs:148-165 | Source/Access/Events/_ReportEvents2.cs:405-422 | Source/Access/Events/_SectionEvents.cs:153-170 | Source/Access/Events/_SectionInReportEvents.cs:214-231 | Source/Access/Events/_TabControlEvents.cs:169-186 | Source/Access/Events/_TextBoxEvents.cs:287-304 | Source/Access/Events/_ToggleButtonEvents.cs:265-282 | Source/Access/Events/_ToggleButtonInOptionEvents.cs:160-177 — before extracting anything, compare `Source/Access/Events/DispAttachmentEvents.cs` and `Source/Access/Events/DispBoundObjectFrameEvents.cs` as WHOLE FILES: this scan already matched 29 separate duplicated blocks between them, totalling at least 271 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (18 lines × 3) · ×2
  • Duplicated block (18 lines × 3) Toolbox/Toolbox/ToolboxControls/RegistryEditor/ChangeBinaryDialog.cs:54 — Toolbox/Toolbox/ToolboxControls/RegistryEditor/ChangeBinaryDialog.cs:54-71 | Toolbox/Toolbox/ToolboxControls/RegistryEditor/ChangeDWordDialog.cs:79-96 | Toolbox/Toolbox/ToolboxControls/RegistryEditor/ChangeStringDialog.cs:77-94 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (18 lines × 3) Examples/Access/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:94 — Examples/Access/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:94-111 | Examples/Excel/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:89-106 | Examples/PowerPoint/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:93-110 — before extracting anything, compare `Examples/Access/IExtensibility COMAddin Examples/RibbonUI/Addin.cs` and `Examples/Excel/IExtensibility COMAddin Examples/RibbonUI/Addin.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 94 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Examples/Access/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:94` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (16–19 lines × 2) · ×2
  • Duplicated block (16–19 lines × 2) Source/NetOffice/Invoker.cs:139 — Source/NetOffice/Invoker.cs:139-157 | Source/NetOffice/Invoker.cs:208-223 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/NetOffice/Invoker.cs:139` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16–19 lines × 2) Source/NetOffice/Invoker.cs:472 — Source/NetOffice/Invoker.cs:472-490 | Source/NetOffice/Invoker.cs:504-519 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/NetOffice/Invoker.cs:472` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (16 lines × 3) · ×2
  • Duplicated block (16 lines × 3) Source/Excel/Events/AppEvents.cs:861 — Source/Excel/Events/AppEvents.cs:861-876 | Source/Excel/Events/WorkbookEvents.cs:733-748 | Source/Excel/Events/WorkbookEvents.cs:756-771 — before extracting anything, compare `Source/Excel/Events/AppEvents.cs` and `Source/Excel/Events/WorkbookEvents.cs` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 377 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (16 lines × 3) Source/Word/Events/ApplicationEvents2.cs:197 — Source/Word/Events/ApplicationEvents2.cs:197-212 | Source/Word/Events/ApplicationEvents3.cs:262-277 | Source/Word/Events/ApplicationEvents4.cs:335-350 — before extracting anything, compare `Source/Word/Events/ApplicationEvents2.cs` and `Source/Word/Events/ApplicationEvents3.cs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 270 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (17 lines × 3) · ×2
  • Duplicated block (17 lines × 3) Source/OWC10/Events/IChartEvents.cs:510 — Source/OWC10/Events/IChartEvents.cs:510-526 | Source/OWC10/Events/IPivotControlEvents.cs:588-604 | Source/OWC10/Events/ISpreadsheetEventSink.cs:227-243 — before extracting anything, compare `Source/OWC10/Events/IChartEvents.cs` and `Source/OWC10/Events/IPivotControlEvents.cs` as WHOLE FILES: this scan already matched 39 separate duplicated blocks between them, totalling at least 404 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (17 lines × 3) Source/NetOffice/Invoker.cs:356 — Source/NetOffice/Invoker.cs:356-372 | Source/NetOffice/Invoker.cs:652-668 | Source/NetOffice/Invoker.cs:684-700 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/NetOffice/Invoker.cs:356` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/NetOffice/Invoker.cs:353` calls `EntityIsAvailable`, `EntityNotSupportedException` and `Source/NetOffice/Invoker.cs:682` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (15 lines × 6) · ×2
  • Duplicated block (15 lines × 6) Source/Access/Tools/COMAddin.cs:532 — Source/Access/Tools/COMAddin.cs:532-546 | Source/Excel/Tools/COMAddin.cs:531-545 | Source/Office/Tools/COMAddin.cs:675-689 | Source/Outlook/Tools/COMAddin.cs:573-587 | Source/PowerPoint/Tools/COMAddin.cs:533-547 | Source/Word/Tools/COMAddin.cs:534-548 — before extracting anything, compare `Source/Access/Tools/COMAddin.cs` and `Source/Excel/Tools/COMAddin.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 284 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Source/Access/Tools/COMAddin.cs:532` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 6) Source/Access/Tools/COMAddin.cs:569 — Source/Access/Tools/COMAddin.cs:569-583 | Source/Excel/Tools/COMAddin.cs:568-582 | Source/Office/Tools/COMAddin.cs:712-726 | Source/Outlook/Tools/COMAddin.cs:610-624 | Source/PowerPoint/Tools/COMAddin.cs:570-584 | Source/Word/Tools/COMAddin.cs:571-585 — before extracting anything, compare `Source/Access/Tools/COMAddin.cs` and `Source/Excel/Tools/COMAddin.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 284 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Source/Access/Tools/COMAddin.cs:569` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (14–17 lines × 2) · ×2
  • Duplicated block (14–17 lines × 2) Source/NetOffice/Invoker.cs:991 — Source/NetOffice/Invoker.cs:991-1004 | Source/NetOffice/Invoker.cs:1152-1168 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/NetOffice/Invoker.cs:991` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. Note first that the copies are not typed on the same thing: the declarations holding them bind `value` to `object` in one and `object[]` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (14–17 lines × 2) Source/NetOffice/Invoker.cs:1029 — Source/NetOffice/Invoker.cs:1029-1042 | Source/NetOffice/Invoker.cs:1121-1137 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/NetOffice/Invoker.cs:1029` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. Note first that the copies are not typed on the same thing: the declarations holding them bind `value` to `object` in one and `object[]` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (15–16 lines × 3) · ×2
  • Duplicated block (15–16 lines × 3) Source/Access/Events/_FormEvents.cs:735 — Source/Access/Events/_FormEvents.cs:735-749 | Source/Access/Events/_FormEvents2.cs:712-726 | Source/Access/Events/_ReportEvents2.cs:502-517 — before extracting anything, compare `Source/Access/Events/_FormEvents.cs` and `Source/Access/Events/_FormEvents2.cs` as WHOLE FILES: this scan already matched 72 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (15–16 lines × 3) Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/ReportControl.cs:278 — Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/ReportControl.cs:278-292 | Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/ReportControl.cs:299-313 | Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/ReportControl.cs:320-335 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/ReportControl.cs:278` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (13 lines × 4) · ×2
  • Duplicated block (13 lines × 4) Toolbox/Toolbox/ToolboxControls/About/AboutControl.cs:199 — Toolbox/Toolbox/ToolboxControls/About/AboutControl.cs:199-211 | Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/OfficeCompatibilityControl.cs:297-309 | Toolbox/Toolbox/ToolboxControls/OutlookSecurity/OutlookSecurityControl.cs:226-238 | Toolbox/Toolbox/ToolboxControls/Welcome/WelcomeControl.cs:293-305 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Toolbox/Toolbox/ToolboxControls/About/AboutControl.cs:199` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (13 lines × 4) Examples/Excel/Automation/Examples/Example01.cs:17 — Examples/Excel/Automation/Examples/Example01.cs:17-30 | Examples/Excel/Automation/Examples/Example02.cs:16-29 | Examples/Excel/Automation/Examples/Example04.cs:16-28 | Examples/Excel/Automation/Examples/Example10.cs:18-31 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Examples/Excel/Automation/Examples/Example01.cs:17` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (11 lines × 11) · ×2
  • Duplicated block (11 lines × 11) Source/Outlook/Events/OlkCategoryEvents.cs:217 — Source/Outlook/Events/OlkCategoryEvents.cs:217-227 | Source/Outlook/Events/OlkCheckBoxEvents.cs:226-236 | Source/Outlook/Events/OlkComboBoxEvents.cs:230-240 | Source/Outlook/Events/OlkCommandButtonEvents.cs:222-232 | Source/Outlook/Events/OlkContactPhotoEvents.cs:217-227 | Source/Outlook/Events/OlkDateControlEvents.cs:230-240 | Source/Outlook/Events/OlkListBoxEvents.cs:226-236 | Source/Outlook/Events/OlkOptionButtonEvents.cs:226-236 | Source/Outlook/Events/OlkTextBoxEvents.cs:226-236 | Source/Outlook/Events/OlkTimeControlEvents.cs:230-240 | Source/Outlook/Events/OlkTimeZoneControlEvents.cs:230-240 — before extracting anything, compare `Source/Outlook/Events/OlkCategoryEvents.cs` and `Source/Outlook/Events/OlkCheckBoxEvents.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 160 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (11 lines × 11) Source/Word/Events/ApplicationEvents2.cs:163 — Source/Word/Events/ApplicationEvents2.cs:163-173 | Source/Word/Events/ApplicationEvents2.cs:180-190 | Source/Word/Events/ApplicationEvents3.cs:228-238 | Source/Word/Events/ApplicationEvents3.cs:245-255 | Source/Word/Events/ApplicationEvents3.cs:454-464 | Source/Word/Events/ApplicationEvents3.cs:485-495 | Source/Word/Events/ApplicationEvents4.cs:301-311 | Source/Word/Events/ApplicationEvents4.cs:318-328 | Source/Word/Events/ApplicationEvents4.cs:527-537 | Source/Word/Events/ApplicationEvents4.cs:558-568 | Source/Word/Events/ApplicationEvents4.cs:712-722 — before extracting anything, compare `Source/Word/Events/ApplicationEvents2.cs` and `Source/Word/Events/ApplicationEvents3.cs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 270 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (12 lines × 9) · ×2
  • Duplicated block (12 lines × 9) Source/Outlook/Events/OlkCheckBoxEvents.cs:297 — Source/Outlook/Events/OlkCheckBoxEvents.cs:297-308 | Source/Outlook/Events/OlkComboBoxEvents.cs:312-323 | Source/Outlook/Events/OlkCommandButtonEvents.cs:282-293 | Source/Outlook/Events/OlkDateControlEvents.cs:312-323 | Source/Outlook/Events/OlkListBoxEvents.cs:297-308 | Source/Outlook/Events/OlkOptionButtonEvents.cs:297-308 | Source/Outlook/Events/OlkTextBoxEvents.cs:297-308 | Source/Outlook/Events/OlkTimeControlEvents.cs:312-323 | Source/Outlook/Events/OlkTimeZoneControlEvents.cs:312-323 — before extracting anything, compare `Source/Outlook/Events/OlkCheckBoxEvents.cs` and `Source/Outlook/Events/OlkComboBoxEvents.cs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 189 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (12 lines × 9) Source/Access/Events/DispAttachmentEvents.cs:188 — Source/Access/Events/DispAttachmentEvents.cs:188-199 | Source/Access/Events/DispComboBoxEvents.cs:384-395 | Source/Access/Events/DispNavigationControlEvents.cs:360-371 | Source/Access/Events/DispTextBoxEvents.cs:360-371 | Source/Access/Events/DispWebBrowserControlEvents.cs:227-238 | Source/Access/Events/_ComboBoxEvents.cs:382-393 | Source/Access/Events/_FormEvents.cs:753-764 | Source/Access/Events/_FormEvents2.cs:730-741 | Source/Access/Events/_TextBoxEvents.cs:357-368 — before extracting anything, compare `Source/Access/Events/DispAttachmentEvents.cs` and `Source/Access/Events/DispComboBoxEvents.cs` as WHOLE FILES: this scan already matched 36 separate duplicated blocks between them, totalling at least 321 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (12 lines × 8) · ×2
  • Duplicated block (12 lines × 8) Source/Access/Events/DispListBoxEvents.cs:123 — Source/Access/Events/DispListBoxEvents.cs:123-134 | Source/Access/Events/DispNavigationControlEvents.cs:137-148 | Source/Access/Events/DispOptionButtonEvents.cs:132-143 | Source/Access/Events/DispOptionGroupEvents.cs:98-109 | Source/Access/Events/DispPaletteButtonEvents.cs:134-145 | Source/Access/Events/DispTextBoxEvents.cs:137-148 | Source/Access/Events/DispToggleButtonEvents.cs:134-145 | Source/Access/Events/DispWebBrowserControlEvents.cs:175-186 — before extracting anything, compare `Source/Access/Events/DispListBoxEvents.cs` and `Source/Access/Events/DispNavigationControlEvents.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 192 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (12 lines × 8) Source/MSComctlLib/Events/DImageComboEvents.cs:261 — Source/MSComctlLib/Events/DImageComboEvents.cs:261-272 | Source/MSComctlLib/Events/IProgressBarEvents.cs:251-262 | Source/MSComctlLib/Events/ISliderEvents.cs:347-358 | Source/MSComctlLib/Events/IStatusBarEvents.cs:304-315 | Source/MSComctlLib/Events/ITabStripEvents.cs:337-348 | Source/MSComctlLib/Events/IToolbarEvents.cs:310-321 | Source/MSComctlLib/Events/ITreeViewEvents.cs:450-461 | Source/MSComctlLib/Events/ListViewEvents.cs:418-429 — before extracting anything, compare `Source/MSComctlLib/Events/DImageComboEvents.cs` and `Source/MSComctlLib/Events/IProgressBarEvents.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 157 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (12 lines × 6) · ×2
  • Duplicated block (12 lines × 6) Source/Access/Events/DispBoundObjectFrameEvents.cs:128 — Source/Access/Events/DispBoundObjectFrameEvents.cs:128-139 | Source/Access/Events/DispCustomControlEvents.cs:69-80 | Source/Access/Events/DispWebBrowserControlEvents.cs:160-171 | Source/Access/Events/_BoundObjectFrameEvents.cs:128-139 | Source/Access/Events/_CustomControlEvents.cs:68-79 | Source/Access/Events/_ObjectFrameEvents.cs:102-113 — before extracting anything, compare `Source/Access/Events/DispBoundObjectFrameEvents.cs` and `Source/Access/Events/DispCustomControlEvents.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 69 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (12 lines × 6) Source/Access/Events/_FormEvents.cs:995 — Source/Access/Events/_FormEvents.cs:995-1006 | Source/Access/Events/_FormEvents.cs:1011-1022 | Source/Access/Events/_FormEvents.cs:1027-1038 | Source/Access/Events/_FormEvents2.cs:874-885 | Source/Access/Events/_FormEvents2.cs:890-901 | Source/Access/Events/_FormEvents2.cs:906-917 — before extracting anything, compare `Source/Access/Events/_FormEvents.cs` and `Source/Access/Events/_FormEvents2.cs` as WHOLE FILES: this scan already matched 72 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (13 lines × 5) · ×2
  • Duplicated block (13 lines × 5) Source/NetOffice/Invoker.cs:360 — Source/NetOffice/Invoker.cs:360-372 | Source/NetOffice/Invoker.cs:427-439 | Source/NetOffice/Invoker.cs:656-668 | Source/NetOffice/Invoker.cs:688-700 | Source/NetOffice/Invoker.cs:723-735 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/NetOffice/Invoker.cs:360` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 5) REDACTED:84 — REDACTED:84-96 | REDACTED:84-96 | REDACTED:87-99 | REDACTED:86-98 | REDACTED:85-97 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 106 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (9 lines × 7) · ×2
  • Duplicated block (9 lines × 7) Source/NetOffice/Invoker.cs:326 — Source/NetOffice/Invoker.cs:326-334 | Source/NetOffice/Invoker.cs:360-368 | Source/NetOffice/Invoker.cs:427-435 | Source/NetOffice/Invoker.cs:622-630 | Source/NetOffice/Invoker.cs:656-664 | Source/NetOffice/Invoker.cs:688-696 | Source/NetOffice/Invoker.cs:723-731 — all 7 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/NetOffice/Invoker.cs:326` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (9 lines × 7) Source/Access/Tools/COMAddin.cs:725 — Source/Access/Tools/COMAddin.cs:725-733 | Source/Excel/Tools/COMAddin.cs:727-735 | Source/Office/Tools/COMAddin.cs:902-910 | Source/Outlook/Tools/COMAddin.cs:942-950 | Source/PowerPoint/Tools/COMAddin.cs:726-734 | Source/VBIDE/Tools/COMAddin.cs:421-429 | Source/Word/Tools/COMAddin.cs:865-873 — before extracting anything, compare `Source/Access/Tools/COMAddin.cs` and `Source/Excel/Tools/COMAddin.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 284 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (11 lines × 6) · ×2
  • Duplicated block (11 lines × 6) Source/Word/Events/ApplicationEvents2.cs:276 — Source/Word/Events/ApplicationEvents2.cs:276-286 | Source/Word/Events/ApplicationEvents2.cs:293-303 | Source/Word/Events/ApplicationEvents3.cs:341-351 | Source/Word/Events/ApplicationEvents3.cs:358-368 | Source/Word/Events/ApplicationEvents4.cs:414-424 | Source/Word/Events/ApplicationEvents4.cs:431-441 — before extracting anything, compare `Source/Word/Events/ApplicationEvents2.cs` and `Source/Word/Events/ApplicationEvents3.cs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 270 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (11 lines × 6) Source/Outlook/Events/ItemEvents.cs:339 — Source/Outlook/Events/ItemEvents.cs:339-349 | Source/Outlook/Events/ItemEvents_10.cs:396-406 | Source/Outlook/Events/ItemEvents_10.cs:444-454 | Source/Outlook/Events/ItemEvents_10.cs:461-471 | Source/Outlook/Events/ItemEvents_10.cs:478-488 | Source/Outlook/Events/ItemEvents_10.cs:495-505 — before extracting anything, compare `Source/Outlook/Events/ItemEvents.cs` and `Source/Outlook/Events/ItemEvents_10.cs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 292 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (8 lines × 10) · ×2
  • Duplicated block (8 lines × 10) Source/Access/Events/_BoundObjectFrameEvents.cs:26 — Source/Access/Events/_BoundObjectFrameEvents.cs:26-33 | Source/Access/Events/_CheckBoxEvents.cs:25-32 | Source/Access/Events/_ComboBoxEvents.cs:21-28 | Source/Access/Events/_FormEvents.cs:36-43 | Source/Access/Events/_ListBoxEvents.cs:20-27 | Source/Access/Events/_OptionButtonEvents.cs:25-32 | Source/Access/Events/_OptionGroupEvents.cs:21-28 | Source/Access/Events/_PaletteButtonEvents.cs:25-32 | Source/Access/Events/_TextBoxEvents.cs:20-27 | Source/Access/Events/_ToggleButtonEvents.cs:25-32 — before extracting anything, compare `Source/Access/Events/_BoundObjectFrameEvents.cs` and `Source/Access/Events/_CheckBoxEvents.cs` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 292 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Source/Access/Events/_BoundObjectFrameEvents.cs:34` calls `MethodImpl`, `DispId`, `Enter` and `Source/Access/Events/_FormEvents.cs:44` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (8 lines × 10) Source/Access/Events/_BoundObjectFrameEvents.cs:33 — Source/Access/Events/_BoundObjectFrameEvents.cs:33-40 | Source/Access/Events/_CheckBoxEvents.cs:32-39 | Source/Access/Events/_ListBoxEvents.cs:27-34 | Source/Access/Events/_ObjectFrameEvents.cs:24-31 | Source/Access/Events/_OptionButtonEvents.cs:32-39 | Source/Access/Events/_OptionGroupEvents.cs:28-35 | Source/Access/Events/_PaletteButtonEvents.cs:32-39 | Source/Access/Events/_SubFormEvents.cs:19-26 | Source/Access/Events/_SubReportEvents.cs:19-26 | Source/Access/Events/_ToggleButtonEvents.cs:32-39 — before extracting anything, compare `Source/Access/Events/_BoundObjectFrameEvents.cs` and `Source/Access/Events/_CheckBoxEvents.cs` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 292 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (9–10 lines × 5) · ×2
  • Duplicated block (9–10 lines × 5) Source/ADODB/Events/RecordsetEvents.cs:138 — Source/ADODB/Events/RecordsetEvents.cs:138-147 | Source/ADODB/Events/RecordsetEvents.cs:181-189 | Source/ADODB/Events/RecordsetEvents.cs:242-250 | Source/ADODB/Events/RecordsetEvents.cs:280-288 | Source/ADODB/Events/RecordsetEvents.cs:319-327 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (9–10 lines × 5) Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/ReportControl.cs:245 — Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/ReportControl.cs:245-253 | Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/ReportControl.cs:266-274 | Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/ReportControl.cs:287-295 | Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/ReportControl.cs:308-316 | Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/ReportControl.cs:329-338 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/ReportControl.cs:245` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (9 lines × 5) · ×2
  • Duplicated block (9 lines × 5) Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/NetOfficeSupportTable.cs:132 — Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/NetOfficeSupportTable.cs:132-140 | Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/NetOfficeSupportTable.cs:197-205 | Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/NetOfficeSupportTable.cs:327-335 | Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/NetOfficeSupportTable.cs:348-356 | Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/NetOfficeSupportTable.cs:375-383 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/NetOfficeSupportTable.cs:132` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (9 lines × 5) Source/ADODB/Events/ConnectionEvents.cs:119 — Source/ADODB/Events/ConnectionEvents.cs:119-127 | Source/ADODB/Events/ConnectionEvents.cs:157-165 | Source/ADODB/Events/ConnectionEvents.cs:175-183 | Source/ADODB/Events/ConnectionEvents.cs:271-279 | Source/ADODB/Events/RecordsetEvents.cs:332-340 — there are 5 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 5 sites; resolving a subset leaves the remainder to drift apart.
D4 · Code Duplication · Duplicated block (6–10 lines × 3) · ×2
  • Duplicated block (6–10 lines × 3) Source/Outlook/Events/ItemEvents.cs:40 — Source/Outlook/Events/ItemEvents.cs:40-45 | Source/Outlook/Events/ItemEvents.cs:66-75 | Source/Outlook/Events/ItemEvents.cs:76-81 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (6–10 lines × 3) Source/PowerPoint/Events/EApplication.cs:39 — Source/PowerPoint/Events/EApplication.cs:39-48 | Source/PowerPoint/Events/EApplication.cs:49-54 | Source/PowerPoint/Events/EApplication.cs:91-96 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (6–10 lines × 2) · ×2
  • Duplicated block (6–10 lines × 2) Source/Excel/Events/DocEvents.cs:56 — Source/Excel/Events/DocEvents.cs:56-61 | Source/Excel/Events/WorkbookEvents.cs:126-135 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (6–10 lines × 2) Source/PowerPoint/Events/EApplication.cs:71 — Source/PowerPoint/Events/EApplication.cs:71-80 | Source/PowerPoint/Events/EApplication.cs:81-86 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (8 lines × 14) · ×2
  • Duplicated block (8 lines × 14) Source/Access/Events/_BoundObjectFrameEvents.cs:43 — Source/Access/Events/_BoundObjectFrameEvents.cs:43-50 | Source/Access/Events/_CheckBoxEvents.cs:42-49 | Source/Access/Events/_CheckBoxInOptionEvents.cs:20-27 | Source/Access/Events/_ComboBoxEvents.cs:47-54 | Source/Access/Events/_CommandButtonEvents.cs:32-39 | Source/Access/Events/_FormEvents.cs:86-93 | Source/Access/Events/_ListBoxEvents.cs:37-44 | Source/Access/Events/_ObjectFrameEvents.cs:34-41 | Source/Access/Events/_OptionButtonEvents.cs:42-49 | Source/Access/Events/_OptionButtonInOptionEvents.cs:20-27 | Source/Access/Events/_PaletteButtonEvents.cs:42-49 | Source/Access/Events/_TextBoxEvents.cs:40-47 | Source/Access/Events/_ToggleButtonEvents.cs:42-49 | Source/Access/Events/_ToggleButtonInOptionEvents.cs:20-27 — before extracting anything, compare `Source/Access/Events/_BoundObjectFrameEvents.cs` and `Source/Access/Events/_CheckBoxEvents.cs` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 292 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Source/Access/Events/_BoundObjectFrameEvents.cs:51` calls `MethodImpl`, `DispId`, `Click` and `Source/Access/Events/_CheckBoxEvents.cs:50` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (8 lines × 14) Source/Access/Events/DispAttachmentEvents.cs:28 — Source/Access/Events/DispAttachmentEvents.cs:28-35 | Source/Access/Events/DispBoundObjectFrameEvents.cs:33-40 | Source/Access/Events/DispCheckBoxEvents.cs:32-39 | Source/Access/Events/DispComboBoxEvents.cs:38-45 | Source/Access/Events/DispCustomControlEvents.cs:24-31 | Source/Access/Events/DispListBoxEvents.cs:28-35 | Source/Access/Events/DispObjectFrameEvents.cs:24-31 | Source/Access/Events/DispOptionButtonEvents.cs:31-38 | Source/Access/Events/DispOptionGroupEvents.cs:28-35 | Source/Access/Events/DispPaletteButtonEvents.cs:32-39 | Source/Access/Events/DispSubFormEvents.cs:19-26 | Source/Access/Events/DispSubReportEvents.cs:19-26 | Source/Access/Events/DispTextBoxEvents.cs:32-39 | Source/Access/Events/DispToggleButtonEvents.cs:32-39 — before extracting anything, compare `Source/Access/Events/DispAttachmentEvents.cs` and `Source/Access/Events/DispBoundObjectFrameEvents.cs` as WHOLE FILES: this scan already matched 29 separate duplicated blocks between them, totalling at least 271 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Access/Events/DispTextBoxEvents.cs:28` calls `SupportByVersion`, `MethodImpl`, `DispId` and `Source/Access/Events/DispAttachmentEvents.cs:26` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (9 lines × 4) · ×2
  • Duplicated block (9 lines × 4) Source/Excel/Events/AppEvents.cs:861 — Source/Excel/Events/AppEvents.cs:861-869 | Source/Excel/Events/AppEvents.cs:884-892 | Source/Excel/Events/WorkbookEvents.cs:733-741 | Source/Excel/Events/WorkbookEvents.cs:756-764 — before extracting anything, compare `Source/Excel/Events/AppEvents.cs` and `Source/Excel/Events/WorkbookEvents.cs` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 377 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (9 lines × 4) REDACTED:130 — REDACTED:130-138 | REDACTED:201-209 | REDACTED:142-150 | REDACTED:141-149 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 106 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (5 lines × 9) · ×2
  • Duplicated block (5 lines × 9) Source/Access/Events/DispNavigationButtonEvents.cs:45 — Source/Access/Events/DispNavigationButtonEvents.cs:45-49 | Source/Access/Events/DispNavigationButtonEvents.cs:53-57 | Source/Access/Events/DispNavigationButtonEvents.cs:61-65 | Source/Access/Events/DispNavigationControlEvents.cs:58-62 | Source/Access/Events/DispNavigationControlEvents.cs:66-70 | Source/Access/Events/DispNavigationControlEvents.cs:74-78 | Source/Access/Events/DispWebBrowserControlEvents.cs:68-72 | Source/Access/Events/DispWebBrowserControlEvents.cs:76-80 | Source/Access/Events/DispWebBrowserControlEvents.cs:84-88 — before extracting anything, compare `Source/Access/Events/DispNavigationButtonEvents.cs` and `Source/Access/Events/DispNavigationControlEvents.cs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 226 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 9) Source/OWC10/Events/IChartEvents.cs:282 — Source/OWC10/Events/IChartEvents.cs:282-286 | Source/OWC10/Events/IChartEvents.cs:300-304 | Source/OWC10/Events/IChartEvents.cs:317-321 | Source/OWC10/Events/IPivotControlEvents.cs:543-547 | Source/OWC10/Events/IPivotControlEvents.cs:561-565 | Source/OWC10/Events/IPivotControlEvents.cs:578-582 | Source/OWC10/Events/ISpreadsheetEventSink.cs:254-258 | Source/OWC10/Events/ISpreadsheetEventSink.cs:272-276 | Source/OWC10/Events/ISpreadsheetEventSink.cs:289-293 — before extracting anything, compare `Source/OWC10/Events/IChartEvents.cs` and `Source/OWC10/Events/IPivotControlEvents.cs` as WHOLE FILES: this scan already matched 39 separate duplicated blocks between them, totalling at least 404 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (7–8 lines × 3) · ×2
  • Duplicated block (7–8 lines × 3) Source/Outlook/Events/ApplicationEvents.cs:118 — Source/Outlook/Events/ApplicationEvents.cs:118-125 | Source/Outlook/Events/ApplicationEvents_10.cs:133-140 | Source/Outlook/Events/ApplicationEvents_11.cs:191-197 — before extracting anything, compare `Source/Outlook/Events/ApplicationEvents.cs` and `Source/Outlook/Events/ApplicationEvents_10.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 82 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Source/Outlook/Events/ApplicationEvents.cs:118` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Outlook/Events/ApplicationEvents_10.cs:132` calls `ReleaseParamsArray` and `Source/Outlook/Events/ApplicationEvents.cs:117` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (7–8 lines × 3) Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/ReportControl.cs:219 — Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/ReportControl.cs:219-226 | Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/ReportControl.cs:244-250 | Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/ReportControl.cs:265-271 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/ReportControl.cs:219` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (6 lines × 22) · ×2
  • Duplicated block (6 lines × 22) Source/Access/Events/DispAttachmentEvents.cs:54 — Source/Access/Events/DispAttachmentEvents.cs:54-59 | Source/Access/Events/DispBoundObjectFrameEvents.cs:50-55 | Source/Access/Events/DispCheckBoxEvents.cs:19-24 | Source/Access/Events/DispComboBoxEvents.cs:55-60 | Source/Access/Events/DispImageEvents.cs:19-24 | Source/Access/Events/DispLabelEvents.cs:19-24 | Source/Access/Events/DispListBoxEvents.cs:45-50 | Source/Access/Events/DispObjectFrameEvents.cs:41-46 | Source/Access/Events/DispOptionGroupEvents.cs:37-42 | Source/Access/Events/DispPageEvents.cs:19-24 | Source/Access/Events/DispPageHdrFtrInReportEvents.cs:31-36 | Source/Access/Events/DispPaletteButtonEvents.cs:19-24 | Source/Access/Events/DispRectangleEvents.cs:19-24 | Source/Access/Events/DispSectionEvents.cs:19-24 | Source/Access/Events/DispSectionInReportEvents.cs:35-40 | Source/Access/Events/DispTabControlEvents.cs:19-24 | Source/Access/Events/DispTextBoxEvents.cs:49-54 | Source/Access/Events/DispToggleButtonEvents.cs:19-24 | Source/Access/Events/_FormEvents2.cs:95-100 | Source/Access/Events/_PageHdrFtrInReportEvents.cs:31-36 | Source/Access/Events/_ReportEvents2.cs:76-81 | Source/Access/Events/_SectionInReportEvents.cs:35-40 — before extracting anything, compare `Source/Access/Events/DispAttachmentEvents.cs` and `Source/Access/Events/DispBoundObjectFrameEvents.cs` as WHOLE FILES: this scan already matched 29 separate duplicated blocks between them, totalling at least 271 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Access/Events/DispSectionInReportEvents.cs:31` calls `SupportByVersion`, `MethodImpl`, `DispId` and `Source/Access/Events/DispPageHdrFtrInReportEvents.cs:29` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (6 lines × 22) Source/Access/Events/DispAttachmentEvents.cs:32 — Source/Access/Events/DispAttachmentEvents.cs:32-37 | Source/Access/Events/DispBoundObjectFrameEvents.cs:37-42 | Source/Access/Events/DispCheckBoxEvents.cs:36-41 | Source/Access/Events/DispComboBoxEvents.cs:42-47 | Source/Access/Events/DispCustomControlEvents.cs:28-33 | Source/Access/Events/DispListBoxEvents.cs:32-37 | Source/Access/Events/DispNavigationButtonEvents.cs:27-32 | Source/Access/Events/DispNavigationControlEvents.cs:36-41 | Source/Access/Events/DispObjectFrameEvents.cs:28-33 | Source/Access/Events/DispOptionButtonEvents.cs:35-40 | Source/Access/Events/DispOptionGroupEvents.cs:32-37 | Source/Access/Events/DispPaletteButtonEvents.cs:36-41 | Source/Access/Events/DispTextBoxEvents.cs:36-41 | Source/Access/Events/DispToggleButtonEvents.cs:36-41 | Source/Access/Events/_BoundObjectFrameEvents.cs:37-42 | Source/Access/Events/_CheckBoxEvents.cs:36-41 | Source/Access/Events/_ListBoxEvents.cs:31-36 | Source/Access/Events/_ObjectFrameEvents.cs:28-33 | Source/Access/Events/_OptionButtonEvents.cs:36-41 | Source/Access/Events/_OptionGroupEvents.cs:32-37 | Source/Access/Events/_PaletteButtonEvents.cs:36-41 | Source/Access/Events/_ToggleButtonEvents.cs:36-41 — before extracting anything, compare `Source/Access/Events/DispAttachmentEvents.cs` and `Source/Access/Events/DispBoundObjectFrameEvents.cs` as WHOLE FILES: this scan already matched 29 separate duplicated blocks between them, totalling at least 271 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (5 lines × 12) · ×2
  • Duplicated block (5 lines × 12) Source/Access/Events/_BoundObjectFrameEvents.cs:33 — Source/Access/Events/_BoundObjectFrameEvents.cs:33-37 | Source/Access/Events/_CheckBoxEvents.cs:32-36 | Source/Access/Events/_ComboBoxEvents.cs:38-42 | Source/Access/Events/_CommandButtonEvents.cs:23-27 | Source/Access/Events/_CustomControlEvents.cs:24-28 | Source/Access/Events/_ListBoxEvents.cs:27-31 | Source/Access/Events/_ObjectFrameEvents.cs:24-28 | Source/Access/Events/_OptionButtonEvents.cs:32-36 | Source/Access/Events/_OptionGroupEvents.cs:28-32 | Source/Access/Events/_PaletteButtonEvents.cs:32-36 | Source/Access/Events/_TextBoxEvents.cs:31-35 | Source/Access/Events/_ToggleButtonEvents.cs:32-36 — before extracting anything, compare `Source/Access/Events/_BoundObjectFrameEvents.cs` and `Source/Access/Events/_CheckBoxEvents.cs` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 292 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Source/Access/Events/_BoundObjectFrameEvents.cs:38` calls `SinkArgument` and `Source/Access/Events/_ComboBoxEvents.cs:43` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 12) Source/Outlook/Events/OlkCategoryEvents.cs:47 — Source/Outlook/Events/OlkCategoryEvents.cs:47-51 | Source/Outlook/Events/OlkCheckBoxEvents.cs:47-51 | Source/Outlook/Events/OlkComboBoxEvents.cs:47-51 | Source/Outlook/Events/OlkCommandButtonEvents.cs:47-51 | Source/Outlook/Events/OlkContactPhotoEvents.cs:47-51 | Source/Outlook/Events/OlkDateControlEvents.cs:47-51 | Source/Outlook/Events/OlkListBoxEvents.cs:47-51 | Source/Outlook/Events/OlkOptionButtonEvents.cs:47-51 | Source/Outlook/Events/OlkSenderPhotoEvents.cs:47-51 | Source/Outlook/Events/OlkTextBoxEvents.cs:47-51 | Source/Outlook/Events/OlkTimeControlEvents.cs:47-51 | Source/Outlook/Events/OlkTimeZoneControlEvents.cs:47-51 — before extracting anything, compare `Source/Outlook/Events/OlkCategoryEvents.cs` and `Source/Outlook/Events/OlkCheckBoxEvents.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 160 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (5 lines × 14) · ×2
  • Duplicated block (5 lines × 14) Source/Access/Events/_BoundObjectFrameEvents.cs:33 — Source/Access/Events/_BoundObjectFrameEvents.cs:33-37 | Source/Access/Events/_CheckBoxEvents.cs:32-36 | Source/Access/Events/_ComboBoxEvents.cs:38-42 | Source/Access/Events/_CommandButtonEvents.cs:23-27 | Source/Access/Events/_CustomControlEvents.cs:24-28 | Source/Access/Events/_ListBoxEvents.cs:27-31 | Source/Access/Events/_ObjectFrameEvents.cs:24-28 | Source/Access/Events/_OptionButtonEvents.cs:32-36 | Source/Access/Events/_OptionGroupEvents.cs:28-32 | Source/Access/Events/_PaletteButtonEvents.cs:32-36 | Source/Access/Events/_SubFormEvents.cs:19-23 | Source/Access/Events/_SubReportEvents.cs:19-23 | Source/Access/Events/_TextBoxEvents.cs:31-35 | Source/Access/Events/_ToggleButtonEvents.cs:32-36 — before extracting anything, compare `Source/Access/Events/_BoundObjectFrameEvents.cs` and `Source/Access/Events/_CheckBoxEvents.cs` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 292 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Source/Access/Events/_BoundObjectFrameEvents.cs:38` calls `SinkArgument` and `Source/Access/Events/_ComboBoxEvents.cs:43` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 14) Source/Outlook/Classes/ContactItem.cs:46 — Source/Outlook/Classes/ContactItem.cs:46-50 | Source/Outlook/Classes/DistListItem.cs:46-50 | Source/Outlook/Classes/DocumentItem.cs:46-50 | Source/Outlook/Classes/JournalItem.cs:46-50 | Source/Outlook/Classes/MailItem.cs:46-50 | Source/Outlook/Classes/MeetingItem.cs:46-50 | Source/Outlook/Classes/PostItem.cs:46-50 | Source/Outlook/Classes/RemoteItem.cs:46-50 | Source/Outlook/Classes/ReportItem.cs:46-50 | Source/Outlook/Classes/TaskItem.cs:46-50 | Source/Outlook/Classes/TaskRequestAcceptItem.cs:46-50 | Source/Outlook/Classes/TaskRequestDeclineItem.cs:46-50 | Source/Outlook/Classes/TaskRequestItem.cs:46-50 | Source/Outlook/Classes/TaskRequestUpdateItem.cs:46-50 — before extracting anything, compare `Source/Outlook/Classes/ContactItem.cs` and `Source/Outlook/Classes/DistListItem.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (701 lines × 2) · ×2
  • Duplicated block (701 lines × 2) Source/Excel/DispatchInterfaces/WorksheetFunction.Aggregate.cs:54 — Source/Excel/DispatchInterfaces/WorksheetFunction.Aggregate.cs:54-754 | Source/Excel/Interfaces/IWorksheetFunction.Aggregate.cs:54-754 — before extracting anything, compare `Source/Excel/DispatchInterfaces/WorksheetFunction.Aggregate.cs` and `Source/Excel/Interfaces/IWorksheetFunction.Aggregate.cs` as WHOLE FILES: 99% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (701 lines × 2) Source/Excel/DispatchInterfaces/WorksheetFunction.RTD.cs:54 — Source/Excel/DispatchInterfaces/WorksheetFunction.RTD.cs:54-754 | Source/Excel/Interfaces/IWorksheetFunction.RTD.cs:54-754 — before extracting anything, compare `Source/Excel/DispatchInterfaces/WorksheetFunction.RTD.cs` and `Source/Excel/Interfaces/IWorksheetFunction.RTD.cs` as WHOLE FILES: 99% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (11 lines × 5) · ×2
  • Duplicated block (11 lines × 5) Source/Access/Tools/COMAddin.cs:606 — Source/Access/Tools/COMAddin.cs:606-616 | Source/Excel/Tools/COMAddin.cs:605-615 | Source/Office/Tools/COMAddin.cs:749-759 | Source/PowerPoint/Tools/COMAddin.cs:607-617 | Source/Word/Tools/COMAddin.cs:608-618 — before extracting anything, compare `Source/Access/Tools/COMAddin.cs` and `Source/Excel/Tools/COMAddin.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 284 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 5) Toolbox/Toolbox/ToolboxControls/ProjectWizard/Controls/EnvironmentControl.cs:190 — Toolbox/Toolbox/ToolboxControls/ProjectWizard/Controls/EnvironmentControl.cs:190-200 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/Controls/EnvironmentControl.cs:203-213 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/Controls/HostControl.cs:216-226 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/Controls/LoadControl.cs:225-235 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/Controls/LoadControl.cs:238-251 — there are 5 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 5 sites; resolving a subset leaves the remainder to drift apart.
D4 · Code Duplication · Duplicated block (8 lines × 7) · ×2
  • Duplicated block (8 lines × 7) Source/Access/Events/_FormEvents.cs:984 — Source/Access/Events/_FormEvents.cs:984-991 | Source/Access/Events/_FormEvents2.cs:863-870 | Source/OWC10/Events/IChartEvents.cs:403-410 | Source/OWC10/Events/IPivotControlEvents.cs:215-222 | Source/OWC10/Events/ISpreadsheetEventSink.cs:601-608 | Source/Outlook/Events/ExplorerEvents.cs:160-167 | Source/Outlook/Events/ExplorerEvents_10.cs:209-216 — before extracting anything, compare `Source/Access/Events/_FormEvents.cs` and `Source/Access/Events/_FormEvents2.cs` as WHOLE FILES: this scan already matched 72 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (8 lines × 7) Source/MSComctlLib/Events/IStatusBarEvents.cs:232 — Source/MSComctlLib/Events/IStatusBarEvents.cs:232-239 | Source/MSComctlLib/Events/IToolbarEvents.cs:238-245 | Source/MSComctlLib/Events/ITreeViewEvents.cs:364-371 | Source/MSComctlLib/Events/ListViewEvents.cs:346-353 | Source/OWC10/Events/IChartEvents.cs:207-214 | Source/OWC10/Events/IPivotControlEvents.cs:399-406 | Source/OWC10/Events/ISpreadsheetEventSink.cs:390-397 — before extracting anything, compare `Source/MSComctlLib/Events/IStatusBarEvents.cs` and `Source/MSComctlLib/Events/IToolbarEvents.cs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 205 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Edited copy of a member (22 corresponding lines) · ×2
  • Edited copy of a member (22 corresponding lines) Examples/PowerPoint/Automation/Examples/Example01.cs:18 — Examples/PowerPoint/Automation/Examples/Example01.cs:18-39 | Examples/PowerPoint/Automation/Examples/Example05.cs:18-42 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) Examples/Other/Outlook Addin - Use Twitter/Outlook Addin - Use Twitter/Twitter/TwitterTimer.cs:283 — Examples/Other/Outlook Addin - Use Twitter/Outlook Addin - Use Twitter/Twitter/TwitterTimer.cs:283-311 | Examples/Other/Outlook Addin - Use Twitter/Outlook Addin - Use Twitter/Twitter/TwitterTimer.cs:320-341 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (17 lines × 5) · ×2
  • Duplicated block (17 lines × 5) Examples/Access/NetOffice COMAddin Examples/02 Ribbons And Panes/SamplePane.cs:77 — Examples/Access/NetOffice COMAddin Examples/02 Ribbons And Panes/SamplePane.cs:77-93 | Examples/Excel/NetOffice COMAddin Examples/02 Ribbons And Panes/SamplePane.cs:77-93 | Examples/Outlook/NetOffice COMAddin Examples/02 Ribbons And Panes/SamplePane.cs:78-94 | Examples/PowerPoint/NetOffice COMAddin Examples/02 Ribbons And Panes/SamplePane.cs:77-93 | Examples/Word/NetOffice COMAddin Examples/02 Ribbons And Panes/SamplePane.cs:77-93 — before extracting anything, compare `Examples/Access/NetOffice COMAddin Examples/02 Ribbons And Panes/SamplePane.cs` and `Examples/Excel/NetOffice COMAddin Examples/02 Ribbons And Panes/SamplePane.cs` as WHOLE FILES: 86% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (17 lines × 5) RegAddin/RegAddinTest/CmdLineTest02.cs:17 — RegAddin/RegAddinTest/CmdLineTest02.cs:17-33 | RegAddin/RegAddinTest/CmdLineTest02.cs:41-57 | RegAddin/RegAddinTest/CmdLineTest02.cs:65-81 | RegAddin/RegAddinTest/CmdLineTest02.cs:90-106 | RegAddin/RegAddinTest/CmdLineTest02.cs:115-131 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
X12 · Unreachable branch · Branch is unreachable · ×2
  • Branch is unreachable — its condition cannot hold here RegAddin/RegAddin/Common/AddinRegAnalyzer.cs:106 — `regLocation == 2` can never be true where it stands: the guard on line 103 (`regLocation < 0 || regLocation > 2`) left this block when it was true; the enclosing `if` on line 105 (`0 == regLocation`) holds. No value of `regLocation` satisfies all of that, so the true arm of this conditional expression never runs. Reorder the tests, drop the dead branch, or fix the bound that was meant.
  • Branch is unreachable — its condition cannot hold here RegAddin/RegAddin/Metrics/AddinMetrics.cs:108 — `case PossibleAddin.No:` can never be true where it stands: the guard on line 97 (`possible == PossibleAddin.No`) left this block when it was true. No value of `possible` satisfies all of that, so this case label never runs. Reorder the tests, drop the dead branch, or fix the bound that was meant.
C1 · Data Protection · No data-protection/encryption · ×1
  • No data-protection/encryption — No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.
D17 · Explicit Debt · BarePragmaDisable repeated across 2519 files · ×1
  • BarePragmaDisable repeated across 2519 files Source/ADODB/Classes/Command.cs:10 — The identical BarePragmaDisable (`#pragma warning disable`) appears in 2519 files (2840 occurrences) — a single repo-wide policy (e.g. a Directory.Build.props decision or an idiomatic suppression), not 2840 independent debts. Decide it once centrally rather than file-by-file. (Every occurrence still counts toward the score and metrics.)
D17 · Explicit Debt · BarePragmaDisable repeated across 162 files · ×1
  • BarePragmaDisable repeated across 162 files Source/ADODB/Events/ConnectionEvents.cs:10 — The identical BarePragmaDisable (`#pragma warning disable CS1591`) appears in 162 files (162 occurrences) — a single repo-wide policy (e.g. a Directory.Build.props decision or an idiomatic suppression), not 162 independent debts. Decide it once centrally rather than file-by-file. (Every occurrence still counts toward the score and metrics.)
D18 · Solution Shape · Build failed · ×1
  • Build failed — The target solution did not build cleanly (errors: 960), which caps Solution Shape at 3/10 — the most basic shape signal is that it compiles. First errors: CS2001: Source file 'Toolbox/Toolbox/Controls/Text/RichTextEditor.designer.cs' could not be found.; CS2001: Source file 'Toolbox/Toolbox/Controls/Text/Scroller.designer.cs' could not be found.; CS0246: The type or namespace name 'NetOffice' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'COMAddin' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'COMAddinAttribute' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'TweakAttribute' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'Tweak' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'CodebaseAttribute' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'Codebase' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'Extensibility' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'IDTExtensibility2' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'ext_ConnectMode' could not be found (are you missing a using directive or an assembly reference?); CS0538: 'IDTExtensibility2' in explicit interface declaration is not an interface; CS0246: The type or namespace name 'CustomPaneAttribute' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'CustomPane' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'ICOMObject' could not be found (are you missing a using directive or an assembly reference?).
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Near-duplicate member family (6 members, 42 shared lines) · ×1
  • Near-duplicate member family (6 members, 42 shared lines) Source/Access/Tools/COMAddin.cs:321 — Source/Access/Tools/COMAddin.cs:321-399 | Source/Excel/Tools/COMAddin.cs:321-398 | Source/Office/Tools/COMAddin.cs:326-404 | Source/Outlook/Tools/COMAddin.cs:331-432 | Source/PowerPoint/Tools/COMAddin.cs:322-400 | Source/Word/Tools/COMAddin.cs:324-401 — These 6 members are variants of one another: a block of 42 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
D4 · Code Duplication · Near-duplicate member family (4 members, 11 shared lines) · ×1
  • Near-duplicate member family (4 members, 11 shared lines) Source/Excel/Events/AppEvents.cs:860 — Source/Excel/Events/AppEvents.cs:860-880 | Source/Excel/Events/WorkbookEvents.cs:732-752 | Source/Excel/Events/WorkbookEvents.cs:755-775 | Source/Excel/Events/WorkbookEvents.cs:778-795 — These 4 members are variants of one another: a block of 11 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Near-duplicate member family (3 members, 15 shared lines) · ×1
  • Near-duplicate member family (3 members, 15 shared lines) Source/Outlook/Events/OlkTimeZoneControlEvents.cs:143 — Source/Outlook/Events/OlkTimeZoneControlEvents.cs:143-160 | Source/Outlook/Events/OlkTimeZoneControlEvents.cs:163-180 | Source/Outlook/Events/OlkTimeZoneControlEvents.cs:183-200 — These 3 members are variants of one another: a block of 15 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 3 times.
D4 · Code Duplication · Near-duplicate member pair (26 shared lines) · ×1
  • Near-duplicate member pair (26 shared lines) RegAddin/RegAddin/Common/AddinRegAnalyzer.cs:40 — RegAddin/RegAddin/Common/AddinRegAnalyzer.cs:40-82 | RegAddin/RegAddin/Common/AddinRegAnalyzer.cs:85-130 — These two members are variants of one another: 26 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication · Members sharing a duplicated core (144 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (144 members, 50+ identical tokens) Source/Access/Events/DispAttachmentEvents.cs:261 — Source/Access/Events/DispAttachmentEvents.cs:261-279 | Source/Access/Events/DispAttachmentEvents.cs:282-300 | Source/Access/Events/DispAttachmentEvents.cs:303-321 | Source/Access/Events/DispBoundObjectFrameEvents.cs:242-260 | Source/Access/Events/DispBoundObjectFrameEvents.cs:263-281 | Source/Access/Events/DispBoundObjectFrameEvents.cs:284-302 | Source/Access/Events/DispCheckBoxEvents.cs:223-241 | Source/Access/Events/DispCheckBoxEvents.cs:244-262 | Source/Access/Events/DispCheckBoxEvents.cs:265-283 | Source/Access/Events/DispComboBoxEvents.cs:271-289 | Source/Access/Events/DispComboBoxEvents.cs:292-310 | Source/Access/Events/DispComboBoxEvents.cs:313-331 | Source/Access/Events/DispCommandButtonEvents.cs:186-204 | Source/Access/Events/DispCommandButtonEvents.cs:207-225 | Source/Access/Events/DispCommandButtonEvents.cs:228-246 | Source/Access/Events/DispImageEvents.cs:105-123 | Source/Access/Events/DispImageEvents.cs:126-144 | Source/Access/Events/DispImageEvents.cs:147-165 | Source/Access/Events/DispLabelEvents.cs:105-123 | Source/Access/Events/DispLabelEvents.cs:126-144 | Source/Access/Events/DispLabelEvents.cs:147-165 | Source/Access/Events/DispListBoxEvents.cs:222-240 | Source/Access/Events/DispListBoxEvents.cs:243-261 | Source/Access/Events/DispListBoxEvents.cs:264-282 | Source/Access/Events/DispNavigationButtonEvents.cs:187-205 | Source/Access/Events/DispNavigationButtonEvents.cs:208-226 | Source/Access/Events/DispNavigationButtonEvents.cs:229-247 | Source/Access/Events/DispNavigationControlEvents.cs:247-265 | Source/Access/Events/DispNavigationControlEvents.cs:268-286 | Source/Access/Events/DispNavigationControlEvents.cs:289-307 | Source/Access/Events/DispObjectFrameEvents.cs:190-208 | Source/Access/Events/DispObjectFrameEvents.cs:211-229 | Source/Access/Events/DispObjectFrameEvents.cs:232-250 | Source/Access/Events/DispOptionButtonEvents.cs:220-238 | Source/Access/Events/DispOptionButtonEvents.cs:241-259 | Source/Access/Events/DispOptionButtonEvents.cs:262-280 | Source/Access/Events/DispOptionGroupEvents.cs:175-193 | Source/Access/Events/DispOptionGroupEvents.cs:196-214 | Source/Access/Events/DispOptionGroupEvents.cs:217-235 | Source/Access/Events/DispPageEvents.cs:105-123 | Source/Access/Events/DispPageEvents.cs:126-144 | Source/Access/Events/DispPageEvents.cs:147-165 | Source/Access/Events/DispPageHdrFtrInReportEvents.cs:155-173 | Source/Access/Events/DispPageHdrFtrInReportEvents.cs:176-194 | Source/Access/Events/DispPageHdrFtrInReportEvents.cs:197-215 | Source/Access/Events/DispPaletteButtonEvents.cs:222-240 | Source/Access/Events/DispPaletteButtonEvents.cs:243-261 | Source/Access/Events/DispPaletteButtonEvents.cs:264-282 | Source/Access/Events/DispRectangleEvents.cs:105-123 | Source/Access/Events/DispRectangleEvents.cs:126-144 | Source/Access/Events/DispRectangleEvents.cs:147-165 | Source/Access/Events/DispSectionEvents.cs:109-127 | Source/Access/Events/DispSectionEvents.cs:130-148 | Source/Access/Events/DispSectionEvents.cs:151-169 | Source/Access/Events/DispSectionInReportEvents.cs:170-188 | Source/Access/Events/DispSectionInReportEvents.cs:191-209 | Source/Access/Events/DispSectionInReportEvents.cs:212-230 | Source/Access/Events/DispTabControlEvents.cs:126-144 | Source/Access/Events/DispTabControlEvents.cs:147-165 | Source/Access/Events/DispTabControlEvents.cs:168-186 | Source/Access/Events/DispTextBoxEvents.cs:247-265 | Source/Access/Events/DispTextBoxEvents.cs:268-286 | Source/Access/Events/DispTextBoxEvents.cs:289-307 | Source/Access/Events/DispToggleButtonEvents.cs:222-240 | Source/Access/Events/DispToggleButtonEvents.cs:243-261 | Source/Access/Events/DispToggleButtonEvents.cs:264-282 | Source/Access/Events/DispWebBrowserControlEvents.cs:300-318 | Source/Access/Events/DispWebBrowserControlEvents.cs:321-339 | Source/Access/Events/DispWebBrowserControlEvents.cs:342-360 | Source/Access/Events/_BoundObjectFrameEvents.cs:242-260 | Source/Access/Events/_BoundObjectFrameEvents.cs:263-281 | Source/Access/Events/_BoundObjectFrameEvents.cs:284-302 | Source/Access/Events/_CheckBoxEvents.cs:222-240 | Source/Access/Events/_CheckBoxEvents.cs:243-261 | Source/Access/Events/_CheckBoxEvents.cs:264-282 | Source/Access/Events/_CheckBoxInOptionEvents.cs:117-135 | Source/Access/Events/_CheckBoxInOptionEvents.cs:138-156 | Source/Access/Events/_CheckBoxInOptionEvents.cs:159-177 | Source/Access/Events/_ComboBoxEvents.cs:269-287 | Source/Access/Events/_ComboBoxEvents.cs:290-308 | Source/Access/Events/_ComboBoxEvents.cs:311-329 | Source/Access/Events/_CommandButtonEvents.cs:186-204 | Source/Access/Events/_CommandButtonEvents.cs:207-225 | Source/Access/Events/_CommandButtonEvents.cs:228-246 | Source/Access/Events/_FormEvents.cs:579-597 | Source/Access/Events/_FormEvents.cs:600-618 | Source/Access/Events/_FormEvents.cs:621-639 | Source/Access/Events/_FormEvents2.cs:555-573 | Source/Access/Events/_FormEvents2.cs:576-594 | Source/Access/Events/_FormEvents2.cs:597-615 | Source/Access/Events/_ImageEvents.cs:105-123 | Source/Access/Events/_ImageEvents.cs:126-144 | Source/Access/Events/_ImageEvents.cs:147-165 | Source/Access/Events/_LabelEvents.cs:105-123 | Source/Access/Events/_LabelEvents.cs:126-144 | Source/Access/Events/_LabelEvents.cs:147-165 | Source/Access/Events/_ListBoxEvents.cs:221-239 | Source/Access/Events/_ListBoxEvents.cs:242-260 | Source/Access/Events/_ListBoxEvents.cs:263-281 | Source/Access/Events/_ObjectFrameEvents.cs:190-208 | Source/Access/Events/_ObjectFrameEvents.cs:211-229 | Source/Access/Events/_ObjectFrameEvents.cs:232-250 | Source/Access/Events/_OptionButtonEvents.cs:222-240 | Source/Access/Events/_OptionButtonEvents.cs:243-261 | Source/Access/Events/_OptionButtonEvents.cs:264-282 | Source/Access/Events/_OptionButtonInOptionEvents.cs:117-135 | Source/Access/Events/_OptionButtonInOptionEvents.cs:138-156 | Source/Access/Events/_OptionButtonInOptionEvents.cs:159-177 | Source/Access/Events/_OptionGroupEvents.cs:175-193 | Source/Access/Events/_OptionGroupEvents.cs:196-214 | Source/Access/Events/_OptionGroupEvents.cs:217-235 | Source/Access/Events/_PageEvents.cs:105-123 | Source/Access/Events/_PageEvents.cs:126-144 | Source/Access/Events/_PageEvents.cs:147-165 | Source/Access/Events/_PageHdrFtrInReportEvents.cs:151-169 | Source/Access/Events/_PageHdrFtrInReportEvents.cs:172-190 | Source/Access/Events/_PageHdrFtrInReportEvents.cs:193-211 | Source/Access/Events/_PaletteButtonEvents.cs:222-240 | Source/Access/Events/_PaletteButtonEvents.cs:243-261 | Source/Access/Events/_PaletteButtonEvents.cs:264-282 | Source/Access/Events/_RectangleEvents.cs:105-123 | Source/Access/Events/_RectangleEvents.cs:126-144 | Source/Access/Events/_RectangleEvents.cs:147-165 | Source/Access/Events/_ReportEvents2.cs:362-380 | Source/Access/Events/_ReportEvents2.cs:383-401 | Source/Access/Events/_ReportEvents2.cs:404-422 | Source/Access/Events/_SectionEvents.cs:110-128 | Source/Access/Events/_SectionEvents.cs:131-149 | Source/Access/Events/_SectionEvents.cs:152-170 | Source/Access/Events/_SectionInReportEvents.cs:171-189 | Source/Access/Events/_SectionInReportEvents.cs:192-210 | Source/Access/Events/_SectionInReportEvents.cs:213-231 | Source/Access/Events/_TabControlEvents.cs:126-144 | Source/Access/Events/_TabControlEvents.cs:147-165 | Source/Access/Events/_TabControlEvents.cs:168-186 | Source/Access/Events/_TextBoxEvents.cs:244-262 | Source/Access/Events/_TextBoxEvents.cs:265-283 | Source/Access/Events/_TextBoxEvents.cs:286-304 | Source/Access/Events/_ToggleButtonEvents.cs:222-240 | Source/Access/Events/_ToggleButtonEvents.cs:243-261 | Source/Access/Events/_ToggleButtonEvents.cs:264-282 | Source/Access/Events/_ToggleButtonInOptionEvents.cs:117-135 | Source/Access/Events/_ToggleButtonInOptionEvents.cs:138-156 | Source/Access/Events/_ToggleButtonInOptionEvents.cs:159-177 — These 144 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 144 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 144 times.
D4 · Code Duplication · Members sharing a duplicated core (35 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (35 members, 50+ identical tokens) Source/Access/Events/DispAttachmentEvents.cs:341 — Source/Access/Events/DispAttachmentEvents.cs:341-353 | Source/Access/Events/DispBoundObjectFrameEvents.cs:322-334 | Source/Access/Events/DispCheckBoxEvents.cs:303-315 | Source/Access/Events/DispComboBoxEvents.cs:351-363 | Source/Access/Events/DispCommandButtonEvents.cs:266-278 | Source/Access/Events/DispListBoxEvents.cs:302-314 | Source/Access/Events/DispNavigationButtonEvents.cs:267-279 | Source/Access/Events/DispNavigationControlEvents.cs:327-339 | Source/Access/Events/DispOptionButtonEvents.cs:300-312 | Source/Access/Events/DispPaletteButtonEvents.cs:302-314 | Source/Access/Events/DispTabControlEvents.cs:206-218 | Source/Access/Events/DispTextBoxEvents.cs:327-339 | Source/Access/Events/DispToggleButtonEvents.cs:302-314 | Source/Access/Events/DispWebBrowserControlEvents.cs:380-392 | Source/Access/Events/_BoundObjectFrameEvents.cs:322-334 | Source/Access/Events/_CheckBoxEvents.cs:302-314 | Source/Access/Events/_CheckBoxInOptionEvents.cs:197-209 | Source/Access/Events/_ComboBoxEvents.cs:349-361 | Source/Access/Events/_CommandButtonEvents.cs:266-278 | Source/Access/Events/_FormEvents.cs:659-671 | Source/Access/Events/_FormEvents2.cs:635-647 | Source/Access/Events/_ListBoxEvents.cs:301-313 | Source/Access/Events/_OptionButtonEvents.cs:302-314 | Source/Access/Events/_OptionButtonInOptionEvents.cs:197-209 | Source/Access/Events/_PaletteButtonEvents.cs:302-314 | Source/Access/Events/_ReportEvents2.cs:442-454 | Source/Access/Events/_TabControlEvents.cs:206-218 | Source/Access/Events/_TextBoxEvents.cs:324-336 | Source/Access/Events/_ToggleButtonEvents.cs:302-314 | Source/Access/Events/_ToggleButtonInOptionEvents.cs:197-209 | Source/MSComctlLib/Events/DImageComboEvents.cs:184-196 | Source/MSComctlLib/Events/ISliderEvents.cs:171-183 | Source/MSComctlLib/Events/ITabStripEvents.cs:185-197 | Source/MSComctlLib/Events/ITreeViewEvents.cs:278-290 | Source/MSComctlLib/Events/ListViewEvents.cs:259-271 — These 35 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 35 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 35 times.
D4 · Code Duplication · Members sharing a duplicated core (32 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (32 members, 50+ identical tokens) Source/MSComctlLib/Events/DImageComboEvents.cs:199 — Source/MSComctlLib/Events/DImageComboEvents.cs:199-218 | Source/MSComctlLib/Events/DImageComboEvents.cs:238-257 | Source/MSComctlLib/Events/DImageComboEvents.cs:275-304 | Source/MSComctlLib/Events/DImageComboEvents.cs:307-334 | Source/MSComctlLib/Events/IProgressBarEvents.cs:189-208 | Source/MSComctlLib/Events/IProgressBarEvents.cs:228-247 | Source/MSComctlLib/Events/IProgressBarEvents.cs:265-294 | Source/MSComctlLib/Events/IProgressBarEvents.cs:297-324 | Source/MSComctlLib/Events/ISliderEvents.cs:285-304 | Source/MSComctlLib/Events/ISliderEvents.cs:324-343 | Source/MSComctlLib/Events/ISliderEvents.cs:361-390 | Source/MSComctlLib/Events/ISliderEvents.cs:393-420 | Source/MSComctlLib/Events/IStatusBarEvents.cs:242-261 | Source/MSComctlLib/Events/IStatusBarEvents.cs:281-300 | Source/MSComctlLib/Events/IStatusBarEvents.cs:318-347 | Source/MSComctlLib/Events/IStatusBarEvents.cs:350-377 | Source/MSComctlLib/Events/ITabStripEvents.cs:275-294 | Source/MSComctlLib/Events/ITabStripEvents.cs:314-333 | Source/MSComctlLib/Events/ITabStripEvents.cs:351-380 | Source/MSComctlLib/Events/ITabStripEvents.cs:383-410 | Source/MSComctlLib/Events/IToolbarEvents.cs:248-267 | Source/MSComctlLib/Events/IToolbarEvents.cs:287-306 | Source/MSComctlLib/Events/IToolbarEvents.cs:324-353 | Source/MSComctlLib/Events/IToolbarEvents.cs:356-383 | Source/MSComctlLib/Events/ITreeViewEvents.cs:388-407 | Source/MSComctlLib/Events/ITreeViewEvents.cs:427-446 | Source/MSComctlLib/Events/ITreeViewEvents.cs:464-493 | Source/MSComctlLib/Events/ITreeViewEvents.cs:496-523 | Source/MSComctlLib/Events/ListViewEvents.cs:356-375 | Source/MSComctlLib/Events/ListViewEvents.cs:395-414 | Source/MSComctlLib/Events/ListViewEvents.cs:432-461 | Source/MSComctlLib/Events/ListViewEvents.cs:464-491 — These 32 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 32 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 32 times.
D4 · Code Duplication · Members sharing a duplicated core (31 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (31 members, 50+ identical tokens) Source/Access/Events/DispAttachmentEvents.cs:172 — Source/Access/Events/DispAttachmentEvents.cs:172-184 | Source/Access/Events/DispBoundObjectFrameEvents.cs:179-191 | Source/Access/Events/DispCheckBoxEvents.cs:171-183 | Source/Access/Events/DispComboBoxEvents.cs:208-220 | Source/Access/Events/DispCommandButtonEvents.cs:134-146 | Source/Access/Events/DispCustomControlEvents.cs:94-106 | Source/Access/Events/DispListBoxEvents.cs:159-171 | Source/Access/Events/DispNavigationButtonEvents.cs:135-147 | Source/Access/Events/DispNavigationControlEvents.cs:184-196 | Source/Access/Events/DispObjectFrameEvents.cs:127-139 | Source/Access/Events/DispOptionButtonEvents.cs:168-180 | Source/Access/Events/DispOptionGroupEvents.cs:134-146 | Source/Access/Events/DispPaletteButtonEvents.cs:170-182 | Source/Access/Events/DispSubFormEvents.cs:66-78 | Source/Access/Events/DispSubReportEvents.cs:66-78 | Source/Access/Events/DispTextBoxEvents.cs:184-196 | Source/Access/Events/DispToggleButtonEvents.cs:170-182 | Source/Access/Events/DispWebBrowserControlEvents.cs:211-223 | Source/Access/Events/_BoundObjectFrameEvents.cs:179-191 | Source/Access/Events/_CheckBoxEvents.cs:170-182 | Source/Access/Events/_ComboBoxEvents.cs:206-218 | Source/Access/Events/_CommandButtonEvents.cs:134-146 | Source/Access/Events/_CustomControlEvents.cs:93-105 | Source/Access/Events/_ListBoxEvents.cs:158-170 | Source/Access/Events/_ObjectFrameEvents.cs:127-139 | Source/Access/Events/_OptionButtonEvents.cs:170-182 | Source/Access/Events/_OptionGroupEvents.cs:134-146 | Source/Access/Events/_PaletteButtonEvents.cs:170-182 | Source/Access/Events/_SubFormEvents.cs:66-78 | Source/Access/Events/_TextBoxEvents.cs:182-194 | Source/Access/Events/_ToggleButtonEvents.cs:170-182 — These 31 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 31 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 31 times.
D4 · Code Duplication · Members sharing a duplicated core (29 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (29 members, 50+ identical tokens) Source/OWC10/Events/IChartEvents.cs:274 — Source/OWC10/Events/IChartEvents.cs:274-289 | Source/OWC10/Events/IChartEvents.cs:292-307 | Source/OWC10/Events/IChartEvents.cs:310-323 | Source/OWC10/Events/IChartEvents.cs:429-442 | Source/OWC10/Events/IChartEvents.cs:445-458 | Source/OWC10/Events/IChartEvents.cs:461-474 | Source/OWC10/Events/IChartEvents.cs:477-490 | Source/OWC10/Events/IChartEvents.cs:509-526 | Source/OWC10/Events/IChartEvents.cs:529-544 | Source/OWC10/Events/IPivotControlEvents.cs:409-422 | Source/OWC10/Events/IPivotControlEvents.cs:425-438 | Source/OWC10/Events/IPivotControlEvents.cs:441-454 | Source/OWC10/Events/IPivotControlEvents.cs:457-470 | Source/OWC10/Events/IPivotControlEvents.cs:535-550 | Source/OWC10/Events/IPivotControlEvents.cs:553-568 | Source/OWC10/Events/IPivotControlEvents.cs:571-584 | Source/OWC10/Events/IPivotControlEvents.cs:587-604 | Source/OWC10/Events/IPivotControlEvents.cs:607-630 | Source/OWC10/Events/IPivotControlEvents.cs:633-650 | Source/OWC10/Events/ISpreadsheetEventSink.cs:226-243 | Source/OWC10/Events/ISpreadsheetEventSink.cs:246-261 | Source/OWC10/Events/ISpreadsheetEventSink.cs:264-279 | Source/OWC10/Events/ISpreadsheetEventSink.cs:282-295 | Source/OWC10/Events/ISpreadsheetEventSink.cs:309-322 | Source/OWC10/Events/ISpreadsheetEventSink.cs:325-338 | Source/OWC10/Events/ISpreadsheetEventSink.cs:341-354 | Source/OWC10/Events/ISpreadsheetEventSink.cs:357-370 | Source/OWC10/Events/ISpreadsheetEventSink.cs:400-417 | Source/OWC10/Events/ISpreadsheetEventSink.cs:699-716 — These 29 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 29 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 29 times.
D4 · Code Duplication · Members sharing a duplicated core (26 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (26 members, 50+ identical tokens) Source/Access/DispatchInterfaces/_Attachment.cs:2452 — Source/Access/DispatchInterfaces/_Attachment.cs:2452-2464 | Source/Access/DispatchInterfaces/_BoundObjectFrame.cs:2300-2312 | Source/Access/DispatchInterfaces/_Checkbox.cs:1983-1995 | Source/Access/DispatchInterfaces/_Combobox.cs:3371-3383 | Source/Access/DispatchInterfaces/_CommandButton.cs:2729-2741 | Source/Access/DispatchInterfaces/_Control.cs:827-839 | Source/Access/DispatchInterfaces/_CustomControl.cs:1544-1556 | Source/Access/DispatchInterfaces/_EmptyCell.cs:975-987 | Source/Access/DispatchInterfaces/_Form.cs:3118-3130 | Source/Access/DispatchInterfaces/_Image.cs:1575-1587 | Source/Access/DispatchInterfaces/_ListBox.cs:2753-2765 | Source/Access/DispatchInterfaces/_NavigationButton.cs:2717-2729 | Source/Access/DispatchInterfaces/_NavigationControl.cs:1893-1905 | Source/Access/DispatchInterfaces/_ObjectFrame.cs:2174-2186 | Source/Access/DispatchInterfaces/_OptionButton.cs:1973-1985 | Source/Access/DispatchInterfaces/_OptionGroup.cs:1522-1534 | Source/Access/DispatchInterfaces/_Page.cs:803-815 | Source/Access/DispatchInterfaces/_PageBreak.cs:392-404 | Source/Access/DispatchInterfaces/_PaletteButton.cs:1415-1427 | Source/Access/DispatchInterfaces/_Rectangle.cs:914-926 | Source/Access/DispatchInterfaces/_Report.cs:2039-2051 | Source/Access/DispatchInterfaces/_SubForm.cs:1362-1374 | Source/Access/DispatchInterfaces/_TabControl.cs:2089-2101 | Source/Access/DispatchInterfaces/_Textbox.cs:3105-3117 | Source/Access/DispatchInterfaces/_ToggleButton.cs:2759-2771 | Source/Access/DispatchInterfaces/_WebBrowserControl.cs:1676-1688 — These 26 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 26 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 26 times.
D4 · Code Duplication · Members sharing a duplicated core (19 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (19 members, 50+ identical tokens) Source/ADODB/Events/ConnectionEvents.cs:118 — Source/ADODB/Events/ConnectionEvents.cs:118-133 | Source/ADODB/Events/ConnectionEvents.cs:136-153 | Source/ADODB/Events/ConnectionEvents.cs:156-171 | Source/ADODB/Events/ConnectionEvents.cs:174-189 | Source/ADODB/Events/ConnectionEvents.cs:192-218 | Source/ADODB/Events/ConnectionEvents.cs:221-242 | Source/ADODB/Events/ConnectionEvents.cs:245-267 | Source/ADODB/Events/ConnectionEvents.cs:270-285 | Source/ADODB/Events/ConnectionEvents.cs:288-301 | Source/ADODB/Events/RecordsetEvents.cs:130-148 | Source/ADODB/Events/RecordsetEvents.cs:151-170 | Source/ADODB/Events/RecordsetEvents.cs:173-190 | Source/ADODB/Events/RecordsetEvents.cs:193-212 | Source/ADODB/Events/RecordsetEvents.cs:215-230 | Source/ADODB/Events/RecordsetEvents.cs:233-251 | Source/ADODB/Events/RecordsetEvents.cs:254-269 | Source/ADODB/Events/RecordsetEvents.cs:272-289 | Source/ADODB/Events/RecordsetEvents.cs:311-328 | Source/ADODB/Events/RecordsetEvents.cs:331-346 — These 19 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 19 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 19 times.
D4 · Code Duplication · Members sharing a duplicated core (16 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (16 members, 50+ identical tokens) Source/Word/Events/ApplicationEvents2.cs:162 — Source/Word/Events/ApplicationEvents2.cs:162-176 | Source/Word/Events/ApplicationEvents2.cs:179-193 | Source/Word/Events/ApplicationEvents2.cs:196-212 | Source/Word/Events/ApplicationEvents3.cs:227-241 | Source/Word/Events/ApplicationEvents3.cs:244-258 | Source/Word/Events/ApplicationEvents3.cs:261-277 | Source/Word/Events/ApplicationEvents3.cs:453-467 | Source/Word/Events/ApplicationEvents3.cs:484-498 | Source/Word/Events/ApplicationEvents3.cs:515-533 | Source/Word/Events/ApplicationEvents4.cs:300-314 | Source/Word/Events/ApplicationEvents4.cs:317-331 | Source/Word/Events/ApplicationEvents4.cs:334-350 | Source/Word/Events/ApplicationEvents4.cs:526-540 | Source/Word/Events/ApplicationEvents4.cs:557-571 | Source/Word/Events/ApplicationEvents4.cs:588-606 | Source/Word/Events/ApplicationEvents4.cs:711-725 — These 16 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 16 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 16 times.
D4 · Code Duplication · Edited copy of a member (91 corresponding lines) · ×1
  • Edited copy of a member (91 corresponding lines) Source/Office/Tools/COMAddin.cs:536 — Source/Office/Tools/COMAddin.cs:536-626 | Source/Office/Tools/CustomTaskPaneHandler.cs:74-176 — These two members are one piece of code written twice and then edited apart: 91 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (41 corresponding lines) · ×1
  • Edited copy of a member (41 corresponding lines) Source/NetOffice/COMObject.cs:1331 — Source/NetOffice/COMObject.cs:1331-1371 | Source/NetOffice/Core.cs:1267-1307 — These two members are one piece of code written twice and then edited apart: 41 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 42+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 42+ corresponding lines) BuildTools/VersionUpdater/Form1.cs:111 — BuildTools/VersionUpdater/Form1.cs:111-152 | BuildTools/VersionUpdater/Form1.cs:155-196 | BuildTools/VersionUpdater/Form1.cs:263-306 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 42 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (35 corresponding lines) · ×1
  • Edited copy of a member (35 corresponding lines) Source/NetOffice/Core.cs:845 — Source/NetOffice/Core.cs:845-886 | Source/NetOffice/Core.cs:897-931 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 37+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 37+ corresponding lines) RegAddin/RegAddin/RegFile/RegFileOperationHandler.cs:16 — RegAddin/RegAddin/RegFile/RegFileOperationHandler.cs:16-52 | RegAddin/RegAddin/Register/RegisterOperationHandler.cs:16-53 | RegAddin/RegAddin/Unregister/UnregisterOperationHandler.cs:16-56 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 37 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (30 corresponding lines) · ×1
  • Edited copy of a member (30 corresponding lines) Source/NetOffice/Extensions/EnumerableExtensions.cs:558 — Source/NetOffice/Extensions/EnumerableExtensions.cs:558-590 | Source/NetOffice/Extensions/EnumerableExtensions.cs:603-632 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (33 corresponding lines) · ×1
  • Edited copy of a member (33 corresponding lines) Source/Office.Extensions/Dialogs/RichTextDialog.cs:49 — Source/Office.Extensions/Dialogs/RichTextDialog.cs:49-81 | Source/Office.Extensions/Dialogs/RichTextDialog.cs:110-151 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 36+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 36+ corresponding lines) Source/NetOffice/Running/ChildWindowBatchEnumerator.cs:117 — Source/NetOffice/Running/ChildWindowBatchEnumerator.cs:117-156 | Source/NetOffice/Running/ChildWindowEnumerator.cs:79-114 | Source/NetOffice/Running/WindowEnumerator.cs:185-220 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 36 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (38 corresponding lines) · ×1
  • Edited copy of a member (38 corresponding lines) Source/Word/Tools/Contribution/ApplicationUtils.cs:115 — Source/Word/Tools/Contribution/ApplicationUtils.cs:115-152 | Source/PowerPoint/Tools/Contribution/ApplicationUtils.cs:103-147 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 16+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 16+ corresponding lines) Source/Excel/Events/AppEvents.cs:906 — Source/Excel/Events/AppEvents.cs:906-923 | Source/Excel/Events/DocEvents.cs:276-294 | Source/Excel/Events/DocEvents.cs:297-315 | Source/Excel/Events/DocEvents.cs:318-333 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (25 corresponding lines) · ×1
  • Edited copy of a member (25 corresponding lines) Toolbox/Toolbox/ToolboxControls/OfficeUI/OfficeUIControl.cs:319 — Toolbox/Toolbox/ToolboxControls/OfficeUI/OfficeUIControl.cs:319-343 | Toolbox/Toolbox/ToolboxControls/OfficeUI/OfficeUIControl.cs:346-377 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 19+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 19+ corresponding lines) Source/Access/Tools/COMAddin.cs:482 — Source/Access/Tools/COMAddin.cs:482-500 | Source/Excel/Tools/COMAddin.cs:481-499 | Source/Outlook/Tools/COMAddin.cs:523-541 | Source/PowerPoint/Tools/COMAddin.cs:483-501 | Source/Word/Tools/COMAddin.cs:484-502 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (28 corresponding lines) · ×1
  • Edited copy of a member (28 corresponding lines) Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectWizardControl.cs:488 — Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectWizardControl.cs:488-515 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectWizardControl.cs:518-550 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 23+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 23+ corresponding lines) Source/Word/Tools/COMAddin.cs:1056 — Source/Word/Tools/COMAddin.cs:1056-1078 | Source/Word/Tools/COMAddin.cs:1081-1104 | Source/Word/Tools/DocumentInspectorBase.cs:243-265 | Source/Word/Tools/DocumentInspectorBase.cs:268-291 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (7 members, 11+ corresponding lines) · ×1
  • Edited copies of one member (7 members, 11+ corresponding lines) Source/OWC10/Interfaces/IEnumOleUndoUnits.cs:162 — Source/OWC10/Interfaces/IEnumOleUndoUnits.cs:162-172 | Source/OWC10/Interfaces/IOleUndoManager.cs:197-207 | Source/OWC10/Interfaces/IOleUndoManager.cs:215-225 | Source/Office/Interfaces/IConverter.cs:125-135 | Source/Office/Interfaces/IConverter.cs:159-169 | Source/Office/Interfaces/IConverter.cs:183-193 | Source/Office/Interfaces/IConverter.cs:206-218 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 20+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 20+ corresponding lines) Source/Access/Tools/COMAddin.cs:762 — Source/Access/Tools/COMAddin.cs:762-782 | Source/Excel/Tools/COMAddin.cs:764-783 | Source/Outlook/Tools/COMAddin.cs:1000-1020 | Source/PowerPoint/Tools/COMAddin.cs:763-783 | Source/Word/Tools/COMAddin.cs:902-922 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (7 members, 22+ corresponding lines) · ×1
  • Edited copies of one member (7 members, 22+ corresponding lines) Source/NetOffice/Extensions/EnumerableExtensions.cs:27 — Source/NetOffice/Extensions/EnumerableExtensions.cs:27-48 | Source/NetOffice/Extensions/EnumerableExtensions.cs:107-130 | Source/NetOffice/Extensions/EnumerableExtensions.cs:143-171 | Source/NetOffice/Extensions/EnumerableExtensions.cs:371-394 | Source/NetOffice/Extensions/EnumerableExtensions.cs:407-431 | Source/NetOffice/Extensions/EnumerableExtensions.cs:482-507 | Source/NetOffice/Extensions/EnumerableExtensions.cs:520-545 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 12+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 12+ corresponding lines) Source/Word/Events/DocumentEvents2.cs:201 — Source/Word/Events/DocumentEvents2.cs:201-214 | Source/Word/Events/DocumentEvents2.cs:217-230 | Source/Word/Events/DocumentEvents2.cs:233-247 | Source/Word/Events/DocumentEvents2.cs:250-261 | Source/Word/Events/DocumentEvents2.cs:264-278 | Source/Word/Events/DocumentEvents2.cs:281-295 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 10+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 10+ corresponding lines) Source/Word/DispatchInterfaces/ConnectorFormat.cs:257 — Source/Word/DispatchInterfaces/ConnectorFormat.cs:257-266 | Source/Word/DispatchInterfaces/ConnectorFormat.cs:284-293 | Source/Word/DispatchInterfaces/DiagramNode.cs:285-294 | Source/Word/DispatchInterfaces/DiagramNode.cs:302-311 | Source/Word/DispatchInterfaces/DiagramNode.cs:320-329 | Source/Word/DispatchInterfaces/DiagramNode.cs:338-347 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (7 members, 20+ corresponding lines) · ×1
  • Edited copies of one member (7 members, 20+ corresponding lines) Source/NetOffice/COMObject.cs:247 — Source/NetOffice/COMObject.cs:247-267 | Source/NetOffice/COMObject.cs:299-320 | Source/NetOffice/COMObject.cs:330-349 | Source/NetOffice/COMObject.cs:360-380 | Source/NetOffice/COMObject.cs:392-413 | Source/NetOffice/COMObject.cs:424-447 | Source/NetOffice/COMObject.cs:457-481 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 19+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 19+ corresponding lines) Source/Outlook/Tools/COMAddin.cs:1168 — Source/Outlook/Tools/COMAddin.cs:1168-1186 | Source/Outlook/Tools/COMAddin.cs:1189-1207 | Source/Outlook/Tools/COMAddin.cs:1210-1229 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 13+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 13+ corresponding lines) Source/NetOffice/Tools/AttributeReflector.cs:44 — Source/NetOffice/Tools/AttributeReflector.cs:44-56 | Source/NetOffice/Tools/AttributeReflector.cs:66-78 | Source/NetOffice/Tools/AttributeReflector.cs:88-100 | Source/NetOffice/Tools/AttributeReflector.cs:110-122 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 11+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 11+ corresponding lines) Source/NetOffice/COMObject.cs:1419 — Source/NetOffice/COMObject.cs:1419-1429 | Source/NetOffice/COMObject.cs:1438-1448 | Source/NetOffice/COMObject.cs:1457-1473 | Source/NetOffice/COMObject.cs:1482-1492 | Source/NetOffice/COMObject.cs:1501-1511 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 18+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 18+ corresponding lines) Source/NetOffice/Events/CoClassEventReflector.cs:45 — Source/NetOffice/Events/CoClassEventReflector.cs:45-62 | Source/NetOffice/Events/CoClassEventReflector.cs:72-89 | Source/NetOffice/Events/CoClassEventReflector.cs:99-116 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (7 members, 7+ corresponding lines) · ×1
  • Edited copies of one member (7 members, 7+ corresponding lines) Source/OWC10/DispatchInterfaces/IXRangeEnum.cs:233 — Source/OWC10/DispatchInterfaces/IXRangeEnum.cs:233-239 | Source/OWC10/Interfaces/FieldListHierarchySite.cs:125-132 | Source/OWC10/Interfaces/FieldListHierarchySite.cs:156-163 | Source/OWC10/Interfaces/FieldListHierarchySite.cs:232-239 | Source/OWC10/Interfaces/FieldListHierarchySite.cs:307-314 | Source/Office/Interfaces/IConverterUICallback.cs:137-144 | Source/PowerPoint/DispatchInterfaces/_Presentation.cs:2008-2014 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (7 members, 8+ corresponding lines) · ×1
  • Edited copies of one member (7 members, 8+ corresponding lines) Source/Access/DispatchInterfaces/Module.cs:291 — Source/Access/DispatchInterfaces/Module.cs:291-298 | Source/OWC10/Interfaces/IOleUndoUnit.cs:147-156 | Source/Office/DispatchInterfaces/IAccessible.cs:556-563 | Source/Office/DispatchInterfaces/_CommandBars.cs:268-275 | Source/Office/DispatchInterfaces/_CommandBars.cs:298-305 | Source/Office/Interfaces/IDocumentInspector.cs:124-133 | Source/VBIDE/DispatchInterfaces/_CodeModule.cs:276-283 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 6+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 6+ corresponding lines) Source/DAO/Modules/Global.cs:590 — Source/DAO/Modules/Global.cs:590-595 | Source/DAO/Modules/Global.cs:604-609 | Source/DAO/Modules/Global.cs:619-624 | Source/DAO/Modules/Global.cs:635-640 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (17 corresponding lines) · ×1
  • Edited copy of a member (17 corresponding lines) Toolbox/Toolbox/Controls/Hex/HexBox.cs:580 — Toolbox/Toolbox/Controls/Hex/HexBox.cs:580-596 | Toolbox/Toolbox/Controls/Hex/HexBox.cs:599-615 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 6+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 6+ corresponding lines) Source/DAO/Modules/Global.cs:363 — Source/DAO/Modules/Global.cs:363-368 | Source/DAO/Modules/Global.cs:377-382 | Source/DAO/Modules/Global.cs:392-397 | Source/DAO/Modules/Global.cs:408-413 | Source/DAO/Modules/Global.cs:423-428 | Source/DAO/Modules/Global.cs:438-443 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 15+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 15+ corresponding lines) Toolbox/Toolbox/ToolboxControls/ControlContainer.cs:200 — Toolbox/Toolbox/ToolboxControls/ControlContainer.cs:200-215 | Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/OfficeCompatibilityControl.cs:236-252 | Toolbox/Toolbox/ToolboxControls/OfficeUI/OfficeUIControl.cs:228-242 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 7+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 7+ corresponding lines) Source/OWC10/DispatchInterfaces/IDataSourceControl.cs:1270 — Source/OWC10/DispatchInterfaces/IDataSourceControl.cs:1270-1276 | Source/Office/DispatchInterfaces/DocumentInspector.cs:167-175 | Source/Office/DispatchInterfaces/DocumentInspector.cs:185-193 | Source/Office/DispatchInterfaces/IBlogPictureExtensibility.cs:124-132 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 13+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 13+ corresponding lines) Source/Access/Tools/COMAddin.cs:282 — Source/Access/Tools/COMAddin.cs:282-295 | Source/Excel/Tools/COMAddin.cs:282-295 | Source/Outlook/Tools/COMAddin.cs:292-305 | Source/PowerPoint/Tools/COMAddin.cs:283-296 | Source/VBIDE/Tools/COMAddin.cs:249-261 | Source/Word/Tools/COMAddin.cs:285-298 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 8+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 8+ corresponding lines) Source/Access/Tools/COMAddin.cs:147 — Source/Access/Tools/COMAddin.cs:147-154 | Source/Excel/Tools/COMAddin.cs:147-154 | Source/Office/Tools/COMAddin.cs:267-274 | Source/Outlook/Tools/COMAddin.cs:278-285 | Source/PowerPoint/Tools/COMAddin.cs:148-155 | Source/Word/Tools/COMAddin.cs:150-157 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 7+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 7+ corresponding lines) Source/Access/Tools/COMAddin.cs:54 — Source/Access/Tools/COMAddin.cs:54-60 | Source/Excel/Tools/COMAddin.cs:54-60 | Source/Office/Tools/COMAddin.cs:53-59 | Source/Outlook/Tools/COMAddin.cs:61-68 | Source/PowerPoint/Tools/COMAddin.cs:55-61 | Source/Word/Tools/COMAddin.cs:57-63 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (6 corresponding lines) · ×1
  • Edited copy of a member (6 corresponding lines) Toolbox/Toolbox/ToolboxControls/RegistryEditor/ChangeBinaryControl.cs:101 — Toolbox/Toolbox/ToolboxControls/RegistryEditor/ChangeBinaryControl.cs:101-106 | Toolbox/Toolbox/Utils/Registry/UtilsRegistryEntry.cs:181-186 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 5+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 5+ corresponding lines) Source/ADODB/DispatchInterfaces/Fields.cs:277 — Source/ADODB/DispatchInterfaces/Fields.cs:277-281 | Source/ADODB/DispatchInterfaces/Fields_Deprecated.cs:268-272 | Source/ADODB/DispatchInterfaces/Parameters.cs:156-160 | Source/ADODB/DispatchInterfaces/Parameters_Deprecated.cs:177-181 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (8 members, 3+ corresponding lines) · ×1
  • Edited copies of one member (8 members, 3+ corresponding lines) Source/Outlook/DispatchInterfaces/View.cs:324 — Source/Outlook/DispatchInterfaces/View.cs:324-326 | Source/Outlook/DispatchInterfaces/_BusinessCardView.cs:369-371 | Source/Outlook/DispatchInterfaces/_CalendarView.cs:562-564 | Source/Outlook/DispatchInterfaces/_CardView.cs:465-467 | Source/Outlook/DispatchInterfaces/_IconView.cs:373-375 | Source/Outlook/DispatchInterfaces/_PeopleView.cs:337-339 | Source/Outlook/DispatchInterfaces/_TableView.cs:744-746 | Source/Outlook/DispatchInterfaces/_TimelineView.cs:505-507 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (67 lines × 2) · ×1
  • Duplicated block (67 lines × 2) Source/Office/Tools/COMAddin.cs:93 — Source/Office/Tools/COMAddin.cs:93-159 | Source/Outlook/Tools/COMAddin.cs:102-170 — before extracting anything, compare `Source/Office/Tools/COMAddin.cs` and `Source/Outlook/Tools/COMAddin.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 275 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (56 lines × 3) · ×1
  • Duplicated block (56 lines × 3) Source/Word/Events/ApplicationEvents2.cs:32 — Source/Word/Events/ApplicationEvents2.cs:32-87 | Source/Word/Events/ApplicationEvents3.cs:32-87 | Source/Word/Events/ApplicationEvents4.cs:32-87 — before extracting anything, compare `Source/Word/Events/ApplicationEvents2.cs` and `Source/Word/Events/ApplicationEvents3.cs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 270 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (52 lines × 5) · ×1
  • Duplicated block (52 lines × 5) Source/Access/Tools/COMAddin.cs:348 — Source/Access/Tools/COMAddin.cs:348-399 | Source/Office/Tools/COMAddin.cs:353-404 | Source/Outlook/Tools/COMAddin.cs:381-432 | Source/PowerPoint/Tools/COMAddin.cs:349-400 | Source/Word/Tools/COMAddin.cs:350-401 — before extracting anything, compare `Source/Access/Tools/COMAddin.cs` and `Source/Office/Tools/COMAddin.cs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 287 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Source/Access/Tools/COMAddin.cs:348` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (43 lines × 8) · ×1
  • Duplicated block (43 lines × 8) Source/MSComctlLib/Events/DImageComboEvents.cs:48 — Source/MSComctlLib/Events/DImageComboEvents.cs:48-90 | Source/MSComctlLib/Events/IProgressBarEvents.cs:47-89 | Source/MSComctlLib/Events/ISliderEvents.cs:72-114 | Source/MSComctlLib/Events/IStatusBarEvents.cs:61-103 | Source/MSComctlLib/Events/ITabStripEvents.cs:69-111 | Source/MSComctlLib/Events/IToolbarEvents.cs:60-102 | Source/MSComctlLib/Events/ITreeViewEvents.cs:99-141 | Source/MSComctlLib/Events/ListViewEvents.cs:89-131 — before extracting anything, compare `Source/MSComctlLib/Events/DImageComboEvents.cs` and `Source/MSComctlLib/Events/IProgressBarEvents.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 157 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/MSComctlLib/Events/IStatusBarEvents.cs:57` calls `SupportByVersion`, `MethodImpl`, `DispId` and `Source/MSComctlLib/Events/IProgressBarEvents.cs:45` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (36 lines × 2) · ×1
  • Duplicated block (36 lines × 2) Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsMultiAddinConverterCS.cs:160 — Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsMultiAddinConverterCS.cs:160-195 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsSingleAddinConverterCS.cs:157-192 — before extracting anything, compare `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsMultiAddinConverterCS.cs` and `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsSingleAddinConverterCS.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 112 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsMultiAddinConverterCS.cs:160` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (34 lines × 3) · ×1
  • Duplicated block (34 lines × 3) Source/Access/Tools/COMAddin.cs:76 — Source/Access/Tools/COMAddin.cs:76-109 | Source/Excel/Tools/COMAddin.cs:76-109 | Source/Word/Tools/COMAddin.cs:79-112 — before extracting anything, compare `Source/Access/Tools/COMAddin.cs` and `Source/Excel/Tools/COMAddin.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 284 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (31–35 lines × 2) · ×1
  • Duplicated block (31–35 lines × 2) Source/Outlook/Events/ExplorerEvents_10.cs:40 — Source/Outlook/Events/ExplorerEvents_10.cs:40-74 | Source/Outlook/Events/InspectorEvents_10.cs:21-51 — before extracting anything, compare `Source/Outlook/Events/ExplorerEvents_10.cs` and `Source/Outlook/Events/InspectorEvents_10.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 130 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (32–33 lines × 3) · ×1
  • Duplicated block (32–33 lines × 3) Source/NetOffice/Running/ChildWindowBatchEnumerator.cs:124 — Source/NetOffice/Running/ChildWindowBatchEnumerator.cs:124-156 | Source/NetOffice/Running/ChildWindowEnumerator.cs:83-114 | Source/NetOffice/Running/WindowEnumerator.cs:189-220 — before extracting anything, compare `Source/NetOffice/Running/ChildWindowBatchEnumerator.cs` and `Source/NetOffice/Running/ChildWindowEnumerator.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Source/NetOffice/Running/ChildWindowBatchEnumerator.cs:124` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (31–33 lines × 2) · ×1
  • Duplicated block (31–33 lines × 2) Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/Converter.cs:286 — Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/Converter.cs:286-316 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/Converter.cs:323-355 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (32 lines × 2) · ×1
  • Duplicated block (32 lines × 2) Source/NetOffice/Running/RunningObjectTable.cs:423 — Source/NetOffice/Running/RunningObjectTable.cs:423-454 | Source/NetOffice/Running/RunningObjectTable.cs:509-540 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/NetOffice/Running/RunningObjectTable.cs:509` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (30 lines × 7) · ×1
  • Duplicated block (30 lines × 7) REDACTED:157 — REDACTED:157-186 | REDACTED:388-417 | REDACTED:633-662 | REDACTED:878-907 | REDACTED:1123-1152 | REDACTED:1368-1397 | REDACTED:1618-1647 — all 7 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:157` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (30 lines × 2) · ×1
  • Duplicated block (30 lines × 2) Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleMultiAddinConverterCS.cs:139 — Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleMultiAddinConverterCS.cs:139-168 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleSingleAddinConverterCS.cs:125-154 — before extracting anything, compare `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleMultiAddinConverterCS.cs` and `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleSingleAddinConverterCS.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 129 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleMultiAddinConverterCS.cs:139` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (29 lines × 11) · ×1
  • Duplicated block (29 lines × 11) Source/Outlook/Events/OlkCategoryEvents.cs:49 — Source/Outlook/Events/OlkCategoryEvents.cs:49-77 | Source/Outlook/Events/OlkCheckBoxEvents.cs:49-77 | Source/Outlook/Events/OlkComboBoxEvents.cs:49-77 | Source/Outlook/Events/OlkCommandButtonEvents.cs:49-77 | Source/Outlook/Events/OlkContactPhotoEvents.cs:49-77 | Source/Outlook/Events/OlkDateControlEvents.cs:49-77 | Source/Outlook/Events/OlkListBoxEvents.cs:49-77 | Source/Outlook/Events/OlkOptionButtonEvents.cs:49-77 | Source/Outlook/Events/OlkTextBoxEvents.cs:49-77 | Source/Outlook/Events/OlkTimeControlEvents.cs:49-77 | Source/Outlook/Events/OlkTimeZoneControlEvents.cs:49-77 — before extracting anything, compare `Source/Outlook/Events/OlkCategoryEvents.cs` and `Source/Outlook/Events/OlkCheckBoxEvents.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 160 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Source/Outlook/Events/OlkCheckBoxEvents.cs:78` calls `MethodImpl`, `DispId`, `Change` and `Source/Outlook/Events/OlkCommandButtonEvents.cs:78` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (27–30 lines × 5) · ×1
  • Duplicated block (27–30 lines × 5) Source/Access/Classes/Hyperlink.cs:76 — Source/Access/Classes/Hyperlink.cs:76-105 | Source/Excel/DispatchInterfaces/Hyperlink.cs:68-94 | Source/OWC10/DispatchInterfaces/Hyperlink.cs:67-93 | Source/PowerPoint/DispatchInterfaces/Hyperlink.cs:68-94 | Source/Word/DispatchInterfaces/Hyperlink.cs:68-94 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times.
D4 · Code Duplication · Duplicated block (28–29 lines × 2) · ×1
  • Duplicated block (28–29 lines × 2) Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsMultiAddinConverterVB.cs:141 — Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsMultiAddinConverterVB.cs:141-169 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsSingleAddinConverterVB.cs:127-154 — before extracting anything, compare `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsMultiAddinConverterVB.cs` and `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsSingleAddinConverterVB.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 180 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsMultiAddinConverterVB.cs:141` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (27 lines × 2) · ×1
  • Duplicated block (27 lines × 2) Source/MSComctlLib/Events/ISliderEvents.cs:19 — Source/MSComctlLib/Events/ISliderEvents.cs:19-45 | Source/MSComctlLib/Events/ITabStripEvents.cs:19-45 — before extracting anything, compare `Source/MSComctlLib/Events/ISliderEvents.cs` and `Source/MSComctlLib/Events/ITabStripEvents.cs` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 295 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (27 lines × 5) · ×1
  • Duplicated block (27 lines × 5) Source/Access/Tools/Contribution/CommonUtils.cs:48 — Source/Access/Tools/Contribution/CommonUtils.cs:48-74 | Source/Excel/Tools/Contribution/CommonUtils.cs:47-73 | Source/Outlook/Tools/Contribution/CommonUtils.cs:52-78 | Source/PowerPoint/Tools/Contribution/CommonUtils.cs:48-74 | Source/Word/Tools/Contribution/CommonUtils.cs:48-74 — before extracting anything, compare `Source/Access/Tools/Contribution/CommonUtils.cs` and `Source/Excel/Tools/Contribution/CommonUtils.cs` as WHOLE FILES: 86% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (26 lines × 4) · ×1
  • Duplicated block (26 lines × 4) Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleMultiAddinConverterCS.cs:112 — Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleMultiAddinConverterCS.cs:112-137 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleMultiAddinConverterVB.cs:120-145 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleSingleAddinConverterCS.cs:98-123 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleSingleAddinConverterVB.cs:108-133 — before extracting anything, compare `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleMultiAddinConverterCS.cs` and `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleMultiAddinConverterVB.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 85 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleMultiAddinConverterCS.cs:112` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (22 lines × 4) · ×1
  • Duplicated block (22 lines × 4) Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleMultiAddinConverterVB.cs:13 — Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleMultiAddinConverterVB.cs:13-34 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleSingleAddinConverterVB.cs:13-34 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsMultiAddinConverterVB.cs:13-34 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsSingleAddinConverterVB.cs:13-34 — before extracting anything, compare `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleMultiAddinConverterVB.cs` and `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleSingleAddinConverterVB.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 151 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (26 lines × 2) · ×1
  • Duplicated block (26 lines × 2) Source/NetOffice/Trace/DebugConsole.cs:366 — Source/NetOffice/Trace/DebugConsole.cs:366-391 | Source/NetOffice/Trace/DebugConsole.cs:413-438 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/NetOffice/Trace/DebugConsole.cs:366` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (22–25 lines × 2) · ×1
  • Duplicated block (22–25 lines × 2) Source/NetOffice/Invoker.cs:879 — Source/NetOffice/Invoker.cs:879-903 | Source/NetOffice/Invoker.cs:914-935 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (22 lines × 15) · ×1
  • Duplicated block (22 lines × 15) Source/Outlook/Classes/AppointmentItem.cs:767 — Source/Outlook/Classes/AppointmentItem.cs:767-788 | Source/Outlook/Classes/ContactItem.cs:769-790 | Source/Outlook/Classes/DistListItem.cs:769-790 | Source/Outlook/Classes/DocumentItem.cs:769-790 | Source/Outlook/Classes/JournalItem.cs:769-790 | Source/Outlook/Classes/MailItem.cs:769-790 | Source/Outlook/Classes/MeetingItem.cs:769-790 | Source/Outlook/Classes/PostItem.cs:769-790 | Source/Outlook/Classes/RemoteItem.cs:769-790 | Source/Outlook/Classes/ReportItem.cs:769-790 | Source/Outlook/Classes/TaskItem.cs:769-790 | Source/Outlook/Classes/TaskRequestAcceptItem.cs:769-790 | Source/Outlook/Classes/TaskRequestDeclineItem.cs:769-790 | Source/Outlook/Classes/TaskRequestItem.cs:769-790 | Source/Outlook/Classes/TaskRequestUpdateItem.cs:769-790 — before extracting anything, compare `Source/Outlook/Classes/ContactItem.cs` and `Source/Outlook/Classes/DistListItem.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (22–23 lines × 6) · ×1
  • Duplicated block (22–23 lines × 6) Source/Access/Tools/COMAddin.cs:321 — Source/Access/Tools/COMAddin.cs:321-343 | Source/Excel/Tools/COMAddin.cs:321-342 | Source/Office/Tools/COMAddin.cs:326-348 | Source/Outlook/Tools/COMAddin.cs:331-352 | Source/PowerPoint/Tools/COMAddin.cs:322-344 | Source/Word/Tools/COMAddin.cs:324-345 — before extracting anything, compare `Source/Access/Tools/COMAddin.cs` and `Source/Excel/Tools/COMAddin.cs` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 284 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Source/Access/Tools/COMAddin.cs:321` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (22 lines × 6) · ×1
  • Duplicated block (22 lines × 6) REDACTED:59 — REDACTED:59-80 | REDACTED:59-80 | REDACTED:62-83 | REDACTED:61-82 | REDACTED:60-81 | Toolbox/Toolbox/Translator.cs:76-97 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 106 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:59` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (21 lines × 8) · ×1
  • Duplicated block (21 lines × 8) Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleMultiAddinConverterCS.cs:63 — Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleMultiAddinConverterCS.cs:63-83 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleMultiAddinConverterVB.cs:73-93 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleSingleAddinConverterCS.cs:63-83 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleSingleAddinConverterVB.cs:73-93 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsMultiAddinConverterCS.cs:63-83 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsMultiAddinConverterVB.cs:73-93 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsSingleAddinConverterCS.cs:63-83 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsSingleAddinConverterVB.cs:73-93 — before extracting anything, compare `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleMultiAddinConverterCS.cs` and `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleMultiAddinConverterVB.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 85 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (19 lines × 21) · ×1
  • Duplicated block (19 lines × 21) REDACTED:208 — REDACTED:208-226 | REDACTED:237-255 | REDACTED:266-284 | REDACTED:439-457 | REDACTED:468-486 | REDACTED:497-515 | REDACTED:684-702 | REDACTED:713-731 | REDACTED:742-760 | REDACTED:929-947 | REDACTED:958-976 | REDACTED:987-1005 | REDACTED:1174-1192 | REDACTED:1203-1221 | REDACTED:1232-1250 | REDACTED:1419-1437 | REDACTED:1448-1466 | REDACTED:1477-1495 | REDACTED:1669-1687 | REDACTED:1698-1716 | REDACTED:1727-1745 — all 21 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:208` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (19 lines × 8) · ×1
  • Duplicated block (19 lines × 8) Source/MSComctlLib/Events/DImageComboEvents.cs:200 — Source/MSComctlLib/Events/DImageComboEvents.cs:200-218 | Source/MSComctlLib/Events/IProgressBarEvents.cs:190-208 | Source/MSComctlLib/Events/ISliderEvents.cs:286-304 | Source/MSComctlLib/Events/IStatusBarEvents.cs:243-261 | Source/MSComctlLib/Events/ITabStripEvents.cs:276-294 | Source/MSComctlLib/Events/IToolbarEvents.cs:249-267 | Source/MSComctlLib/Events/ITreeViewEvents.cs:389-407 | Source/MSComctlLib/Events/ListViewEvents.cs:357-375 — before extracting anything, compare `Source/MSComctlLib/Events/DImageComboEvents.cs` and `Source/MSComctlLib/Events/IProgressBarEvents.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 157 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (13 lines × 8) · ×1
  • Duplicated block (13 lines × 8) Source/MSComctlLib/Events/DImageComboEvents.cs:314 — Source/MSComctlLib/Events/DImageComboEvents.cs:314-326 | Source/MSComctlLib/Events/IProgressBarEvents.cs:304-316 | Source/MSComctlLib/Events/ISliderEvents.cs:400-412 | Source/MSComctlLib/Events/IStatusBarEvents.cs:357-369 | Source/MSComctlLib/Events/ITabStripEvents.cs:390-402 | Source/MSComctlLib/Events/IToolbarEvents.cs:363-375 | Source/MSComctlLib/Events/ITreeViewEvents.cs:503-515 | Source/MSComctlLib/Events/ListViewEvents.cs:471-483 — before extracting anything, compare `Source/MSComctlLib/Events/DImageComboEvents.cs` and `Source/MSComctlLib/Events/IProgressBarEvents.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 157 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Source/MSComctlLib/Events/DImageComboEvents.cs:327` calls `ToInt32` and `Source/MSComctlLib/Events/IStatusBarEvents.cs:370` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (18 lines × 7) · ×1
  • Duplicated block (18 lines × 7) REDACTED:85 — REDACTED:85-102 | REDACTED:316-333 | REDACTED:561-578 | REDACTED:806-823 | REDACTED:1051-1068 | REDACTED:1296-1313 | REDACTED:1542-1559 — all 7 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:85` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (19–20 lines × 5) · ×1
  • Duplicated block (19–20 lines × 5) Source/NetOffice/Running/RunningObjectTable.cs:131 — Source/NetOffice/Running/RunningObjectTable.cs:131-150 | Source/NetOffice/Running/RunningObjectTable.cs:215-234 | Source/NetOffice/Running/RunningObjectTable.cs:296-315 | Source/NetOffice/Running/RunningObjectTable.cs:376-395 | Source/NetOffice/Running/RunningObjectTable.cs:488-506 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/NetOffice/Running/RunningObjectTable.cs:131` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (20 lines × 3) · ×1
  • Duplicated block (20 lines × 3) Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/OfficeCompatibilityControl.cs:299 — Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/OfficeCompatibilityControl.cs:299-318 | Toolbox/Toolbox/ToolboxControls/OutlookSecurity/OutlookSecurityControl.cs:228-247 | Toolbox/Toolbox/ToolboxControls/Welcome/WelcomeControl.cs:295-314 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Toolbox/Toolbox/ToolboxControls/OfficeCompatibility/OfficeCompatibilityControl.cs:299` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (19–20 lines × 2) · ×1
  • Duplicated block (19–20 lines × 2) Source/PowerPoint/Tools/Contribution/ApplicationUtils.cs:38 — Source/PowerPoint/Tools/Contribution/ApplicationUtils.cs:38-57 | Source/Word/Tools/Contribution/ApplicationUtils.cs:20-38 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (18 lines × 15) · ×1
  • Duplicated block (18 lines × 15) Source/Outlook/Events/OlkBusinessCardControlEvents.cs:19 — Source/Outlook/Events/OlkBusinessCardControlEvents.cs:19-36 | Source/Outlook/Events/OlkCategoryEvents.cs:19-36 | Source/Outlook/Events/OlkCheckBoxEvents.cs:19-36 | Source/Outlook/Events/OlkComboBoxEvents.cs:19-36 | Source/Outlook/Events/OlkCommandButtonEvents.cs:19-36 | Source/Outlook/Events/OlkContactPhotoEvents.cs:19-36 | Source/Outlook/Events/OlkDateControlEvents.cs:19-36 | Source/Outlook/Events/OlkInfoBarEvents.cs:19-36 | Source/Outlook/Events/OlkLabelEvents.cs:19-36 | Source/Outlook/Events/OlkListBoxEvents.cs:19-36 | Source/Outlook/Events/OlkOptionButtonEvents.cs:19-36 | Source/Outlook/Events/OlkSenderPhotoEvents.cs:19-36 | Source/Outlook/Events/OlkTextBoxEvents.cs:19-36 | Source/Outlook/Events/OlkTimeControlEvents.cs:19-36 | Source/Outlook/Events/OlkTimeZoneControlEvents.cs:19-36 — before extracting anything, compare `Source/Outlook/Events/OlkBusinessCardControlEvents.cs` and `Source/Outlook/Events/OlkCategoryEvents.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 61 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (19 lines × 3) · ×1
  • Duplicated block (19 lines × 3) Source/Access/Events/DispNavigationButtonEvents.cs:66 — Source/Access/Events/DispNavigationButtonEvents.cs:66-84 | Source/Access/Events/DispNavigationControlEvents.cs:79-97 | Source/Access/Events/DispWebBrowserControlEvents.cs:89-107 — before extracting anything, compare `Source/Access/Events/DispNavigationButtonEvents.cs` and `Source/Access/Events/DispNavigationControlEvents.cs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 226 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (19 lines × 14) · ×1
  • Duplicated block (19 lines × 14) Source/Access/Events/_BoundObjectFrameEvents.cs:80 — Source/Access/Events/_BoundObjectFrameEvents.cs:80-98 | Source/Access/Events/_CheckBoxEvents.cs:75-93 | Source/Access/Events/_CheckBoxInOptionEvents.cs:48-66 | Source/Access/Events/_ComboBoxEvents.cs:84-102 | Source/Access/Events/_CommandButtonEvents.cs:65-83 | Source/Access/Events/_FormEvents.cs:123-141 | Source/Access/Events/_ListBoxEvents.cs:74-92 | Source/Access/Events/_OptionButtonEvents.cs:75-93 | Source/Access/Events/_OptionButtonInOptionEvents.cs:48-66 | Source/Access/Events/_PaletteButtonEvents.cs:75-93 | Source/Access/Events/_TabControlEvents.cs:49-67 | Source/Access/Events/_TextBoxEvents.cs:77-95 | Source/Access/Events/_ToggleButtonEvents.cs:75-93 | Source/Access/Events/_ToggleButtonInOptionEvents.cs:48-66 — before extracting anything, compare `Source/Access/Events/_BoundObjectFrameEvents.cs` and `Source/Access/Events/_CheckBoxEvents.cs` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 292 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Source/Access/Events/_TabControlEvents.cs:69` calls `SupportByVersion`, `MethodImpl`, `DispId` and `Source/Access/Events/_BoundObjectFrameEvents.cs:99` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (15 lines × 4) · ×1
  • Duplicated block (15 lines × 4) Source/NetOffice/Invoker.cs:243 — Source/NetOffice/Invoker.cs:243-257 | Source/NetOffice/Invoker.cs:539-553 | Source/NetOffice/Invoker.cs:755-769 | Source/NetOffice/Invoker.cs:837-851 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (15–17 lines × 3) · ×1
  • Duplicated block (15–17 lines × 3) Source/OWC10/Events/IChartEvents.cs:35 — Source/OWC10/Events/IChartEvents.cs:35-51 | Source/OWC10/Events/IPivotControlEvents.cs:121-137 | Source/OWC10/Events/ISpreadsheetEventSink.cs:96-110 — before extracting anything, compare `Source/OWC10/Events/IChartEvents.cs` and `Source/OWC10/Events/IPivotControlEvents.cs` as WHOLE FILES: this scan already matched 39 separate duplicated blocks between them, totalling at least 404 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (16 lines × 48) · ×1
  • Duplicated block (16 lines × 48) Source/Access/Events/DispAttachmentEvents.cs:264 — Source/Access/Events/DispAttachmentEvents.cs:264-279 | Source/Access/Events/DispBoundObjectFrameEvents.cs:245-260 | Source/Access/Events/DispCheckBoxEvents.cs:226-241 | Source/Access/Events/DispComboBoxEvents.cs:274-289 | Source/Access/Events/DispCommandButtonEvents.cs:189-204 | Source/Access/Events/DispImageEvents.cs:108-123 | Source/Access/Events/DispLabelEvents.cs:108-123 | Source/Access/Events/DispListBoxEvents.cs:225-240 | Source/Access/Events/DispNavigationButtonEvents.cs:190-205 | Source/Access/Events/DispNavigationControlEvents.cs:250-265 | Source/Access/Events/DispObjectFrameEvents.cs:193-208 | Source/Access/Events/DispOptionButtonEvents.cs:223-238 | Source/Access/Events/DispOptionGroupEvents.cs:178-193 | Source/Access/Events/DispPageEvents.cs:108-123 | Source/Access/Events/DispPageHdrFtrInReportEvents.cs:158-173 | Source/Access/Events/DispPaletteButtonEvents.cs:225-240 | Source/Access/Events/DispRectangleEvents.cs:108-123 | Source/Access/Events/DispSectionEvents.cs:112-127 | Source/Access/Events/DispSectionInReportEvents.cs:173-188 | Source/Access/Events/DispTabControlEvents.cs:129-144 | Source/Access/Events/DispTextBoxEvents.cs:250-265 | Source/Access/Events/DispToggleButtonEvents.cs:225-240 | Source/Access/Events/DispWebBrowserControlEvents.cs:303-318 | Source/Access/Events/_BoundObjectFrameEvents.cs:245-260 | Source/Access/Events/_CheckBoxEvents.cs:225-240 | Source/Access/Events/_CheckBoxInOptionEvents.cs:120-135 | Source/Access/Events/_ComboBoxEvents.cs:272-287 | Source/Access/Events/_CommandButtonEvents.cs:189-204 | Source/Access/Events/_FormEvents.cs:582-597 | Source/Access/Events/_FormEvents2.cs:558-573 | Source/Access/Events/_ImageEvents.cs:108-123 | Source/Access/Events/_LabelEvents.cs:108-123 | Source/Access/Events/_ListBoxEvents.cs:224-239 | Source/Access/Events/_ObjectFrameEvents.cs:193-208 | Source/Access/Events/_OptionButtonEvents.cs:225-240 | Source/Access/Events/_OptionButtonInOptionEvents.cs:120-135 | Source/Access/Events/_OptionGroupEvents.cs:178-193 | Source/Access/Events/_PageEvents.cs:108-123 | Source/Access/Events/_PageHdrFtrInReportEvents.cs:154-169 | Source/Access/Events/_PaletteButtonEvents.cs:225-240 | Source/Access/Events/_RectangleEvents.cs:108-123 | Source/Access/Events/_ReportEvents2.cs:365-380 | Source/Access/Events/_SectionEvents.cs:113-128 | Source/Access/Events/_SectionInReportEvents.cs:174-189 | Source/Access/Events/_TabControlEvents.cs:129-144 | Source/Access/Events/_TextBoxEvents.cs:247-262 | Source/Access/Events/_ToggleButtonEvents.cs:225-240 | Source/Access/Events/_ToggleButtonInOptionEvents.cs:120-135 — before extracting anything, compare `Source/Access/Events/DispAttachmentEvents.cs` and `Source/Access/Events/DispBoundObjectFrameEvents.cs` as WHOLE FILES: this scan already matched 29 separate duplicated blocks between them, totalling at least 271 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Source/Access/Events/DispAttachmentEvents.cs:264` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (15–16 lines × 13) · ×1
  • Duplicated block (15–16 lines × 13) Source/Access/Events/DispAttachmentEvents.cs:85 — Source/Access/Events/DispAttachmentEvents.cs:85-99 | Source/Access/Events/DispBoundObjectFrameEvents.cs:81-95 | Source/Access/Events/DispCheckBoxEvents.cs:76-90 | Source/Access/Events/DispComboBoxEvents.cs:86-101 | Source/Access/Events/DispCommandButtonEvents.cs:66-80 | Source/Access/Events/DispListBoxEvents.cs:76-90 | Source/Access/Events/DispOptionButtonEvents.cs:74-88 | Source/Access/Events/DispPaletteButtonEvents.cs:76-90 | Source/Access/Events/DispTabControlEvents.cs:50-64 | Source/Access/Events/DispTextBoxEvents.cs:80-94 | Source/Access/Events/DispToggleButtonEvents.cs:76-90 | Source/Access/Events/_FormEvents2.cs:126-140 | Source/Access/Events/_ReportEvents2.cs:107-121 — before extracting anything, compare `Source/Access/Events/DispAttachmentEvents.cs` and `Source/Access/Events/DispBoundObjectFrameEvents.cs` as WHOLE FILES: this scan already matched 29 separate duplicated blocks between them, totalling at least 271 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (15 lines × 3) · ×1
  • Duplicated block (15 lines × 3) Source/OWC10/Events/IChartEvents.cs:275 — Source/OWC10/Events/IChartEvents.cs:275-289 | Source/OWC10/Events/IPivotControlEvents.cs:536-550 | Source/OWC10/Events/ISpreadsheetEventSink.cs:247-261 — before extracting anything, compare `Source/OWC10/Events/IChartEvents.cs` and `Source/OWC10/Events/IPivotControlEvents.cs` as WHOLE FILES: this scan already matched 39 separate duplicated blocks between them, totalling at least 404 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (14–15 lines × 42) · ×1
  • Duplicated block (14–15 lines × 42) REDACTED:77 — REDACTED:77-91 | REDACTED:118-132 | REDACTED:167-181 | REDACTED:211-224 | REDACTED:240-253 | REDACTED:269-282 | REDACTED:308-322 | REDACTED:349-363 | REDACTED:398-412 | REDACTED:442-455 | REDACTED:471-484 | REDACTED:500-513 | REDACTED:553-567 | REDACTED:594-608 | REDACTED:643-657 | REDACTED:687-700 | REDACTED:716-729 | REDACTED:745-758 | REDACTED:798-812 | REDACTED:839-853 | REDACTED:888-902 | REDACTED:932-945 | REDACTED:961-974 | REDACTED:990-1003 | REDACTED:1043-1057 | REDACTED:1084-1098 | REDACTED:1133-1147 | REDACTED:1177-1190 | REDACTED:1206-1219 | REDACTED:1235-1248 | REDACTED:1288-1302 | REDACTED:1329-1343 | REDACTED:1378-1392 | REDACTED:1422-1435 | REDACTED:1451-1464 | REDACTED:1480-1493 | REDACTED:1534-1548 | REDACTED:1575-1589 | REDACTED:1628-1642 | REDACTED:1672-1685 | REDACTED:1701-1714 | REDACTED:1730-1743 — all 42 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:77` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `REDACTED:92` calls `EndsWith` and `REDACTED:133` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (14 lines × 30) · ×1
  • Duplicated block (14 lines × 30) Source/Access/Events/DispAttachmentEvents.cs:357 — Source/Access/Events/DispAttachmentEvents.cs:357-370 | Source/Access/Events/DispBoundObjectFrameEvents.cs:338-351 | Source/Access/Events/DispCheckBoxEvents.cs:319-332 | Source/Access/Events/DispComboBoxEvents.cs:367-380 | Source/Access/Events/DispCommandButtonEvents.cs:282-295 | Source/Access/Events/DispListBoxEvents.cs:318-331 | Source/Access/Events/DispNavigationButtonEvents.cs:283-296 | Source/Access/Events/DispNavigationControlEvents.cs:343-356 | Source/Access/Events/DispOptionButtonEvents.cs:316-329 | Source/Access/Events/DispPaletteButtonEvents.cs:318-331 | Source/Access/Events/DispTabControlEvents.cs:222-235 | Source/Access/Events/DispTextBoxEvents.cs:343-356 | Source/Access/Events/DispToggleButtonEvents.cs:318-331 | Source/Access/Events/DispWebBrowserControlEvents.cs:396-409 | Source/Access/Events/_BoundObjectFrameEvents.cs:338-351 | Source/Access/Events/_CheckBoxEvents.cs:318-331 | Source/Access/Events/_CheckBoxInOptionEvents.cs:213-226 | Source/Access/Events/_ComboBoxEvents.cs:365-378 | Source/Access/Events/_CommandButtonEvents.cs:282-295 | Source/Access/Events/_FormEvents.cs:675-688 | Source/Access/Events/_FormEvents2.cs:651-664 | Source/Access/Events/_ListBoxEvents.cs:317-330 | Source/Access/Events/_OptionButtonEvents.cs:318-331 | Source/Access/Events/_OptionButtonInOptionEvents.cs:213-226 | Source/Access/Events/_PaletteButtonEvents.cs:318-331 | Source/Access/Events/_ReportEvents2.cs:458-471 | Source/Access/Events/_TabControlEvents.cs:222-235 | Source/Access/Events/_TextBoxEvents.cs:340-353 | Source/Access/Events/_ToggleButtonEvents.cs:318-331 | Source/Access/Events/_ToggleButtonInOptionEvents.cs:213-226 — before extracting anything, compare `Source/Access/Events/DispAttachmentEvents.cs` and `Source/Access/Events/DispBoundObjectFrameEvents.cs` as WHOLE FILES: this scan already matched 29 separate duplicated blocks between them, totalling at least 271 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (9 lines × 21) · ×1
  • Duplicated block (9 lines × 21) Source/MSComctlLib/Events/IProgressBarEvents.cs:125 — Source/MSComctlLib/Events/IProgressBarEvents.cs:125-133 | Source/MSComctlLib/Events/IProgressBarEvents.cs:145-153 | Source/MSComctlLib/Events/IProgressBarEvents.cs:165-173 | Source/MSComctlLib/Events/ISliderEvents.cs:210-218 | Source/MSComctlLib/Events/ISliderEvents.cs:230-238 | Source/MSComctlLib/Events/ISliderEvents.cs:250-258 | Source/MSComctlLib/Events/IStatusBarEvents.cs:167-175 | Source/MSComctlLib/Events/IStatusBarEvents.cs:187-195 | Source/MSComctlLib/Events/IStatusBarEvents.cs:207-215 | Source/MSComctlLib/Events/ITabStripEvents.cs:207-215 | Source/MSComctlLib/Events/ITabStripEvents.cs:227-235 | Source/MSComctlLib/Events/ITabStripEvents.cs:247-255 | Source/MSComctlLib/Events/IToolbarEvents.cs:184-192 | Source/MSComctlLib/Events/IToolbarEvents.cs:204-212 | Source/MSComctlLib/Events/IToolbarEvents.cs:224-232 | Source/MSComctlLib/Events/ITreeViewEvents.cs:299-307 | Source/MSComctlLib/Events/ITreeViewEvents.cs:319-327 | Source/MSComctlLib/Events/ITreeViewEvents.cs:339-347 | Source/MSComctlLib/Events/ListViewEvents.cs:281-289 | Source/MSComctlLib/Events/ListViewEvents.cs:301-309 | Source/MSComctlLib/Events/ListViewEvents.cs:321-329 — before extracting anything, compare `Source/MSComctlLib/Events/IProgressBarEvents.cs` and `Source/MSComctlLib/Events/ISliderEvents.cs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 197 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (9 lines × 12) · ×1
  • Duplicated block (9 lines × 12) Source/Excel/Events/ChartEvents.cs:160 — Source/Excel/Events/ChartEvents.cs:160-168 | Source/Excel/Events/ChartEvents.cs:180-188 | Source/Excel/Events/ChartEvents.cs:200-208 | Source/OWC10/Events/IChartEvents.cs:333-341 | Source/OWC10/Events/IChartEvents.cs:353-361 | Source/OWC10/Events/IChartEvents.cs:373-381 | Source/OWC10/Events/IPivotControlEvents.cs:318-326 | Source/OWC10/Events/IPivotControlEvents.cs:338-346 | Source/OWC10/Events/IPivotControlEvents.cs:358-366 | Source/OWC10/Events/ISpreadsheetEventSink.cs:495-503 | Source/OWC10/Events/ISpreadsheetEventSink.cs:515-523 | Source/OWC10/Events/ISpreadsheetEventSink.cs:535-543 — there are 12 copies across 4 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 12 sites; resolving a subset leaves the remainder to drift apart.
D4 · Code Duplication · Duplicated block (14 lines × 11) · ×1
  • Duplicated block (14 lines × 11) Source/Outlook/Events/OlkCategoryEvents.cs:249 — Source/Outlook/Events/OlkCategoryEvents.cs:249-262 | Source/Outlook/Events/OlkCheckBoxEvents.cs:258-271 | Source/Outlook/Events/OlkComboBoxEvents.cs:262-275 | Source/Outlook/Events/OlkCommandButtonEvents.cs:254-267 | Source/Outlook/Events/OlkContactPhotoEvents.cs:249-262 | Source/Outlook/Events/OlkDateControlEvents.cs:262-275 | Source/Outlook/Events/OlkListBoxEvents.cs:258-271 | Source/Outlook/Events/OlkOptionButtonEvents.cs:258-271 | Source/Outlook/Events/OlkTextBoxEvents.cs:258-271 | Source/Outlook/Events/OlkTimeControlEvents.cs:262-275 | Source/Outlook/Events/OlkTimeZoneControlEvents.cs:262-275 — before extracting anything, compare `Source/Outlook/Events/OlkCategoryEvents.cs` and `Source/Outlook/Events/OlkCheckBoxEvents.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 160 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (12–15 lines × 4) · ×1
  • Duplicated block (12–15 lines × 4) Source/MSComctlLib/Events/ISliderEvents.cs:27 — Source/MSComctlLib/Events/ISliderEvents.cs:27-41 | Source/MSComctlLib/Events/ITabStripEvents.cs:27-41 | Source/MSComctlLib/Events/ITreeViewEvents.cs:49-60 | Source/MSComctlLib/Events/ListViewEvents.cs:44-55 — before extracting anything, compare `Source/MSComctlLib/Events/ISliderEvents.cs` and `Source/MSComctlLib/Events/ITabStripEvents.cs` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 295 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Source/MSComctlLib/Events/ITreeViewEvents.cs:60` calls `KeyPress`, `SupportByVersion` and `Source/MSComctlLib/Events/ISliderEvents.cs:41` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (4–15 lines × 8) · ×1
  • Duplicated block (4–15 lines × 8) Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ClassLibraryConverterVB.cs:102 — Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ClassLibraryConverterVB.cs:102-105 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ConsoleConverterVB.cs:101-104 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleMultiAddinConverterVB.cs:210-224 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleSingleAddinConverterVB.cs:198-212 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsMultiAddinConverterVB.cs:248-262 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsSingleAddinConverterVB.cs:245-259 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/WindowsFormsConverterCS.cs:106-109 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/WindowsFormsConverterVB.cs:109-112 — before extracting anything, compare `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ClassLibraryConverterVB.cs` and `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ConsoleConverterVB.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleMultiAddinConverterVB.cs:210` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ClassLibraryConverterVB.cs:107` calls `AppendAllText`, `Combine` and `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/WindowsFormsConverterCS.cs:111` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (14–15 lines × 3) · ×1
  • Duplicated block (14–15 lines × 3) Source/OWC10/Events/IChartEvents.cs:55 — Source/OWC10/Events/IChartEvents.cs:55-69 | Source/OWC10/Events/IPivotControlEvents.cs:141-155 | Source/OWC10/Events/ISpreadsheetEventSink.cs:35-48 — before extracting anything, compare `Source/OWC10/Events/IChartEvents.cs` and `Source/OWC10/Events/IPivotControlEvents.cs` as WHOLE FILES: this scan already matched 39 separate duplicated blocks between them, totalling at least 404 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/OWC10/Events/ISpreadsheetEventSink.cs:35` calls `SinkArgument` and `Source/OWC10/Events/IChartEvents.cs:55` does not — after which the two agree again for 5 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (13 lines × 42) · ×1
  • Duplicated block (13 lines × 42) Source/Outlook/Events/OlkBusinessCardControlEvents.cs:103 — Source/Outlook/Events/OlkBusinessCardControlEvents.cs:103-115 | Source/Outlook/Events/OlkBusinessCardControlEvents.cs:123-135 | Source/Outlook/Events/OlkBusinessCardControlEvents.cs:143-155 | Source/Outlook/Events/OlkCategoryEvents.cs:133-145 | Source/Outlook/Events/OlkCategoryEvents.cs:153-165 | Source/Outlook/Events/OlkCategoryEvents.cs:173-185 | Source/Outlook/Events/OlkCheckBoxEvents.cs:142-154 | Source/Outlook/Events/OlkCheckBoxEvents.cs:162-174 | Source/Outlook/Events/OlkCheckBoxEvents.cs:182-194 | Source/Outlook/Events/OlkComboBoxEvents.cs:146-158 | Source/Outlook/Events/OlkComboBoxEvents.cs:166-178 | Source/Outlook/Events/OlkComboBoxEvents.cs:186-198 | Source/Outlook/Events/OlkCommandButtonEvents.cs:138-150 | Source/Outlook/Events/OlkCommandButtonEvents.cs:158-170 | Source/Outlook/Events/OlkCommandButtonEvents.cs:178-190 | Source/Outlook/Events/OlkContactPhotoEvents.cs:133-145 | Source/Outlook/Events/OlkContactPhotoEvents.cs:153-165 | Source/Outlook/Events/OlkContactPhotoEvents.cs:173-185 | Source/Outlook/Events/OlkDateControlEvents.cs:146-158 | Source/Outlook/Events/OlkDateControlEvents.cs:166-178 | Source/Outlook/Events/OlkDateControlEvents.cs:186-198 | Source/Outlook/Events/OlkInfoBarEvents.cs:103-115 | Source/Outlook/Events/OlkInfoBarEvents.cs:123-135 | Source/Outlook/Events/OlkInfoBarEvents.cs:143-155 | Source/Outlook/Events/OlkLabelEvents.cs:103-115 | Source/Outlook/Events/OlkLabelEvents.cs:123-135 | Source/Outlook/Events/OlkLabelEvents.cs:143-155 | Source/Outlook/Events/OlkListBoxEvents.cs:142-154 | Source/Outlook/Events/OlkListBoxEvents.cs:162-174 | Source/Outlook/Events/OlkListBoxEvents.cs:182-194 | Source/Outlook/Events/OlkOptionButtonEvents.cs:142-154 | Source/Outlook/Events/OlkOptionButtonEvents.cs:162-174 | Source/Outlook/Events/OlkOptionButtonEvents.cs:182-194 | Source/Outlook/Events/OlkSenderPhotoEvents.cs:107-119 | Source/Outlook/Events/OlkSenderPhotoEvents.cs:127-139 | Source/Outlook/Events/OlkSenderPhotoEvents.cs:147-159 | Source/Outlook/Events/OlkTextBoxEvents.cs:142-154 | Source/Outlook/Events/OlkTextBoxEvents.cs:162-174 | Source/Outlook/Events/OlkTextBoxEvents.cs:182-194 | Source/Outlook/Events/OlkTimeControlEvents.cs:146-158 | Source/Outlook/Events/OlkTimeControlEvents.cs:166-178 | Source/Outlook/Events/OlkTimeControlEvents.cs:186-198 — before extracting anything, compare `Source/Outlook/Events/OlkBusinessCardControlEvents.cs` and `Source/Outlook/Events/OlkCategoryEvents.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 61 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Source/Outlook/Events/OlkBusinessCardControlEvents.cs:103` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (13 lines × 24) · ×1
  • Duplicated block (13 lines × 24) Source/Access/Events/DispAttachmentEvents.cs:60 — Source/Access/Events/DispAttachmentEvents.cs:60-72 | Source/Access/Events/DispBoundObjectFrameEvents.cs:56-68 | Source/Access/Events/DispCheckBoxEvents.cs:51-63 | Source/Access/Events/DispComboBoxEvents.cs:61-73 | Source/Access/Events/DispCommandButtonEvents.cs:41-53 | Source/Access/Events/DispImageEvents.cs:25-37 | Source/Access/Events/DispLabelEvents.cs:25-37 | Source/Access/Events/DispListBoxEvents.cs:51-63 | Source/Access/Events/DispObjectFrameEvents.cs:47-59 | Source/Access/Events/DispOptionButtonEvents.cs:49-61 | Source/Access/Events/DispOptionGroupEvents.cs:43-55 | Source/Access/Events/DispPageEvents.cs:25-37 | Source/Access/Events/DispPageHdrFtrInReportEvents.cs:37-49 | Source/Access/Events/DispPaletteButtonEvents.cs:51-63 | Source/Access/Events/DispRectangleEvents.cs:25-37 | Source/Access/Events/DispSectionEvents.cs:25-37 | Source/Access/Events/DispSectionInReportEvents.cs:41-53 | Source/Access/Events/DispTabControlEvents.cs:25-37 | Source/Access/Events/DispTextBoxEvents.cs:55-67 | Source/Access/Events/DispToggleButtonEvents.cs:51-63 | Source/Access/Events/_FormEvents2.cs:101-113 | Source/Access/Events/_PageHdrFtrInReportEvents.cs:37-49 | Source/Access/Events/_ReportEvents2.cs:82-94 | Source/Access/Events/_SectionInReportEvents.cs:41-53 — before extracting anything, compare `Source/Access/Events/DispAttachmentEvents.cs` and `Source/Access/Events/DispBoundObjectFrameEvents.cs` as WHOLE FILES: this scan already matched 29 separate duplicated blocks between them, totalling at least 271 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Access/Events/DispCheckBoxEvents.cs:50` calls `SinkArgument` and `Source/Access/Events/DispOptionButtonEvents.cs:48` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (11–14 lines × 4) · ×1
  • Duplicated block (11–14 lines × 4) Source/NetOffice/Invoker.cs:348 — Source/NetOffice/Invoker.cs:348-361 | Source/NetOffice/Invoker.cs:383-393 | Source/NetOffice/Invoker.cs:644-657 | Source/NetOffice/Invoker.cs:679-689 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/NetOffice/Invoker.cs:348` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (3–14 lines × 7) · ×1
  • Duplicated block (3–14 lines × 7) Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ClassLibraryConverterCS.cs:80 — Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ClassLibraryConverterCS.cs:80-83 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ConsoleConverterCS.cs:80-83 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleMultiAddinConverterCS.cs:190-203 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleSingleAddinConverterCS.cs:176-189 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsMultiAddinConverterCS.cs:211-224 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsSingleAddinConverterCS.cs:208-221 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/WindowsFormsConverterCS.cs:108-110 — before extracting anything, compare `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ClassLibraryConverterCS.cs` and `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ConsoleConverterCS.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ClassLibraryConverterCS.cs:80` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ClassLibraryConverterCS.cs:84` calls `AppendAllText`, `Combine` and `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/WindowsFormsConverterCS.cs:111` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (12 lines × 42) · ×1
  • Duplicated block (12 lines × 42) Source/Access/Events/DispAttachmentEvents.cs:247 — Source/Access/Events/DispAttachmentEvents.cs:247-258 | Source/Access/Events/DispBoundObjectFrameEvents.cs:228-239 | Source/Access/Events/DispCheckBoxEvents.cs:209-220 | Source/Access/Events/DispComboBoxEvents.cs:257-268 | Source/Access/Events/DispCommandButtonEvents.cs:172-183 | Source/Access/Events/DispImageEvents.cs:91-102 | Source/Access/Events/DispLabelEvents.cs:91-102 | Source/Access/Events/DispListBoxEvents.cs:208-219 | Source/Access/Events/DispNavigationButtonEvents.cs:173-184 | Source/Access/Events/DispNavigationControlEvents.cs:233-244 | Source/Access/Events/DispObjectFrameEvents.cs:176-187 | Source/Access/Events/DispOptionButtonEvents.cs:206-217 | Source/Access/Events/DispOptionGroupEvents.cs:161-172 | Source/Access/Events/DispPageEvents.cs:91-102 | Source/Access/Events/DispPageHdrFtrInReportEvents.cs:141-152 | Source/Access/Events/DispPaletteButtonEvents.cs:208-219 | Source/Access/Events/DispRectangleEvents.cs:91-102 | Source/Access/Events/DispSectionEvents.cs:95-106 | Source/Access/Events/DispSectionInReportEvents.cs:156-167 | Source/Access/Events/DispTabControlEvents.cs:112-123 | Source/Access/Events/DispTextBoxEvents.cs:233-244 | Source/Access/Events/DispToggleButtonEvents.cs:208-219 | Source/Access/Events/DispWebBrowserControlEvents.cs:286-297 | Source/Access/Events/_BoundObjectFrameEvents.cs:228-239 | Source/Access/Events/_CheckBoxEvents.cs:208-219 | Source/Access/Events/_ComboBoxEvents.cs:255-266 | Source/Access/Events/_CommandButtonEvents.cs:172-183 | Source/Access/Events/_FormEvents.cs:565-576 | Source/Access/Events/_FormEvents2.cs:541-552 | Source/Access/Events/_ImageEvents.cs:91-102 | Source/Access/Events/_LabelEvents.cs:91-102 | Source/Access/Events/_ListBoxEvents.cs:207-218 | Source/Access/Events/_ObjectFrameEvents.cs:176-187 | Source/Access/Events/_OptionButtonEvents.cs:208-219 | Source/Access/Events/_OptionGroupEvents.cs:161-172 | Source/Access/Events/_PageEvents.cs:91-102 | Source/Access/Events/_PageHdrFtrInReportEvents.cs:137-148 | Source/Access/Events/_RectangleEvents.cs:91-102 | Source/Access/Events/_ReportEvents2.cs:348-359 | Source/Access/Events/_SectionEvents.cs:95-106 | Source/Access/Events/_SectionInReportEvents.cs:156-167 | Source/Access/Events/_ToggleButtonEvents.cs:208-219 — before extracting anything, compare `Source/Access/Events/DispAttachmentEvents.cs` and `Source/Access/Events/DispBoundObjectFrameEvents.cs` as WHOLE FILES: this scan already matched 29 separate duplicated blocks between them, totalling at least 271 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (12 lines × 35) · ×1
  • Duplicated block (12 lines × 35) Source/Access/Events/DispAttachmentEvents.cs:342 — Source/Access/Events/DispAttachmentEvents.cs:342-353 | Source/Access/Events/DispBoundObjectFrameEvents.cs:323-334 | Source/Access/Events/DispCheckBoxEvents.cs:304-315 | Source/Access/Events/DispComboBoxEvents.cs:352-363 | Source/Access/Events/DispCommandButtonEvents.cs:267-278 | Source/Access/Events/DispListBoxEvents.cs:303-314 | Source/Access/Events/DispNavigationButtonEvents.cs:268-279 | Source/Access/Events/DispNavigationControlEvents.cs:328-339 | Source/Access/Events/DispOptionButtonEvents.cs:301-312 | Source/Access/Events/DispPaletteButtonEvents.cs:303-314 | Source/Access/Events/DispTabControlEvents.cs:207-218 | Source/Access/Events/DispTextBoxEvents.cs:328-339 | Source/Access/Events/DispToggleButtonEvents.cs:303-314 | Source/Access/Events/DispWebBrowserControlEvents.cs:381-392 | Source/Access/Events/_BoundObjectFrameEvents.cs:323-334 | Source/Access/Events/_CheckBoxEvents.cs:303-314 | Source/Access/Events/_CheckBoxInOptionEvents.cs:198-209 | Source/Access/Events/_ComboBoxEvents.cs:350-361 | Source/Access/Events/_CommandButtonEvents.cs:267-278 | Source/Access/Events/_FormEvents.cs:660-671 | Source/Access/Events/_FormEvents2.cs:636-647 | Source/Access/Events/_ListBoxEvents.cs:302-313 | Source/Access/Events/_OptionButtonEvents.cs:303-314 | Source/Access/Events/_OptionButtonInOptionEvents.cs:198-209 | Source/Access/Events/_PaletteButtonEvents.cs:303-314 | Source/Access/Events/_ReportEvents2.cs:443-454 | Source/Access/Events/_TabControlEvents.cs:207-218 | Source/Access/Events/_TextBoxEvents.cs:325-336 | Source/Access/Events/_ToggleButtonEvents.cs:303-314 | Source/Access/Events/_ToggleButtonInOptionEvents.cs:198-209 | Source/MSComctlLib/Events/DImageComboEvents.cs:185-196 | Source/MSComctlLib/Events/ISliderEvents.cs:172-183 | Source/MSComctlLib/Events/ITabStripEvents.cs:186-197 | Source/MSComctlLib/Events/ITreeViewEvents.cs:279-290 | Source/MSComctlLib/Events/ListViewEvents.cs:260-271 — before extracting anything, compare `Source/Access/Events/DispAttachmentEvents.cs` and `Source/Access/Events/DispBoundObjectFrameEvents.cs` as WHOLE FILES: this scan already matched 29 separate duplicated blocks between them, totalling at least 271 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (12 lines × 31) · ×1
  • Duplicated block (12 lines × 31) Source/Access/Events/DispAttachmentEvents.cs:173 — Source/Access/Events/DispAttachmentEvents.cs:173-184 | Source/Access/Events/DispBoundObjectFrameEvents.cs:180-191 | Source/Access/Events/DispCheckBoxEvents.cs:172-183 | Source/Access/Events/DispComboBoxEvents.cs:209-220 | Source/Access/Events/DispCommandButtonEvents.cs:135-146 | Source/Access/Events/DispCustomControlEvents.cs:95-106 | Source/Access/Events/DispListBoxEvents.cs:160-171 | Source/Access/Events/DispNavigationButtonEvents.cs:136-147 | Source/Access/Events/DispNavigationControlEvents.cs:185-196 | Source/Access/Events/DispObjectFrameEvents.cs:128-139 | Source/Access/Events/DispOptionButtonEvents.cs:169-180 | Source/Access/Events/DispOptionGroupEvents.cs:135-146 | Source/Access/Events/DispPaletteButtonEvents.cs:171-182 | Source/Access/Events/DispSubFormEvents.cs:67-78 | Source/Access/Events/DispSubReportEvents.cs:67-78 | Source/Access/Events/DispTextBoxEvents.cs:185-196 | Source/Access/Events/DispToggleButtonEvents.cs:171-182 | Source/Access/Events/DispWebBrowserControlEvents.cs:212-223 | Source/Access/Events/_BoundObjectFrameEvents.cs:180-191 | Source/Access/Events/_CheckBoxEvents.cs:171-182 | Source/Access/Events/_ComboBoxEvents.cs:207-218 | Source/Access/Events/_CommandButtonEvents.cs:135-146 | Source/Access/Events/_CustomControlEvents.cs:94-105 | Source/Access/Events/_ListBoxEvents.cs:159-170 | Source/Access/Events/_ObjectFrameEvents.cs:128-139 | Source/Access/Events/_OptionButtonEvents.cs:171-182 | Source/Access/Events/_OptionGroupEvents.cs:135-146 | Source/Access/Events/_PaletteButtonEvents.cs:171-182 | Source/Access/Events/_SubFormEvents.cs:67-78 | Source/Access/Events/_TextBoxEvents.cs:183-194 | Source/Access/Events/_ToggleButtonEvents.cs:171-182 — before extracting anything, compare `Source/Access/Events/DispAttachmentEvents.cs` and `Source/Access/Events/DispBoundObjectFrameEvents.cs` as WHOLE FILES: this scan already matched 29 separate duplicated blocks between them, totalling at least 271 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (6 lines × 30) · ×1
  • Duplicated block (6 lines × 30) Source/Access/Events/DispAttachmentEvents.cs:331 — Source/Access/Events/DispAttachmentEvents.cs:331-336 | Source/Access/Events/DispBoundObjectFrameEvents.cs:312-317 | Source/Access/Events/DispCheckBoxEvents.cs:293-298 | Source/Access/Events/DispComboBoxEvents.cs:341-346 | Source/Access/Events/DispCommandButtonEvents.cs:256-261 | Source/Access/Events/DispListBoxEvents.cs:292-297 | Source/Access/Events/DispNavigationButtonEvents.cs:257-262 | Source/Access/Events/DispNavigationControlEvents.cs:317-322 | Source/Access/Events/DispOptionButtonEvents.cs:290-295 | Source/Access/Events/DispPaletteButtonEvents.cs:292-297 | Source/Access/Events/DispTabControlEvents.cs:196-201 | Source/Access/Events/DispTextBoxEvents.cs:317-322 | Source/Access/Events/DispToggleButtonEvents.cs:292-297 | Source/Access/Events/DispWebBrowserControlEvents.cs:370-375 | Source/Access/Events/_BoundObjectFrameEvents.cs:312-317 | Source/Access/Events/_CheckBoxEvents.cs:292-297 | Source/Access/Events/_CheckBoxInOptionEvents.cs:187-192 | Source/Access/Events/_ComboBoxEvents.cs:339-344 | Source/Access/Events/_CommandButtonEvents.cs:256-261 | Source/Access/Events/_FormEvents.cs:649-654 | Source/Access/Events/_FormEvents2.cs:625-630 | Source/Access/Events/_ListBoxEvents.cs:291-296 | Source/Access/Events/_OptionButtonEvents.cs:292-297 | Source/Access/Events/_OptionButtonInOptionEvents.cs:187-192 | Source/Access/Events/_PaletteButtonEvents.cs:292-297 | Source/Access/Events/_ReportEvents2.cs:432-437 | Source/Access/Events/_TabControlEvents.cs:196-201 | Source/Access/Events/_TextBoxEvents.cs:314-319 | Source/Access/Events/_ToggleButtonEvents.cs:292-297 | Source/Access/Events/_ToggleButtonInOptionEvents.cs:187-192 — before extracting anything, compare `Source/Access/Events/DispAttachmentEvents.cs` and `Source/Access/Events/DispBoundObjectFrameEvents.cs` as WHOLE FILES: this scan already matched 29 separate duplicated blocks between them, totalling at least 271 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (12 lines × 26) · ×1
  • Duplicated block (12 lines × 26) Source/Access/DispatchInterfaces/_Attachment.cs:2453 — Source/Access/DispatchInterfaces/_Attachment.cs:2453-2464 | Source/Access/DispatchInterfaces/_BoundObjectFrame.cs:2301-2312 | Source/Access/DispatchInterfaces/_Checkbox.cs:1984-1995 | Source/Access/DispatchInterfaces/_Combobox.cs:3372-3383 | Source/Access/DispatchInterfaces/_CommandButton.cs:2730-2741 | Source/Access/DispatchInterfaces/_Control.cs:828-839 | Source/Access/DispatchInterfaces/_CustomControl.cs:1545-1556 | Source/Access/DispatchInterfaces/_EmptyCell.cs:976-987 | Source/Access/DispatchInterfaces/_Form.cs:3119-3130 | Source/Access/DispatchInterfaces/_Image.cs:1576-1587 | Source/Access/DispatchInterfaces/_ListBox.cs:2754-2765 | Source/Access/DispatchInterfaces/_NavigationButton.cs:2718-2729 | Source/Access/DispatchInterfaces/_NavigationControl.cs:1894-1905 | Source/Access/DispatchInterfaces/_ObjectFrame.cs:2175-2186 | Source/Access/DispatchInterfaces/_OptionButton.cs:1974-1985 | Source/Access/DispatchInterfaces/_OptionGroup.cs:1523-1534 | Source/Access/DispatchInterfaces/_Page.cs:804-815 | Source/Access/DispatchInterfaces/_PageBreak.cs:393-404 | Source/Access/DispatchInterfaces/_PaletteButton.cs:1416-1427 | Source/Access/DispatchInterfaces/_Rectangle.cs:915-926 | Source/Access/DispatchInterfaces/_Report.cs:2040-2051 | Source/Access/DispatchInterfaces/_SubForm.cs:1363-1374 | Source/Access/DispatchInterfaces/_TabControl.cs:2090-2101 | Source/Access/DispatchInterfaces/_Textbox.cs:3106-3117 | Source/Access/DispatchInterfaces/_ToggleButton.cs:2760-2771 | Source/Access/DispatchInterfaces/_WebBrowserControl.cs:1677-1688 — before extracting anything, compare `Source/Access/DispatchInterfaces/_BoundObjectFrame.cs` and `Source/Access/DispatchInterfaces/_Checkbox.cs` as WHOLE FILES: 87% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (13 lines × 16) · ×1
  • Duplicated block (13 lines × 16) Source/MSComctlLib/Events/DImageComboEvents.cs:200 — Source/MSComctlLib/Events/DImageComboEvents.cs:200-212 | Source/MSComctlLib/Events/DImageComboEvents.cs:239-251 | Source/MSComctlLib/Events/IProgressBarEvents.cs:190-202 | Source/MSComctlLib/Events/IProgressBarEvents.cs:229-241 | Source/MSComctlLib/Events/ISliderEvents.cs:286-298 | Source/MSComctlLib/Events/ISliderEvents.cs:325-337 | Source/MSComctlLib/Events/IStatusBarEvents.cs:243-255 | Source/MSComctlLib/Events/IStatusBarEvents.cs:282-294 | Source/MSComctlLib/Events/ITabStripEvents.cs:276-288 | Source/MSComctlLib/Events/ITabStripEvents.cs:315-327 | Source/MSComctlLib/Events/IToolbarEvents.cs:249-261 | Source/MSComctlLib/Events/IToolbarEvents.cs:288-300 | Source/MSComctlLib/Events/ITreeViewEvents.cs:389-401 | Source/MSComctlLib/Events/ITreeViewEvents.cs:428-440 | Source/MSComctlLib/Events/ListViewEvents.cs:357-369 | Source/MSComctlLib/Events/ListViewEvents.cs:396-408 — before extracting anything, compare `Source/MSComctlLib/Events/DImageComboEvents.cs` and `Source/MSComctlLib/Events/IProgressBarEvents.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 157 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (12 lines × 15) · ×1
  • Duplicated block (12 lines × 15) Source/Access/Events/DispAttachmentEvents.cs:136 — Source/Access/Events/DispAttachmentEvents.cs:136-147 | Source/Access/Events/DispBoundObjectFrameEvents.cs:143-154 | Source/Access/Events/DispCheckBoxEvents.cs:135-146 | Source/Access/Events/DispComboBoxEvents.cs:144-155 | Source/Access/Events/_BoundObjectFrameEvents.cs:143-154 | Source/Access/Events/_CheckBoxEvents.cs:134-145 | Source/Access/Events/_ComboBoxEvents.cs:142-153 | Source/Access/Events/_FormEvents.cs:386-397 | Source/Access/Events/_FormEvents2.cs:361-372 | Source/Access/Events/_ListBoxEvents.cs:122-133 | Source/Access/Events/_OptionButtonEvents.cs:134-145 | Source/Access/Events/_OptionGroupEvents.cs:98-109 | Source/Access/Events/_PaletteButtonEvents.cs:134-145 | Source/Access/Events/_TextBoxEvents.cs:135-146 | Source/Access/Events/_ToggleButtonEvents.cs:134-145 — before extracting anything, compare `Source/Access/Events/DispAttachmentEvents.cs` and `Source/Access/Events/DispBoundObjectFrameEvents.cs` as WHOLE FILES: this scan already matched 29 separate duplicated blocks between them, totalling at least 271 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (10 lines × 12) · ×1
  • Duplicated block (10 lines × 12) Source/Access/Events/DispAttachmentEvents.cs:28 — Source/Access/Events/DispAttachmentEvents.cs:28-37 | Source/Access/Events/DispBoundObjectFrameEvents.cs:33-42 | Source/Access/Events/DispCheckBoxEvents.cs:32-41 | Source/Access/Events/DispComboBoxEvents.cs:38-47 | Source/Access/Events/DispCustomControlEvents.cs:24-33 | Source/Access/Events/DispListBoxEvents.cs:28-37 | Source/Access/Events/DispObjectFrameEvents.cs:24-33 | Source/Access/Events/DispOptionButtonEvents.cs:31-40 | Source/Access/Events/DispOptionGroupEvents.cs:28-37 | Source/Access/Events/DispPaletteButtonEvents.cs:32-41 | Source/Access/Events/DispTextBoxEvents.cs:32-41 | Source/Access/Events/DispToggleButtonEvents.cs:32-41 — before extracting anything, compare `Source/Access/Events/DispAttachmentEvents.cs` and `Source/Access/Events/DispBoundObjectFrameEvents.cs` as WHOLE FILES: this scan already matched 29 separate duplicated blocks between them, totalling at least 271 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Access/Events/DispTextBoxEvents.cs:28` calls `SupportByVersion`, `MethodImpl`, `DispId` and `Source/Access/Events/DispAttachmentEvents.cs:26` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (12 lines × 11) · ×1
  • Duplicated block (12 lines × 11) Source/Outlook/Events/OlkCategoryEvents.cs:202 — Source/Outlook/Events/OlkCategoryEvents.cs:202-213 | Source/Outlook/Events/OlkCheckBoxEvents.cs:211-222 | Source/Outlook/Events/OlkComboBoxEvents.cs:215-226 | Source/Outlook/Events/OlkCommandButtonEvents.cs:207-218 | Source/Outlook/Events/OlkContactPhotoEvents.cs:202-213 | Source/Outlook/Events/OlkDateControlEvents.cs:215-226 | Source/Outlook/Events/OlkListBoxEvents.cs:211-222 | Source/Outlook/Events/OlkOptionButtonEvents.cs:211-222 | Source/Outlook/Events/OlkTextBoxEvents.cs:211-222 | Source/Outlook/Events/OlkTimeControlEvents.cs:215-226 | Source/Outlook/Events/OlkTimeZoneControlEvents.cs:215-226 — before extracting anything, compare `Source/Outlook/Events/OlkCategoryEvents.cs` and `Source/Outlook/Events/OlkCheckBoxEvents.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 160 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (12 lines × 10) · ×1
  • Duplicated block (12 lines × 10) Source/Outlook/Events/OlkCategoryEvents.cs:234 — Source/Outlook/Events/OlkCategoryEvents.cs:234-245 | Source/Outlook/Events/OlkComboBoxEvents.cs:247-258 | Source/Outlook/Events/OlkCommandButtonEvents.cs:239-250 | Source/Outlook/Events/OlkContactPhotoEvents.cs:234-245 | Source/Outlook/Events/OlkDateControlEvents.cs:247-258 | Source/Outlook/Events/OlkListBoxEvents.cs:243-254 | Source/Outlook/Events/OlkOptionButtonEvents.cs:243-254 | Source/Outlook/Events/OlkTextBoxEvents.cs:243-254 | Source/Outlook/Events/OlkTimeControlEvents.cs:247-258 | Source/Outlook/Events/OlkTimeZoneControlEvents.cs:247-258 — before extracting anything, compare `Source/Outlook/Events/OlkCategoryEvents.cs` and `Source/Outlook/Events/OlkComboBoxEvents.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 172 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (12–13 lines × 6) · ×1
  • Duplicated block (12–13 lines × 6) Source/Access/Events/DispWebBrowserControlEvents.cs:457 — Source/Access/Events/DispWebBrowserControlEvents.cs:457-469 | Source/Excel/Events/ChartEvents.cs:290-301 | Source/OWC10/Events/IChartEvents.cs:229-240 | Source/OWC10/Events/IChartEvents.cs:245-256 | Source/OWC10/Events/IPivotControlEvents.cs:490-501 | Source/OWC10/Events/IPivotControlEvents.cs:506-517 — there are 6 copies across 4 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 6 sites; resolving a subset leaves the remainder to drift apart.
D4 · Code Duplication · Duplicated block (12–13 lines × 2) · ×1
  • Duplicated block (12–13 lines × 2) Source/ADODB/Events/RecordsetEvents.cs:234 — Source/ADODB/Events/RecordsetEvents.cs:234-246 | Source/ADODB/Events/RecordsetEvents.cs:273-284 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (5 lines × 144) · ×1
  • Duplicated block (5 lines × 144) Source/Access/Events/DispAttachmentEvents.cs:268 — Source/Access/Events/DispAttachmentEvents.cs:268-272 | Source/Access/Events/DispAttachmentEvents.cs:289-293 | Source/Access/Events/DispAttachmentEvents.cs:310-314 | Source/Access/Events/DispBoundObjectFrameEvents.cs:249-253 | Source/Access/Events/DispBoundObjectFrameEvents.cs:270-274 | Source/Access/Events/DispBoundObjectFrameEvents.cs:291-295 | Source/Access/Events/DispCheckBoxEvents.cs:230-234 | Source/Access/Events/DispCheckBoxEvents.cs:251-255 | Source/Access/Events/DispCheckBoxEvents.cs:272-276 | Source/Access/Events/DispComboBoxEvents.cs:278-282 | Source/Access/Events/DispComboBoxEvents.cs:299-303 | Source/Access/Events/DispComboBoxEvents.cs:320-324 | Source/Access/Events/DispCommandButtonEvents.cs:193-197 | Source/Access/Events/DispCommandButtonEvents.cs:214-218 | Source/Access/Events/DispCommandButtonEvents.cs:235-239 | Source/Access/Events/DispImageEvents.cs:112-116 | Source/Access/Events/DispImageEvents.cs:133-137 | Source/Access/Events/DispImageEvents.cs:154-158 | Source/Access/Events/DispLabelEvents.cs:112-116 | Source/Access/Events/DispLabelEvents.cs:133-137 | Source/Access/Events/DispLabelEvents.cs:154-158 | Source/Access/Events/DispListBoxEvents.cs:229-233 | Source/Access/Events/DispListBoxEvents.cs:250-254 | Source/Access/Events/DispListBoxEvents.cs:271-275 | Source/Access/Events/DispNavigationButtonEvents.cs:194-198 | Source/Access/Events/DispNavigationButtonEvents.cs:215-219 | Source/Access/Events/DispNavigationButtonEvents.cs:236-240 | Source/Access/Events/DispNavigationControlEvents.cs:254-258 | Source/Access/Events/DispNavigationControlEvents.cs:275-279 | Source/Access/Events/DispNavigationControlEvents.cs:296-300 | Source/Access/Events/DispObjectFrameEvents.cs:197-201 | Source/Access/Events/DispObjectFrameEvents.cs:218-222 | Source/Access/Events/DispObjectFrameEvents.cs:239-243 | Source/Access/Events/DispOptionButtonEvents.cs:227-231 | Source/Access/Events/DispOptionButtonEvents.cs:248-252 | Source/Access/Events/DispOptionButtonEvents.cs:269-273 | Source/Access/Events/DispOptionGroupEvents.cs:182-186 | Source/Access/Events/DispOptionGroupEvents.cs:203-207 | Source/Access/Events/DispOptionGroupEvents.cs:224-228 | Source/Access/Events/DispPageEvents.cs:112-116 | Source/Access/Events/DispPageEvents.cs:133-137 | Source/Access/Events/DispPageEvents.cs:154-158 | Source/Access/Events/DispPageHdrFtrInReportEvents.cs:162-166 | Source/Access/Events/DispPageHdrFtrInReportEvents.cs:183-187 | Source/Access/Events/DispPageHdrFtrInReportEvents.cs:204-208 | Source/Access/Events/DispPaletteButtonEvents.cs:229-233 | Source/Access/Events/DispPaletteButtonEvents.cs:250-254 | Source/Access/Events/DispPaletteButtonEvents.cs:271-275 | Source/Access/Events/DispRectangleEvents.cs:112-116 | Source/Access/Events/DispRectangleEvents.cs:133-137 | Source/Access/Events/DispRectangleEvents.cs:154-158 | Source/Access/Events/DispSectionEvents.cs:116-120 | Source/Access/Events/DispSectionEvents.cs:137-141 | Source/Access/Events/DispSectionEvents.cs:158-162 | Source/Access/Events/DispSectionInReportEvents.cs:177-181 | Source/Access/Events/DispSectionInReportEvents.cs:198-202 | Source/Access/Events/DispSectionInReportEvents.cs:219-223 | Source/Access/Events/DispTabControlEvents.cs:133-137 | Source/Access/Events/DispTabControlEvents.cs:154-158 | Source/Access/Events/DispTabControlEvents.cs:175-179 | Source/Access/Events/DispTextBoxEvents.cs:254-258 | Source/Access/Events/DispTextBoxEvents.cs:275-279 | Source/Access/Events/DispTextBoxEvents.cs:296-300 | Source/Access/Events/DispToggleButtonEvents.cs:229-233 | Source/Access/Events/DispToggleButtonEvents.cs:250-254 | Source/Access/Events/DispToggleButtonEvents.cs:271-275 | Source/Access/Events/DispWebBrowserControlEvents.cs:307-311 | Source/Access/Events/DispWebBrowserControlEvents.cs:328-332 | Source/Access/Events/DispWebBrowserControlEvents.cs:349-353 | Source/Access/Events/_BoundObjectFrameEvents.cs:249-253 | Source/Access/Events/_BoundObjectFrameEvents.cs:270-274 | Source/Access/Events/_BoundObjectFrameEvents.cs:291-295 | Source/Access/Events/_CheckBoxEvents.cs:229-233 | Source/Access/Events/_CheckBoxEvents.cs:250-254 | Source/Access/Events/_CheckBoxEvents.cs:271-275 | Source/Access/Events/_CheckBoxInOptionEvents.cs:124-128 | Source/Access/Events/_CheckBoxInOptionEvents.cs:145-149 | Source/Access/Events/_CheckBoxInOptionEvents.cs:166-170 | Source/Access/Events/_ComboBoxEvents.cs:276-280 | Source/Access/Events/_ComboBoxEvents.cs:297-301 | Source/Access/Events/_ComboBoxEvents.cs:318-322 | Source/Access/Events/_CommandButtonEvents.cs:193-197 | Source/Access/Events/_CommandButtonEvents.cs:214-218 | Source/Access/Events/_CommandButtonEvents.cs:235-239 | Source/Access/Events/_FormEvents.cs:586-590 | Source/Access/Events/_FormEvents.cs:607-611 | Source/Access/Events/_FormEvents.cs:628-632 | Source/Access/Events/_FormEvents2.cs:562-566 | Source/Access/Events/_FormEvents2.cs:583-587 | Source/Access/Events/_FormEvents2.cs:604-608 | Source/Access/Events/_ImageEvents.cs:112-116 | Source/Access/Events/_ImageEvents.cs:133-137 | Source/Access/Events/_ImageEvents.cs:154-158 | Source/Access/Events/_LabelEvents.cs:112-116 | Source/Access/Events/_LabelEvents.cs:133-137 | Source/Access/Events/_LabelEvents.cs:154-158 | Source/Access/Events/_ListBoxEvents.cs:228-232 | Source/Access/Events/_ListBoxEvents.cs:249-253 | Source/Access/Events/_ListBoxEvents.cs:270-274 | Source/Access/Events/_ObjectFrameEvents.cs:197-201 | Source/Access/Events/_ObjectFrameEvents.cs:218-222 | Source/Access/Events/_ObjectFrameEvents.cs:239-243 | Source/Access/Events/_OptionButtonEvents.cs:229-233 | Source/Access/Events/_OptionButtonEvents.cs:250-254 | Source/Access/Events/_OptionButtonEvents.cs:271-275 | Source/Access/Events/_OptionButtonInOptionEvents.cs:124-128 | Source/Access/Events/_OptionButtonInOptionEvents.cs:145-149 | Source/Access/Events/_OptionButtonInOptionEvents.cs:166-170 | Source/Access/Events/_OptionGroupEvents.cs:182-186 | Source/Access/Events/_OptionGroupEvents.cs:203-207 | Source/Access/Events/_OptionGroupEvents.cs:224-228 | Source/Access/Events/_PageEvents.cs:112-116 | Source/Access/Events/_PageEvents.cs:133-137 | Source/Access/Events/_PageEvents.cs:154-158 | Source/Access/Events/_PageHdrFtrInReportEvents.cs:158-162 | Source/Access/Events/_PageHdrFtrInReportEvents.cs:179-183 | Source/Access/Events/_PageHdrFtrInReportEvents.cs:200-204 | Source/Access/Events/_PaletteButtonEvents.cs:229-233 | Source/Access/Events/_PaletteButtonEvents.cs:250-254 | Source/Access/Events/_PaletteButtonEvents.cs:271-275 | Source/Access/Events/_RectangleEvents.cs:112-116 | Source/Access/Events/_RectangleEvents.cs:133-137 | Source/Access/Events/_RectangleEvents.cs:154-158 | Source/Access/Events/_ReportEvents2.cs:369-373 | Source/Access/Events/_ReportEvents2.cs:390-394 | Source/Access/Events/_ReportEvents2.cs:411-415 | Source/Access/Events/_SectionEvents.cs:117-121 | Source/Access/Events/_SectionEvents.cs:138-142 | Source/Access/Events/_SectionEvents.cs:159-163 | Source/Access/Events/_SectionInReportEvents.cs:178-182 | Source/Access/Events/_SectionInReportEvents.cs:199-203 | Source/Access/Events/_SectionInReportEvents.cs:220-224 | Source/Access/Events/_TabControlEvents.cs:133-137 | Source/Access/Events/_TabControlEvents.cs:154-158 | Source/Access/Events/_TabControlEvents.cs:175-179 | Source/Access/Events/_TextBoxEvents.cs:251-255 | Source/Access/Events/_TextBoxEvents.cs:272-276 | Source/Access/Events/_TextBoxEvents.cs:293-297 | Source/Access/Events/_ToggleButtonEvents.cs:229-233 | Source/Access/Events/_ToggleButtonEvents.cs:250-254 | Source/Access/Events/_ToggleButtonEvents.cs:271-275 | Source/Access/Events/_ToggleButtonInOptionEvents.cs:124-128 | Source/Access/Events/_ToggleButtonInOptionEvents.cs:145-149 | Source/Access/Events/_ToggleButtonInOptionEvents.cs:166-170 — before extracting anything, compare `Source/Access/Events/DispAttachmentEvents.cs` and `Source/Access/Events/DispBoundObjectFrameEvents.cs` as WHOLE FILES: this scan already matched 29 separate duplicated blocks between them, totalling at least 271 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (10 lines × 18) · ×1
  • Duplicated block (10 lines × 18) Source/Access/Events/_BoundObjectFrameEvents.cs:54 — Source/Access/Events/_BoundObjectFrameEvents.cs:54-63 | Source/Access/Events/_CheckBoxEvents.cs:49-58 | Source/Access/Events/_ComboBoxEvents.cs:58-67 | Source/Access/Events/_CommandButtonEvents.cs:39-48 | Source/Access/Events/_FormEvents.cs:97-106 | Source/Access/Events/_ImageEvents.cs:23-32 | Source/Access/Events/_LabelEvents.cs:23-32 | Source/Access/Events/_ListBoxEvents.cs:48-57 | Source/Access/Events/_ObjectFrameEvents.cs:45-54 | Source/Access/Events/_OptionButtonEvents.cs:49-58 | Source/Access/Events/_OptionGroupEvents.cs:41-50 | Source/Access/Events/_PageEvents.cs:23-32 | Source/Access/Events/_PaletteButtonEvents.cs:49-58 | Source/Access/Events/_RectangleEvents.cs:23-32 | Source/Access/Events/_SectionEvents.cs:23-32 | Source/Access/Events/_TabControlEvents.cs:23-32 | Source/Access/Events/_TextBoxEvents.cs:51-60 | Source/Access/Events/_ToggleButtonEvents.cs:49-58 — before extracting anything, compare `Source/Access/Events/_BoundObjectFrameEvents.cs` and `Source/Access/Events/_CheckBoxEvents.cs` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 292 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Access/Events/_BoundObjectFrameEvents.cs:50` calls `SupportByVersion`, `MethodImpl`, `DispId` and `Source/Access/Events/_CheckBoxEvents.cs:47` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (10 lines × 14) · ×1
  • Duplicated block (10 lines × 14) Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ClassLibraryConverterCS.cs:52 — Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ClassLibraryConverterCS.cs:52-61 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ClassLibraryConverterVB.cs:63-72 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ConsoleConverterCS.cs:52-61 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ConsoleConverterVB.cs:62-71 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleMultiAddinConverterCS.cs:57-66 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleMultiAddinConverterVB.cs:67-76 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleSingleAddinConverterCS.cs:57-66 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/SimpleSingleAddinConverterVB.cs:67-76 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsMultiAddinConverterCS.cs:57-66 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsMultiAddinConverterVB.cs:67-76 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsSingleAddinConverterCS.cs:57-66 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsSingleAddinConverterVB.cs:67-76 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/WindowsFormsConverterCS.cs:69-78 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/WindowsFormsConverterVB.cs:70-79 — before extracting anything, compare `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ClassLibraryConverterCS.cs` and `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ConsoleConverterCS.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ClassLibraryConverterVB.cs:59` calls `Replace` and `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ClassLibraryConverterCS.cs:50` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (12 lines × 12) · ×1
  • Duplicated block (12 lines × 12) Source/OWC10/Events/IChartEvents.cs:430 — Source/OWC10/Events/IChartEvents.cs:430-441 | Source/OWC10/Events/IChartEvents.cs:446-457 | Source/OWC10/Events/IChartEvents.cs:462-473 | Source/OWC10/Events/IChartEvents.cs:478-489 | Source/OWC10/Events/IPivotControlEvents.cs:410-421 | Source/OWC10/Events/IPivotControlEvents.cs:426-437 | Source/OWC10/Events/IPivotControlEvents.cs:442-453 | Source/OWC10/Events/IPivotControlEvents.cs:458-469 | Source/OWC10/Events/ISpreadsheetEventSink.cs:310-321 | Source/OWC10/Events/ISpreadsheetEventSink.cs:326-337 | Source/OWC10/Events/ISpreadsheetEventSink.cs:342-353 | Source/OWC10/Events/ISpreadsheetEventSink.cs:358-369 — before extracting anything, compare `Source/OWC10/Events/IChartEvents.cs` and `Source/OWC10/Events/IPivotControlEvents.cs` as WHOLE FILES: this scan already matched 39 separate duplicated blocks between them, totalling at least 404 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (9 lines × 6) · ×1
  • Duplicated block (9 lines × 6) Source/NetOffice/Invoker.cs:775 — Source/NetOffice/Invoker.cs:775-783 | Source/NetOffice/Invoker.cs:808-816 | Source/NetOffice/Invoker.cs:857-865 | Source/NetOffice/Invoker.cs:891-899 | Source/NetOffice/Invoker.cs:923-931 | Source/NetOffice/Invoker.cs:958-966 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/NetOffice/Invoker.cs:775` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (10–12 lines × 2) · ×1
  • Duplicated block (10–12 lines × 2) Source/Office/Events/_CustomXMLPartEvents.cs:87 — Source/Office/Events/_CustomXMLPartEvents.cs:87-98 | Source/Office/Events/_CustomXMLPartEvents.cs:107-116 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Source/Office/Events/_CustomXMLPartEvents.cs:87` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (3–12 lines × 4) · ×1
  • Duplicated block (3–12 lines × 4) Source/Access/Events/_FormEvents.cs:265 — Source/Access/Events/_FormEvents.cs:265-276 | Source/Access/Events/_FormEvents2.cs:240-251 | Source/OWC10/Events/IChartEvents.cs:144-146 | Source/OWC10/Events/IPivotControlEvents.cs:183-185 — before extracting anything, compare `Source/Access/Events/_FormEvents.cs` and `Source/Access/Events/_FormEvents2.cs` as WHOLE FILES: this scan already matched 72 separate duplicated blocks between them, totalling at least 744 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/OWC10/Events/IChartEvents.cs:144` calls `SinkArgument` and `Source/OWC10/Events/IPivotControlEvents.cs:183` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (11 lines × 22) · ×1
  • Duplicated block (11 lines × 22) Source/Outlook/Events/OlkCategoryEvents.cs:217 — Source/Outlook/Events/OlkCategoryEvents.cs:217-227 | Source/Outlook/Events/OlkCategoryEvents.cs:249-259 | Source/Outlook/Events/OlkCheckBoxEvents.cs:226-236 | Source/Outlook/Events/OlkCheckBoxEvents.cs:258-268 | Source/Outlook/Events/OlkComboBoxEvents.cs:230-240 | Source/Outlook/Events/OlkComboBoxEvents.cs:262-272 | Source/Outlook/Events/OlkCommandButtonEvents.cs:222-232 | Source/Outlook/Events/OlkCommandButtonEvents.cs:254-264 | Source/Outlook/Events/OlkContactPhotoEvents.cs:217-227 | Source/Outlook/Events/OlkContactPhotoEvents.cs:249-259 | Source/Outlook/Events/OlkDateControlEvents.cs:230-240 | Source/Outlook/Events/OlkDateControlEvents.cs:262-272 | Source/Outlook/Events/OlkListBoxEvents.cs:226-236 | Source/Outlook/Events/OlkListBoxEvents.cs:258-268 | Source/Outlook/Events/OlkOptionButtonEvents.cs:226-236 | Source/Outlook/Events/OlkOptionButtonEvents.cs:258-268 | Source/Outlook/Events/OlkTextBoxEvents.cs:226-236 | Source/Outlook/Events/OlkTextBoxEvents.cs:258-268 | Source/Outlook/Events/OlkTimeControlEvents.cs:230-240 | Source/Outlook/Events/OlkTimeControlEvents.cs:262-272 | Source/Outlook/Events/OlkTimeZoneControlEvents.cs:230-240 | Source/Outlook/Events/OlkTimeZoneControlEvents.cs:262-272 — before extracting anything, compare `Source/Outlook/Events/OlkCategoryEvents.cs` and `Source/Outlook/Events/OlkCheckBoxEvents.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 160 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (10 lines × 16) · ×1
  • Duplicated block (10 lines × 16) Source/MSComctlLib/Events/DImageComboEvents.cs:279 — Source/MSComctlLib/Events/DImageComboEvents.cs:279-288 | Source/MSComctlLib/Events/DImageComboEvents.cs:311-320 | Source/MSComctlLib/Events/IProgressBarEvents.cs:269-278 | Source/MSComctlLib/Events/IProgressBarEvents.cs:301-310 | Source/MSComctlLib/Events/ISliderEvents.cs:365-374 | Source/MSComctlLib/Events/ISliderEvents.cs:397-406 | Source/MSComctlLib/Events/IStatusBarEvents.cs:322-331 | Source/MSComctlLib/Events/IStatusBarEvents.cs:354-363 | Source/MSComctlLib/Events/ITabStripEvents.cs:355-364 | Source/MSComctlLib/Events/ITabStripEvents.cs:387-396 | Source/MSComctlLib/Events/IToolbarEvents.cs:328-337 | Source/MSComctlLib/Events/IToolbarEvents.cs:360-369 | Source/MSComctlLib/Events/ITreeViewEvents.cs:468-477 | Source/MSComctlLib/Events/ITreeViewEvents.cs:500-509 | Source/MSComctlLib/Events/ListViewEvents.cs:436-445 | Source/MSComctlLib/Events/ListViewEvents.cs:468-477 — before extracting anything, compare `Source/MSComctlLib/Events/DImageComboEvents.cs` and `Source/MSComctlLib/Events/IProgressBarEvents.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 157 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Source/MSComctlLib/Events/DImageComboEvents.cs:279` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (11 lines × 13) · ×1
  • Duplicated block (11 lines × 13) Source/Access/Events/DispWebBrowserControlEvents.cs:440 — Source/Access/Events/DispWebBrowserControlEvents.cs:440-450 | Source/Outlook/Events/ApplicationEvents.cs:75-85 | Source/Outlook/Events/ApplicationEvents_10.cs:89-99 | Source/Outlook/Events/ApplicationEvents_11.cs:146-156 | Source/Outlook/Events/ExplorerEvents.cs:104-114 | Source/Outlook/Events/ExplorerEvents_10.cs:153-163 | Source/Outlook/Events/ItemEvents.cs:175-185 | Source/Outlook/Events/ItemEvents.cs:232-242 | Source/Outlook/Events/ItemEvents.cs:249-259 | Source/Outlook/Events/ItemEvents_10.cs:232-242 | Source/Outlook/Events/ItemEvents_10.cs:289-299 | Source/Outlook/Events/ItemEvents_10.cs:306-316 | Source/Outlook/Events/ItemEvents_10.cs:413-423 — before extracting anything, compare `Source/Outlook/Events/ApplicationEvents.cs` and `Source/Outlook/Events/ApplicationEvents_10.cs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 82 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (10–11 lines × 2) · ×1
  • Duplicated block (10–11 lines × 2) Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsMultiAddinConverterCS.cs:137 — Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsMultiAddinConverterCS.cs:137-146 | Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsMultiAddinConverterVB.cs:160-170 — before extracting anything, compare `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsMultiAddinConverterCS.cs` and `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsMultiAddinConverterVB.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsMultiAddinConverterCS.cs:137` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (5 lines × 32) · ×1
  • Duplicated block (5 lines × 32) Source/MSComctlLib/Events/DImageComboEvents.cs:203 — Source/MSComctlLib/Events/DImageComboEvents.cs:203-207 | Source/MSComctlLib/Events/DImageComboEvents.cs:242-246 | Source/MSComctlLib/Events/DImageComboEvents.cs:279-283 | Source/MSComctlLib/Events/DImageComboEvents.cs:311-315 | Source/MSComctlLib/Events/IProgressBarEvents.cs:193-197 | Source/MSComctlLib/Events/IProgressBarEvents.cs:232-236 | Source/MSComctlLib/Events/IProgressBarEvents.cs:269-273 | Source/MSComctlLib/Events/IProgressBarEvents.cs:301-305 | Source/MSComctlLib/Events/ISliderEvents.cs:289-293 | Source/MSComctlLib/Events/ISliderEvents.cs:328-332 | Source/MSComctlLib/Events/ISliderEvents.cs:365-369 | Source/MSComctlLib/Events/ISliderEvents.cs:397-401 | Source/MSComctlLib/Events/IStatusBarEvents.cs:246-250 | Source/MSComctlLib/Events/IStatusBarEvents.cs:285-289 | Source/MSComctlLib/Events/IStatusBarEvents.cs:322-326 | Source/MSComctlLib/Events/IStatusBarEvents.cs:354-358 | Source/MSComctlLib/Events/ITabStripEvents.cs:279-283 | Source/MSComctlLib/Events/ITabStripEvents.cs:318-322 | Source/MSComctlLib/Events/ITabStripEvents.cs:355-359 | Source/MSComctlLib/Events/ITabStripEvents.cs:387-391 | Source/MSComctlLib/Events/IToolbarEvents.cs:252-256 | Source/MSComctlLib/Events/IToolbarEvents.cs:291-295 | Source/MSComctlLib/Events/IToolbarEvents.cs:328-332 | Source/MSComctlLib/Events/IToolbarEvents.cs:360-364 | Source/MSComctlLib/Events/ITreeViewEvents.cs:392-396 | Source/MSComctlLib/Events/ITreeViewEvents.cs:431-435 | Source/MSComctlLib/Events/ITreeViewEvents.cs:468-472 | Source/MSComctlLib/Events/ITreeViewEvents.cs:500-504 | Source/MSComctlLib/Events/ListViewEvents.cs:360-364 | Source/MSComctlLib/Events/ListViewEvents.cs:399-403 | Source/MSComctlLib/Events/ListViewEvents.cs:436-440 | Source/MSComctlLib/Events/ListViewEvents.cs:468-472 — before extracting anything, compare `Source/MSComctlLib/Events/DImageComboEvents.cs` and `Source/MSComctlLib/Events/IProgressBarEvents.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 157 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Source/MSComctlLib/Events/DImageComboEvents.cs:203` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (10 lines × 22) · ×1
  • Duplicated block (10 lines × 22) Source/OWC10/Events/_DataSourceControlEvent.cs:157 — Source/OWC10/Events/_DataSourceControlEvent.cs:157-166 | Source/OWC10/Events/_DataSourceControlEvent.cs:171-180 | Source/OWC10/Events/_DataSourceControlEvent.cs:185-194 | Source/OWC10/Events/_DataSourceControlEvent.cs:199-208 | Source/OWC10/Events/_DataSourceControlEvent.cs:213-222 | Source/OWC10/Events/_DataSourceControlEvent.cs:227-236 | Source/OWC10/Events/_DataSourceControlEvent.cs:241-250 | Source/OWC10/Events/_DataSourceControlEvent.cs:255-264 | Source/OWC10/Events/_DataSourceControlEvent.cs:269-278 | Source/OWC10/Events/_DataSourceControlEvent.cs:283-292 | Source/OWC10/Events/_DataSourceControlEvent.cs:297-306 | Source/OWC10/Events/_DataSourceControlEvent.cs:311-320 | Source/OWC10/Events/_DataSourceControlEvent.cs:325-334 | Source/OWC10/Events/_DataSourceControlEvent.cs:339-348 | Source/OWC10/Events/_DataSourceControlEvent.cs:353-362 | Source/OWC10/Events/_DataSourceControlEvent.cs:367-376 | Source/OWC10/Events/_DataSourceControlEvent.cs:381-390 | Source/OWC10/Events/_DataSourceControlEvent.cs:395-404 | Source/OWC10/Events/_DataSourceControlEvent.cs:409-418 | Source/OWC10/Events/_DataSourceControlEvent.cs:423-432 | Source/OWC10/Events/_DataSourceControlEvent.cs:437-446 | Source/OWC10/Events/_DataSourceControlEvent.cs:451-460 — all 22 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (10 lines × 13) · ×1
  • Duplicated block (10 lines × 13) Source/Word/Events/ApplicationEvents2.cs:216 — Source/Word/Events/ApplicationEvents2.cs:216-225 | Source/Word/Events/ApplicationEvents3.cs:281-290 | Source/Word/Events/ApplicationEvents3.cs:375-384 | Source/Word/Events/ApplicationEvents3.cs:389-398 | Source/Word/Events/ApplicationEvents3.cs:419-428 | Source/Word/Events/ApplicationEvents3.cs:471-480 | Source/Word/Events/ApplicationEvents3.cs:502-511 | Source/Word/Events/ApplicationEvents4.cs:354-363 | Source/Word/Events/ApplicationEvents4.cs:448-457 | Source/Word/Events/ApplicationEvents4.cs:462-471 | Source/Word/Events/ApplicationEvents4.cs:492-501 | Source/Word/Events/ApplicationEvents4.cs:544-553 | Source/Word/Events/ApplicationEvents4.cs:575-584 — before extracting anything, compare `Source/Word/Events/ApplicationEvents2.cs` and `Source/Word/Events/ApplicationEvents3.cs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 270 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (8 lines × 9) · ×1
  • Duplicated block (8 lines × 9) Source/Outlook/Events/OlkCheckBoxEvents.cs:81 — Source/Outlook/Events/OlkCheckBoxEvents.cs:81-88 | Source/Outlook/Events/OlkComboBoxEvents.cs:85-92 | Source/Outlook/Events/OlkCommandButtonEvents.cs:77-84 | Source/Outlook/Events/OlkDateControlEvents.cs:85-92 | Source/Outlook/Events/OlkListBoxEvents.cs:81-88 | Source/Outlook/Events/OlkOptionButtonEvents.cs:81-88 | Source/Outlook/Events/OlkTextBoxEvents.cs:81-88 | Source/Outlook/Events/OlkTimeControlEvents.cs:85-92 | Source/Outlook/Events/OlkTimeZoneControlEvents.cs:85-92 — before extracting anything, compare `Source/Outlook/Events/OlkCheckBoxEvents.cs` and `Source/Outlook/Events/OlkComboBoxEvents.cs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 189 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Outlook/Events/OlkComboBoxEvents.cs:81` calls `SupportByVersion`, `MethodImpl`, `DispId` and `Source/Outlook/Events/OlkCheckBoxEvents.cs:79` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (10 lines × 9) · ×1
  • Duplicated block (10 lines × 9) Source/PowerPoint/Events/EApplication.cs:273 — Source/PowerPoint/Events/EApplication.cs:273-282 | Source/PowerPoint/Events/EApplication.cs:287-296 | Source/PowerPoint/Events/EApplication.cs:301-310 | Source/PowerPoint/Events/EApplication.cs:315-324 | Source/PowerPoint/Events/EApplication.cs:417-426 | Source/PowerPoint/Events/EApplication.cs:431-440 | Source/PowerPoint/Events/EApplication.cs:506-515 | Source/PowerPoint/Events/EApplication.cs:520-529 | Source/PowerPoint/Events/EApplication.cs:673-682 — all 9 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (6–10 lines × 8) · ×1
  • Duplicated block (6–10 lines × 8) Source/Outlook/Events/ExplorerEvents_10.cs:57 — Source/Outlook/Events/ExplorerEvents_10.cs:57-66 | Source/Outlook/Events/ExplorerEvents_10.cs:67-76 | Source/Outlook/Events/ExplorerEvents_10.cs:77-82 | Source/Outlook/Events/InspectorEvents_10.cs:34-43 | Source/Outlook/Events/InspectorEvents_10.cs:44-49 | Source/Outlook/Events/ItemEvents_10.cs:40-45 | Source/Outlook/Events/ItemEvents_10.cs:66-75 | Source/Outlook/Events/ItemEvents_10.cs:76-81 — before extracting anything, compare `Source/Outlook/Events/ExplorerEvents_10.cs` and `Source/Outlook/Events/InspectorEvents_10.cs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 130 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (6–10 lines × 4) · ×1
  • Duplicated block (6–10 lines × 4) Source/Access/Events/_ComboBoxEvents.cs:107 — Source/Access/Events/_ComboBoxEvents.cs:107-112 | Source/Access/Events/_FormEvents.cs:168-177 | Source/Access/Events/_FormEvents.cs:178-187 | Source/Access/Events/_TextBoxEvents.cs:100-105 — before extracting anything, compare `Source/Access/Events/_ComboBoxEvents.cs` and `Source/Access/Events/_FormEvents.cs` as WHOLE FILES: this scan already matched 31 separate duplicated blocks between them, totalling at least 285 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (9 lines × 45) · ×1
  • Duplicated block (9 lines × 45) Source/Outlook/Events/OlkBusinessCardControlEvents.cs:101 — Source/Outlook/Events/OlkBusinessCardControlEvents.cs:101-109 | Source/Outlook/Events/OlkBusinessCardControlEvents.cs:121-129 | Source/Outlook/Events/OlkBusinessCardControlEvents.cs:141-149 | Source/Outlook/Events/OlkCategoryEvents.cs:131-139 | Source/Outlook/Events/OlkCategoryEvents.cs:151-159 | Source/Outlook/Events/OlkCategoryEvents.cs:171-179 | Source/Outlook/Events/OlkCheckBoxEvents.cs:140-148 | Source/Outlook/Events/OlkCheckBoxEvents.cs:160-168 | Source/Outlook/Events/OlkCheckBoxEvents.cs:180-188 | Source/Outlook/Events/OlkComboBoxEvents.cs:144-152 | Source/Outlook/Events/OlkComboBoxEvents.cs:164-172 | Source/Outlook/Events/OlkComboBoxEvents.cs:184-192 | Source/Outlook/Events/OlkCommandButtonEvents.cs:136-144 | Source/Outlook/Events/OlkCommandButtonEvents.cs:156-164 | Source/Outlook/Events/OlkCommandButtonEvents.cs:176-184 | Source/Outlook/Events/OlkContactPhotoEvents.cs:131-139 | Source/Outlook/Events/OlkContactPhotoEvents.cs:151-159 | Source/Outlook/Events/OlkContactPhotoEvents.cs:171-179 | Source/Outlook/Events/OlkDateControlEvents.cs:144-152 | Source/Outlook/Events/OlkDateControlEvents.cs:164-172 | Source/Outlook/Events/OlkDateControlEvents.cs:184-192 | Source/Outlook/Events/OlkInfoBarEvents.cs:101-109 | Source/Outlook/Events/OlkInfoBarEvents.cs:121-129 | Source/Outlook/Events/OlkInfoBarEvents.cs:141-149 | Source/Outlook/Events/OlkLabelEvents.cs:101-109 | Source/Outlook/Events/OlkLabelEvents.cs:121-129 | Source/Outlook/Events/OlkLabelEvents.cs:141-149 | Source/Outlook/Events/OlkListBoxEvents.cs:140-148 | Source/Outlook/Events/OlkListBoxEvents.cs:160-168 | Source/Outlook/Events/OlkListBoxEvents.cs:180-188 | Source/Outlook/Events/OlkOptionButtonEvents.cs:140-148 | Source/Outlook/Events/OlkOptionButtonEvents.cs:160-168 | Source/Outlook/Events/OlkOptionButtonEvents.cs:180-188 | Source/Outlook/Events/OlkSenderPhotoEvents.cs:105-113 | Source/Outlook/Events/OlkSenderPhotoEvents.cs:125-133 | Source/Outlook/Events/OlkSenderPhotoEvents.cs:145-153 | Source/Outlook/Events/OlkTextBoxEvents.cs:140-148 | Source/Outlook/Events/OlkTextBoxEvents.cs:160-168 | Source/Outlook/Events/OlkTextBoxEvents.cs:180-188 | Source/Outlook/Events/OlkTimeControlEvents.cs:144-152 | Source/Outlook/Events/OlkTimeControlEvents.cs:164-172 | Source/Outlook/Events/OlkTimeControlEvents.cs:184-192 | Source/Outlook/Events/OlkTimeZoneControlEvents.cs:144-152 | Source/Outlook/Events/OlkTimeZoneControlEvents.cs:164-172 | Source/Outlook/Events/OlkTimeZoneControlEvents.cs:184-192 — before extracting anything, compare `Source/Outlook/Events/OlkBusinessCardControlEvents.cs` and `Source/Outlook/Events/OlkCategoryEvents.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 61 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (9 lines × 35) · ×1
  • Duplicated block (9 lines × 35) Source/Excel/Events/ChartEvents.cs:161 — Source/Excel/Events/ChartEvents.cs:161-169 | Source/Excel/Events/ChartEvents.cs:181-189 | Source/Excel/Events/ChartEvents.cs:201-209 | Source/Excel/Events/WorkbookEvents.cs:786-794 | Source/MSComctlLib/Events/IProgressBarEvents.cs:126-134 | Source/MSComctlLib/Events/IProgressBarEvents.cs:146-154 | Source/MSComctlLib/Events/IProgressBarEvents.cs:166-174 | Source/MSComctlLib/Events/ISliderEvents.cs:211-219 | Source/MSComctlLib/Events/ISliderEvents.cs:231-239 | Source/MSComctlLib/Events/ISliderEvents.cs:251-259 | Source/MSComctlLib/Events/IStatusBarEvents.cs:168-176 | Source/MSComctlLib/Events/IStatusBarEvents.cs:188-196 | Source/MSComctlLib/Events/IStatusBarEvents.cs:208-216 | Source/MSComctlLib/Events/ITabStripEvents.cs:208-216 | Source/MSComctlLib/Events/ITabStripEvents.cs:228-236 | Source/MSComctlLib/Events/ITabStripEvents.cs:248-256 | Source/MSComctlLib/Events/IToolbarEvents.cs:185-193 | Source/MSComctlLib/Events/IToolbarEvents.cs:205-213 | Source/MSComctlLib/Events/IToolbarEvents.cs:225-233 | Source/MSComctlLib/Events/ITreeViewEvents.cs:300-308 | Source/MSComctlLib/Events/ITreeViewEvents.cs:320-328 | Source/MSComctlLib/Events/ITreeViewEvents.cs:340-348 | Source/MSComctlLib/Events/ListViewEvents.cs:282-290 | Source/MSComctlLib/Events/ListViewEvents.cs:302-310 | Source/MSComctlLib/Events/ListViewEvents.cs:322-330 | Source/OWC10/Events/IChartEvents.cs:334-342 | Source/OWC10/Events/IChartEvents.cs:354-362 | Source/OWC10/Events/IChartEvents.cs:374-382 | Source/OWC10/Events/IPivotControlEvents.cs:319-327 | Source/OWC10/Events/IPivotControlEvents.cs:339-347 | Source/OWC10/Events/IPivotControlEvents.cs:359-367 | Source/OWC10/Events/ISpreadsheetEventSink.cs:496-504 | Source/OWC10/Events/ISpreadsheetEventSink.cs:516-524 | Source/OWC10/Events/ISpreadsheetEventSink.cs:536-544 | Source/Outlook/Events/SyncObjectEvents.cs:87-95 — there are 35 copies across 13 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 35 sites; resolving a subset leaves the remainder to drift apart.
D4 · Code Duplication · Duplicated block (7 lines × 14) · ×1
  • Duplicated block (7 lines × 14) Source/Access/Events/DispAttachmentEvents.cs:46 — Source/Access/Events/DispAttachmentEvents.cs:46-52 | Source/Access/Events/DispBoundObjectFrameEvents.cs:42-48 | Source/Access/Events/DispCheckBoxEvents.cs:41-47 | Source/Access/Events/DispComboBoxEvents.cs:47-53 | Source/Access/Events/DispCommandButtonEvents.cs:31-37 | Source/Access/Events/DispCustomControlEvents.cs:33-39 | Source/Access/Events/DispListBoxEvents.cs:37-43 | Source/Access/Events/DispObjectFrameEvents.cs:33-39 | Source/Access/Events/DispOptionButtonEvents.cs:40-46 | Source/Access/Events/DispPaletteButtonEvents.cs:41-47 | Source/Access/Events/DispTextBoxEvents.cs:41-47 | Source/Access/Events/DispToggleButtonEvents.cs:41-47 | Source/Access/Events/_FormEvents2.cs:87-93 | Source/Access/Events/_ReportEvents2.cs:68-74 — before extracting anything, compare `Source/Access/Events/DispAttachmentEvents.cs` and `Source/Access/Events/DispBoundObjectFrameEvents.cs` as WHOLE FILES: this scan already matched 29 separate duplicated blocks between them, totalling at least 271 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Access/Events/DispBoundObjectFrameEvents.cs:38` calls `SinkArgument` and `Source/Access/Events/DispCommandButtonEvents.cs:27` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (5 lines × 72) · ×1
  • Duplicated block (5 lines × 72) Source/Access/Events/DispAttachmentEvents.cs:63 — Source/Access/Events/DispAttachmentEvents.cs:63-67 | Source/Access/Events/DispAttachmentEvents.cs:71-75 | Source/Access/Events/DispAttachmentEvents.cs:79-83 | Source/Access/Events/DispBoundObjectFrameEvents.cs:59-63 | Source/Access/Events/DispBoundObjectFrameEvents.cs:67-71 | Source/Access/Events/DispBoundObjectFrameEvents.cs:75-79 | Source/Access/Events/DispCheckBoxEvents.cs:54-58 | Source/Access/Events/DispCheckBoxEvents.cs:62-66 | Source/Access/Events/DispCheckBoxEvents.cs:70-74 | Source/Access/Events/DispComboBoxEvents.cs:64-68 | Source/Access/Events/DispComboBoxEvents.cs:72-76 | Source/Access/Events/DispComboBoxEvents.cs:80-84 | Source/Access/Events/DispCommandButtonEvents.cs:44-48 | Source/Access/Events/DispCommandButtonEvents.cs:52-56 | Source/Access/Events/DispCommandButtonEvents.cs:60-64 | Source/Access/Events/DispImageEvents.cs:28-32 | Source/Access/Events/DispImageEvents.cs:36-40 | Source/Access/Events/DispImageEvents.cs:44-48 | Source/Access/Events/DispLabelEvents.cs:28-32 | Source/Access/Events/DispLabelEvents.cs:36-40 | Source/Access/Events/DispLabelEvents.cs:44-48 | Source/Access/Events/DispListBoxEvents.cs:54-58 | Source/Access/Events/DispListBoxEvents.cs:62-66 | Source/Access/Events/DispListBoxEvents.cs:70-74 | Source/Access/Events/DispObjectFrameEvents.cs:50-54 | Source/Access/Events/DispObjectFrameEvents.cs:58-62 | Source/Access/Events/DispObjectFrameEvents.cs:66-70 | Source/Access/Events/DispOptionButtonEvents.cs:52-56 | Source/Access/Events/DispOptionButtonEvents.cs:60-64 | Source/Access/Events/DispOptionButtonEvents.cs:68-72 | Source/Access/Events/DispOptionGroupEvents.cs:46-50 | Source/Access/Events/DispOptionGroupEvents.cs:54-58 | Source/Access/Events/DispOptionGroupEvents.cs:62-66 | Source/Access/Events/DispPageEvents.cs:28-32 | Source/Access/Events/DispPageEvents.cs:36-40 | Source/Access/Events/DispPageEvents.cs:44-48 | Source/Access/Events/DispPageHdrFtrInReportEvents.cs:40-44 | Source/Access/Events/DispPageHdrFtrInReportEvents.cs:48-52 | Source/Access/Events/DispPageHdrFtrInReportEvents.cs:56-60 | Source/Access/Events/DispPaletteButtonEvents.cs:54-58 | Source/Access/Events/DispPaletteButtonEvents.cs:62-66 | Source/Access/Events/DispPaletteButtonEvents.cs:70-74 | Source/Access/Events/DispRectangleEvents.cs:28-32 | Source/Access/Events/DispRectangleEvents.cs:36-40 | Source/Access/Events/DispRectangleEvents.cs:44-48 | Source/Access/Events/DispSectionEvents.cs:28-32 | Source/Access/Events/DispSectionEvents.cs:36-40 | Source/Access/Events/DispSectionEvents.cs:44-48 | Source/Access/Events/DispSectionInReportEvents.cs:44-48 | Source/Access/Events/DispSectionInReportEvents.cs:52-56 | Source/Access/Events/DispSectionInReportEvents.cs:60-64 | Source/Access/Events/DispTabControlEvents.cs:28-32 | Source/Access/Events/DispTabControlEvents.cs:36-40 | Source/Access/Events/DispTabControlEvents.cs:44-48 | Source/Access/Events/DispTextBoxEvents.cs:58-62 | Source/Access/Events/DispTextBoxEvents.cs:66-70 | Source/Access/Events/DispTextBoxEvents.cs:74-78 | Source/Access/Events/DispToggleButtonEvents.cs:54-58 | Source/Access/Events/DispToggleButtonEvents.cs:62-66 | Source/Access/Events/DispToggleButtonEvents.cs:70-74 | Source/Access/Events/_FormEvents2.cs:104-108 | Source/Access/Events/_FormEvents2.cs:112-116 | Source/Access/Events/_FormEvents2.cs:120-124 | Source/Access/Events/_PageHdrFtrInReportEvents.cs:40-44 | Source/Access/Events/_PageHdrFtrInReportEvents.cs:48-52 | Source/Access/Events/_PageHdrFtrInReportEvents.cs:56-60 | Source/Access/Events/_ReportEvents2.cs:85-89 | Source/Access/Events/_ReportEvents2.cs:93-97 | Source/Access/Events/_ReportEvents2.cs:101-105 | Source/Access/Events/_SectionInReportEvents.cs:44-48 | Source/Access/Events/_SectionInReportEvents.cs:52-56 | Source/Access/Events/_SectionInReportEvents.cs:60-64 — before extracting anything, compare `Source/Access/Events/DispAttachmentEvents.cs` and `Source/Access/Events/DispBoundObjectFrameEvents.cs` as WHOLE FILES: this scan already matched 29 separate duplicated blocks between them, totalling at least 271 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Access/Events/DispCheckBoxEvents.cs:50` calls `SinkArgument` and `Source/Access/Events/DispOptionButtonEvents.cs:48` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (5 lines × 63) · ×1
  • Duplicated block (5 lines × 63) Source/Access/Events/_BoundObjectFrameEvents.cs:59 — Source/Access/Events/_BoundObjectFrameEvents.cs:59-63 | Source/Access/Events/_BoundObjectFrameEvents.cs:67-71 | Source/Access/Events/_BoundObjectFrameEvents.cs:75-79 | Source/Access/Events/_CheckBoxEvents.cs:54-58 | Source/Access/Events/_CheckBoxEvents.cs:62-66 | Source/Access/Events/_CheckBoxEvents.cs:70-74 | Source/Access/Events/_CheckBoxInOptionEvents.cs:27-31 | Source/Access/Events/_CheckBoxInOptionEvents.cs:35-39 | Source/Access/Events/_CheckBoxInOptionEvents.cs:43-47 | Source/Access/Events/_ComboBoxEvents.cs:63-67 | Source/Access/Events/_ComboBoxEvents.cs:71-75 | Source/Access/Events/_ComboBoxEvents.cs:79-83 | Source/Access/Events/_CommandButtonEvents.cs:44-48 | Source/Access/Events/_CommandButtonEvents.cs:52-56 | Source/Access/Events/_CommandButtonEvents.cs:60-64 | Source/Access/Events/_FormEvents.cs:102-106 | Source/Access/Events/_FormEvents.cs:110-114 | Source/Access/Events/_FormEvents.cs:118-122 | Source/Access/Events/_ImageEvents.cs:28-32 | Source/Access/Events/_ImageEvents.cs:36-40 | Source/Access/Events/_ImageEvents.cs:44-48 | Source/Access/Events/_LabelEvents.cs:28-32 | Source/Access/Events/_LabelEvents.cs:36-40 | Source/Access/Events/_LabelEvents.cs:44-48 | Source/Access/Events/_ListBoxEvents.cs:53-57 | Source/Access/Events/_ListBoxEvents.cs:61-65 | Source/Access/Events/_ListBoxEvents.cs:69-73 | Source/Access/Events/_ObjectFrameEvents.cs:50-54 | Source/Access/Events/_ObjectFrameEvents.cs:58-62 | Source/Access/Events/_ObjectFrameEvents.cs:66-70 | Source/Access/Events/_OptionButtonEvents.cs:54-58 | Source/Access/Events/_OptionButtonEvents.cs:62-66 | Source/Access/Events/_OptionButtonEvents.cs:70-74 | Source/Access/Events/_OptionButtonInOptionEvents.cs:27-31 | Source/Access/Events/_OptionButtonInOptionEvents.cs:35-39 | Source/Access/Events/_OptionButtonInOptionEvents.cs:43-47 | Source/Access/Events/_OptionGroupEvents.cs:46-50 | Source/Access/Events/_OptionGroupEvents.cs:54-58 | Source/Access/Events/_OptionGroupEvents.cs:62-66 | Source/Access/Events/_PageEvents.cs:28-32 | Source/Access/Events/_PageEvents.cs:36-40 | Source/Access/Events/_PageEvents.cs:44-48 | Source/Access/Events/_PaletteButtonEvents.cs:54-58 | Source/Access/Events/_PaletteButtonEvents.cs:62-66 | Source/Access/Events/_PaletteButtonEvents.cs:70-74 | Source/Access/Events/_RectangleEvents.cs:28-32 | Source/Access/Events/_RectangleEvents.cs:36-40 | Source/Access/Events/_RectangleEvents.cs:44-48 | Source/Access/Events/_SectionEvents.cs:28-32 | Source/Access/Events/_SectionEvents.cs:36-40 | Source/Access/Events/_SectionEvents.cs:44-48 | Source/Access/Events/_TabControlEvents.cs:28-32 | Source/Access/Events/_TabControlEvents.cs:36-40 | Source/Access/Events/_TabControlEvents.cs:44-48 | Source/Access/Events/_TextBoxEvents.cs:56-60 | Source/Access/Events/_TextBoxEvents.cs:64-68 | Source/Access/Events/_TextBoxEvents.cs:72-76 | Source/Access/Events/_ToggleButtonEvents.cs:54-58 | Source/Access/Events/_ToggleButtonEvents.cs:62-66 | Source/Access/Events/_ToggleButtonEvents.cs:70-74 | Source/Access/Events/_ToggleButtonInOptionEvents.cs:27-31 | Source/Access/Events/_ToggleButtonInOptionEvents.cs:35-39 | Source/Access/Events/_ToggleButtonInOptionEvents.cs:43-47 — before extracting anything, compare `Source/Access/Events/_BoundObjectFrameEvents.cs` and `Source/Access/Events/_CheckBoxEvents.cs` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 292 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (5 lines × 20) · ×1
  • Duplicated block (5 lines × 20) Source/MSComctlLib/Events/IProgressBarEvents.cs:27 — Source/MSComctlLib/Events/IProgressBarEvents.cs:27-31 | Source/MSComctlLib/Events/IProgressBarEvents.cs:35-39 | Source/MSComctlLib/Events/ISliderEvents.cs:40-44 | Source/MSComctlLib/Events/ISliderEvents.cs:48-52 | Source/MSComctlLib/Events/ISliderEvents.cs:56-60 | Source/MSComctlLib/Events/IStatusBarEvents.cs:29-33 | Source/MSComctlLib/Events/IStatusBarEvents.cs:37-41 | Source/MSComctlLib/Events/IStatusBarEvents.cs:45-49 | Source/MSComctlLib/Events/ITabStripEvents.cs:40-44 | Source/MSComctlLib/Events/ITabStripEvents.cs:48-52 | Source/MSComctlLib/Events/ITabStripEvents.cs:56-60 | Source/MSComctlLib/Events/IToolbarEvents.cs:32-36 | Source/MSComctlLib/Events/IToolbarEvents.cs:40-44 | Source/MSComctlLib/Events/IToolbarEvents.cs:48-52 | Source/MSComctlLib/Events/ITreeViewEvents.cs:62-66 | Source/MSComctlLib/Events/ITreeViewEvents.cs:70-74 | Source/MSComctlLib/Events/ITreeViewEvents.cs:78-82 | Source/MSComctlLib/Events/ListViewEvents.cs:57-61 | Source/MSComctlLib/Events/ListViewEvents.cs:65-69 | Source/MSComctlLib/Events/ListViewEvents.cs:73-77 — before extracting anything, compare `Source/MSComctlLib/Events/IProgressBarEvents.cs` and `Source/MSComctlLib/Events/ISliderEvents.cs` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 197 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (6 lines × 16) · ×1
  • Duplicated block (6 lines × 16) Source/Word/Events/ApplicationEvents2.cs:166 — Source/Word/Events/ApplicationEvents2.cs:166-171 | Source/Word/Events/ApplicationEvents2.cs:183-188 | Source/Word/Events/ApplicationEvents2.cs:200-205 | Source/Word/Events/ApplicationEvents3.cs:231-236 | Source/Word/Events/ApplicationEvents3.cs:248-253 | Source/Word/Events/ApplicationEvents3.cs:265-270 | Source/Word/Events/ApplicationEvents3.cs:457-462 | Source/Word/Events/ApplicationEvents3.cs:488-493 | Source/Word/Events/ApplicationEvents3.cs:519-524 | Source/Word/Events/ApplicationEvents4.cs:304-309 | Source/Word/Events/ApplicationEvents4.cs:321-326 | Source/Word/Events/ApplicationEvents4.cs:338-343 | Source/Word/Events/ApplicationEvents4.cs:530-535 | Source/Word/Events/ApplicationEvents4.cs:561-566 | Source/Word/Events/ApplicationEvents4.cs:592-597 | Source/Word/Events/ApplicationEvents4.cs:715-720 — before extracting anything, compare `Source/Word/Events/ApplicationEvents2.cs` and `Source/Word/Events/ApplicationEvents3.cs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 270 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Source/Word/Events/ApplicationEvents2.cs:166` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Source/Word/Events/ApplicationEvents2.cs:207` calls `SetValue` and `Source/Word/Events/ApplicationEvents2.cs:173` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (7–8 lines × 10) · ×1
  • Duplicated block (7–8 lines × 10) Source/ADODB/Events/RecordsetEvents.cs:138 — Source/ADODB/Events/RecordsetEvents.cs:138-145 | Source/ADODB/Events/RecordsetEvents.cs:160-166 | Source/ADODB/Events/RecordsetEvents.cs:181-187 | Source/ADODB/Events/RecordsetEvents.cs:202-208 | Source/ADODB/Events/RecordsetEvents.cs:222-228 | Source/ADODB/Events/RecordsetEvents.cs:242-248 | Source/ADODB/Events/RecordsetEvents.cs:261-267 | Source/ADODB/Events/RecordsetEvents.cs:280-286 | Source/ADODB/Events/RecordsetEvents.cs:319-325 | Source/ADODB/Events/RecordsetEvents.cs:338-344 — all 10 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (7–8 lines × 5) · ×1
  • Duplicated block (7–8 lines × 5) Source/NetOffice/CoreExtensions/CorePropertySetExtensions.cs:109 — Source/NetOffice/CoreExtensions/CorePropertySetExtensions.cs:109-115 | Source/NetOffice/CoreExtensions/CorePropertySetExtensions.cs:205-211 | Source/NetOffice/CoreExtensions/CorePropertySetExtensions.cs:398-404 | Source/NetOffice/CoreExtensions/CorePropertySetExtensions.cs:494-500 | Source/NetOffice/CoreExtensions/CorePropertySetExtensions.cs:687-694 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (4–8 lines × 3) · ×1
  • Duplicated block (4–8 lines × 3) Source/Excel/Events/AppEvents.cs:221 — Source/Excel/Events/AppEvents.cs:221-228 | Source/Excel/Events/AppEvents.cs:230-237 | Source/Excel/Events/WorkbookEvents.cs:199-202 — before extracting anything, compare `Source/Excel/Events/AppEvents.cs` and `Source/Excel/Events/WorkbookEvents.cs` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 377 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Excel/Events/AppEvents.cs:229` calls `MethodImpl`, `DispId`, `SheetPivotTableBeforeCommitChanges` and `Source/Excel/Events/WorkbookEvents.cs:199` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (7–8 lines × 2) · ×1
  • Duplicated block (7–8 lines × 2) RegAddin/RegAddin/RegFile/RegFileOperationHost.cs:256 — RegAddin/RegAddin/RegFile/RegFileOperationHost.cs:256-263 | RegAddin/RegAddin/RegFile/RegFileOperationHost.cs:267-273 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (7 lines × 144) · ×1
  • Duplicated block (7 lines × 144) Source/Access/Events/DispAttachmentEvents.cs:63 — Source/Access/Events/DispAttachmentEvents.cs:63-69 | Source/Access/Events/DispAttachmentEvents.cs:71-77 | Source/Access/Events/DispAttachmentEvents.cs:79-85 | Source/Access/Events/DispBoundObjectFrameEvents.cs:59-65 | Source/Access/Events/DispBoundObjectFrameEvents.cs:67-73 | Source/Access/Events/DispBoundObjectFrameEvents.cs:75-81 | Source/Access/Events/DispCheckBoxEvents.cs:54-60 | Source/Access/Events/DispCheckBoxEvents.cs:62-68 | Source/Access/Events/DispCheckBoxEvents.cs:70-76 | Source/Access/Events/DispComboBoxEvents.cs:64-70 | Source/Access/Events/DispComboBoxEvents.cs:72-78 | Source/Access/Events/DispComboBoxEvents.cs:80-86 | Source/Access/Events/DispCommandButtonEvents.cs:44-50 | Source/Access/Events/DispCommandButtonEvents.cs:52-58 | Source/Access/Events/DispCommandButtonEvents.cs:60-66 | Source/Access/Events/DispImageEvents.cs:28-34 | Source/Access/Events/DispImageEvents.cs:36-42 | Source/Access/Events/DispImageEvents.cs:44-50 | Source/Access/Events/DispLabelEvents.cs:28-34 | Source/Access/Events/DispLabelEvents.cs:36-42 | Source/Access/Events/DispLabelEvents.cs:44-50 | Source/Access/Events/DispListBoxEvents.cs:54-60 | Source/Access/Events/DispListBoxEvents.cs:62-68 | Source/Access/Events/DispListBoxEvents.cs:70-76 | Source/Access/Events/DispNavigationButtonEvents.cs:45-51 | Source/Access/Events/DispNavigationButtonEvents.cs:53-59 | Source/Access/Events/DispNavigationButtonEvents.cs:61-67 | Source/Access/Events/DispNavigationControlEvents.cs:58-64 | Source/Access/Events/DispNavigationControlEvents.cs:66-72 | Source/Access/Events/DispNavigationControlEvents.cs:74-80 | Source/Access/Events/DispObjectFrameEvents.cs:50-56 | Source/Access/Events/DispObjectFrameEvents.cs:58-64 | Source/Access/Events/DispObjectFrameEvents.cs:66-72 | Source/Access/Events/DispOptionButtonEvents.cs:52-58 | Source/Access/Events/DispOptionButtonEvents.cs:60-66 | Source/Access/Events/DispOptionButtonEvents.cs:68-74 | Source/Access/Events/DispOptionGroupEvents.cs:46-52 | Source/Access/Events/DispOptionGroupEvents.cs:54-60 | Source/Access/Events/DispOptionGroupEvents.cs:62-68 | Source/Access/Events/DispPageEvents.cs:28-34 | Source/Access/Events/DispPageEvents.cs:36-42 | Source/Access/Events/DispPageEvents.cs:44-50 | Source/Access/Events/DispPageHdrFtrInReportEvents.cs:40-46 | Source/Access/Events/DispPageHdrFtrInReportEvents.cs:48-54 | Source/Access/Events/DispPageHdrFtrInReportEvents.cs:56-62 | Source/Access/Events/DispPaletteButtonEvents.cs:54-60 | Source/Access/Events/DispPaletteButtonEvents.cs:62-68 | Source/Access/Events/DispPaletteButtonEvents.cs:70-76 | Source/Access/Events/DispRectangleEvents.cs:28-34 | Source/Access/Events/DispRectangleEvents.cs:36-42 | Source/Access/Events/DispRectangleEvents.cs:44-50 | Source/Access/Events/DispSectionEvents.cs:28-34 | Source/Access/Events/DispSectionEvents.cs:36-42 | Source/Access/Events/DispSectionEvents.cs:44-50 | Source/Access/Events/DispSectionInReportEvents.cs:44-50 | Source/Access/Events/DispSectionInReportEvents.cs:52-58 | Source/Access/Events/DispSectionInReportEvents.cs:60-66 | Source/Access/Events/DispTabControlEvents.cs:28-34 | Source/Access/Events/DispTabControlEvents.cs:36-42 | Source/Access/Events/DispTabControlEvents.cs:44-50 | Source/Access/Events/DispTextBoxEvents.cs:58-64 | Source/Access/Events/DispTextBoxEvents.cs:66-72 | Source/Access/Events/DispTextBoxEvents.cs:74-80 | Source/Access/Events/DispToggleButtonEvents.cs:54-60 | Source/Access/Events/DispToggleButtonEvents.cs:62-68 | Source/Access/Events/DispToggleButtonEvents.cs:70-76 | Source/Access/Events/DispWebBrowserControlEvents.cs:68-74 | Source/Access/Events/DispWebBrowserControlEvents.cs:76-82 | Source/Access/Events/DispWebBrowserControlEvents.cs:84-90 | Source/Access/Events/_BoundObjectFrameEvents.cs:59-65 | Source/Access/Events/_BoundObjectFrameEvents.cs:67-73 | Source/Access/Events/_BoundObjectFrameEvents.cs:75-81 | Source/Access/Events/_CheckBoxEvents.cs:54-60 | Source/Access/Events/_CheckBoxEvents.cs:62-68 | Source/Access/Events/_CheckBoxEvents.cs:70-76 | Source/Access/Events/_CheckBoxInOptionEvents.cs:27-33 | Source/Access/Events/_CheckBoxInOptionEvents.cs:35-41 | Source/Access/Events/_CheckBoxInOptionEvents.cs:43-49 | Source/Access/Events/_ComboBoxEvents.cs:63-69 | Source/Access/Events/_ComboBoxEvents.cs:71-77 | Source/Access/Events/_ComboBoxEvents.cs:79-85 | Source/Access/Events/_CommandButtonEvents.cs:44-50 | Source/Access/Events/_CommandButtonEvents.cs:52-58 | Source/Access/Events/_CommandButtonEvents.cs:60-66 | Source/Access/Events/_FormEvents.cs:102-108 | Source/Access/Events/_FormEvents.cs:110-116 | Source/Access/Events/_FormEvents.cs:118-124 | Source/Access/Events/_FormEvents2.cs:104-110 | Source/Access/Events/_FormEvents2.cs:112-118 | Source/Access/Events/_FormEvents2.cs:120-126 | Source/Access/Events/_ImageEvents.cs:28-34 | Source/Access/Events/_ImageEvents.cs:36-42 | Source/Access/Events/_ImageEvents.cs:44-50 | Source/Access/Events/_LabelEvents.cs:28-34 | Source/Access/Events/_LabelEvents.cs:36-42 | Source/Access/Events/_LabelEvents.cs:44-50 | Source/Access/Events/_ListBoxEvents.cs:53-59 | Source/Access/Events/_ListBoxEvents.cs:61-67 | Source/Access/Events/_ListBoxEvents.cs:69-75 | Source/Access/Events/_ObjectFrameEvents.cs:50-56 | Source/Access/Events/_ObjectFrameEvents.cs:58-64 | Source/Access/Events/_ObjectFrameEvents.cs:66-72 | Source/Access/Events/_OptionButtonEvents.cs:54-60 | Source/Access/Events/_OptionButtonEvents.cs:62-68 | Source/Access/Events/_OptionButtonEvents.cs:70-76 | Source/Access/Events/_OptionButtonInOptionEvents.cs:27-33 | Source/Access/Events/_OptionButtonInOptionEvents.cs:35-41 | Source/Access/Events/_OptionButtonInOptionEvents.cs:43-49 | Source/Access/Events/_OptionGroupEvents.cs:46-52 | Source/Access/Events/_OptionGroupEvents.cs:54-60 | Source/Access/Events/_OptionGroupEvents.cs:62-68 | Source/Access/Events/_PageEvents.cs:28-34 | Source/Access/Events/_PageEvents.cs:36-42 | Source/Access/Events/_PageEvents.cs:44-50 | Source/Access/Events/_PageHdrFtrInReportEvents.cs:40-46 | Source/Access/Events/_PageHdrFtrInReportEvents.cs:48-54 | Source/Access/Events/_PageHdrFtrInReportEvents.cs:56-62 | Source/Access/Events/_PaletteButtonEvents.cs:54-60 | Source/Access/Events/_PaletteButtonEvents.cs:62-68 | Source/Access/Events/_PaletteButtonEvents.cs:70-76 | Source/Access/Events/_RectangleEvents.cs:28-34 | Source/Access/Events/_RectangleEvents.cs:36-42 | Source/Access/Events/_RectangleEvents.cs:44-50 | Source/Access/Events/_ReportEvents2.cs:85-91 | Source/Access/Events/_ReportEvents2.cs:93-99 | Source/Access/Events/_ReportEvents2.cs:101-107 | Source/Access/Events/_SectionEvents.cs:28-34 | Source/Access/Events/_SectionEvents.cs:36-42 | Source/Access/Events/_SectionEvents.cs:44-50 | Source/Access/Events/_SectionInReportEvents.cs:44-50 | Source/Access/Events/_SectionInReportEvents.cs:52-58 | Source/Access/Events/_SectionInReportEvents.cs:60-66 | Source/Access/Events/_TabControlEvents.cs:28-34 | Source/Access/Events/_TabControlEvents.cs:36-42 | Source/Access/Events/_TabControlEvents.cs:44-50 | Source/Access/Events/_TextBoxEvents.cs:56-62 | Source/Access/Events/_TextBoxEvents.cs:64-70 | Source/Access/Events/_TextBoxEvents.cs:72-78 | Source/Access/Events/_ToggleButtonEvents.cs:54-60 | Source/Access/Events/_ToggleButtonEvents.cs:62-68 | Source/Access/Events/_ToggleButtonEvents.cs:70-76 | Source/Access/Events/_ToggleButtonInOptionEvents.cs:27-33 | Source/Access/Events/_ToggleButtonInOptionEvents.cs:35-41 | Source/Access/Events/_ToggleButtonInOptionEvents.cs:43-49 — before extracting anything, compare `Source/Access/Events/DispAttachmentEvents.cs` and `Source/Access/Events/DispBoundObjectFrameEvents.cs` as WHOLE FILES: this scan already matched 29 separate duplicated blocks between them, totalling at least 271 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Access/Events/DispCheckBoxEvents.cs:50` calls `SinkArgument` and `Source/Access/Events/DispOptionButtonEvents.cs:48` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (7 lines × 30) · ×1
  • Duplicated block (7 lines × 30) Source/Access/Events/DispAttachmentEvents.cs:87 — Source/Access/Events/DispAttachmentEvents.cs:87-93 | Source/Access/Events/DispBoundObjectFrameEvents.cs:83-89 | Source/Access/Events/DispCheckBoxEvents.cs:78-84 | Source/Access/Events/DispComboBoxEvents.cs:88-94 | Source/Access/Events/DispCommandButtonEvents.cs:68-74 | Source/Access/Events/DispListBoxEvents.cs:78-84 | Source/Access/Events/DispNavigationButtonEvents.cs:69-75 | Source/Access/Events/DispNavigationControlEvents.cs:82-88 | Source/Access/Events/DispOptionButtonEvents.cs:76-82 | Source/Access/Events/DispPaletteButtonEvents.cs:78-84 | Source/Access/Events/DispTabControlEvents.cs:52-58 | Source/Access/Events/DispTextBoxEvents.cs:82-88 | Source/Access/Events/DispToggleButtonEvents.cs:78-84 | Source/Access/Events/DispWebBrowserControlEvents.cs:92-98 | Source/Access/Events/_BoundObjectFrameEvents.cs:83-89 | Source/Access/Events/_CheckBoxEvents.cs:78-84 | Source/Access/Events/_CheckBoxInOptionEvents.cs:51-57 | Source/Access/Events/_ComboBoxEvents.cs:87-93 | Source/Access/Events/_CommandButtonEvents.cs:68-74 | Source/Access/Events/_FormEvents.cs:126-132 | Source/Access/Events/_FormEvents2.cs:128-134 | Source/Access/Events/_ListBoxEvents.cs:77-83 | Source/Access/Events/_OptionButtonEvents.cs:78-84 | Source/Access/Events/_OptionButtonInOptionEvents.cs:51-57 | Source/Access/Events/_PaletteButtonEvents.cs:78-84 | Source/Access/Events/_ReportEvents2.cs:109-115 | Source/Access/Events/_TabControlEvents.cs:52-58 | Source/Access/Events/_TextBoxEvents.cs:80-86 | Source/Access/Events/_ToggleButtonEvents.cs:78-84 | Source/Access/Events/_ToggleButtonInOptionEvents.cs:51-57 — before extracting anything, compare `Source/Access/Events/DispAttachmentEvents.cs` and `Source/Access/Events/DispBoundObjectFrameEvents.cs` as WHOLE FILES: this scan already matched 29 separate duplicated blocks between them, totalling at least 271 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Source/Access/Events/DispComboBoxEvents.cs:96` calls `SinkArgument` and `Source/Access/Events/DispAttachmentEvents.cs:95` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (6 lines × 17) · ×1
  • Duplicated block (6 lines × 17) Source/Access/Events/_BoundObjectFrameEvents.cs:50 — Source/Access/Events/_BoundObjectFrameEvents.cs:50-55 | Source/Access/Events/_CheckBoxEvents.cs:19-24 | Source/Access/Events/_ComboBoxEvents.cs:54-59 | Source/Access/Events/_FormEvents.cs:93-98 | Source/Access/Events/_ImageEvents.cs:19-24 | Source/Access/Events/_LabelEvents.cs:19-24 | Source/Access/Events/_ListBoxEvents.cs:44-49 | Source/Access/Events/_ObjectFrameEvents.cs:41-46 | Source/Access/Events/_OptionButtonEvents.cs:19-24 | Source/Access/Events/_OptionGroupEvents.cs:37-42 | Source/Access/Events/_PageEvents.cs:19-24 | Source/Access/Events/_PaletteButtonEvents.cs:19-24 | Source/Access/Events/_RectangleEvents.cs:19-24 | Source/Access/Events/_SectionEvents.cs:19-24 | Source/Access/Events/_TabControlEvents.cs:19-24 | Source/Access/Events/_TextBoxEvents.cs:47-52 | Source/Access/Events/_ToggleButtonEvents.cs:19-24 — before extracting anything, compare `Source/Access/Events/_BoundObjectFrameEvents.cs` and `Source/Access/Events/_CheckBoxEvents.cs` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 292 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (7 lines × 15) · ×1
  • Duplicated block (7 lines × 15) Source/Access/Events/_BoundObjectFrameEvents.cs:42 — Source/Access/Events/_BoundObjectFrameEvents.cs:42-48 | Source/Access/Events/_CheckBoxEvents.cs:41-47 | Source/Access/Events/_CheckBoxInOptionEvents.cs:19-25 | Source/Access/Events/_ComboBoxEvents.cs:46-52 | Source/Access/Events/_CommandButtonEvents.cs:31-37 | Source/Access/Events/_CustomControlEvents.cs:32-38 | Source/Access/Events/_FormEvents.cs:85-91 | Source/Access/Events/_ListBoxEvents.cs:36-42 | Source/Access/Events/_ObjectFrameEvents.cs:33-39 | Source/Access/Events/_OptionButtonEvents.cs:41-47 | Source/Access/Events/_OptionButtonInOptionEvents.cs:19-25 | Source/Access/Events/_PaletteButtonEvents.cs:41-47 | Source/Access/Events/_TextBoxEvents.cs:39-45 | Source/Access/Events/_ToggleButtonEvents.cs:41-47 | Source/Access/Events/_ToggleButtonInOptionEvents.cs:19-25 — before extracting anything, compare `Source/Access/Events/_BoundObjectFrameEvents.cs` and `Source/Access/Events/_CheckBoxEvents.cs` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 292 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Access/Events/_BoundObjectFrameEvents.cs:38` calls `SinkArgument` and `Source/Access/Events/_ComboBoxEvents.cs:42` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (7 lines × 11) · ×1
  • Duplicated block (7 lines × 11) Source/Excel/Events/ChartEvents.cs:31 — Source/Excel/Events/ChartEvents.cs:31-37 | Source/Excel/Events/ChartEvents.cs:39-45 | Source/Excel/Events/ChartEvents.cs:47-53 | Source/OWC10/Events/IChartEvents.cs:68-74 | Source/OWC10/Events/IChartEvents.cs:76-82 | Source/OWC10/Events/IChartEvents.cs:84-90 | Source/OWC10/Events/IPivotControlEvents.cs:54-60 | Source/OWC10/Events/IPivotControlEvents.cs:62-68 | Source/OWC10/Events/IPivotControlEvents.cs:70-76 | Source/OWC10/Events/ISpreadsheetEventSink.cs:113-119 | Source/OWC10/Events/ISpreadsheetEventSink.cs:135-141 — there are 11 copies across 4 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 11 sites; resolving a subset leaves the remainder to drift apart.
D4 · Code Duplication · Duplicated block (5 lines × 7) · ×1
  • Duplicated block (5 lines × 7) Source/OWC10/Events/IChartEvents.cs:283 — Source/OWC10/Events/IChartEvents.cs:283-287 | Source/OWC10/Events/IChartEvents.cs:301-305 | Source/OWC10/Events/IChartEvents.cs:538-542 | Source/OWC10/Events/IPivotControlEvents.cs:544-548 | Source/OWC10/Events/IPivotControlEvents.cs:562-566 | Source/OWC10/Events/ISpreadsheetEventSink.cs:255-259 | Source/OWC10/Events/ISpreadsheetEventSink.cs:273-277 — before extracting anything, compare `Source/OWC10/Events/IChartEvents.cs` and `Source/OWC10/Events/IPivotControlEvents.cs` as WHOLE FILES: this scan already matched 39 separate duplicated blocks between them, totalling at least 404 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (7 lines × 7) · ×1
  • Duplicated block (7 lines × 7) Source/OWC10/Events/IChartEvents.cs:518 — Source/OWC10/Events/IChartEvents.cs:518-524 | Source/OWC10/Events/IPivotControlEvents.cs:596-602 | Source/OWC10/Events/IPivotControlEvents.cs:619-625 | Source/OWC10/Events/IPivotControlEvents.cs:642-648 | Source/OWC10/Events/ISpreadsheetEventSink.cs:235-241 | Source/OWC10/Events/ISpreadsheetEventSink.cs:409-415 | Source/OWC10/Events/ISpreadsheetEventSink.cs:708-714 — before extracting anything, compare `Source/OWC10/Events/IChartEvents.cs` and `Source/OWC10/Events/IPivotControlEvents.cs` as WHOLE FILES: this scan already matched 39 separate duplicated blocks between them, totalling at least 404 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (6 lines × 152) · ×1
  • Duplicated block (6 lines × 152) Source/Access/Events/DispAttachmentEvents.cs:63 — Source/Access/Events/DispAttachmentEvents.cs:63-68 | Source/Access/Events/DispAttachmentEvents.cs:71-76 | Source/Access/Events/DispAttachmentEvents.cs:79-84 | Source/Access/Events/DispBoundObjectFrameEvents.cs:59-64 | Source/Access/Events/DispBoundObjectFrameEvents.cs:67-72 | Source/Access/Events/DispBoundObjectFrameEvents.cs:75-80 | Source/Access/Events/DispCheckBoxEvents.cs:54-59 | Source/Access/Events/DispCheckBoxEvents.cs:62-67 | Source/Access/Events/DispCheckBoxEvents.cs:70-75 | Source/Access/Events/DispComboBoxEvents.cs:64-69 | Source/Access/Events/DispComboBoxEvents.cs:72-77 | Source/Access/Events/DispComboBoxEvents.cs:80-85 | Source/Access/Events/DispCommandButtonEvents.cs:44-49 | Source/Access/Events/DispCommandButtonEvents.cs:52-57 | Source/Access/Events/DispCommandButtonEvents.cs:60-65 | Source/Access/Events/DispImageEvents.cs:28-33 | Source/Access/Events/DispImageEvents.cs:36-41 | Source/Access/Events/DispImageEvents.cs:44-49 | Source/Access/Events/DispLabelEvents.cs:28-33 | Source/Access/Events/DispLabelEvents.cs:36-41 | Source/Access/Events/DispLabelEvents.cs:44-49 | Source/Access/Events/DispListBoxEvents.cs:54-59 | Source/Access/Events/DispListBoxEvents.cs:62-67 | Source/Access/Events/DispListBoxEvents.cs:70-75 | Source/Access/Events/DispNavigationButtonEvents.cs:45-50 | Source/Access/Events/DispNavigationButtonEvents.cs:53-58 | Source/Access/Events/DispNavigationButtonEvents.cs:61-66 | Source/Access/Events/DispNavigationControlEvents.cs:58-63 | Source/Access/Events/DispNavigationControlEvents.cs:66-71 | Source/Access/Events/DispNavigationControlEvents.cs:74-79 | Source/Access/Events/DispObjectFrameEvents.cs:50-55 | Source/Access/Events/DispObjectFrameEvents.cs:58-63 | Source/Access/Events/DispObjectFrameEvents.cs:66-71 | Source/Access/Events/DispOptionButtonEvents.cs:52-57 | Source/Access/Events/DispOptionButtonEvents.cs:60-65 | Source/Access/Events/DispOptionButtonEvents.cs:68-73 | Source/Access/Events/DispOptionGroupEvents.cs:46-51 | Source/Access/Events/DispOptionGroupEvents.cs:54-59 | Source/Access/Events/DispOptionGroupEvents.cs:62-67 | Source/Access/Events/DispPageEvents.cs:28-33 | Source/Access/Events/DispPageEvents.cs:36-41 | Source/Access/Events/DispPageEvents.cs:44-49 | Source/Access/Events/DispPageHdrFtrInReportEvents.cs:40-45 | Source/Access/Events/DispPageHdrFtrInReportEvents.cs:48-53 | Source/Access/Events/DispPageHdrFtrInReportEvents.cs:56-61 | Source/Access/Events/DispPaletteButtonEvents.cs:54-59 | Source/Access/Events/DispPaletteButtonEvents.cs:62-67 | Source/Access/Events/DispPaletteButtonEvents.cs:70-75 | Source/Access/Events/DispRectangleEvents.cs:28-33 | Source/Access/Events/DispRectangleEvents.cs:36-41 | Source/Access/Events/DispRectangleEvents.cs:44-49 | Source/Access/Events/DispSectionEvents.cs:28-33 | Source/Access/Events/DispSectionEvents.cs:36-41 | Source/Access/Events/DispSectionEvents.cs:44-49 | Source/Access/Events/DispSectionInReportEvents.cs:44-49 | Source/Access/Events/DispSectionInReportEvents.cs:52-57 | Source/Access/Events/DispSectionInReportEvents.cs:60-65 | Source/Access/Events/DispTabControlEvents.cs:28-33 | Source/Access/Events/DispTabControlEvents.cs:36-41 | Source/Access/Events/DispTabControlEvents.cs:44-49 | Source/Access/Events/DispTextBoxEvents.cs:58-63 | Source/Access/Events/DispTextBoxEvents.cs:66-71 | Source/Access/Events/DispTextBoxEvents.cs:74-79 | Source/Access/Events/DispToggleButtonEvents.cs:54-59 | Source/Access/Events/DispToggleButtonEvents.cs:62-67 | Source/Access/Events/DispToggleButtonEvents.cs:70-75 | Source/Access/Events/DispWebBrowserControlEvents.cs:68-73 | Source/Access/Events/DispWebBrowserControlEvents.cs:76-81 | Source/Access/Events/DispWebBrowserControlEvents.cs:84-89 | Source/Access/Events/_BoundObjectFrameEvents.cs:59-64 | Source/Access/Events/_BoundObjectFrameEvents.cs:67-72 | Source/Access/Events/_BoundObjectFrameEvents.cs:75-80 | Source/Access/Events/_CheckBoxEvents.cs:54-59 | Source/Access/Events/_CheckBoxEvents.cs:62-67 | Source/Access/Events/_CheckBoxEvents.cs:70-75 | Source/Access/Events/_CheckBoxInOptionEvents.cs:27-32 | Source/Access/Events/_CheckBoxInOptionEvents.cs:35-40 | Source/Access/Events/_CheckBoxInOptionEvents.cs:43-48 | Source/Access/Events/_ComboBoxEvents.cs:63-68 | Source/Access/Events/_ComboBoxEvents.cs:71-76 | Source/Access/Events/_ComboBoxEvents.cs:79-84 | Source/Access/Events/_CommandButtonEvents.cs:44-49 | Source/Access/Events/_CommandButtonEvents.cs:52-57 | Source/Access/Events/_CommandButtonEvents.cs:60-65 | Source/Access/Events/_FormEvents.cs:102-107 | Source/Access/Events/_FormEvents.cs:110-115 | Source/Access/Events/_FormEvents.cs:118-123 | Source/Access/Events/_FormEvents2.cs:104-109 | Source/Access/Events/_FormEvents2.cs:112-117 | Source/Access/Events/_FormEvents2.cs:120-125 | Source/Access/Events/_ImageEvents.cs:28-33 | Source/Access/Events/_ImageEvents.cs:36-41 | Source/Access/Events/_ImageEvents.cs:44-49 | Source/Access/Events/_LabelEvents.cs:28-33 | Source/Access/Events/_LabelEvents.cs:36-41 | Source/Access/Events/_LabelEvents.cs:44-49 | Source/Access/Events/_ListBoxEvents.cs:53-58 | Source/Access/Events/_ListBoxEvents.cs:61-66 | Source/Access/Events/_ListBoxEvents.cs:69-74 | Source/Access/Events/_ObjectFrameEvents.cs:50-55 | Source/Access/Events/_ObjectFrameEvents.cs:58-63 | Source/Access/Events/_ObjectFrameEvents.cs:66-71 | Source/Access/Events/_OptionButtonEvents.cs:54-59 | Source/Access/Events/_OptionButtonEvents.cs:62-67 | Source/Access/Events/_OptionButtonEvents.cs:70-75 | Source/Access/Events/_OptionButtonInOptionEvents.cs:27-32 | Source/Access/Events/_OptionButtonInOptionEvents.cs:35-40 | Source/Access/Events/_OptionButtonInOptionEvents.cs:43-48 | Source/Access/Events/_OptionGroupEvents.cs:46-51 | Source/Access/Events/_OptionGroupEvents.cs:54-59 | Source/Access/Events/_OptionGroupEvents.cs:62-67 | Source/Access/Events/_PageEvents.cs:28-33 | Source/Access/Events/_PageEvents.cs:36-41 | Source/Access/Events/_PageEvents.cs:44-49 | Source/Access/Events/_PageHdrFtrInReportEvents.cs:40-45 | Source/Access/Events/_PageHdrFtrInReportEvents.cs:48-53 | Source/Access/Events/_PageHdrFtrInReportEvents.cs:56-61 | Source/Access/Events/_PaletteButtonEvents.cs:54-59 | Source/Access/Events/_PaletteButtonEvents.cs:62-67 | Source/Access/Events/_PaletteButtonEvents.cs:70-75 | Source/Access/Events/_RectangleEvents.cs:28-33 | Source/Access/Events/_RectangleEvents.cs:36-41 | Source/Access/Events/_RectangleEvents.cs:44-49 | Source/Access/Events/_ReportEvents2.cs:85-90 | Source/Access/Events/_ReportEvents2.cs:93-98 | Source/Access/Events/_ReportEvents2.cs:101-106 | Source/Access/Events/_SectionEvents.cs:28-33 | Source/Access/Events/_SectionEvents.cs:36-41 | Source/Access/Events/_SectionEvents.cs:44-49 | Source/Access/Events/_SectionInReportEvents.cs:44-49 | Source/Access/Events/_SectionInReportEvents.cs:52-57 | Source/Access/Events/_SectionInReportEvents.cs:60-65 | Source/Access/Events/_TabControlEvents.cs:28-33 | Source/Access/Events/_TabControlEvents.cs:36-41 | Source/Access/Events/_TabControlEvents.cs:44-49 | Source/Access/Events/_TextBoxEvents.cs:56-61 | Source/Access/Events/_TextBoxEvents.cs:64-69 | Source/Access/Events/_TextBoxEvents.cs:72-77 | Source/Access/Events/_ToggleButtonEvents.cs:54-59 | Source/Access/Events/_ToggleButtonEvents.cs:62-67 | Source/Access/Events/_ToggleButtonEvents.cs:70-75 | Source/Access/Events/_ToggleButtonInOptionEvents.cs:27-32 | Source/Access/Events/_ToggleButtonInOptionEvents.cs:35-40 | Source/Access/Events/_ToggleButtonInOptionEvents.cs:43-48 | Source/MSComctlLib/Events/DImageComboEvents.cs:84-89 | Source/MSComctlLib/Events/IProgressBarEvents.cs:83-88 | Source/MSComctlLib/Events/ISliderEvents.cs:108-113 | Source/MSComctlLib/Events/IStatusBarEvents.cs:97-102 | Source/MSComctlLib/Events/ITabStripEvents.cs:105-110 | Source/MSComctlLib/Events/IToolbarEvents.cs:96-101 | Source/MSComctlLib/Events/ITreeViewEvents.cs:135-140 | Source/MSComctlLib/Events/ListViewEvents.cs:125-130 — before extracting anything, compare `Source/Access/Events/DispAttachmentEvents.cs` and `Source/Access/Events/DispBoundObjectFrameEvents.cs` as WHOLE FILES: this scan already matched 29 separate duplicated blocks between them, totalling at least 271 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Access/Events/DispCheckBoxEvents.cs:50` calls `SinkArgument` and `Source/Access/Events/DispOptionButtonEvents.cs:48` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (5 lines × 45) · ×1
  • Duplicated block (5 lines × 45) Source/Outlook/Events/OlkBusinessCardControlEvents.cs:27 — Source/Outlook/Events/OlkBusinessCardControlEvents.cs:27-31 | Source/Outlook/Events/OlkBusinessCardControlEvents.cs:35-39 | Source/Outlook/Events/OlkBusinessCardControlEvents.cs:43-47 | Source/Outlook/Events/OlkCategoryEvents.cs:27-31 | Source/Outlook/Events/OlkCategoryEvents.cs:35-39 | Source/Outlook/Events/OlkCategoryEvents.cs:43-47 | Source/Outlook/Events/OlkCheckBoxEvents.cs:27-31 | Source/Outlook/Events/OlkCheckBoxEvents.cs:35-39 | Source/Outlook/Events/OlkCheckBoxEvents.cs:43-47 | Source/Outlook/Events/OlkComboBoxEvents.cs:27-31 | Source/Outlook/Events/OlkComboBoxEvents.cs:35-39 | Source/Outlook/Events/OlkComboBoxEvents.cs:43-47 | Source/Outlook/Events/OlkCommandButtonEvents.cs:27-31 | Source/Outlook/Events/OlkCommandButtonEvents.cs:35-39 | Source/Outlook/Events/OlkCommandButtonEvents.cs:43-47 | Source/Outlook/Events/OlkContactPhotoEvents.cs:27-31 | Source/Outlook/Events/OlkContactPhotoEvents.cs:35-39 | Source/Outlook/Events/OlkContactPhotoEvents.cs:43-47 | Source/Outlook/Events/OlkDateControlEvents.cs:27-31 | Source/Outlook/Events/OlkDateControlEvents.cs:35-39 | Source/Outlook/Events/OlkDateControlEvents.cs:43-47 | Source/Outlook/Events/OlkInfoBarEvents.cs:27-31 | Source/Outlook/Events/OlkInfoBarEvents.cs:35-39 | Source/Outlook/Events/OlkInfoBarEvents.cs:43-47 | Source/Outlook/Events/OlkLabelEvents.cs:27-31 | Source/Outlook/Events/OlkLabelEvents.cs:35-39 | Source/Outlook/Events/OlkLabelEvents.cs:43-47 | Source/Outlook/Events/OlkListBoxEvents.cs:27-31 | Source/Outlook/Events/OlkListBoxEvents.cs:35-39 | Source/Outlook/Events/OlkListBoxEvents.cs:43-47 | Source/Outlook/Events/OlkOptionButtonEvents.cs:27-31 | Source/Outlook/Events/OlkOptionButtonEvents.cs:35-39 | Source/Outlook/Events/OlkOptionButtonEvents.cs:43-47 | Source/Outlook/Events/OlkSenderPhotoEvents.cs:27-31 | Source/Outlook/Events/OlkSenderPhotoEvents.cs:35-39 | Source/Outlook/Events/OlkSenderPhotoEvents.cs:43-47 | Source/Outlook/Events/OlkTextBoxEvents.cs:27-31 | Source/Outlook/Events/OlkTextBoxEvents.cs:35-39 | Source/Outlook/Events/OlkTextBoxEvents.cs:43-47 | Source/Outlook/Events/OlkTimeControlEvents.cs:27-31 | Source/Outlook/Events/OlkTimeControlEvents.cs:35-39 | Source/Outlook/Events/OlkTimeControlEvents.cs:43-47 | Source/Outlook/Events/OlkTimeZoneControlEvents.cs:27-31 | Source/Outlook/Events/OlkTimeZoneControlEvents.cs:35-39 | Source/Outlook/Events/OlkTimeZoneControlEvents.cs:43-47 — before extracting anything, compare `Source/Outlook/Events/OlkBusinessCardControlEvents.cs` and `Source/Outlook/Events/OlkCategoryEvents.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 61 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (6 lines × 32) · ×1
  • Duplicated block (6 lines × 32) Source/Excel/Events/ChartEvents.cs:31 — Source/Excel/Events/ChartEvents.cs:31-36 | Source/Excel/Events/ChartEvents.cs:39-44 | Source/Excel/Events/ChartEvents.cs:47-52 | Source/MSComctlLib/Events/IProgressBarEvents.cs:19-24 | Source/MSComctlLib/Events/IProgressBarEvents.cs:27-32 | Source/MSComctlLib/Events/IProgressBarEvents.cs:35-40 | Source/MSComctlLib/Events/ISliderEvents.cs:40-45 | Source/MSComctlLib/Events/ISliderEvents.cs:48-53 | Source/MSComctlLib/Events/ISliderEvents.cs:56-61 | Source/MSComctlLib/Events/IStatusBarEvents.cs:29-34 | Source/MSComctlLib/Events/IStatusBarEvents.cs:37-42 | Source/MSComctlLib/Events/IStatusBarEvents.cs:45-50 | Source/MSComctlLib/Events/ITabStripEvents.cs:40-45 | Source/MSComctlLib/Events/ITabStripEvents.cs:48-53 | Source/MSComctlLib/Events/ITabStripEvents.cs:56-61 | Source/MSComctlLib/Events/IToolbarEvents.cs:32-37 | Source/MSComctlLib/Events/IToolbarEvents.cs:40-45 | Source/MSComctlLib/Events/IToolbarEvents.cs:48-53 | Source/MSComctlLib/Events/ITreeViewEvents.cs:62-67 | Source/MSComctlLib/Events/ITreeViewEvents.cs:70-75 | Source/MSComctlLib/Events/ITreeViewEvents.cs:78-83 | Source/MSComctlLib/Events/ListViewEvents.cs:57-62 | Source/MSComctlLib/Events/ListViewEvents.cs:65-70 | Source/MSComctlLib/Events/ListViewEvents.cs:73-78 | Source/OWC10/Events/IChartEvents.cs:68-73 | Source/OWC10/Events/IChartEvents.cs:76-81 | Source/OWC10/Events/IChartEvents.cs:84-89 | Source/OWC10/Events/IPivotControlEvents.cs:54-59 | Source/OWC10/Events/IPivotControlEvents.cs:62-67 | Source/OWC10/Events/IPivotControlEvents.cs:70-75 | Source/OWC10/Events/ISpreadsheetEventSink.cs:113-118 | Source/OWC10/Events/ISpreadsheetEventSink.cs:135-140 — there are 32 copies across 11 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 32 sites; resolving a subset leaves the remainder to drift apart. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (6 lines × 27) · ×1
  • Duplicated block (6 lines × 27) Source/Access/Events/DispAttachmentEvents.cs:93 — Source/Access/Events/DispAttachmentEvents.cs:93-98 | Source/Access/Events/DispBoundObjectFrameEvents.cs:89-94 | Source/Access/Events/DispCheckBoxEvents.cs:84-89 | Source/Access/Events/DispComboBoxEvents.cs:95-100 | Source/Access/Events/DispCommandButtonEvents.cs:74-79 | Source/Access/Events/DispListBoxEvents.cs:84-89 | Source/Access/Events/DispOptionButtonEvents.cs:82-87 | Source/Access/Events/DispPaletteButtonEvents.cs:84-89 | Source/Access/Events/DispTabControlEvents.cs:58-63 | Source/Access/Events/DispTextBoxEvents.cs:88-93 | Source/Access/Events/DispToggleButtonEvents.cs:84-89 | Source/Access/Events/_BoundObjectFrameEvents.cs:89-94 | Source/Access/Events/_CheckBoxEvents.cs:84-89 | Source/Access/Events/_CheckBoxInOptionEvents.cs:57-62 | Source/Access/Events/_ComboBoxEvents.cs:93-98 | Source/Access/Events/_CommandButtonEvents.cs:74-79 | Source/Access/Events/_FormEvents.cs:132-137 | Source/Access/Events/_FormEvents2.cs:134-139 | Source/Access/Events/_ListBoxEvents.cs:83-88 | Source/Access/Events/_OptionButtonEvents.cs:84-89 | Source/Access/Events/_OptionButtonInOptionEvents.cs:57-62 | Source/Access/Events/_PaletteButtonEvents.cs:84-89 | Source/Access/Events/_ReportEvents2.cs:115-120 | Source/Access/Events/_TabControlEvents.cs:58-63 | Source/Access/Events/_TextBoxEvents.cs:86-91 | Source/Access/Events/_ToggleButtonEvents.cs:84-89 | Source/Access/Events/_ToggleButtonInOptionEvents.cs:57-62 — before extracting anything, compare `Source/Access/Events/DispAttachmentEvents.cs` and `Source/Access/Events/DispBoundObjectFrameEvents.cs` as WHOLE FILES: this scan already matched 29 separate duplicated blocks between them, totalling at least 271 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Access/Events/DispComboBoxEvents.cs:95` calls `SinkArgument` and `Source/Access/Events/DispAttachmentEvents.cs:93` does not — after which the two agree again for 5 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (6 lines × 19) · ×1
  • Duplicated block (6 lines × 19) Source/Access/Events/DispAttachmentEvents.cs:19 — Source/Access/Events/DispAttachmentEvents.cs:19-24 | Source/Access/Events/DispBoundObjectFrameEvents.cs:24-29 | Source/Access/Events/DispCheckBoxEvents.cs:23-28 | Source/Access/Events/DispComboBoxEvents.cs:19-24 | Source/Access/Events/DispListBoxEvents.cs:19-24 | Source/Access/Events/DispNavigationControlEvents.cs:19-24 | Source/Access/Events/DispOptionGroupEvents.cs:19-24 | Source/Access/Events/DispPaletteButtonEvents.cs:23-28 | Source/Access/Events/DispTextBoxEvents.cs:19-24 | Source/Access/Events/DispToggleButtonEvents.cs:23-28 | Source/Access/Events/_BoundObjectFrameEvents.cs:24-29 | Source/Access/Events/_CheckBoxEvents.cs:23-28 | Source/Access/Events/_ComboBoxEvents.cs:19-24 | Source/Access/Events/_FormEvents2.cs:36-41 | Source/Access/Events/_ListBoxEvents.cs:18-23 | Source/Access/Events/_OptionButtonEvents.cs:23-28 | Source/Access/Events/_OptionGroupEvents.cs:19-24 | Source/Access/Events/_PaletteButtonEvents.cs:23-28 | Source/Access/Events/_ToggleButtonEvents.cs:23-28 — before extracting anything, compare `Source/Access/Events/DispAttachmentEvents.cs` and `Source/Access/Events/DispBoundObjectFrameEvents.cs` as WHOLE FILES: this scan already matched 29 separate duplicated blocks between them, totalling at least 271 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Access/Events/DispCheckBoxEvents.cs:19` calls `SupportByVersion`, `MethodImpl`, `DispId` and `Source/Access/Events/DispAttachmentEvents.cs:18` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (5 lines × 18) · ×1
  • Duplicated block (5 lines × 18) Source/Access/Events/_BoundObjectFrameEvents.cs:50 — Source/Access/Events/_BoundObjectFrameEvents.cs:50-54 | Source/Access/Events/_CheckBoxEvents.cs:19-23 | Source/Access/Events/_ComboBoxEvents.cs:54-58 | Source/Access/Events/_CommandButtonEvents.cs:19-23 | Source/Access/Events/_FormEvents.cs:93-97 | Source/Access/Events/_ImageEvents.cs:19-23 | Source/Access/Events/_LabelEvents.cs:19-23 | Source/Access/Events/_ListBoxEvents.cs:44-48 | Source/Access/Events/_ObjectFrameEvents.cs:41-45 | Source/Access/Events/_OptionButtonEvents.cs:19-23 | Source/Access/Events/_OptionGroupEvents.cs:37-41 | Source/Access/Events/_PageEvents.cs:19-23 | Source/Access/Events/_PaletteButtonEvents.cs:19-23 | Source/Access/Events/_RectangleEvents.cs:19-23 | Source/Access/Events/_SectionEvents.cs:19-23 | Source/Access/Events/_TabControlEvents.cs:19-23 | Source/Access/Events/_TextBoxEvents.cs:47-51 | Source/Access/Events/_ToggleButtonEvents.cs:19-23 — before extracting anything, compare `Source/Access/Events/_BoundObjectFrameEvents.cs` and `Source/Access/Events/_CheckBoxEvents.cs` as WHOLE FILES: this scan already matched 33 separate duplicated blocks between them, totalling at least 292 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (6 lines × 15) · ×1
  • Duplicated block (6 lines × 15) Source/OWC10/Events/IChartEvents.cs:317 — Source/OWC10/Events/IChartEvents.cs:317-322 | Source/OWC10/Events/IChartEvents.cs:436-441 | Source/OWC10/Events/IChartEvents.cs:452-457 | Source/OWC10/Events/IChartEvents.cs:468-473 | Source/OWC10/Events/IChartEvents.cs:484-489 | Source/OWC10/Events/IPivotControlEvents.cs:416-421 | Source/OWC10/Events/IPivotControlEvents.cs:432-437 | Source/OWC10/Events/IPivotControlEvents.cs:448-453 | Source/OWC10/Events/IPivotControlEvents.cs:464-469 | Source/OWC10/Events/IPivotControlEvents.cs:578-583 | Source/OWC10/Events/ISpreadsheetEventSink.cs:289-294 | Source/OWC10/Events/ISpreadsheetEventSink.cs:316-321 | Source/OWC10/Events/ISpreadsheetEventSink.cs:332-337 | Source/OWC10/Events/ISpreadsheetEventSink.cs:348-353 | Source/OWC10/Events/ISpreadsheetEventSink.cs:364-369 — before extracting anything, compare `Source/OWC10/Events/IChartEvents.cs` and `Source/OWC10/Events/IPivotControlEvents.cs` as WHOLE FILES: this scan already matched 39 separate duplicated blocks between them, totalling at least 404 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (6 lines × 14) · ×1
  • Duplicated block (6 lines × 14) Source/OWC10/Events/IChartEvents.cs:282 — Source/OWC10/Events/IChartEvents.cs:282-287 | Source/OWC10/Events/IChartEvents.cs:300-305 | Source/OWC10/Events/IChartEvents.cs:518-523 | Source/OWC10/Events/IChartEvents.cs:537-542 | Source/OWC10/Events/IPivotControlEvents.cs:543-548 | Source/OWC10/Events/IPivotControlEvents.cs:561-566 | Source/OWC10/Events/IPivotControlEvents.cs:596-601 | Source/OWC10/Events/IPivotControlEvents.cs:619-624 | Source/OWC10/Events/IPivotControlEvents.cs:642-647 | Source/OWC10/Events/ISpreadsheetEventSink.cs:235-240 | Source/OWC10/Events/ISpreadsheetEventSink.cs:254-259 | Source/OWC10/Events/ISpreadsheetEventSink.cs:272-277 | Source/OWC10/Events/ISpreadsheetEventSink.cs:409-414 | Source/OWC10/Events/ISpreadsheetEventSink.cs:708-713 — before extracting anything, compare `Source/OWC10/Events/IChartEvents.cs` and `Source/OWC10/Events/IPivotControlEvents.cs` as WHOLE FILES: this scan already matched 39 separate duplicated blocks between them, totalling at least 404 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (6 lines × 12) · ×1
  • Duplicated block (6 lines × 12) Source/Access/Events/DispBoundObjectFrameEvents.cs:38 — Source/Access/Events/DispBoundObjectFrameEvents.cs:38-43 | Source/Access/Events/DispCheckBoxEvents.cs:37-42 | Source/Access/Events/DispComboBoxEvents.cs:43-48 | Source/Access/Events/DispCommandButtonEvents.cs:27-32 | Source/Access/Events/DispCustomControlEvents.cs:29-34 | Source/Access/Events/DispListBoxEvents.cs:33-38 | Source/Access/Events/DispObjectFrameEvents.cs:29-34 | Source/Access/Events/DispOptionButtonEvents.cs:36-41 | Source/Access/Events/DispOptionGroupEvents.cs:33-38 | Source/Access/Events/DispPaletteButtonEvents.cs:37-42 | Source/Access/Events/DispTextBoxEvents.cs:37-42 | Source/Access/Events/DispToggleButtonEvents.cs:37-42 — before extracting anything, compare `Source/Access/Events/DispBoundObjectFrameEvents.cs` and `Source/Access/Events/DispCheckBoxEvents.cs` as WHOLE FILES: this scan already matched 30 separate duplicated blocks between them, totalling at least 277 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Access/Events/DispBoundObjectFrameEvents.cs:38` calls `SinkArgument` and `Source/Access/Events/DispCommandButtonEvents.cs:27` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (6 lines × 11) · ×1
  • Duplicated block (6 lines × 11) Source/Access/Events/DispAttachmentEvents.cs:99 — Source/Access/Events/DispAttachmentEvents.cs:99-104 | Source/Access/Events/DispComboBoxEvents.cs:101-106 | Source/Access/Events/DispNavigationControlEvents.cs:94-99 | Source/Access/Events/DispTabControlEvents.cs:64-69 | Source/Access/Events/DispTextBoxEvents.cs:94-99 | Source/Access/Events/DispWebBrowserControlEvents.cs:104-109 | Source/Access/Events/_ComboBoxEvents.cs:99-104 | Source/Access/Events/_FormEvents.cs:138-143 | Source/Access/Events/_FormEvents2.cs:140-145 | Source/Access/Events/_TabControlEvents.cs:64-69 | Source/Access/Events/_TextBoxEvents.cs:92-97 — before extracting anything, compare `Source/Access/Events/DispAttachmentEvents.cs` and `Source/Access/Events/DispComboBoxEvents.cs` as WHOLE FILES: this scan already matched 36 separate duplicated blocks between them, totalling at least 321 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (6 lines × 8) · ×1
  • Duplicated block (6 lines × 8) Source/Access/Events/DispAttachmentEvents.cs:37 — Source/Access/Events/DispAttachmentEvents.cs:37-42 | Source/Access/Events/DispComboBoxEvents.cs:106-111 | Source/Access/Events/DispNavigationControlEvents.cs:99-104 | Source/Access/Events/DispTextBoxEvents.cs:99-104 | Source/Access/Events/_ComboBoxEvents.cs:104-109 | Source/Access/Events/_FormEvents.cs:165-170 | Source/Access/Events/_FormEvents2.cs:167-172 | Source/Access/Events/_TextBoxEvents.cs:97-102 — before extracting anything, compare `Source/Access/Events/DispAttachmentEvents.cs` and `Source/Access/Events/DispComboBoxEvents.cs` as WHOLE FILES: this scan already matched 36 separate duplicated blocks between them, totalling at least 321 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (5 lines × 34) · ×1
  • Duplicated block (5 lines × 34) Source/Access/Events/DispAttachmentEvents.cs:87 — Source/Access/Events/DispAttachmentEvents.cs:87-91 | Source/Access/Events/DispBoundObjectFrameEvents.cs:83-87 | Source/Access/Events/DispCheckBoxEvents.cs:78-82 | Source/Access/Events/DispComboBoxEvents.cs:88-92 | Source/Access/Events/DispCommandButtonEvents.cs:68-72 | Source/Access/Events/DispListBoxEvents.cs:78-82 | Source/Access/Events/DispNavigationButtonEvents.cs:69-73 | Source/Access/Events/DispNavigationControlEvents.cs:82-86 | Source/Access/Events/DispOptionButtonEvents.cs:76-80 | Source/Access/Events/DispPaletteButtonEvents.cs:78-82 | Source/Access/Events/DispTabControlEvents.cs:52-56 | Source/Access/Events/DispTextBoxEvents.cs:82-86 | Source/Access/Events/DispToggleButtonEvents.cs:78-82 | Source/Access/Events/DispWebBrowserControlEvents.cs:92-96 | Source/Access/Events/_BoundObjectFrameEvents.cs:83-87 | Source/Access/Events/_CheckBoxEvents.cs:78-82 | Source/Access/Events/_CheckBoxInOptionEvents.cs:51-55 | Source/Access/Events/_ComboBoxEvents.cs:87-91 | Source/Access/Events/_CommandButtonEvents.cs:68-72 | Source/Access/Events/_FormEvents.cs:126-130 | Source/Access/Events/_FormEvents2.cs:128-132 | Source/Access/Events/_ListBoxEvents.cs:77-81 | Source/Access/Events/_OptionButtonEvents.cs:78-82 | Source/Access/Events/_OptionButtonInOptionEvents.cs:51-55 | Source/Access/Events/_PaletteButtonEvents.cs:78-82 | Source/Access/Events/_ReportEvents2.cs:109-113 | Source/Access/Events/_TabControlEvents.cs:52-56 | Source/Access/Events/_TextBoxEvents.cs:80-84 | Source/Access/Events/_ToggleButtonEvents.cs:78-82 | Source/Access/Events/_ToggleButtonInOptionEvents.cs:51-55 | Source/MSComctlLib/Events/ISliderEvents.cs:23-27 | Source/MSComctlLib/Events/ITabStripEvents.cs:23-27 | Source/MSComctlLib/Events/ITreeViewEvents.cs:45-49 | Source/MSComctlLib/Events/ListViewEvents.cs:40-44 — before extracting anything, compare `Source/Access/Events/DispAttachmentEvents.cs` and `Source/Access/Events/DispBoundObjectFrameEvents.cs` as WHOLE FILES: this scan already matched 29 separate duplicated blocks between them, totalling at least 271 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Source/Access/Events/DispComboBoxEvents.cs:96` calls `SinkArgument` and `Source/Access/Events/DispAttachmentEvents.cs:95` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (5 lines × 33) · ×1
  • Duplicated block (5 lines × 33) Source/Access/Events/DispAttachmentEvents.cs:98 — Source/Access/Events/DispAttachmentEvents.cs:98-102 | Source/Access/Events/DispBoundObjectFrameEvents.cs:94-98 | Source/Access/Events/DispCheckBoxEvents.cs:89-93 | Source/Access/Events/DispComboBoxEvents.cs:100-104 | Source/Access/Events/DispCommandButtonEvents.cs:79-83 | Source/Access/Events/DispListBoxEvents.cs:89-93 | Source/Access/Events/DispNavigationButtonEvents.cs:80-84 | Source/Access/Events/DispNavigationControlEvents.cs:93-97 | Source/Access/Events/DispOptionButtonEvents.cs:87-91 | Source/Access/Events/DispPaletteButtonEvents.cs:89-93 | Source/Access/Events/DispTabControlEvents.cs:63-67 | Source/Access/Events/DispTextBoxEvents.cs:93-97 | Source/Access/Events/DispToggleButtonEvents.cs:89-93 | Source/Access/Events/DispWebBrowserControlEvents.cs:103-107 | Source/Access/Events/_BoundObjectFrameEvents.cs:94-98 | Source/Access/Events/_CheckBoxEvents.cs:89-93 | Source/Access/Events/_CheckBoxInOptionEvents.cs:62-66 | Source/Access/Events/_ComboBoxEvents.cs:98-102 | Source/Access/Events/_CommandButtonEvents.cs:79-83 | Source/Access/Events/_FormEvents.cs:137-141 | Source/Access/Events/_FormEvents2.cs:139-143 | Source/Access/Events/_ListBoxEvents.cs:88-92 | Source/Access/Events/_OptionButtonEvents.cs:89-93 | Source/Access/Events/_OptionButtonInOptionEvents.cs:62-66 | Source/Access/Events/_PaletteButtonEvents.cs:89-93 | Source/Access/Events/_TabControlEvents.cs:63-67 | Source/Access/Events/_TextBoxEvents.cs:91-95 | Source/Access/Events/_ToggleButtonEvents.cs:89-93 | Source/Access/Events/_ToggleButtonInOptionEvents.cs:62-66 | Source/MSComctlLib/Events/ISliderEvents.cs:34-38 | Source/MSComctlLib/Events/ITabStripEvents.cs:34-38 | Source/MSComctlLib/Events/ITreeViewEvents.cs:51-55 | Source/MSComctlLib/Events/ListViewEvents.cs:46-50 — before extracting anything, compare `Source/Access/Events/DispAttachmentEvents.cs` and `Source/Access/Events/DispBoundObjectFrameEvents.cs` as WHOLE FILES: this scan already matched 29 separate duplicated blocks between them, totalling at least 271 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Source/Access/Events/DispAttachmentEvents.cs:104` calls `SupportByVersion`, `MethodImpl`, `DispId` and `Source/Access/Events/DispBoundObjectFrameEvents.cs:99` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (5 lines × 10) · ×1
  • Duplicated block (5 lines × 10) Source/Access/Events/DispAttachmentEvents.cs:100 — Source/Access/Events/DispAttachmentEvents.cs:100-104 | Source/Access/Events/DispComboBoxEvents.cs:102-106 | Source/Access/Events/DispTabControlEvents.cs:65-69 | Source/Access/Events/DispTextBoxEvents.cs:95-99 | Source/Access/Events/_ComboBoxEvents.cs:100-104 | Source/Access/Events/_FormEvents.cs:139-143 | Source/Access/Events/_FormEvents2.cs:141-145 | Source/Access/Events/_ReportEvents2.cs:120-124 | Source/Access/Events/_TabControlEvents.cs:65-69 | Source/Access/Events/_TextBoxEvents.cs:93-97 — before extracting anything, compare `Source/Access/Events/DispAttachmentEvents.cs` and `Source/Access/Events/DispComboBoxEvents.cs` as WHOLE FILES: this scan already matched 36 separate duplicated blocks between them, totalling at least 321 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Access/Events/DispAttachmentEvents.cs:99` calls `SinkArgument` and `Source/Access/Events/_ReportEvents2.cs:120` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (81 lines × 5) · ×1
  • Duplicated block (81 lines × 5) Source/ADODB/Utils/ProjectInfo.cs:35 — Source/ADODB/Utils/ProjectInfo.cs:35-115 | Source/DAO/Utils/ProjectInfo.cs:35-115 | Source/MSComctlLib/Utils/ProjectInfo.cs:35-115 | Source/MSDATASRC/Utils/ProjectInfo.cs:35-115 | Source/Office/Utils/ProjectInfo.cs:35-115 — before extracting anything, compare `Source/ADODB/Utils/ProjectInfo.cs` and `Source/DAO/Utils/ProjectInfo.cs` as WHOLE FILES: 95% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (81 lines × 7) · ×1
  • Duplicated block (81 lines × 7) Source/Access/Utils/ProjectInfo.cs:35 — Source/Access/Utils/ProjectInfo.cs:35-115 | Source/Excel/Utils/ProjectInfo.cs:35-115 | Source/OWC10/Utils/ProjectInfo.cs:35-115 | Source/Outlook/Utils/ProjectInfo.cs:35-115 | Source/PowerPoint/Utils/ProjectInfo.cs:35-115 | Source/VBIDE/Utils/ProjectInfo.cs:35-115 | Source/Word/Utils/ProjectInfo.cs:35-115 — before extracting anything, compare `Source/Access/Utils/ProjectInfo.cs` and `Source/Excel/Utils/ProjectInfo.cs` as WHOLE FILES: 93% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (712 lines × 2) · ×1
  • Duplicated block (712 lines × 2) Source/Excel/DispatchInterfaces/WorksheetFunction.AverageIf.cs:27 — Source/Excel/DispatchInterfaces/WorksheetFunction.AverageIf.cs:27-738 | Source/Excel/Interfaces/IWorksheetFunction.AverageIf.cs:27-738 — before extracting anything, compare `Source/Excel/DispatchInterfaces/WorksheetFunction.AverageIf.cs` and `Source/Excel/Interfaces/IWorksheetFunction.AverageIf.cs` as WHOLE FILES: 99% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (753 lines × 2) · ×1
  • Duplicated block (753 lines × 2) Source/Excel/DispatchInterfaces/WorksheetFunction.Dummy19.cs:55 — Source/Excel/DispatchInterfaces/WorksheetFunction.Dummy19.cs:55-807 | Source/Excel/Interfaces/IWorksheetFunction.Dummy19.cs:55-807 — before extracting anything, compare `Source/Excel/DispatchInterfaces/WorksheetFunction.Dummy19.cs` and `Source/Excel/Interfaces/IWorksheetFunction.Dummy19.cs` as WHOLE FILES: 99% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (662 lines × 2) · ×1
  • Duplicated block (662 lines × 2) Source/Excel/DispatchInterfaces/WorksheetFunction.SumIfs.cs:53 — Source/Excel/DispatchInterfaces/WorksheetFunction.SumIfs.cs:53-714 | Source/Excel/Interfaces/IWorksheetFunction.SumIfs.cs:53-714 — before extracting anything, compare `Source/Excel/DispatchInterfaces/WorksheetFunction.SumIfs.cs` and `Source/Excel/Interfaces/IWorksheetFunction.SumIfs.cs` as WHOLE FILES: 99% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (764 lines × 2) · ×1
  • Duplicated block (764 lines × 2) Source/Excel/DispatchInterfaces/WorksheetFunction._WSFunction.cs:55 — Source/Excel/DispatchInterfaces/WorksheetFunction._WSFunction.cs:55-818 | Source/Excel/Interfaces/IWorksheetFunction._WSFunction.cs:55-818 — before extracting anything, compare `Source/Excel/DispatchInterfaces/WorksheetFunction._WSFunction.cs` and `Source/Excel/Interfaces/IWorksheetFunction._WSFunction.cs` as WHOLE FILES: 99% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (25 lines × 3) · ×1
  • Duplicated block (25 lines × 3) Source/Excel/Events/OLEObjectEvents.cs:49 — Source/Excel/Events/OLEObjectEvents.cs:49-73 | Source/PowerPoint/Events/OCXExtenderEvents.cs:49-73 | Source/Word/Events/OCXEvents.cs:49-73 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
D4 · Code Duplication · Duplicated block (5 lines × 102) · ×1
  • Duplicated block (5 lines × 102) Source/ADODB/DispatchInterfaces/Fields20.cs:213 — Source/ADODB/DispatchInterfaces/Fields20.cs:213-217 | Source/ADODB/DispatchInterfaces/Fields20_Deprecated.cs:213-217 | Source/ADODB/DispatchInterfaces/_Collection.cs:162-166 | Source/Access/DispatchInterfaces/Children.cs:180-184 | Source/Access/DispatchInterfaces/Controls.cs:211-215 | Source/Access/DispatchInterfaces/Properties.cs:211-215 | Source/Access/DispatchInterfaces/_Form.cs:3167-3171 | Source/Access/DispatchInterfaces/_Form2.cs:1001-1005 | Source/Access/DispatchInterfaces/_Form3.cs:1519-1523 | Source/Access/DispatchInterfaces/_Report.cs:2088-2092 | Source/Access/DispatchInterfaces/_Report2.cs:502-506 | Source/Access/DispatchInterfaces/_Report3.cs:1230-1234 | Source/Access/DispatchInterfaces/_TabControl.cs:2188-2192 | Source/DAO/DispatchInterfaces/_Collection.cs:162-166 | Source/Excel/DispatchInterfaces/Arcs.cs:1008-1012 | Source/Excel/DispatchInterfaces/Buttons.cs:1074-1078 | Source/Excel/DispatchInterfaces/ChartObjects.cs:712-716 | Source/Excel/DispatchInterfaces/Charts.cs:885-889 | Source/Excel/DispatchInterfaces/CheckBoxes.cs:947-951 | Source/Excel/DispatchInterfaces/DialogSheets.cs:852-856 | Source/Excel/DispatchInterfaces/DrawingObjects.cs:1621-1625 | Source/Excel/DispatchInterfaces/Drawings.cs:1074-1078 | Source/Excel/DispatchInterfaces/DropDowns.cs:1066-1070 | Source/Excel/DispatchInterfaces/EditBoxes.cs:901-905 | Source/Excel/DispatchInterfaces/FormatConditions.cs:406-410 | Source/Excel/DispatchInterfaces/GroupBoxes.cs:873-877 | Source/Excel/DispatchInterfaces/GroupObjects.cs:1216-1220 | Source/Excel/DispatchInterfaces/IconSets.cs:214-218 | Source/Excel/DispatchInterfaces/Labels.cs:866-870 | Source/Excel/DispatchInterfaces/Lines.cs:636-640 | Source/Excel/DispatchInterfaces/ListBoxes.cs:945-949 | Source/Excel/DispatchInterfaces/MenuItems.cs:359-363 | Source/Excel/DispatchInterfaces/Modules.cs:860-864 | Source/Excel/DispatchInterfaces/OLEObjects.cs:966-970 | Source/Excel/DispatchInterfaces/OptionButtons.cs:959-963 | Source/Excel/DispatchInterfaces/Ovals.cs:1014-1018 | Source/Excel/DispatchInterfaces/Phonetics.cs:351-355 | Source/Excel/DispatchInterfaces/Pictures.cs:674-678 | Source/Excel/DispatchInterfaces/PivotFields.cs:211-215 | Source/Excel/DispatchInterfaces/PivotItems.cs:222-226 | Source/Excel/DispatchInterfaces/Rectangles.cs:1031-1035 | Source/Excel/DispatchInterfaces/ScrollBars.cs:704-708 | Source/Excel/DispatchInterfaces/ServerViewableItems.cs:246-250 | Source/Excel/DispatchInterfaces/SheetViews.cs:214-218 | Source/Excel/DispatchInterfaces/Sheets.cs:937-941 | Source/Excel/DispatchInterfaces/Spinners.cs:687-691 | Source/Excel/DispatchInterfaces/TextBoxes.cs:1031-1035 | Source/Excel/DispatchInterfaces/UsedObjects.cs:214-218 | Source/Excel/DispatchInterfaces/Worksheets.cs:937-941 | Source/Excel/Interfaces/IArcs.cs:993-997 | Source/Excel/Interfaces/IButtons.cs:1073-1077 | Source/Excel/Interfaces/IChartObjects.cs:687-691 | Source/Excel/Interfaces/ICharts.cs:852-856 | Source/Excel/Interfaces/ICheckBoxes.cs:946-950 | Source/Excel/Interfaces/IDialogSheets.cs:852-856 | Source/Excel/Interfaces/IDrawingObjects.cs:1620-1624 | Source/Excel/Interfaces/IDrawings.cs:1073-1077 | Source/Excel/Interfaces/IDropDowns.cs:1065-1069 | Source/Excel/Interfaces/IEditBoxes.cs:900-904 | Source/Excel/Interfaces/IGroupBoxes.cs:873-877 | Source/Excel/Interfaces/IGroupObjects.cs:1216-1220 | Source/Excel/Interfaces/IIconSets.cs:209-213 | Source/Excel/Interfaces/ILabels.cs:866-870 | Source/Excel/Interfaces/ILines.cs:636-640 | Source/Excel/Interfaces/IListBoxes.cs:945-949 | Source/Excel/Interfaces/IMenuItems.cs:359-363 | Source/Excel/Interfaces/IModules.cs:860-864 | Source/Excel/Interfaces/IOLEObjects.cs:922-926 | Source/Excel/Interfaces/IOptionButtons.cs:959-963 | Source/Excel/Interfaces/IOvals.cs:1014-1018 | Source/Excel/Interfaces/IPhonetics.cs:337-341 | Source/Excel/Interfaces/IPictures.cs:674-678 | Source/Excel/Interfaces/IPivotFields.cs:206-210 | Source/Excel/Interfaces/IPivotItems.cs:216-220 | Source/Excel/Interfaces/IRange.cs:6566-6570 | Source/Excel/Interfaces/IRectangles.cs:1031-1035 | Source/Excel/Interfaces/IScrollBars.cs:704-708 | Source/Excel/Interfaces/IServerViewableItems.cs:238-242 | Source/Excel/Interfaces/ISheetViews.cs:209-213 | Source/Excel/Interfaces/ISpinners.cs:687-691 | Source/Excel/Interfaces/ITextBoxes.cs:1031-1035 | Source/Excel/Interfaces/IUsedObjects.cs:209-213 | Source/Excel/Interfaces/IWorksheets.cs:896-900 | Source/MSComctlLib/DispatchInterfaces/IControls.cs:169-173 | Source/OWC10/DispatchInterfaces/Criteria.cs:239-243 | Source/OWC10/DispatchInterfaces/Sheets.cs:365-369 | Source/OWC10/DispatchInterfaces/Worksheets.cs:365-369 | Source/OWC10/DispatchInterfaces/_Range.cs:1940-1944 | Source/Office/DispatchInterfaces/BalloonCheckboxes.cs:200-204 | Source/Office/DispatchInterfaces/BalloonLabels.cs:200-204 | Source/Office/DispatchInterfaces/ODSOColumns.cs:188-192 | Source/Office/DispatchInterfaces/ODSOFilters.cs:256-260 | Source/Office/DispatchInterfaces/ThemeColorScheme.cs:214-218 | Source/Outlook/DispatchInterfaces/Pages.cs:265-269 | Source/Outlook/DispatchInterfaces/Panes.cs:232-236 | Source/Outlook/DispatchInterfaces/PropertyPages.cs:267-271 | Source/Outlook/DispatchInterfaces/Selection.cs:257-261 | Source/Outlook/DispatchInterfaces/_Items.cs:415-419 | Source/Outlook/DispatchInterfaces/_Results.cs:349-353 | Source/Outlook/DispatchInterfaces/_SimpleItems.cs:231-235 | Source/PowerPoint/DispatchInterfaces/Collection.cs:163-167 | Source/Word/DispatchInterfaces/Frameset.cs:488-492 — before extracting anything, compare `Source/ADODB/DispatchInterfaces/Fields20.cs` and `Source/ADODB/DispatchInterfaces/Fields20_Deprecated.cs` as WHOLE FILES: 89% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (8 lines × 60) · ×1
  • Duplicated block (8 lines × 60) Source/Excel/DispatchInterfaces/CategoryCollection.cs:235 — Source/Excel/DispatchInterfaces/CategoryCollection.cs:235-242 | Source/Excel/DispatchInterfaces/Panes.cs:235-242 | Source/Excel/Interfaces/ICategoryCollection.cs:229-236 | Source/Excel/Interfaces/IPanes.cs:230-237 | Source/OWC10/DispatchInterfaces/ChChartFields.cs:203-210 | Source/OWC10/DispatchInterfaces/ChDataLabels.cs:465-472 | Source/OWC10/DispatchInterfaces/ChErrorBarsCollection.cs:222-229 | Source/OWC10/DispatchInterfaces/ChSegments.cs:222-229 | Source/OWC10/DispatchInterfaces/FieldListDragDataList.cs:190-197 | Source/OWC10/DispatchInterfaces/Headings.cs:217-224 | Source/Office/DispatchInterfaces/ODSOColumns.cs:206-213 | Source/Office/DispatchInterfaces/ODSOFilters.cs:274-281 | Source/Office/DispatchInterfaces/ServerPolicy.cs:277-284 | Source/Office/Interfaces/CategoryCollection.cs:231-238 | Source/Outlook/DispatchInterfaces/Actions.cs:271-278 | Source/Outlook/DispatchInterfaces/AddressEntries.cs:378-385 | Source/Outlook/DispatchInterfaces/AddressLists.cs:250-257 | Source/Outlook/DispatchInterfaces/Attachments.cs:314-321 | Source/Outlook/DispatchInterfaces/Conflicts.cs:291-298 | Source/Outlook/DispatchInterfaces/Exceptions.cs:250-257 | Source/Outlook/DispatchInterfaces/Links.cs:264-271 | Source/Outlook/DispatchInterfaces/Pages.cs:283-290 | Source/Outlook/DispatchInterfaces/Panes.cs:250-257 | Source/Outlook/DispatchInterfaces/PropertyPages.cs:285-292 | Source/Outlook/DispatchInterfaces/Recipients.cs:282-289 | Source/Outlook/DispatchInterfaces/Selection.cs:275-282 | Source/Outlook/DispatchInterfaces/SyncObjects.cs:265-272 | Source/Outlook/DispatchInterfaces/UserProperties.cs:326-333 | Source/Outlook/DispatchInterfaces/_Accounts.cs:250-257 | Source/Outlook/DispatchInterfaces/_AttachmentSelection.cs:274-281 | Source/Outlook/DispatchInterfaces/_AutoFormatRules.cs:303-310 | Source/Outlook/DispatchInterfaces/_Categories.cs:299-306 | Source/Outlook/DispatchInterfaces/_Columns.cs:282-289 | Source/Outlook/DispatchInterfaces/_Explorers.cs:275-282 | Source/Outlook/DispatchInterfaces/_Folders.cs:346-353 | Source/Outlook/DispatchInterfaces/_Inspectors.cs:261-268 | Source/Outlook/DispatchInterfaces/_Items.cs:433-440 | Source/Outlook/DispatchInterfaces/_NavigationFolders.cs:272-279 | Source/Outlook/DispatchInterfaces/_NavigationGroups.cs:283-290 | Source/Outlook/DispatchInterfaces/_NavigationModules.cs:261-268 | Source/Outlook/DispatchInterfaces/_OrderFields.cs:321-328 | Source/Outlook/DispatchInterfaces/_OutlookBarGroups.cs:284-291 | Source/Outlook/DispatchInterfaces/_OutlookBarShortcuts.cs:286-293 | Source/Outlook/DispatchInterfaces/_Results.cs:367-374 | Source/Outlook/DispatchInterfaces/_RuleActions.cs:488-495 | Source/Outlook/DispatchInterfaces/_RuleConditions.cs:600-607 | Source/Outlook/DispatchInterfaces/_Rules.cs:313-320 | Source/Outlook/DispatchInterfaces/_SimpleItems.cs:249-256 | Source/Outlook/DispatchInterfaces/_Stores.cs:250-257 | Source/Outlook/DispatchInterfaces/_TimeZones.cs:278-285 | Source/Outlook/DispatchInterfaces/_UserDefinedProperties.cs:323-330 | Source/Outlook/DispatchInterfaces/_ViewFields.cs:284-291 | Source/PowerPoint/DispatchInterfaces/CategoryCollection.cs:234-241 | Source/PowerPoint/DispatchInterfaces/PPRadioCluster.cs:232-239 | Source/Word/DispatchInterfaces/BuildingBlockEntries.cs:281-288 | Source/Word/DispatchInterfaces/BuildingBlocks.cs:275-282 | Source/Word/DispatchInterfaces/Categories.cs:234-241 | Source/Word/DispatchInterfaces/Editors.cs:245-252 | Source/Word/DispatchInterfaces/OMathArgs.cs:256-263 | Source/Word/DispatchInterfaces/OMathBreaks.cs:245-252 — before extracting anything, compare `Source/Excel/DispatchInterfaces/CategoryCollection.cs` and `Source/Excel/Interfaces/ICategoryCollection.cs` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (13 lines × 15) · ×1
  • Duplicated block (13 lines × 15) Source/Outlook/Classes/AppointmentItem.cs:857 — Source/Outlook/Classes/AppointmentItem.cs:857-869 | Source/Outlook/Classes/ContactItem.cs:859-871 | Source/Outlook/Classes/DistListItem.cs:859-871 | Source/Outlook/Classes/DocumentItem.cs:859-871 | Source/Outlook/Classes/JournalItem.cs:859-871 | Source/Outlook/Classes/MailItem.cs:859-871 | Source/Outlook/Classes/MeetingItem.cs:859-871 | Source/Outlook/Classes/PostItem.cs:859-871 | Source/Outlook/Classes/RemoteItem.cs:859-871 | Source/Outlook/Classes/ReportItem.cs:859-871 | Source/Outlook/Classes/TaskItem.cs:859-871 | Source/Outlook/Classes/TaskRequestAcceptItem.cs:859-871 | Source/Outlook/Classes/TaskRequestDeclineItem.cs:859-871 | Source/Outlook/Classes/TaskRequestItem.cs:859-871 | Source/Outlook/Classes/TaskRequestUpdateItem.cs:859-871 — before extracting anything, compare `Source/Outlook/Classes/ContactItem.cs` and `Source/Outlook/Classes/DistListItem.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (5 lines × 24) · ×1
  • Duplicated block (5 lines × 24) Source/MSComctlLib/DispatchInterfaces/IImageCombo.cs:294 — Source/MSComctlLib/DispatchInterfaces/IImageCombo.cs:294-298 | Source/MSComctlLib/DispatchInterfaces/IListView.cs:277-281 | Source/MSComctlLib/DispatchInterfaces/IProgressBar.cs:186-190 | Source/MSComctlLib/DispatchInterfaces/ISlider.cs:322-326 | Source/MSComctlLib/DispatchInterfaces/IStatusBar.cs:187-191 | Source/MSComctlLib/DispatchInterfaces/ITabStrip.cs:191-195 | Source/MSComctlLib/DispatchInterfaces/IToolbar.cs:219-223 | Source/MSComctlLib/DispatchInterfaces/ITreeView.cs:240-244 | Source/Outlook/DispatchInterfaces/_OlkBusinessCardControl.cs:119-123 | Source/Outlook/DispatchInterfaces/_OlkCategory.cs:209-213 | Source/Outlook/DispatchInterfaces/_OlkCheckBox.cs:261-265 | Source/Outlook/DispatchInterfaces/_OlkComboBox.cs:351-355 | Source/Outlook/DispatchInterfaces/_OlkCommandButton.cs:207-211 | Source/Outlook/DispatchInterfaces/_OlkContactPhoto.cs:137-141 | Source/Outlook/DispatchInterfaces/_OlkDateControl.cs:315-319 | Source/Outlook/DispatchInterfaces/_OlkFrameHeader.cs:207-211 | Source/Outlook/DispatchInterfaces/_OlkInfoBar.cs:119-123 | Source/Outlook/DispatchInterfaces/_OlkLabel.cs:279-283 | Source/Outlook/DispatchInterfaces/_OlkListBox.cs:243-247 | Source/Outlook/DispatchInterfaces/_OlkOptionButton.cs:279-283 | Source/Outlook/DispatchInterfaces/_OlkSenderPhoto.cs:137-141 | Source/Outlook/DispatchInterfaces/_OlkTextBox.cs:387-391 | Source/Outlook/DispatchInterfaces/_OlkTimeControl.cs:297-301 | Source/Outlook/DispatchInterfaces/_OlkTimeZoneControl.cs:191-195 — before extracting anything, compare `Source/MSComctlLib/DispatchInterfaces/IStatusBar.cs` and `Source/MSComctlLib/DispatchInterfaces/ITabStrip.cs` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (5 lines × 15) · ×1
  • Duplicated block (5 lines × 15) Source/MSComctlLib/DispatchInterfaces/IImageCombo.cs:169 — Source/MSComctlLib/DispatchInterfaces/IImageCombo.cs:169-173 | Source/MSComctlLib/DispatchInterfaces/IListView.cs:538-542 | Source/MSComctlLib/DispatchInterfaces/IStatusBar.cs:276-280 | Source/MSComctlLib/DispatchInterfaces/ITabStrip.cs:153-157 | Source/MSComctlLib/DispatchInterfaces/ITreeView.cs:434-438 | Source/Outlook/DispatchInterfaces/_OlkCheckBox.cs:227-231 | Source/Outlook/DispatchInterfaces/_OlkComboBox.cs:263-267 | Source/Outlook/DispatchInterfaces/_OlkCommandButton.cs:191-195 | Source/Outlook/DispatchInterfaces/_OlkDateControl.cs:245-249 | Source/Outlook/DispatchInterfaces/_OlkFrameHeader.cs:155-159 | Source/Outlook/DispatchInterfaces/_OlkLabel.cs:245-249 | Source/Outlook/DispatchInterfaces/_OlkListBox.cs:173-177 | Source/Outlook/DispatchInterfaces/_OlkOptionButton.cs:227-231 | Source/Outlook/DispatchInterfaces/_OlkTextBox.cs:281-285 | Source/Outlook/DispatchInterfaces/_OlkTimeControl.cs:227-231 — before extracting anything, compare `Source/MSComctlLib/DispatchInterfaces/IStatusBar.cs` and `Source/MSComctlLib/DispatchInterfaces/ITabStrip.cs` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (8 lines × 70) · ×1
  • Duplicated block (8 lines × 70) Source/Access/Events/DispAttachmentEvents.cs:236 — Source/Access/Events/DispAttachmentEvents.cs:236-243 | Source/Access/Events/DispBoundObjectFrameEvents.cs:217-224 | Source/Access/Events/DispCheckBoxEvents.cs:123-130 | Source/Access/Events/DispComboBoxEvents.cs:246-253 | Source/Access/Events/DispCommandButtonEvents.cs:113-120 | Source/Access/Events/DispImageEvents.cs:80-87 | Source/Access/Events/DispLabelEvents.cs:80-87 | Source/Access/Events/DispListBoxEvents.cs:197-204 | Source/Access/Events/DispNavigationButtonEvents.cs:114-121 | Source/Access/Events/DispNavigationControlEvents.cs:222-229 | Source/Access/Events/DispObjectFrameEvents.cs:165-172 | Source/Access/Events/DispOptionButtonEvents.cs:121-128 | Source/Access/Events/DispOptionGroupEvents.cs:150-157 | Source/Access/Events/DispPageEvents.cs:80-87 | Source/Access/Events/DispPageHdrFtrInReportEvents.cs:130-137 | Source/Access/Events/DispPaletteButtonEvents.cs:123-130 | Source/Access/Events/DispRectangleEvents.cs:80-87 | Source/Access/Events/DispSectionEvents.cs:84-91 | Source/Access/Events/DispSectionInReportEvents.cs:145-152 | Source/Access/Events/DispTabControlEvents.cs:101-108 | Source/Access/Events/DispTextBoxEvents.cs:222-229 | Source/Access/Events/DispToggleButtonEvents.cs:123-130 | Source/Access/Events/DispWebBrowserControlEvents.cs:275-282 | Source/Access/Events/_BoundObjectFrameEvents.cs:217-224 | Source/Access/Events/_CheckBoxEvents.cs:123-130 | Source/Access/Events/_ComboBoxEvents.cs:244-251 | Source/Access/Events/_CommandButtonEvents.cs:113-120 | Source/Access/Events/_FormEvents.cs:554-561 | Source/Access/Events/_FormEvents2.cs:530-537 | Source/Access/Events/_ImageEvents.cs:80-87 | Source/Access/Events/_LabelEvents.cs:80-87 | Source/Access/Events/_ListBoxEvents.cs:196-203 | Source/Access/Events/_ObjectFrameEvents.cs:165-172 | Source/Access/Events/_OptionButtonEvents.cs:123-130 | Source/Access/Events/_OptionGroupEvents.cs:150-157 | Source/Access/Events/_PageEvents.cs:80-87 | Source/Access/Events/_PageHdrFtrInReportEvents.cs:126-133 | Source/Access/Events/_PaletteButtonEvents.cs:123-130 | Source/Access/Events/_RectangleEvents.cs:80-87 | Source/Access/Events/_ReportEvents2.cs:337-344 | Source/Access/Events/_SectionEvents.cs:84-91 | Source/Access/Events/_SectionInReportEvents.cs:145-152 | Source/Access/Events/_TabControlEvents.cs:101-108 | Source/Access/Events/_TextBoxEvents.cs:220-227 | Source/Access/Events/_ToggleButtonEvents.cs:123-130 | Source/MSComctlLib/Events/DImageComboEvents.cs:142-149 | Source/MSComctlLib/Events/IProgressBarEvents.cs:179-186 | Source/MSComctlLib/Events/ISliderEvents.cs:144-151 | Source/MSComctlLib/Events/IStatusBarEvents.cs:221-228 | Source/MSComctlLib/Events/IToolbarEvents.cs:167-174 | Source/MSComctlLib/Events/ITreeViewEvents.cs:353-360 | Source/MSComctlLib/Events/ListViewEvents.cs:335-342 | Source/OWC10/Events/IChartEvents.cs:218-225 | Source/OWC10/Events/IPivotControlEvents.cs:388-395 | Source/OWC10/Events/ISpreadsheetEventSink.cs:299-306 | Source/Outlook/Events/OlkBusinessCardControlEvents.cs:79-86 | Source/Outlook/Events/OlkCategoryEvents.cs:109-116 | Source/Outlook/Events/OlkCheckBoxEvents.cs:118-125 | Source/Outlook/Events/OlkComboBoxEvents.cs:122-129 | Source/Outlook/Events/OlkCommandButtonEvents.cs:114-121 | Source/Outlook/Events/OlkContactPhotoEvents.cs:109-116 | Source/Outlook/Events/OlkDateControlEvents.cs:122-129 | Source/Outlook/Events/OlkInfoBarEvents.cs:79-86 | Source/Outlook/Events/OlkLabelEvents.cs:79-86 | Source/Outlook/Events/OlkListBoxEvents.cs:118-125 | Source/Outlook/Events/OlkOptionButtonEvents.cs:118-125 | Source/Outlook/Events/OlkSenderPhotoEvents.cs:83-90 | Source/Outlook/Events/OlkTextBoxEvents.cs:118-125 | Source/Outlook/Events/OlkTimeControlEvents.cs:122-129 | Source/Outlook/Events/OlkTimeZoneControlEvents.cs:122-129 — before extracting anything, compare `Source/Access/Events/DispAttachmentEvents.cs` and `Source/Access/Events/DispBoundObjectFrameEvents.cs` as WHOLE FILES: this scan already matched 29 separate duplicated blocks between them, totalling at least 271 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (8 lines × 15) · ×1
  • Duplicated block (8 lines × 15) Source/Outlook/Events/OlkBusinessCardControlEvents.cs:90 — Source/Outlook/Events/OlkBusinessCardControlEvents.cs:90-97 | Source/Outlook/Events/OlkCategoryEvents.cs:120-127 | Source/Outlook/Events/OlkCheckBoxEvents.cs:129-136 | Source/Outlook/Events/OlkComboBoxEvents.cs:133-140 | Source/Outlook/Events/OlkCommandButtonEvents.cs:125-132 | Source/Outlook/Events/OlkContactPhotoEvents.cs:120-127 | Source/Outlook/Events/OlkDateControlEvents.cs:133-140 | Source/Outlook/Events/OlkInfoBarEvents.cs:90-97 | Source/Outlook/Events/OlkLabelEvents.cs:90-97 | Source/Outlook/Events/OlkListBoxEvents.cs:129-136 | Source/Outlook/Events/OlkOptionButtonEvents.cs:129-136 | Source/Outlook/Events/OlkSenderPhotoEvents.cs:94-101 | Source/Outlook/Events/OlkTextBoxEvents.cs:129-136 | Source/Outlook/Events/OlkTimeControlEvents.cs:133-140 | Source/Outlook/Events/OlkTimeZoneControlEvents.cs:133-140 — before extracting anything, compare `Source/Outlook/Events/OlkBusinessCardControlEvents.cs` and `Source/Outlook/Events/OlkCategoryEvents.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 61 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (8 lines × 43) · ×1
  • Duplicated block (8 lines × 43) Source/Access/Events/DispAttachmentEvents.cs:162 — Source/Access/Events/DispAttachmentEvents.cs:162-169 | Source/Access/Events/DispBoundObjectFrameEvents.cs:169-176 | Source/Access/Events/DispCheckBoxEvents.cs:161-168 | Source/Access/Events/DispComboBoxEvents.cs:198-205 | Source/Access/Events/DispCommandButtonEvents.cs:124-131 | Source/Access/Events/DispCustomControlEvents.cs:84-91 | Source/Access/Events/DispListBoxEvents.cs:149-156 | Source/Access/Events/DispNavigationButtonEvents.cs:125-132 | Source/Access/Events/DispNavigationControlEvents.cs:174-181 | Source/Access/Events/DispObjectFrameEvents.cs:117-124 | Source/Access/Events/DispOptionButtonEvents.cs:158-165 | Source/Access/Events/DispOptionGroupEvents.cs:124-131 | Source/Access/Events/DispPaletteButtonEvents.cs:160-167 | Source/Access/Events/DispSubFormEvents.cs:56-63 | Source/Access/Events/DispSubReportEvents.cs:56-63 | Source/Access/Events/DispTextBoxEvents.cs:174-181 | Source/Access/Events/DispToggleButtonEvents.cs:160-167 | Source/Access/Events/DispWebBrowserControlEvents.cs:201-208 | Source/Access/Events/_BoundObjectFrameEvents.cs:169-176 | Source/Access/Events/_CheckBoxEvents.cs:160-167 | Source/Access/Events/_ComboBoxEvents.cs:196-203 | Source/Access/Events/_CommandButtonEvents.cs:124-131 | Source/Access/Events/_CustomControlEvents.cs:83-90 | Source/Access/Events/_ListBoxEvents.cs:148-155 | Source/Access/Events/_ObjectFrameEvents.cs:117-124 | Source/Access/Events/_OptionButtonEvents.cs:160-167 | Source/Access/Events/_OptionGroupEvents.cs:124-131 | Source/Access/Events/_PaletteButtonEvents.cs:160-167 | Source/Access/Events/_SubFormEvents.cs:56-63 | Source/Access/Events/_SubReportEvents.cs:56-63 | Source/Access/Events/_TextBoxEvents.cs:172-179 | Source/Access/Events/_ToggleButtonEvents.cs:160-167 | Source/Outlook/Events/OlkCategoryEvents.cs:191-198 | Source/Outlook/Events/OlkCheckBoxEvents.cs:200-207 | Source/Outlook/Events/OlkComboBoxEvents.cs:204-211 | Source/Outlook/Events/OlkCommandButtonEvents.cs:196-203 | Source/Outlook/Events/OlkContactPhotoEvents.cs:191-198 | Source/Outlook/Events/OlkDateControlEvents.cs:204-211 | Source/Outlook/Events/OlkListBoxEvents.cs:200-207 | Source/Outlook/Events/OlkOptionButtonEvents.cs:200-207 | Source/Outlook/Events/OlkTextBoxEvents.cs:200-207 | Source/Outlook/Events/OlkTimeControlEvents.cs:204-211 | Source/Outlook/Events/OlkTimeZoneControlEvents.cs:204-211 — before extracting anything, compare `Source/Access/Events/DispAttachmentEvents.cs` and `Source/Access/Events/DispBoundObjectFrameEvents.cs` as WHOLE FILES: this scan already matched 29 separate duplicated blocks between them, totalling at least 271 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (9 lines × 23) · ×1
  • Duplicated block (9 lines × 23) Source/Access/Events/DispAttachmentEvents.cs:202 — Source/Access/Events/DispAttachmentEvents.cs:202-210 | Source/Access/Events/DispComboBoxEvents.cs:169-177 | Source/Access/Events/DispNavigationControlEvents.cs:162-170 | Source/Access/Events/DispTextBoxEvents.cs:162-170 | Source/Access/Events/DispWebBrowserControlEvents.cs:241-249 | Source/Access/Events/_ComboBoxEvents.cs:167-175 | Source/Access/Events/_TabControlEvents.cs:238-246 | Source/Access/Events/_TextBoxEvents.cs:160-168 | Source/MSComctlLib/Events/DImageComboEvents.cs:119-127 | Source/MSComctlLib/Events/ISliderEvents.cs:274-282 | Source/MSComctlLib/Events/IToolbarEvents.cs:155-163 | Source/OWC10/Events/IRangeEvents.cs:50-58 | Source/Outlook/Events/OlkCategoryEvents.cs:265-273 | Source/Outlook/Events/OlkCheckBoxEvents.cs:274-282 | Source/Outlook/Events/OlkComboBoxEvents.cs:278-286 | Source/Outlook/Events/OlkContactPhotoEvents.cs:265-273 | Source/Outlook/Events/OlkDateControlEvents.cs:278-286 | Source/Outlook/Events/OlkListBoxEvents.cs:274-282 | Source/Outlook/Events/OlkOptionButtonEvents.cs:274-282 | Source/Outlook/Events/OlkSenderPhotoEvents.cs:164-172 | Source/Outlook/Events/OlkTextBoxEvents.cs:274-282 | Source/Outlook/Events/OlkTimeControlEvents.cs:278-286 | Source/Outlook/Events/OlkTimeZoneControlEvents.cs:278-286 — before extracting anything, compare `Source/Access/Events/DispAttachmentEvents.cs` and `Source/Access/Events/DispComboBoxEvents.cs` as WHOLE FILES: this scan already matched 36 separate duplicated blocks between them, totalling at least 321 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Source/Outlook/Events/OlkCategoryEvents.cs:261` calls `ToInt32` and `Source/MSComctlLib/Events/IToolbarEvents.cs:151` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (8 lines × 32) · ×1
  • Duplicated block (8 lines × 32) Source/Access/Events/DispAttachmentEvents.cs:150 — Source/Access/Events/DispAttachmentEvents.cs:150-158 | Source/Access/Events/DispBoundObjectFrameEvents.cs:157-165 | Source/Access/Events/DispCheckBoxEvents.cs:149-157 | Source/Access/Events/DispComboBoxEvents.cs:158-166 | Source/Access/Events/DispListBoxEvents.cs:137-145 | Source/Access/Events/DispNavigationControlEvents.cs:151-159 | Source/Access/Events/DispOptionButtonEvents.cs:146-154 | Source/Access/Events/DispOptionGroupEvents.cs:112-120 | Source/Access/Events/DispPaletteButtonEvents.cs:148-156 | Source/Access/Events/DispTextBoxEvents.cs:151-159 | Source/Access/Events/DispToggleButtonEvents.cs:148-156 | Source/Access/Events/DispWebBrowserControlEvents.cs:189-197 | Source/Access/Events/_BoundObjectFrameEvents.cs:157-165 | Source/Access/Events/_CheckBoxEvents.cs:148-156 | Source/Access/Events/_ComboBoxEvents.cs:156-164 | Source/Access/Events/_FormEvents.cs:400-407 | Source/Access/Events/_FormEvents2.cs:375-383 | Source/Access/Events/_ListBoxEvents.cs:136-144 | Source/Access/Events/_OptionButtonEvents.cs:148-156 | Source/Access/Events/_OptionGroupEvents.cs:112-120 | Source/Access/Events/_PaletteButtonEvents.cs:148-156 | Source/Access/Events/_TextBoxEvents.cs:149-157 | Source/Access/Events/_ToggleButtonEvents.cs:148-156 | Source/Outlook/Events/OlkCheckBoxEvents.cs:285-293 | Source/Outlook/Events/OlkComboBoxEvents.cs:300-308 | Source/Outlook/Events/OlkCommandButtonEvents.cs:270-278 | Source/Outlook/Events/OlkDateControlEvents.cs:300-308 | Source/Outlook/Events/OlkListBoxEvents.cs:285-293 | Source/Outlook/Events/OlkOptionButtonEvents.cs:285-293 | Source/Outlook/Events/OlkTextBoxEvents.cs:285-293 | Source/Outlook/Events/OlkTimeControlEvents.cs:300-308 | Source/Outlook/Events/OlkTimeZoneControlEvents.cs:300-308 — before extracting anything, compare `Source/Access/Events/DispAttachmentEvents.cs` and `Source/Access/Events/DispBoundObjectFrameEvents.cs` as WHOLE FILES: this scan already matched 29 separate duplicated blocks between them, totalling at least 271 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Near-duplicate member family (16 members, 17 shared lines) · ×1
  • Near-duplicate member family (16 members, 17 shared lines) Examples/Access/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:149 — Examples/Access/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:149-180 | Examples/Access/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:123-154 | Examples/Access/IExtensibility COMAddin Examples/TaskPane/Addin.cs:101-132 | Examples/Excel/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:92-123 | Examples/Excel/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:117-148 | Examples/Excel/IExtensibility COMAddin Examples/TaskPane/Addin.cs:101-132 | Examples/Other/IExtensibility2 Examples/SuperAddin/Addin.cs:139-169 | Examples/Outlook/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:88-121 | Examples/Outlook/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:118-150 | Examples/Outlook/IExtensibility COMAddin Examples/TaskPane/Addin.cs:103-135 | Examples/PowerPoint/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:90-122 | Examples/PowerPoint/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:121-153 | Examples/PowerPoint/IExtensibility COMAddin Examples/TaskPane/Addin.cs:101-133 | Examples/Word/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:98-130 | Examples/Word/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:119-151 | Examples/Word/IExtensibility COMAddin Examples/TaskPane/Addin.cs:101-133 — These 16 members are variants of one another: a block of 17 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 16 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 16 times.
D4 · Code Duplication · Near-duplicate member family (15 members, 27 shared lines) · ×1
  • Near-duplicate member family (15 members, 27 shared lines) Examples/Access/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:149 — Examples/Access/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:149-180 | Examples/Access/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:123-154 | Examples/Access/IExtensibility COMAddin Examples/TaskPane/Addin.cs:101-132 | Examples/Excel/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:92-123 | Examples/Excel/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:117-148 | Examples/Excel/IExtensibility COMAddin Examples/TaskPane/Addin.cs:101-132 | Examples/Outlook/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:88-121 | Examples/Outlook/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:118-150 | Examples/Outlook/IExtensibility COMAddin Examples/TaskPane/Addin.cs:103-135 | Examples/PowerPoint/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:90-122 | Examples/PowerPoint/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:121-153 | Examples/PowerPoint/IExtensibility COMAddin Examples/TaskPane/Addin.cs:101-133 | Examples/Word/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:98-130 | Examples/Word/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:119-151 | Examples/Word/IExtensibility COMAddin Examples/TaskPane/Addin.cs:101-133 — These 15 members are variants of one another: a block of 27 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 15 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 15 times.
D4 · Code Duplication · Near-duplicate member family (4 members, 42 shared lines) · ×1
  • Near-duplicate member family (4 members, 42 shared lines) Examples/Excel/Automation/Examples/Example09.cs:75 — Examples/Excel/Automation/Examples/Example09.cs:75-174 | Examples/Outlook/Automation/Examples/Example07.cs:74-141 | Examples/PowerPoint/Automation/Examples/Example07.cs:84-168 | Examples/Word/Automation/Examples/Example07.cs:98-186 — These 4 members are variants of one another: a block of 42 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Edited copies of one member (4 members, 22+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 22+ corresponding lines) Examples/Access/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:93 — Examples/Access/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:93-115 | Examples/Excel/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:88-109 | Examples/PowerPoint/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:92-113 | Examples/Word/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:90-111 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (20 corresponding lines) · ×1
  • Edited copy of a member (20 corresponding lines) Examples/Outlook/Automation/Examples/Example03.cs:63 — Examples/Outlook/Automation/Examples/Example03.cs:63-82 | Examples/Outlook/Automation/Examples/Example02.cs:15-35 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 14+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 14+ corresponding lines) Examples/Access/NetOffice COMAddin Examples/02 Ribbons And Panes/SamplePane.cs:43 — Examples/Access/NetOffice COMAddin Examples/02 Ribbons And Panes/SamplePane.cs:43-56 | Examples/Excel/NetOffice COMAddin Examples/02 Ribbons And Panes/SamplePane.cs:43-56 | Examples/Outlook/NetOffice COMAddin Examples/02 Ribbons And Panes/SamplePane.cs:43-57 | Examples/PowerPoint/NetOffice COMAddin Examples/02 Ribbons And Panes/SamplePane.cs:43-56 | Examples/Word/NetOffice COMAddin Examples/02 Ribbons And Panes/SamplePane.cs:43-56 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 13+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 13+ corresponding lines) Examples/Access/NetOffice COMAddin Examples/03 Troubleshooting and Diagnostics/Addin.cs:71 — Examples/Access/NetOffice COMAddin Examples/03 Troubleshooting and Diagnostics/Addin.cs:71-83 | Examples/Excel/NetOffice COMAddin Examples/03 Troubleshooting and Diagnostics/Addin.cs:71-87 | Examples/Word/NetOffice COMAddin Examples/03 Troubleshooting and Diagnostics/Addin.cs:71-83 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 6+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 6+ corresponding lines) Examples/Access/NetOffice COMAddin Examples/02 Ribbons And Panes/SamplePane.cs:68 — Examples/Access/NetOffice COMAddin Examples/02 Ribbons And Panes/SamplePane.cs:68-73 | Examples/Excel/NetOffice COMAddin Examples/02 Ribbons And Panes/SamplePane.cs:68-73 | Examples/Outlook/NetOffice COMAddin Examples/02 Ribbons And Panes/SamplePane.cs:69-74 | Examples/PowerPoint/NetOffice COMAddin Examples/02 Ribbons And Panes/SamplePane.cs:68-73 | Examples/Word/NetOffice COMAddin Examples/02 Ribbons And Panes/SamplePane.cs:68-73 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (28 lines × 5) · ×1
  • Duplicated block (28 lines × 5) Examples/Access/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:95 — Examples/Access/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:95-122 | Examples/Excel/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:157-184 | Examples/Outlook/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:154-181 | Examples/PowerPoint/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:150-177 | Examples/Word/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:207-234 — before extracting anything, compare `Examples/Access/IExtensibility COMAddin Examples/ClassicUI/Addin.cs` and `Examples/Excel/IExtensibility COMAddin Examples/ClassicUI/Addin.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 90 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (25 lines × 5) · ×1
  • Duplicated block (25 lines × 5) REDACTED:53 — REDACTED:53-77 | REDACTED:53-77 | REDACTED:56-80 | REDACTED:55-79 | REDACTED:54-78 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 106 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:53` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (24–25 lines × 6) · ×1
  • Duplicated block (24–25 lines × 6) Examples/Outlook/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:97 — Examples/Outlook/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:97-121 | Examples/Outlook/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:127-150 | Examples/Outlook/IExtensibility COMAddin Examples/TaskPane/Addin.cs:112-135 | Examples/Word/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:107-130 | Examples/Word/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:128-151 | Examples/Word/IExtensibility COMAddin Examples/TaskPane/Addin.cs:110-133 — `Examples/Outlook/IExtensibility COMAddin Examples/ClassicUI/Addin.cs` and `Examples/Outlook/IExtensibility COMAddin Examples/RibbonUI/Addin.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 90 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `Examples/Outlook/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:97` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (24 lines × 5) · ×1
  • Duplicated block (24 lines × 5) Examples/Access/NetOffice COMAddin Examples/03 Troubleshooting and Diagnostics/Addin.cs:45 — Examples/Access/NetOffice COMAddin Examples/03 Troubleshooting and Diagnostics/Addin.cs:45-68 | Examples/Excel/NetOffice COMAddin Examples/03 Troubleshooting and Diagnostics/Addin.cs:45-68 | Examples/Outlook/NetOffice COMAddin Examples/03 Troubleshooting and Diagnostics/Addin.cs:47-70 | Examples/PowerPoint/NetOffice COMAddin Examples/03 Troubleshooting and Diagnostics/Addin.cs:45-68 | Examples/Word/NetOffice COMAddin Examples/03 Troubleshooting and Diagnostics/Addin.cs:45-68 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Examples/Access/NetOffice COMAddin Examples/03 Troubleshooting and Diagnostics/Addin.cs:45` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (23–24 lines × 2) · ×1
  • Duplicated block (23–24 lines × 2) Examples/Excel/Automation/Examples/Example01.cs:19 — Examples/Excel/Automation/Examples/Example01.cs:19-42 | Examples/Excel/Automation/Examples/Example10.cs:20-42 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (10–22 lines × 8) · ×1
  • Duplicated block (10–22 lines × 8) Examples/Excel/Automation/Examples/Example09.cs:92 — Examples/Excel/Automation/Examples/Example09.cs:92-113 | Examples/Excel/Automation/Examples/Example09.cs:131-140 | Examples/Outlook/Automation/Examples/Example07.cs:86-107 | Examples/Outlook/Automation/Examples/Example07.cs:125-134 | Examples/PowerPoint/Automation/Examples/Example07.cs:96-117 | Examples/PowerPoint/Automation/Examples/Example07.cs:135-144 | Examples/Word/Automation/Examples/Example07.cs:113-134 | Examples/Word/Automation/Examples/Example07.cs:152-161 — before extracting anything, compare `Examples/Excel/Automation/Examples/Example09.cs` and `Examples/Outlook/Automation/Examples/Example07.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Examples/Excel/Automation/Examples/Example09.cs:92` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (17 lines × 16) · ×1
  • Duplicated block (17 lines × 16) Examples/Access/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:150 — Examples/Access/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:150-166 | Examples/Access/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:124-140 | Examples/Access/IExtensibility COMAddin Examples/TaskPane/Addin.cs:102-118 | Examples/Excel/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:93-109 | Examples/Excel/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:118-134 | Examples/Excel/IExtensibility COMAddin Examples/TaskPane/Addin.cs:102-118 | Examples/Other/IExtensibility2 Examples/SuperAddin/Addin.cs:140-156 | Examples/Outlook/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:89-105 | Examples/Outlook/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:119-135 | Examples/Outlook/IExtensibility COMAddin Examples/TaskPane/Addin.cs:104-120 | Examples/PowerPoint/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:91-107 | Examples/PowerPoint/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:122-138 | Examples/PowerPoint/IExtensibility COMAddin Examples/TaskPane/Addin.cs:102-118 | Examples/Word/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:99-115 | Examples/Word/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:120-136 | Examples/Word/IExtensibility COMAddin Examples/TaskPane/Addin.cs:102-118 — `Examples/Access/IExtensibility COMAddin Examples/ClassicUI/Addin.cs` and `Examples/Access/IExtensibility COMAddin Examples/RibbonUI/Addin.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 83 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `Examples/Access/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:150` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (17–18 lines × 5) · ×1
  • Duplicated block (17–18 lines × 5) REDACTED:31 — REDACTED:31-47 | REDACTED:31-47 | REDACTED:33-50 | REDACTED:33-49 | REDACTED:32-48 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 106 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:31` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (12–16 lines × 6) · ×1
  • Duplicated block (12–16 lines × 6) Examples/Outlook/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:125 — Examples/Outlook/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:125-136 | Examples/Outlook/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:154-165 | Examples/Outlook/IExtensibility COMAddin Examples/TaskPane/Addin.cs:139-154 | Examples/Word/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:134-145 | Examples/Word/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:155-166 | Examples/Word/IExtensibility COMAddin Examples/TaskPane/Addin.cs:137-152 — `Examples/Outlook/IExtensibility COMAddin Examples/ClassicUI/Addin.cs` and `Examples/Outlook/IExtensibility COMAddin Examples/RibbonUI/Addin.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 90 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
D4 · Code Duplication · Duplicated block (10–14 lines × 9) · ×1
  • Duplicated block (10–14 lines × 9) Examples/Access/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:184 — Examples/Access/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:184-193 | Examples/Access/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:158-167 | Examples/Access/IExtensibility COMAddin Examples/TaskPane/Addin.cs:136-149 | Examples/Excel/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:127-140 | Examples/Excel/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:152-165 | Examples/Excel/IExtensibility COMAddin Examples/TaskPane/Addin.cs:136-148 | Examples/PowerPoint/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:126-135 | Examples/PowerPoint/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:157-166 | Examples/PowerPoint/IExtensibility COMAddin Examples/TaskPane/Addin.cs:137-150 — `Examples/Access/IExtensibility COMAddin Examples/ClassicUI/Addin.cs` and `Examples/Access/IExtensibility COMAddin Examples/RibbonUI/Addin.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 83 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `Examples/Access/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:184` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (11–12 lines × 5) · ×1
  • Duplicated block (11–12 lines × 5) Examples/Excel/Automation/Examples/Example09.cs:121 — Examples/Excel/Automation/Examples/Example09.cs:121-131 | Examples/Outlook/Automation/Examples/Example07.cs:115-125 | Examples/PowerPoint/Automation/Examples/Example07.cs:125-135 | Examples/Word/Automation/Examples/Example07.cs:142-152 | Examples/Word/Automation/Examples/Example07.cs:169-180 — before extracting anything, compare `Examples/Excel/Automation/Examples/Example09.cs` and `Examples/Outlook/Automation/Examples/Example07.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (10–11 lines × 15) · ×1
  • Duplicated block (10–11 lines × 15) Examples/Access/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:169 — Examples/Access/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:169-178 | Examples/Access/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:143-152 | Examples/Access/IExtensibility COMAddin Examples/TaskPane/Addin.cs:121-130 | Examples/Excel/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:112-121 | Examples/Excel/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:137-146 | Examples/Excel/IExtensibility COMAddin Examples/TaskPane/Addin.cs:121-130 | Examples/Outlook/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:109-119 | Examples/Outlook/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:139-148 | Examples/Outlook/IExtensibility COMAddin Examples/TaskPane/Addin.cs:124-133 | Examples/PowerPoint/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:111-120 | Examples/PowerPoint/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:142-151 | Examples/PowerPoint/IExtensibility COMAddin Examples/TaskPane/Addin.cs:122-131 | Examples/Word/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:119-128 | Examples/Word/IExtensibility COMAddin Examples/RibbonUI/Addin.cs:140-149 | Examples/Word/IExtensibility COMAddin Examples/TaskPane/Addin.cs:122-131 — `Examples/Access/IExtensibility COMAddin Examples/ClassicUI/Addin.cs` and `Examples/Access/IExtensibility COMAddin Examples/RibbonUI/Addin.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 83 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `Examples/Access/IExtensibility COMAddin Examples/ClassicUI/Addin.cs:169` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (8–10 lines × 2) · ×1
  • Duplicated block (8–10 lines × 2) Examples/Word/Automation/Examples/Example03.cs:40 — Examples/Word/Automation/Examples/Example03.cs:40-47 | Examples/Word/Automation/Examples/Example03.cs:57-66 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (7 lines × 9) · ×1
  • Duplicated block (7 lines × 9) Examples/Excel/Automation/Examples/Example09.cs:92 — Examples/Excel/Automation/Examples/Example09.cs:92-110 | Examples/Excel/Automation/Examples/Example09.cs:131-137 | Examples/Outlook/Automation/Examples/Example07.cs:86-104 | Examples/Outlook/Automation/Examples/Example07.cs:125-131 | Examples/PowerPoint/Automation/Examples/Example07.cs:96-114 | Examples/PowerPoint/Automation/Examples/Example07.cs:135-141 | Examples/Word/Automation/Examples/Example07.cs:113-131 | Examples/Word/Automation/Examples/Example07.cs:152-158 | Examples/Word/Automation/Examples/Example07.cs:168-174 — before extracting anything, compare `Examples/Excel/Automation/Examples/Example09.cs` and `Examples/Outlook/Automation/Examples/Example07.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Examples/Excel/Automation/Examples/Example09.cs:92` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (17 lines × 4) · ×1
  • Duplicated block (17 lines × 4) Examples/Access/IExtensibility COMAddin Examples/TaskPane/SampleData/Customer.cs:18 — Examples/Access/IExtensibility COMAddin Examples/TaskPane/SampleData/Customer.cs:18-34 | Examples/Excel/IExtensibility COMAddin Examples/TaskPane/SampleData/Customer.cs:18-34 | Examples/PowerPoint/IExtensibility COMAddin Examples/TaskPane/SampleData/Customer.cs:18-34 | Examples/Word/IExtensibility COMAddin Examples/TaskPane/SampleData/Customer.cs:18-40 — before extracting anything, compare `Examples/Access/IExtensibility COMAddin Examples/TaskPane/SampleData/Customer.cs` and `Examples/Excel/IExtensibility COMAddin Examples/TaskPane/SampleData/Customer.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (21 lines × 5) · ×1
  • Duplicated block (21 lines × 5) Examples/Access/NetOffice COMAddin Examples/02 Ribbons And Panes/Addin.cs:29 — Examples/Access/NetOffice COMAddin Examples/02 Ribbons And Panes/Addin.cs:29-49 | Examples/Excel/NetOffice COMAddin Examples/02 Ribbons And Panes/Addin.cs:29-49 | Examples/Outlook/NetOffice COMAddin Examples/02 Ribbons And Panes/Addin.cs:30-50 | Examples/PowerPoint/NetOffice COMAddin Examples/02 Ribbons And Panes/Addin.cs:29-49 | Examples/Word/NetOffice COMAddin Examples/02 Ribbons And Panes/Addin.cs:29-49 — before extracting anything, compare `Examples/Access/NetOffice COMAddin Examples/02 Ribbons And Panes/Addin.cs` and `Examples/Excel/NetOffice COMAddin Examples/02 Ribbons And Panes/Addin.cs` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D5 · Coupling · Unstable project AccessApi · ×1
  • Unstable project AccessApi Source/Access/AccessApi.csproj:1 — AccessApi has instability 0.73 with 3 dependents.
IC1 · Incompleteness & stubs · Both branches are identical · ×1
  • Both branches are identical — the condition decides nothing Toolbox/Toolbox/ToolboxControls/ProjectWizard/Controls/ProjectControl.cs:199 — The `if` and its `else` contain the same 1 statement, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body.
P12 · CI test-gate honesty · CI test gate excludes suites by filter · ×1
  • CI test gate excludes suites by filter REDACTED:67 — `dotnet test --filter "TestCategory != IntegrationTests" Source\NetOffice.sln` filters with `TestCategory != IntegrationTests` — the suites it excludes. Run what it drops in another job before merge (a complementary filter), or remove the filter.
P12 · CI test-gate honesty · Test suite runs only after the merge · ×1
  • Test suite runs only after the merge — `REDACTED` run(s) the test suite, but no workflow that runs tests is triggered by a pull request (or a merge queue) — so the suite reports on code that is already on the default branch. A red build there blocks nothing and the only remedy is a revert. Add the pull-request trigger to the workflow that runs your suite so the gate applies before the merge, not after it.
X27 · Collection changed while being enumerated · Collection is structurally changed while it is being enumerated · ×1
  • Collection is structurally changed while it is being enumerated Source/NetOffice/SinkHelper.cs:238 — The loop walks `_pointList`, and line 239 calls `point.RemoveEventBinding(…)`, which reaches `_pointList.Remove(this)` in `SinkHelper.RemoveEventBinding` — a structural change to that same `List` while the loop's enumerator is live. The next `MoveNext` throws `InvalidOperationException: Collection was modified; enumeration operation may not execute`, so every pass that reaches this call ends the loop by exception instead of by running out of items, and the remaining items are never seen.
Minor — 140 finding(s)
X7 · Silent fallback defaults · Silent fallback default in catch · ×35
  • Silent fallback default in catch Source/Excel/Tools/RealtimeDataServer.cs:409 — `TryCallDerivedUnRegisterMethod` swallows every exception into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Source/Excel/Tools/RealtimeDataServer.cs:440 — `TryCallDerivedRegisterMethod` swallows every exception into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Source/Office/Tools/Contribution/CommonUtils.cs:535 — `TryGetApplicationVersion` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Source/NetOffice/COMObject.cs:1022 — `RaiseOnDispose` swallows every exception and returns `cancelDispose` still holding `false` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Source/NetOffice/COMProxyShare.cs:320 — `TryConvertToCustomAdapter` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Source/NetOffice/Exceptions/ExceptionMessageBuilder.cs:93 — `GetExceptionDiagnosticsMessage` swallows every exception into `return "<Failed to create Exception Message. Please report this bug.>";` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Source/NetOffice/Loader/CurrentAppDomain.cs:85 — `GetAssemblies` swallows `AppDomainUnloadedException` into `return new Assembly[0];` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Source/NetOffice/Loader/NetOfficeAssemblyEx.cs:61 — `ContainsNetOfficePublicKeyToken` swallows `System.IO.FileNotFoundException` into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Source/NetOffice/Running/RunningObjectTable.cs:575 — `TryCreateTypeInfo` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Source/NetOffice/Running/RunningObjectTable.cs:612 — `TryMarshalReleaseComObject` swallows every exception into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Source/NetOffice/Running/RunningWindowTable.cs:386 — `TryInvokeProperty` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Source/NetOffice/SinkHelper.cs:332 — `ToString` swallows every exception into `return String.Empty;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Source/NetOffice/SinkHelper.cs:349 — `ToBoolean` swallows every exception into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Source/NetOffice/SinkHelper.cs:366 — `ToInt16` swallows every exception into `return 0;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Source/NetOffice/SinkHelper.cs:383 — `ToInt32` swallows every exception into `return 0;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Source/NetOffice/SinkHelper.cs:400 — `ToDouble` swallows every exception into `return 0;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Source/NetOffice/SinkHelper.cs:417 — `ToSingle` swallows every exception into `return 0;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Source/NetOffice/SinkHelper.cs:435 — `ToEnum` swallows every exception into `return default(T);` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Source/NetOffice/Tools/LockbackAttribute.cs:36 — `CreateKey` swallows every exception into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Source/NetOffice/Tools/RegistryLocationAttribute.cs:174 — `TryDeleteApplicationKey` swallows every exception into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Source/Word/Tools/COMAddin.cs:777 — `TryDisposeDocumentInspectorDocument` swallows every exception into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Source/Outlook/Tools/Contribution/ApplicationUtils.cs:70 — `TryGetPageContainer` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Source/Outlook/Tools/FormRegionAttribute.cs:218 — `TryDeleteKey` swallows every exception into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Source/Office.Extensions/TrayUtils.cs:469 — `TryGetApplicationIcon` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch RegAddin/RegAddin/Common/AssemblyResolve.cs:31 — `Resolve` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • + 10 more in this group — see findings.md.
D24 · Comment Value · redundant comment · ×20
  • redundant comment REDACTED:5 — "General Information about an assembly is controlled through the following set of attributes. Change these attribute values to modify the information associated …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment REDACTED:17 — "Setting ComVisible to false makes the types in this assembly not visible to COM components. If you need to access a type in this assembly from COM, set the ComV …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment REDACTED:22 — "The following GUID is for the ID of the typelib if this project is exposed to COM" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment REDACTED:25 — "Version information for an assembly consists of the following four values: Major Version Minor Version Build Number Revision You can specify all the values or y …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment BuildTools/VersionUpdater/Form1.cs:361 — "change net marker" repeats the code it sits on: 3 of its 3 words (change, net, marker) are already in `if (!checkBoxChangeNetMarker.Checked)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment REDACTED:5 — "General Information about an assembly is controlled through the following set of attributes. Change these attribute values to modify the information associated …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment REDACTED:17 — "Setting ComVisible to false makes the types in this assembly not visible to COM components. If you need to access a type in this assembly from COM, set the ComV …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment REDACTED:22 — "The following GUID is for the ID of the typelib if this project is exposed to COM" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment REDACTED:25 — "Version information for an assembly consists of the following four values: Major Version Minor Version Build Number Revision You can specify all the values or y …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment Source/NetOffice.Tests/Properties/AssemblyInfo.cs:4 — "Setting ComVisible to false makes the types in this assembly not visible to COM components. If you need to access a type in this assembly from COM, set the ComV …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment Source/NetOffice.Tests/Properties/AssemblyInfo.cs:9 — "The following GUID is for the ID of the typelib if this project is exposed to COM" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment Source/NetOffice/COMObject.cs:163 — "add self as a child to the parent object" repeats the code it sits on: 4 of its 5 words (add, child, parent, object) are already in `parentObject.AddChildObject(this);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment Source/NetOffice/COMObject.cs:206 — "add self as a child to the parent object" repeats the code it sits on: 4 of its 5 words (add, child, parent, object) are already in `parentObject.AddChildObject(this);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment Source/NetOffice/Core.cs:919 — "create new classType" repeats the code it sits on: 4 of its 4 words (create, new, class, type) are already in `ICOMObject newInstance = CreateObjectFromComProxy(factoryInfo, caller, comProxy, comProxyType, className, fullClassName) …`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment Toolbox/Toolbox/Properties/AssemblyInfo.cs:5 — "General Information about an assembly is controlled through the following set of attributes. Change these attribute values to modify the information associated …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment Toolbox/Toolbox/Properties/AssemblyInfo.cs:17 — "Setting ComVisible to false makes the types in this assembly not visible to COM components. If you need to access a type in this assembly from COM, set the ComV …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment Toolbox/Toolbox/Properties/AssemblyInfo.cs:22 — "The following GUID is for the ID of the typelib if this project is exposed to COM" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment Toolbox/Toolbox/Properties/AssemblyInfo.cs:25 — "Version information for an assembly consists of the following four values: Major Version Minor Version Build Number Revision You can specify all the values or y …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment Tutorials/Tutorials/Tutorial02.cs:34 — "we dispose the child instances from book" repeats the code it sits on: 4 of its 4 words (dispose, child, instances, book) are already in `book.DisposeChildInstances();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment Tutorials/Tutorials/Tutorial03.cs:141 — "dispose all child instances from application" repeats the code it sits on: 4 of its 4 words (dispose, child, instances, application) are already in `_application.DisposeChildInstances();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
X10 · Duplicated predicate · Duplicated predicate · ×16
  • Duplicated predicate Source/NetOffice/Tools/COMAddinRegisterHandler.cs:135 — `(null != registerAttribute && true == registerMethodPresent) && (registerAttribute.Value == RegisterMode.CallAfter || registerAttribute.Valu…` appears character-identically in 2 files — Source/NetOffice/Tools/COMAddinRegisterHandler.cs, Source/NetOffice/Tools/COMAddinUnRegisterHandler.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate Source/Office/DispatchInterfaces/IMsoChart.cs:2019 — `(null != returnItem) && (returnItem is MarshalByRefObject)` appears character-identically in 31 files — Source/Access/DispatchInterfaces/_Attachment.cs, Source/Access/DispatchInterfaces/_BoundObjectFrame.cs, Source/Access/DispatchInterfaces/_Checkbox.cs, Source/Access/DispatchInterfaces/_Combobox.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate Source/Access/Events/DispSectionEvents.cs:179 — `(true == EventClass.IsCurrentlyDisposing) || (recipients.Length == 0)` appears character-identically in 3 files — Source/Access/Events/DispSectionEvents.cs, Source/Access/Events/DispTabControlEvents.cs, Source/Access/Events/_ReportEvents2.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsMultiAddinConverterCS.cs:145 — `Options.UseRibbonUI || Options.HiveKey == "LocalMachine"` appears character-identically in 2 files — Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsMultiAddinConverterCS.cs, Toolbox/Toolbox/ToolboxControls/ProjectWizard/ProjectConverters/ToolsMultiAddinConverterVB.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate Toolbox/Toolbox/Utils/Animation/Colors/ControlBackColorAnimator.cs:158 — `_startColor == Color.Empty || _endColor == Color.Empty` appears character-identically in 2 files — Toolbox/Toolbox/Utils/Animation/Colors/ControlBackColorAnimator.cs, Toolbox/Toolbox/Utils/Animation/Colors/ControlForeColorAnimator.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate RegAddin/RegAddin/Dispatcher/RegisterMethod.cs:41 — `arguments.Length == 1 && arguments[0].ParameterType == typeof(Type)` appears character-identically in 2 files — RegAddin/RegAddin/Dispatcher/RegisterMethod.cs, RegAddin/RegAddin/Dispatcher/UnRegisterMethod.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate Source/NetOffice/COMObject.cs:1350 — `hResultA == 0 && hResultB == 0 && ptrA == ptrB` appears character-identically in 2 files — Source/NetOffice/COMObject.cs, Source/NetOffice/Core.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate Source/NetOffice/Contribution/Controls/InstanceMonitor.cs:323 — `null != Parent && Parent.IsHandleCreated` appears character-identically in 2 files — Source/NetOffice/Contribution/Controls/InstanceMonitor.cs, Source/Office.Extensions/TrayMenuUtils/TrayMenuMonitorItemControl.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate Source/Excel/Tools/COMAddin.cs:362 — `null != TaskPaneFactory && false == TaskPaneFactory.IsDisposed` appears character-identically in 6 files — Source/Access/Tools/COMAddin.cs, Source/Excel/Tools/COMAddin.cs, Source/Office/Tools/COMAddin.cs, Source/Outlook/Tools/COMAddin.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate Source/Excel/Tools/RealtimeDataServer.cs:518 — `null != codebase && codebase.Value == true` appears character-identically in 3 files — Source/Excel/Tools/RealtimeDataServer.cs, Source/NetOffice/Tools/COMAddinUnRegisterHandler.cs, Source/Word/Tools/DocumentInspectorBase.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate Source/Word/Tools/COMAddin.cs:766 — `null != document && false == document.IsDisposed` appears character-identically in 2 files — Source/Word/Tools/COMAddin.cs, Source/Word/Tools/DocumentInspectorBase.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate Source/NetOffice/Extensions/EnumerableExtensions.cs:36 — `null != enumerator && enumerator != source` appears character-identically in 2 files — Source/NetOffice/Extensions/EnumerableExtensions.cs, Tutorials/Tutorials/Tutorial11.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate Source/Excel/Tools/COMAddin.cs:351 — `null != item.Pane && !item.Pane.IsDisposed` appears character-identically in 6 files — Source/Access/Tools/COMAddin.cs, Source/Excel/Tools/COMAddin.cs, Source/Office/Tools/COMAddin.cs, Source/Outlook/Tools/COMAddin.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate Source/Excel/Tools/COMAddin.cs:540 — `null != target && item.Pane == customTaskPaneInst` appears character-identically in 6 files — Source/Access/Tools/COMAddin.cs, Source/Excel/Tools/COMAddin.cs, Source/Office/Tools/COMAddin.cs, Source/Outlook/Tools/COMAddin.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate RegAddin/RegAddin/Common/AttributeReflection.cs:21 — `null != type.BaseType && type.BaseType.FullName == "System.Object"` appears character-identically in 3 files — RegAddin/RegAddin/Common/AttributeReflection.cs, RegAddin/RegAddin/Dispatcher/MethodUtils.cs, RegAddin/RegAddin/Metrics/AddinMetrics.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate RegAddin/RegAddin/Common/AddinRegAnalyzer.cs:209 — `target.BaseType.FullName == _systemObject || target.BaseType.FullName == _addinBaseClassName` appears character-identically in 2 files — RegAddin/RegAddin/Common/AddinRegAnalyzer.cs, RegAddin/RegAddin/RegFile/RegFileOperationHost.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
IC1 · Incompleteness & stubs · Commented-out code · ×15
  • Commented-out code RegAddin/RegAddin/CommandLineValidator.cs:256 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code RegAddin/RegAddinTest/Program.cs:17 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code RegAddin/RegAddinTest/Program.cs:19 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code RegAddin/RegAddinTest/Program.cs:22 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code RegAddin/RegAddinTest/Program.cs:24 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code RegAddin/RegAddinTest/Program.cs:26 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code RegAddin/RegAddinTest/Program.cs:28 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code RegAddin/RegAddinTest/Program.cs:30 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code RegAddin/RegAddinTest/Program.cs:33 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code RegAddin/RegAddinTest/Program.cs:35 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code RegAddin/RegAddinTest/Program.cs:37 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code RegAddin/RegAddinTest/Program.cs:43 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code RegAddin/RegAddinTest/Program.cs:46 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code RegAddin/RegAddinTest/Program.cs:48 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code RegAddin/RegAddinTest/Program.cs:51 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×11
  • Projects may be oversized for their cohesion Source/Excel/ExcelApi.csproj:1 — `ExcelApi` overshoots its size bounds (414593 LoC, 1202 public types across 10 namespaces). 11 of 82 project(s) overshoot their size bounds, lowering Project Cohesion to 7.3/10. Size alone is no reason to split a project: where its type references show a separable part, a Split row names it.
  • Projects may be oversized for their cohesion Source/Word/WordApi.csproj:1 — `WordApi` overshoots its size bounds (191551 LoC, 832 public types across 7 namespaces). 11 of 82 project(s) overshoot their size bounds, lowering Project Cohesion to 7.3/10. Size alone is no reason to split a project: where its type references show a separable part, a Split row names it.
  • Projects may be oversized for their cohesion Source/Access/AccessApi.csproj:1 — `AccessApi` overshoots its size bounds (133842 LoC, 950 public types across 8 namespaces). 11 of 82 project(s) overshoot their size bounds, lowering Project Cohesion to 7.3/10. Size alone is no reason to split a project: where its type references show a separable part, a Split row names it.
  • Projects may be oversized for their cohesion Source/Outlook/OutlookApi.csproj:1 — `OutlookApi` overshoots its size bounds (117059 LoC, 1261 public types across 9 namespaces). 11 of 82 project(s) overshoot their size bounds, lowering Project Cohesion to 7.3/10. Size alone is no reason to split a project: where its type references show a separable part, a Split row names it.
  • Projects may be oversized for their cohesion Source/Office/OfficeApi.csproj:1 — `OfficeApi` overshoots its size bounds (91193 LoC, 555 public types across 8 namespaces). 11 of 82 project(s) overshoot their size bounds, lowering Project Cohesion to 7.3/10. Size alone is no reason to split a project: where its type references show a separable part, a Split row names it.
  • Projects may be oversized for their cohesion Source/PowerPoint/PowerPointApi.csproj:1 — `PowerPointApi` overshoots its size bounds (84075 LoC, 434 public types across 7 namespaces). 11 of 82 project(s) overshoot their size bounds, lowering Project Cohesion to 7.3/10. Size alone is no reason to split a project: where its type references show a separable part, a Split row names it.
  • Projects may be oversized for their cohesion Source/OWC10/OWC10Api.csproj:1 — `OWC10Api` overshoots its size bounds (67704 LoC, 495 public types across 4 namespaces). 11 of 82 project(s) overshoot their size bounds, lowering Project Cohesion to 7.3/10. Size alone is no reason to split a project: where its type references show a separable part, a Split row names it.
  • Projects may be oversized for their cohesion Toolbox/Toolbox/NetOffice.DeveloperToolbox.csproj:1 — `NetOffice.DeveloperToolbox` overshoots its size bounds (23329 LoC, 84 public types across 32 namespaces). 11 of 82 project(s) overshoot their size bounds, lowering Project Cohesion to 7.3/10. Size alone is no reason to split a project: where its type references show a separable part, a Split row names it.
  • Projects may be oversized for their cohesion Source/NetOffice/NetOffice.csproj:1 — `NetOffice` overshoots its size bounds (22692 LoC, 204 public types across 22 namespaces). 11 of 82 project(s) overshoot their size bounds, lowering Project Cohesion to 7.3/10. Size alone is no reason to split a project: where its type references show a separable part, a Split row names it.
  • Projects may be oversized for their cohesion Source/MSComctlLib/MSComctlLibApi.csproj:1 — `MSComctlLibApi` overshoots its size bounds (22030 LoC, 243 public types across 4 namespaces). 11 of 82 project(s) overshoot their size bounds, lowering Project Cohesion to 7.3/10. Size alone is no reason to split a project: where its type references show a separable part, a Split row names it.
  • Projects may be oversized for their cohesion Source/ADODB/ADODBApi.csproj:1 — `ADODBApi` overshoots its size bounds (20236 LoC, 141 public types across 4 namespaces). 11 of 82 project(s) overshoot their size bounds, lowering Project Cohesion to 7.3/10. Size alone is no reason to split a project: where its type references show a separable part, a Split row names it.
D19 · Documentation Quality · Documentation · ×10
  • Documentation: no build, run or usage example README.md:1 — the repository holds project manifests and neither `README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example Source/Access/README.md:1 — `Access` is a package (`PackageId`) and neither `Source/Access/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example Source/Excel/README.md:1 — `Excel` is a package (`PackageId`) and neither `Source/Excel/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example Source/NetOffice/README.md:1 — `NetOffice` is a package (`PackageId`) and neither `Source/NetOffice/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example Source/Office/README.md:1 — `Office` is a package (`PackageId`) and neither `Source/Office/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example Source/Office.Extensions/README.md:1 — `Office.Extensions` is a package (`PackageId`) and neither `Source/Office.Extensions/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example Source/Outlook/README.md:1 — `Outlook` is a package (`PackageId`) and neither `Source/Outlook/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example Source/PowerPoint/README.md:1 — `PowerPoint` is a package (`PackageId`) and neither `Source/PowerPoint/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example Source/VBIDE/README.md:1 — `VBIDE` is a package (`PackageId`) and neither `Source/VBIDE/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example Source/Word/README.md:1 — `Word` is a package (`PackageId`) and neither `Source/Word/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
IC1 · Incompleteness & stubs · Blanket warning suppression · ×6
  • Blanket warning suppression Source/ADODB/Classes/Command.cs:10 — A `#pragma warning disable` with no error codes silences every warning for the rest of the file — hidden debt. Suppress specific codes with a justification instead.
  • Blanket warning suppression Source/ADODB/Classes/Command.cs:23 — A `#pragma warning disable` with no error codes silences every warning for the rest of the file — hidden debt. Suppress specific codes with a justification instead.
  • Blanket warning suppression Source/ADODB/Classes/Connection.cs:10 — A `#pragma warning disable` with no error codes silences every warning for the rest of the file — hidden debt. Suppress specific codes with a justification instead.
  • Blanket warning suppression Source/ADODB/Classes/Connection.cs:34 — A `#pragma warning disable` with no error codes silences every warning for the rest of the file — hidden debt. Suppress specific codes with a justification instead.
  • Blanket warning suppression Source/ADODB/Classes/Parameter.cs:10 — A `#pragma warning disable` with no error codes silences every warning for the rest of the file — hidden debt. Suppress specific codes with a justification instead.
  • Blanket warning suppression Source/ADODB/Classes/Parameter.cs:23 — A `#pragma warning disable` with no error codes silences every warning for the rest of the file — hidden debt. Suppress specific codes with a justification instead.
X6 · Hand-rolled structured-format parsing · Hand-rolled JSON/XML parsing via string slicing · ×2
  • Hand-rolled JSON/XML parsing via string slicing BuildTools/VersionUpdater/Form1.cs:86 — A JSON key or XML tag is located in the text with IndexOf/Split and the value cut out around it — a reordered, re-spaced or differently-typed document (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. .NET ships a real parser for it (System.Text.Json, System.Xml.Linq); use it here.
  • Hand-rolled JSON/XML parsing via string slicing BuildTools/VersionUpdater/Form1.cs:93 — A JSON key or XML tag is located in the text with IndexOf/Split and the value cut out around it — a reordered, re-spaced or differently-typed document (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. .NET ships a real parser for it (System.Text.Json, System.Xml.Linq); use it here.
AX6 · Interface segregation · Fat interface · ×1
  • Fat interface: IToolboxControl (17 members) Toolbox/Toolbox/IToolboxControl.cs:33 — `IToolboxControl` declares 17 members: `Host`, `ControlName`, `ControlCaption`, `Icon`, `SupportsHelpContent`, `SupportsInfoMessage`, `InfoMessageKind`, `InfoMessage`, `InitializeControl`, `Activate`, `Deactivated`, `LoadComplete`, `LoadConfiguration`, `SaveConfiguration`, `GetHelpText`, `KeyDown`, `Release`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
C4 · Data Retention · Partial data-retention evidence · ×1
  • Partial data-retention evidence — A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a scheduled purge / cleanup job (PurgeOlderThan / CleanupJob).
D16 · Bus Factor · Off-boarding risk · ×1
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 3 significant file(s) lose their only recent owner: Source/Word/DispatchInterfaces/_Document.cs, Source/Excel/DispatchInterfaces/_Workbook.cs, Source/Analyzers/NetOffice.Analyzers/EventValidateRaiseConsistencyAnalyzer.cs. Pair on, review, or document these before any departure.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found BuildTools/ReferenceAnalyzer/NOBuildTools.ReferenceAnalyzer.csproj:9 — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `BuildTools/ReferenceAnalyzer/NOBuildTools.ReferenceAnalyzer.csproj` makes this repository a deployable product (line 9).
D21 · Naming Consistency · `acSpreadsheetTypeExcel12Xml` spells `Xml` where 55 names in the project spell it `XML` · ×1
  • `acSpreadsheetTypeExcel12Xml` spells `Xml` where 55 names in the project spell it `XML` Source/Access/Enums/AcSpreadSheetType.cs:102 — 55 of 56 names in project AccessApi spell the token `XML` (55 of 56; unit: names in project AccessApi containing `XML`). Peers: _Application.ExportXML (Source/Access/DispatchInterfaces/_Application.cs:3500); _Application.ExportXML (Source/Access/DispatchInterfaces/_Application.cs:3520); _Application.ExportXML (Source/Access/DispatchInterfaces/_Application.cs:3532); _Application.ExportXML (Source/Access/DispatchInterfaces/_Application.cs:3546); _Application.ExportXML (Source/Access/DispatchInterfaces/_Application.cs:3561). Rename to `acSpreadsheetTypeExcel12XML`. [rule N6]
D21 · Naming Consistency · `xlConnectionTypeTEXT` spells `TEXT` where 301 names in the project spell it `Text` · ×1
  • `xlConnectionTypeTEXT` spells `TEXT` where 301 names in the project spell it `Text` Source/Excel/Enums/XlConnectionType.cs:39 — 301 of 302 names in project ExcelApi spell the token `Text` (301 of 302; unit: names in project ExcelApi containing `Text`). Peers: Arc.LockedText (Source/Excel/DispatchInterfaces/Arc.cs:663); Arcs.LockedText (Source/Excel/DispatchInterfaces/Arcs.cs:610); AutoCorrect.ReplaceText (Source/Excel/DispatchInterfaces/AutoCorrect.cs:313); Button.LockedText (Source/Excel/DispatchInterfaces/Button.cs:663); Buttons.LockedText (Source/Excel/DispatchInterfaces/Buttons.cs:610). Rename to `xlConnectionTypeText`. [rule N6]
D21 · Naming Consistency · `xlConnectionTypeWEB` spells `WEB` where 23 names in the project spell it `Web` · ×1
  • `xlConnectionTypeWEB` spells `WEB` where 23 names in the project spell it `Web` Source/Excel/Enums/XlConnectionType.cs:46 — 23 of 24 names in project ExcelApi spell the token `Web` (23 of 24; unit: names in project ExcelApi containing `Web`). Peers: NetOffice.ExcelApi.DefaultWebOptions (Source/Excel/DispatchInterfaces/DefaultWebOptions.cs:13); DefaultWebOptions.SaveNewWebPagesAsWebArchives (Source/Excel/DispatchInterfaces/DefaultWebOptions.cs:475); _Application.DefaultWebOptions (Source/Excel/DispatchInterfaces/_Application.cs:2965); _QueryTable.EditWebPage (Source/Excel/DispatchInterfaces/_QueryTable.cs:1089); XlBuiltInDialog.xlDialogPublishAsWebPage (Source/Excel/Enums/XlBuiltInDialog.cs:1579). Rename to `xlConnectionTypeWeb`. [rule N6]
D21 · Naming Consistency · `xlConnectionTypeMODEL` spells `MODEL` where 40 names in the project spell it `Model` · ×1
  • `xlConnectionTypeMODEL` spells `MODEL` where 40 names in the project spell it `Model` Source/Excel/Enums/XlConnectionType.cs:60 — 40 of 41 names in project ExcelApi spell the token `Model` (40 of 41; unit: names in project ExcelApi containing `Model`). Peers: Application._WorkbookModelChangeEvent (Source/Excel/Classes/Application.cs:1314); Application.WorkbookModelChangeEvent (Source/Excel/Classes/Application.cs:1320); Connections.AddFromFile(createModelConnection) (Source/Excel/DispatchInterfaces/Connections.cs:208); Connections.AddFromFile(createModelConnection) (Source/Excel/DispatchInterfaces/Connections.cs:220); Connections.Add(createModelConnection) (Source/Excel/DispatchInterfaces/Connections.cs:251). Rename to `xlConnectionTypeModel`. [rule N6]
D21 · Naming Consistency · `xlWK1ALL` spells `ALL` where 114 names in the project spell it `All` · ×1
  • `xlWK1ALL` spells `ALL` where 114 names in the project spell it `All` Source/Excel/Enums/XlFileFormat.cs:221 — 114 of 115 names in project ExcelApi spell the token `All` (114 of 115; unit: names in project ExcelApi containing `All`). Peers: AutoFilter.ShowAllData (Source/Excel/DispatchInterfaces/AutoFilter.cs:228); ControlFormat.RemoveAllItems (Source/Excel/DispatchInterfaces/ControlFormat.cs:455); DiagramNodeChildren.SelectAll (Source/Excel/DispatchInterfaces/DiagramNodeChildren.cs:220); DiagramNodes.SelectAll (Source/Excel/DispatchInterfaces/DiagramNodes.cs:162); DialogSheet.ResetAllPageBreaks (Source/Excel/DispatchInterfaces/DialogSheet.cs:1911). Rename to `xlWK1All`. [rule N6]
D21 · Naming Consistency · `HelpContextID` spells `ID` where 32 names in the project spell it `Id` · ×1
  • `HelpContextID` spells `ID` where 32 names in the project spell it `Id` Source/MSComctlLib/DispatchInterfaces/IToolbar.cs:355 — 32 of 33 names in project MSComctlLibApi spell the token `Id` (32 of 33; unit: names in project MSComctlLibApi containing `Id`). Peers: Button._activeSinkId (Source/MSComctlLib/Classes/Button.cs:28); ButtonMenu._activeSinkId (Source/MSComctlLib/Classes/ButtonMenu.cs:28); ButtonMenus._activeSinkId (Source/MSComctlLib/Classes/ButtonMenus.cs:28); Buttons._activeSinkId (Source/MSComctlLib/Classes/Buttons.cs:28); ColumnHeader._activeSinkId (Source/MSComctlLib/Classes/ColumnHeader.cs:28). Rename to `HelpContextId`. [rule N6]
D21 · Naming Consistency · `_IMsoOleAccDispObj` spells `Ole` where 16 names in the project spell it `OLE` · ×1
  • `_IMsoOleAccDispObj` spells `Ole` where 16 names in the project spell it `OLE` Source/Office/DispatchInterfaces/_IMsoOleAccDispObj.cs:13 — 16 of 17 names in project OfficeApi spell the token `OLE` (16 of 17; unit: names in project OfficeApi containing `OLE`). Peers: NetOffice.OfficeApi.Enums.MsoControlOLEUsage (Source/Office/Enums/MsoControlOLEUsage.cs:10); MsoControlOLEUsage.msoControlOLEUsageNeither (Source/Office/Enums/MsoControlOLEUsage.cs:18); MsoControlOLEUsage.msoControlOLEUsageServer (Source/Office/Enums/MsoControlOLEUsage.cs:25); MsoControlOLEUsage.msoControlOLEUsageClient (Source/Office/Enums/MsoControlOLEUsage.cs:32); MsoControlOLEUsage.msoControlOLEUsageBoth (Source/Office/Enums/MsoControlOLEUsage.cs:39). Rename to `_IMsoOLEAccDispObj`. [rule N6]
D21 · Naming Consistency · `ppAlertButtonCLOSE` spells `CLOSE` where 22 names in the project spell it `Close` · ×1
  • `ppAlertButtonCLOSE` spells `CLOSE` where 22 names in the project spell it `Close` Source/PowerPoint/Enums/PpAlertButton.cs:17 — 22 of 23 names in project PowerPointApi spell the token `Close` (22 of 23; unit: names in project PowerPointApi containing `Close`). Peers: Application._PresentationCloseEvent (Source/PowerPoint/Classes/Application.cs:335); Application.PresentationCloseEvent (Source/PowerPoint/Classes/Application.cs:341); Application._PresentationBeforeCloseEvent (Source/PowerPoint/Classes/Application.cs:818); Application.PresentationBeforeCloseEvent (Source/PowerPoint/Classes/Application.cs:824); Application._ProtectedViewWindowBeforeCloseEvent (Source/PowerPoint/Classes/Application.cs:887). Rename to `ppAlertButtonClose`. [rule N6]
D21 · Naming Consistency · `ppAlertButtonNEXT` spells `NEXT` where 22 names in the project spell it `Next` · ×1
  • `ppAlertButtonNEXT` spells `NEXT` where 22 names in the project spell it `Next` Source/PowerPoint/Enums/PpAlertButton.cs:59 — 22 of 23 names in project PowerPointApi spell the token `Next` (22 of 23; unit: names in project PowerPointApi containing `Next`). Peers: Application._SlideShowNextBuildEvent (Source/PowerPoint/Classes/Application.cs:519); Application.SlideShowNextBuildEvent (Source/PowerPoint/Classes/Application.cs:525); Application._SlideShowNextSlideEvent (Source/PowerPoint/Classes/Application.cs:542); Application.SlideShowNextSlideEvent (Source/PowerPoint/Classes/Application.cs:548); Application._SlideShowNextClickEvent (Source/PowerPoint/Classes/Application.cs:680). Rename to `ppAlertButtonNext`. [rule N6]
D21 · Naming Consistency · `DesignerID` spells `ID` where 20 names in the project spell it `Id` · ×1
  • `DesignerID` spells `ID` where 20 names in the project spell it `Id` Source/VBIDE/DispatchInterfaces/_VBComponent.cs:114 — 20 of 22 names in project VBIDEApi spell the token `Id` (20 of 22; unit: names in project VBIDEApi containing `Id`). Peers: Addins._activeSinkId (Source/VBIDE/Classes/Addins.cs:28); CodeModule._activeSinkId (Source/VBIDE/Classes/CodeModule.cs:28); CodePane._activeSinkId (Source/VBIDE/Classes/CodePane.cs:28); CodePanes._activeSinkId (Source/VBIDE/Classes/CodePanes.cs:28); CommandBarEvents._activeSinkId (Source/VBIDE/Classes/CommandBarEvents.cs:31). Rename to `DesignerId`. [rule N6]
D21 · Naming Consistency · `HelpContextID` spells `ID` where 20 names in the project spell it `Id` · ×1
  • `HelpContextID` spells `ID` where 20 names in the project spell it `Id` Source/VBIDE/DispatchInterfaces/_VBProject_Old.cs:131 — 20 of 22 names in project VBIDEApi spell the token `Id` (20 of 22; unit: names in project VBIDEApi containing `Id`). Peers: Addins._activeSinkId (Source/VBIDE/Classes/Addins.cs:28); CodeModule._activeSinkId (Source/VBIDE/Classes/CodeModule.cs:28); CodePane._activeSinkId (Source/VBIDE/Classes/CodePane.cs:28); CodePanes._activeSinkId (Source/VBIDE/Classes/CodePanes.cs:28); CommandBarEvents._activeSinkId (Source/VBIDE/Classes/CommandBarEvents.cs:31). Rename to `HelpContextId`. [rule N6]
D26 · Project Cohesion · Split NetOffice · ×1
  • Split NetOffice Source/NetOffice/NetOffice.csproj:1 — `NetOffice` overshoots its size bounds (22692 LoC, 204 public types across 22 namespaces). These parts reach the rest of the project only through its shared core (`(root)`, `Attributes`, `CollectionsGeneric`, `ComTypes`, `Exceptions`, `Filtering`), so they are the cleanest seams: `NetOffice.Running` (23 types in 12 files): 7 of 217 of its type references cross into a sibling namespace, and the rest of the project uses it 0 times and it uses the rest 50 times. Extract each into its own project.
D27 · Navigability · Pass-through layer · ×1
  • Pass-through layer Source/NetOffice/Dynamics/COMDynamicMetaObject.cs:13 — COMDynamicMetaObject: all 13 public methods forward their arguments unchanged to Underlying and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call Underlying directly, or give the layer a job.
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M2 · Architecture documentation · No architecture diagram/doc · ×1
  • No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST REDACTED:5 — No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 4 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
P3 · Security & performance tooling · Dependabot does not watch nuget · ×1
  • Dependabot does not watch nuget .github/dependabot.yml:2 — `.github/dependabot.yml` schedules updates, but no `package-ecosystem` entry covers `nuget`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list.
Minor — 20 finding(s)
D24 · Comment Value · doc comments repeat the names · ×20
  • doc comments repeat the names Source/ADODB/Classes/Command.cs:35 — 63 of 1564 documented parameters and 71 of 1446 summaries in `ADODBApi` only repeat the member or parameter name (e.g. "Instance Type" for `InstanceType`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names Source/Access/Classes/AccessField.cs:35 — 363 of 5850 documented parameters and 363 of 8532 summaries in `AccessApi` only repeat the member or parameter name (e.g. "Instance Type" for `InstanceType`). 1 documentation tag(s) are empty. This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names Source/DAO/Classes/DBEngine.cs:35 — 17 of 1041 documented parameters and 51 of 903 summaries in `DAOApi` only repeat the member or parameter name (e.g. "Instance Type" for `InstanceType`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names Source/Excel/Classes/Application.cs:87 — 4314 of 75987 documented parameters and 818 of 24896 summaries in `ExcelApi` only repeat the member or parameter name (e.g. "Instance Type" for `InstanceType`). 1 documentation tag(s) are empty. This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names Source/MSComctlLib/Classes/Button.cs:35 — 49 of 872 documented parameters and 100 of 1272 summaries in `MSComctlLibApi` only repeat the member or parameter name (e.g. "Instance Type" for `InstanceType`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names Source/MSDATASRC/Interfaces/DataSource.cs:20 — 0 of 30 documented parameters and 2 of 13 summaries in `MSDATASRCApi` only repeat the member or parameter name (e.g. "Instance Type" for `InstanceType`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names BuildTools/ReferenceAnalyzer/ExceptionDisplayer.cs:17 — 1 of 17 documented parameters and 0 of 12 summaries in `NOBuildTools.ReferenceAnalyzer` only repeat the member or parameter name (e.g. "exception as any" for `exception`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names BuildTools/SearchAndReplace/ConfigManager.cs:16 — 4 of 17 documented parameters and 2 of 9 summaries in `NOBuildTools.SearchAndReplace` only repeat the member or parameter name (e.g. "Save a configuration file" for `SaveConfigurationToXMLFile`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names BuildTools/VersionUpdater/ConfigManager.cs:16 — 3 of 14 documented parameters and 2 of 8 summaries in `NOBuildTools.VersionUpdater` only repeat the member or parameter name (e.g. "Save a configuration file" for `SaveConfigurationToXMLFile`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names Source/NetOffice/Attributes/NetOfficeAssemblyAttribute.cs:34 — 854 of 2824 documented parameters and 130 of 1550 summaries in `NetOffice` only repeat the member or parameter name (e.g. "given assembly as any" for `assembly`). 17 documentation tag(s) are empty. This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names Toolbox/Toolbox/AssemblyInfo.cs:14 — 14 of 226 documented parameters and 34 of 657 summaries in `NetOffice.DeveloperToolbox` only repeat the member or parameter name (e.g. "Title of the Assembly" for `AssemblyTitle`). 29 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names Source/OWC10/Classes/ChartSpace.cs:64 — 148 of 3871 documented parameters and 245 of 4603 summaries in `OWC10Api` only repeat the member or parameter name (e.g. "Instance Type" for `InstanceType`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names Source/Office/Classes/CommandBarButton.cs:40 — 98 of 5073 documented parameters and 342 of 6668 summaries in `OfficeApi` only repeat the member or parameter name (e.g. "Instance Type" for `InstanceType`). 1 documentation tag(s) are empty. This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names Source/Office.Extensions/Dialogs/AboutDialog.cs:39 — 49 of 494 documented parameters and 30 of 678 summaries in `OfficeApi.Extensions` only repeat the member or parameter name (e.g. "assembly title" for `assemblyTitle`). 28 documentation tag(s) are empty. This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names Source/Outlook/Classes/Account.cs:36 — 125 of 3906 documented parameters and 576 of 7312 summaries in `OutlookApi` only repeat the member or parameter name (e.g. "Instance Type" for `InstanceType`). 3 documentation tag(s) are empty. This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names Source/PowerPoint/Classes/Application.cs:73 — 43 of 4846 documented parameters and 263 of 5462 summaries in `PowerPointApi` only repeat the member or parameter name (e.g. "Instance Type" for `InstanceType`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names RegAddin/RegAddin/CommandLineValidator.cs:19 — 0 of 10 documented parameters and 1 of 27 summaries in `RegAddin` only repeat the member or parameter name (e.g. "Validate arguments from command line" for `ValidateCommandLineArguments`). 2 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names Tutorials/TutorialsBase/ErrorForm.cs:18 — 6 of 14 documented parameters and 3 of 24 summaries in `TutorialsBase` only repeat the member or parameter name (e.g. "exception as any" for `exception`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names Source/VBIDE/Classes/Addins.cs:35 — 21 of 677 documented parameters and 63 of 500 summaries in `VBIDEApi` only repeat the member or parameter name (e.g. "Instance Type" for `InstanceType`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names Source/Word/Classes/Application.cs:77 — 283 of 18169 documented parameters and 400 of 13034 summaries in `WordApi` only repeat the member or parameter name (e.g. "Instance Type" for `InstanceType`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.

Appendix B — Reproduction & audit trail

Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-9be54fcfa03c4a8b91e742e7c56f6d1b/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=676" --report-format json --report-path /tmp/watchdog-gitleaks-9be54fcfa03c4a8b91e742e7c56f6d1b/history-1.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-1.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-9be54fcfa03c4a8b91e742e7c56f6d1b/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt .51artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesnuget—nuget: not applicable — nuget: `dotnet list package --vulnerable` could not read this solution's dependency graph — it reported an error for at least one project and returned no package data at all (typically a packages.config / non-PackageReference project, which the command cannot read). An unreadable dependency graph is not a clean one; migrate the project(s) to PackageReference to enable this scan0—
D30 · Dependency Vulnerabilitiesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-959630bba7d140689cfb60a819b3c6a50artifacts/raw/osv-scanner.json
D31 · IaC & Container Securitytrivy—trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.0—
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 2 file(s) — `Source/ADODB/DispatchInterfaces/_Record.cs`, `Source/ADODB/DispatchInterfaces/_Record_Deprecated.cs` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-959630bba7d140689cfb60a819b3c6a50artifacts/raw/osv-scanner.json

Run 01a1e6f4-a9fc-75f6-b41e-71affd22a820 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Appendix C — Personal-data map

Every field, property and record parameter whose name is conventional personal data — 109 field(s) across 4 categories, each with an exact repo-relative file:line. This is the data inventory a compliance review starts from — right-to-erasure, retention, minimisation. Detected by NAME, from the C# syntax tree, with a deliberately specific identifier classifier — the same one the C1–C5 compliance cards use to decide whether personal data is present, so CardDefinition or FileName don't trip. Two caveats stated rather than glossed: those cards additionally require corroboration (a persistence/account signal, or two distinct PII categories) that this inventory deliberately does not, so it lists more than they gate on; and D32 Data Compliance shares nothing with it — that dimension is a separate semgrep ruleset for personal data leaking into logs, URLs and browser storage, and a clean D32 result says nothing about this list. Informational — it feeds no score.

Email — 33 field(s)
  • _Hyperlink.EmailSubject Source/Access/DispatchInterfaces/_Hyperlink.cs:152
  • Hyperlink.EmailSubject Source/Excel/DispatchInterfaces/Hyperlink.cs:252
  • IHyperlink.EmailSubject Source/Excel/Interfaces/IHyperlink.cs:241
  • SharedWorkspaceMember.Email Source/Office/DispatchInterfaces/SharedWorkspaceMember.cs:145
  • SignatureSetup.SuggestedSignerEmail Source/Office/DispatchInterfaces/SignatureSetup.cs:195
  • _ContactItem.MailingAddress Source/Outlook/DispatchInterfaces/_ContactItem.cs:1793
  • _ContactItem.MailingAddressCity Source/Outlook/DispatchInterfaces/_ContactItem.cs:1811
  • _ContactItem.MailingAddressCountry Source/Outlook/DispatchInterfaces/_ContactItem.cs:1829
  • _ContactItem.MailingAddressPostalCode Source/Outlook/DispatchInterfaces/_ContactItem.cs:1847
  • _ContactItem.MailingAddressPostOfficeBox Source/Outlook/DispatchInterfaces/_ContactItem.cs:1865
  • _ContactItem.MailingAddressState Source/Outlook/DispatchInterfaces/_ContactItem.cs:1883
  • _ContactItem.MailingAddressStreet Source/Outlook/DispatchInterfaces/_ContactItem.cs:1901
  • _ContactItem.SelectedMailingAddress Source/Outlook/DispatchInterfaces/_ContactItem.cs:2333
  • _MailItem.SenderEmailAddress Source/Outlook/DispatchInterfaces/_MailItem.cs:1392
  • _MailItem.SenderEmailType Source/Outlook/DispatchInterfaces/_MailItem.cs:1406
  • _MeetingItem.SenderEmailAddress Source/Outlook/DispatchInterfaces/_MeetingItem.cs:1015
  • _MeetingItem.SenderEmailType Source/Outlook/DispatchInterfaces/_MeetingItem.cs:1029
  • _MobileItem.SenderEmailAddress Source/Outlook/DispatchInterfaces/_MobileItem.cs:792
  • _MobileItem.SenderEmailType Source/Outlook/DispatchInterfaces/_MobileItem.cs:805
  • _PostItem.SenderEmailAddress Source/Outlook/DispatchInterfaces/_PostItem.cs:800
  • _PostItem.SenderEmailType Source/Outlook/DispatchInterfaces/_PostItem.cs:814
  • _SharingItem.SenderEmailAddress Source/Outlook/DispatchInterfaces/_SharingItem.cs:1538
  • _SharingItem.SenderEmailType Source/Outlook/DispatchInterfaces/_SharingItem.cs:1552
  • Hyperlink.EmailSubject Source/PowerPoint/DispatchInterfaces/Hyperlink.cs:196
  • CoAuthor.EmailAddress Source/Word/DispatchInterfaces/CoAuthor.cs:216
  • Email.CurrentEmailAuthor Source/Word/DispatchInterfaces/Email.cs:160
  • EmailOptions.EmailSignature Source/Word/DispatchInterfaces/EmailOptions.cs:214
  • EmailSignature.EmailSignatureEntries Source/Word/DispatchInterfaces/EmailSignature.cs:196
  • Hyperlink.EmailSubject Source/Word/DispatchInterfaces/Hyperlink.cs:294
  • _Application.EmailOptions Source/Word/DispatchInterfaces/_Application.cs:1583
  • _Application.EmailTemplate Source/Word/DispatchInterfaces/_Application.cs:1745
  • _Application.AutoCorrectEmail Source/Word/DispatchInterfaces/_Application.cs:1812
  • _Document.Email Source/Word/DispatchInterfaces/_Document.cs:1944
Name — 29 field(s)
  • AccessObject.FullName Source/Access/DispatchInterfaces/AccessObject.cs:216
  • _CurrentProject.FullName Source/Access/DispatchInterfaces/_CurrentProject.cs:255
  • AddIn.FullName Source/Excel/DispatchInterfaces/AddIn.cs:188
  • SmartTagRecognizer.FullName Source/Excel/DispatchInterfaces/SmartTagRecognizer.cs:198
  • _Workbook.FullName Source/Excel/DispatchInterfaces/_Workbook.cs:653
  • _Workbook.FullNameURLEncoded Source/Excel/DispatchInterfaces/_Workbook.cs:1583
  • IAddIn.FullName Source/Excel/Interfaces/IAddIn.cs:183
  • ISmartTagRecognizer.FullName Source/Excel/Interfaces/ISmartTagRecognizer.cs:198
  • _ContactItem.CompanyAndFullName Source/Outlook/DispatchInterfaces/_ContactItem.cs:927
  • _ContactItem.FirstName Source/Outlook/DispatchInterfaces/_ContactItem.cs:1281
  • _ContactItem.FullName Source/Outlook/DispatchInterfaces/_ContactItem.cs:1317
  • _ContactItem.FullNameAndCompany Source/Outlook/DispatchInterfaces/_ContactItem.cs:1335
  • _ContactItem.LastName Source/Outlook/DispatchInterfaces/_ContactItem.cs:1761
  • _ContactItem.LastNameAndFirstName Source/Outlook/DispatchInterfaces/_ContactItem.cs:1779
  • _ContactItem.YomiFirstName Source/Outlook/DispatchInterfaces/_ContactItem.cs:2566
  • _ContactItem.YomiLastName Source/Outlook/DispatchInterfaces/_ContactItem.cs:2584
  • _ExchangeUser.FirstName Source/Outlook/DispatchInterfaces/_ExchangeUser.cs:454
  • _ExchangeUser.LastName Source/Outlook/DispatchInterfaces/_ExchangeUser.cs:490
  • _ExchangeUser.YomiFirstName Source/Outlook/DispatchInterfaces/_ExchangeUser.cs:630
  • _ExchangeUser.YomiLastName Source/Outlook/DispatchInterfaces/_ExchangeUser.cs:648
  • AddIn.FullName Source/PowerPoint/DispatchInterfaces/AddIn.cs:146
  • LinkFormat.SourceFullName Source/PowerPoint/DispatchInterfaces/LinkFormat.cs:146
  • SoundFormat.SourceFullName Source/PowerPoint/DispatchInterfaces/SoundFormat.cs:128
  • _Presentation.FullName Source/PowerPoint/DispatchInterfaces/_Presentation.cs:435
  • LinkFormat.SourceFullName Source/Word/DispatchInterfaces/LinkFormat.cs:238
  • SmartTagRecognizer.FullName Source/Word/DispatchInterfaces/SmartTagRecognizer.cs:115
  • StyleSheet.FullName Source/Word/DispatchInterfaces/StyleSheet.cs:160
  • Template.FullName Source/Word/DispatchInterfaces/Template.cs:251
  • _Document.FullName Source/Word/DispatchInterfaces/_Document.cs:555
Phone — 26 field(s)
  • Customer._phone Examples/Access/IExtensibility COMAddin Examples/TaskPane/SampleData/Customer.cs:15
  • Customer.Phone Examples/Access/IExtensibility COMAddin Examples/TaskPane/SampleData/Customer.cs:34
  • Customer._phone Examples/Excel/IExtensibility COMAddin Examples/TaskPane/SampleData/Customer.cs:15
  • Customer.Phone Examples/Excel/IExtensibility COMAddin Examples/TaskPane/SampleData/Customer.cs:34
  • Customer._phone Examples/Outlook/IExtensibility COMAddin Examples/TaskPane/SampleData/Customer.cs:16
  • Customer.Phone Examples/Outlook/IExtensibility COMAddin Examples/TaskPane/SampleData/Customer.cs:37
  • Customer._phone Examples/PowerPoint/IExtensibility COMAddin Examples/TaskPane/SampleData/Customer.cs:15
  • Customer.Phone Examples/PowerPoint/IExtensibility COMAddin Examples/TaskPane/SampleData/Customer.cs:34
  • Customer._phone Examples/Word/IExtensibility COMAddin Examples/TaskPane/SampleData/Customer.cs:15
  • Customer.Phone Examples/Word/IExtensibility COMAddin Examples/TaskPane/SampleData/Customer.cs:34
  • _ContactItem.AssistantTelephoneNumber Source/Outlook/DispatchInterfaces/_ContactItem.cs:639
  • _ContactItem.Business2TelephoneNumber Source/Outlook/DispatchInterfaces/_ContactItem.cs:675
  • _ContactItem.BusinessTelephoneNumber Source/Outlook/DispatchInterfaces/_ContactItem.cs:855
  • _ContactItem.CallbackTelephoneNumber Source/Outlook/DispatchInterfaces/_ContactItem.cs:873
  • _ContactItem.CarTelephoneNumber Source/Outlook/DispatchInterfaces/_ContactItem.cs:891
  • _ContactItem.CompanyMainTelephoneNumber Source/Outlook/DispatchInterfaces/_ContactItem.cs:969
  • _ContactItem.Home2TelephoneNumber Source/Outlook/DispatchInterfaces/_ContactItem.cs:1403
  • _ContactItem.HomeTelephoneNumber Source/Outlook/DispatchInterfaces/_ContactItem.cs:1565
  • _ContactItem.MobileTelephoneNumber Source/Outlook/DispatchInterfaces/_ContactItem.cs:1955
  • _ContactItem.OtherTelephoneNumber Source/Outlook/DispatchInterfaces/_ContactItem.cs:2207
  • _ContactItem.PrimaryTelephoneNumber Source/Outlook/DispatchInterfaces/_ContactItem.cs:2261
  • _ContactItem.RadioTelephoneNumber Source/Outlook/DispatchInterfaces/_ContactItem.cs:2297
  • _ContactItem.TTYTDDTelephoneNumber Source/Outlook/DispatchInterfaces/_ContactItem.cs:2423
  • _ExchangeUser.BusinessTelephoneNumber Source/Outlook/DispatchInterfaces/_ExchangeUser.cs:364
  • _ExchangeUser.MobileTelephoneNumber Source/Outlook/DispatchInterfaces/_ExchangeUser.cs:508
  • _MobileItem.MobileFormat Source/Outlook/DispatchInterfaces/_MobileItem.cs:572
Address — 21 field(s)
  • Customer._postalCode Examples/Access/IExtensibility COMAddin Examples/TaskPane/SampleData/Customer.cs:13
  • Customer.PostalCode Examples/Access/IExtensibility COMAddin Examples/TaskPane/SampleData/Customer.cs:32
  • Customer._postalCode Examples/Excel/IExtensibility COMAddin Examples/TaskPane/SampleData/Customer.cs:13
  • Customer.PostalCode Examples/Excel/IExtensibility COMAddin Examples/TaskPane/SampleData/Customer.cs:32
  • Customer._postalCode Examples/Outlook/IExtensibility COMAddin Examples/TaskPane/SampleData/Customer.cs:14
  • Customer.PostalCode Examples/Outlook/IExtensibility COMAddin Examples/TaskPane/SampleData/Customer.cs:35
  • Customer._postalCode Examples/PowerPoint/IExtensibility COMAddin Examples/TaskPane/SampleData/Customer.cs:13
  • Customer.PostalCode Examples/PowerPoint/IExtensibility COMAddin Examples/TaskPane/SampleData/Customer.cs:32
  • Customer._postalCode Examples/Word/IExtensibility COMAddin Examples/TaskPane/SampleData/Customer.cs:13
  • Customer.PostalCode Examples/Word/IExtensibility COMAddin Examples/TaskPane/SampleData/Customer.cs:32
  • _ContactItem.BusinessAddressPostalCode Source/Outlook/DispatchInterfaces/_ContactItem.cs:747
  • _ContactItem.HomeAddress Source/Outlook/DispatchInterfaces/_ContactItem.cs:1421
  • _ContactItem.HomeAddressCity Source/Outlook/DispatchInterfaces/_ContactItem.cs:1439
  • _ContactItem.HomeAddressCountry Source/Outlook/DispatchInterfaces/_ContactItem.cs:1457
  • _ContactItem.HomeAddressPostalCode Source/Outlook/DispatchInterfaces/_ContactItem.cs:1475
  • _ContactItem.HomeAddressPostOfficeBox Source/Outlook/DispatchInterfaces/_ContactItem.cs:1493
  • _ContactItem.HomeAddressState Source/Outlook/DispatchInterfaces/_ContactItem.cs:1511
  • _ContactItem.HomeAddressStreet Source/Outlook/DispatchInterfaces/_ContactItem.cs:1529
  • _ContactItem.OtherAddressPostalCode Source/Outlook/DispatchInterfaces/_ContactItem.cs:2117
  • _ExchangeUser.PostalCode Source/Outlook/DispatchInterfaces/_ExchangeUser.cs:544
  • _ExchangeUser.StreetAddress Source/Outlook/DispatchInterfaces/_ExchangeUser.cs:594

Downloadable artifacts

Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.

⬇ Findings, MITRE CWE-tagged .sarif⬇ Health changelog .md