Public report of rudderdon/case-apps, published 21 October 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 reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). Watchdog 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, 21 October 2026, 15:52 UTC · Survey ID cd_95b4f60f8daf42c286526eb216fe15bb
rudderdon/case-apps
Measured 21 October 2026, 15:49 UTC, at code version e8c39e0
Code coverage is not measured: No coverage collector is wired up.
Boundary Type-Coupling is not measured: Bounded contexts not declared.
IL efficiency is not measured: The target did not build.
CAI scoreProvisionalDown 9 since the last survey
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 large codebase: 200,488 lines of product code in 179 projects, tests not counted · Estimated rebuild effort: about 1.3 person-years · Weakest lens: Production Readiness, 18
Findings by how serious they are
4161 critical2289 serious92 minor
6 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks 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
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
21 October 2026, 15:49 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 Watchdog. It is open to any tool that
implements it, and today Watchdog is the only one that does.
The code didn't build, so the score is provisional
Watchdog couldn't build the code: the build stopped with 4587 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: BC30002: Type 'Document' is not defined.; BC30002: Type 'Category' is not defined.; BC30002: Type 'Element' is not defined.; BC30002: Type 'ElementId' is not defined.; BC30002: Type 'RevitLinkType' is not defined.
The score is deterministic, which means the same code always gets the same score. Watchdog works 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 ▸
53of 57 dimensions measured by tools. The other 4 are advisory notes from an AI model, which explain the code but don't count towards the score.
6528of 6542 findings point to an exact file and line, so you can open each one in the code. The other 14 concern the repository as a whole, such as missing documentation.
57dimensions across 5 lenses, read from 200,488 lines of product code in 179 projects.
rudderdon/case-apps scores 38 out of 100, but the score is provisional because the code didn't build, so the ratings below may change once it does.
The weakest lens counts most in the score, and here that is Production Readiness, which scores 18 and is rated Critical. Its Secret Scanning dimension scores 0 out of 10, and until that reaches 4, Production Readiness can't be rated higher than Adequate. The first actions are to resolve the 88 Leaked secret finding(s) in Secret Scanning and to add a CI workflow that builds and runs the test suite on every push/PR, and if Production Readiness rose to 70, the score would rise from 38 to about 55.
4161 findings are critical: 4071 in Explicit Debt, 88 in Secret Scanning and two in Dependency Vulnerabilities.
Watchdog couldn't measure 4 dimensions in this code, among them Test Reliability, Dependency Hygiene and Platform End-of-Life, so they are left out of the score. The product code is 200,488 lines, which would take an estimated 1.3 person-years, around €180,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 forThe 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.
If Production Readiness rose from 18 to 70, the lowest score rated Strong, the score would rise from 38 to about 55.
Code composition: what the lines of code are
Business logic 11%Supporting code 11%Tests 1%Generated by tools 77%
New since the last survey: 184 findings
These 184 critical or serious findings weren't in the previous survey, on 6 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
Code Duplication · Near-duplicate member family (4 members, 192 shared lines) 2015/Case.RoomSync/Case.RoomSync/UI/form_Sync.vb
Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 214 findings
These 214 critical or serious findings were in the previous survey, on 6 October 2026, and are gone from this one. The first 100 are listed here.
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) 2015/Case.RoomSync/Case.RoomSync/UI/form_Sync.vb
€60,000 to €300,000, for 1,004 to 3,199 hours of work, about 1.3 person-years for 1 to 3 engineers
Difficulty of the problem
Standard, 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 38. 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.
Size
Large: 200,488 lines of product code
Comment lines
The estimate prices 192,909 lines. Comment lines count towards the size of 200,488 lines but aren't priced as work.
How the estimate is made: Watchdog prices 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
Resolve the 88 Leaked secret finding(s) in Secret Scanning — start with REDACTED (57), REDACTED (25), REDACTED (4).
Raises the score by about 17 points · Medium effort · Secret Scanning
2
Add a CI workflow that builds and runs the test suite on every push/PR.
Raises the score by about 10 points · Medium effort · CI/CD gates
3
Run what this repository's stack ships: a Roslyn security analyzer package referenced from the project (the analyzer packages do analyse VB.NET), plus gitleaks for committed secrets — CodeQL has no VB.NET extractor, so its csharp pack would extract nothing from this tree and then report it clean — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
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: BC30002: Type 'Document' is not defined.; BC30002: Type 'Category' is not defined.; BC30002: Type 'Element' is not defined.; BC30002: Type 'ElementId' is not defined.; BC30002: Type 'RevitLinkType' is not defined.
Based on: Solution Shape
Where the investment is most exposed · Value at risk
This code would cost about €180,000 to build again, about 1.3 person-years of work. Its weakest lens is Production Readiness, at 18 (Critical). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness 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.2 out of 10. Code at that level is slower to change than clean code, and Watchdog estimates the extra work at 4% to 10% on every change.
How this is estimated: It rests on an assumption of Watchdog's 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. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4)
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: 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.
190 modules, with 42 dependencies between them. 3 loops run through 6 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 150 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.
Case.ApplySysOrient.UI uses Case.ApplySysOrient.Data, so a change to Case.ApplySysOrient.Data can break Case.ApplySysOrient.UI, while a change to Case.ApplySysOrient.UI can't break Case.ApplySysOrient.Data.
Position
Below the diagonal: Case.ApplySysOrient.UI uses a module listed above it, which is the healthy direction.
Case.DimensionOverrides.UI uses Case.DimensionOverrides.Data, so a change to Case.DimensionOverrides.Data can break Case.DimensionOverrides.UI, while a change to Case.DimensionOverrides.UI can't break Case.DimensionOverrides.Data.
Position
Below the diagonal: Case.DimensionOverrides.UI uses a module listed above it, which is the healthy direction.
Case.FamilySubcategories.UI uses Case.FamilySubcategories.Data, so a change to Case.FamilySubcategories.Data can break Case.FamilySubcategories.UI, while a change to Case.FamilySubcategories.UI can't break Case.FamilySubcategories.Data.
Position
Below the diagonal: Case.FamilySubcategories.UI uses a module listed above it, which is the healthy direction.
Case.ObjectStyles.UI uses Case.ObjectStyles.Data, so a change to Case.ObjectStyles.Data can break Case.ObjectStyles.UI, while a change to Case.ObjectStyles.UI can't break Case.ObjectStyles.Data.
Position
Below the diagonal: Case.ObjectStyles.UI uses a module listed above it, which is the healthy direction.
Case.ReportGroupsByView.UI uses Case.ReportGroupsByView.Data, so a change to Case.ReportGroupsByView.Data can break Case.ReportGroupsByView.UI, while a change to Case.ReportGroupsByView.UI can't break Case.ReportGroupsByView.Data.
Position
Below the diagonal: Case.ReportGroupsByView.UI uses a module listed above it, which is the healthy direction.
Case.UngroupAll.UI uses Case.UngroupAll.Data, so a change to Case.UngroupAll.Data can break Case.UngroupAll.UI, while a change to Case.UngroupAll.UI can't break Case.UngroupAll.Data.
Position
Below the diagonal: Case.UngroupAll.UI uses a module listed above it, which is the healthy direction.
[Case].BasicReporting uses [Case].BasicReporting.Data, so a change to [Case].BasicReporting.Data can break [Case].BasicReporting, while a change to [Case].BasicReporting can't break [Case].BasicReporting.Data.
Position
Below the diagonal: [Case].BasicReporting uses a module listed above it, which is the healthy direction.
[Case].ChangeLineStyles uses [Case].ChangeLineStyles.Data, so a change to [Case].ChangeLineStyles.Data can break [Case].ChangeLineStyles, while a change to [Case].ChangeLineStyles can't break [Case].ChangeLineStyles.Data.
Position
Below the diagonal: [Case].ChangeLineStyles uses a module listed above it, which is the healthy direction.
[Case].ChangeReplaceFamTypeNames uses [Case].ChangeReplaceFamTypeNames.Data, so a change to [Case].ChangeReplaceFamTypeNames.Data can break [Case].ChangeReplaceFamTypeNames, while a change to [Case].ChangeReplaceFamTypeNames can't break [Case].ChangeReplaceFamTypeNames.Data.
Position
Below the diagonal: [Case].ChangeReplaceFamTypeNames uses a module listed above it, which is the healthy direction.
[Case].DeleteViewsAndPurge uses [Case].DeleteViewsAndPurge.Data, so a change to [Case].DeleteViewsAndPurge.Data can break [Case].DeleteViewsAndPurge, while a change to [Case].DeleteViewsAndPurge can't break [Case].DeleteViewsAndPurge.Data.
Position
Below the diagonal: [Case].DeleteViewsAndPurge uses a module listed above it, which is the healthy direction.
[Case].Directionality uses [Case].Directionality.Data, so a change to [Case].Directionality.Data can break [Case].Directionality, while a change to [Case].Directionality can't break [Case].Directionality.Data.
Position
Below the diagonal: [Case].Directionality uses a module listed above it, which is the healthy direction.
[Case].DoorMarkRenumber uses [Case].DoorMarkRenumber.Data, so a change to [Case].DoorMarkRenumber.Data can break [Case].DoorMarkRenumber, while a change to [Case].DoorMarkRenumber can't break [Case].DoorMarkRenumber.Data.
Position
Below the diagonal: [Case].DoorMarkRenumber uses a module listed above it, which is the healthy direction.
[Case].Export.Families uses [Case].Export.Families.Data, so a change to [Case].Export.Families.Data can break [Case].Export.Families, while a change to [Case].Export.Families can't break [Case].Export.Families.Data.
Position
Below the diagonal: [Case].Export.Families uses a module listed above it, which is the healthy direction.
[Case].HiddenParameterToParameter uses [Case].HiddenParameterToParameter.Data, so a change to [Case].HiddenParameterToParameter.Data can break [Case].HiddenParameterToParameter, while a change to [Case].HiddenParameterToParameter can't break [Case].HiddenParameterToParameter.Data.
Position
Below the diagonal: [Case].HiddenParameterToParameter uses a module listed above it, which is the healthy direction.
[Case].ImageToDraftingView uses [Case].ImageToDraftingView.Data, so a change to [Case].ImageToDraftingView.Data can break [Case].ImageToDraftingView, while a change to [Case].ImageToDraftingView can't break [Case].ImageToDraftingView.Data.
Position
Below the diagonal: [Case].ImageToDraftingView uses a module listed above it, which is the healthy direction.
34→38 [Case].Subs.DeleteViewsAndPurge.Data uses [Case].Subs.DeleteViewsAndPurgepart of a loop✕
Connections
1 pair of types, where a type in [Case].Subs.DeleteViewsAndPurge.Data uses a type in [Case].Subs.DeleteViewsAndPurge.
[Case].Subs.DeleteViewsAndPurge.Data uses [Case].Subs.DeleteViewsAndPurge, so a change to [Case].Subs.DeleteViewsAndPurge can break [Case].Subs.DeleteViewsAndPurge.Data, while a change to [Case].Subs.DeleteViewsAndPurge.Data can't break [Case].Subs.DeleteViewsAndPurge.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
35→39 [Case].Subs.Exceler8.Data uses [Case].Subs.Exceler8part of a loop✕
Connections
1 pair of types, where a type in [Case].Subs.Exceler8.Data uses a type in [Case].Subs.Exceler8.
[Case].Subs.Exceler8.Data uses [Case].Subs.Exceler8, so a change to [Case].Subs.Exceler8 can break [Case].Subs.Exceler8.Data, while a change to [Case].Subs.Exceler8.Data can't break [Case].Subs.Exceler8.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
36→40 [Case].Subs.MultiViewDuplicate.Data uses [Case].Subs.MultiViewDuplicatepart of a loop✕
Connections
1 pair of types, where a type in [Case].Subs.MultiViewDuplicate.Data uses a type in [Case].Subs.MultiViewDuplicate.
[Case].Subs.MultiViewDuplicate.Data uses [Case].Subs.MultiViewDuplicate, so a change to [Case].Subs.MultiViewDuplicate can break [Case].Subs.MultiViewDuplicate.Data, while a change to [Case].Subs.MultiViewDuplicate.Data can't break [Case].Subs.MultiViewDuplicate.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
[Case].Subs.Worksets.Charts uses [Case].Subs.Worksets.Data, so a change to [Case].Subs.Worksets.Data can break [Case].Subs.Worksets.Charts, while a change to [Case].Subs.Worksets.Charts can't break [Case].Subs.Worksets.Data.
Position
Below the diagonal: [Case].Subs.Worksets.Charts uses a module listed above it, which is the healthy direction.
[Case].Subs.DeleteViewsAndPurge uses [Case].Subs.DeleteViewsAndPurge.Data, so a change to [Case].Subs.DeleteViewsAndPurge.Data can break [Case].Subs.DeleteViewsAndPurge, while a change to [Case].Subs.DeleteViewsAndPurge can't break [Case].Subs.DeleteViewsAndPurge.Data.
Position
Below the diagonal: [Case].Subs.DeleteViewsAndPurge uses a module listed above it, which is the healthy direction.
[Case].Subs.Exceler8 uses [Case].Subs.Exceler8.Data, so a change to [Case].Subs.Exceler8.Data can break [Case].Subs.Exceler8, while a change to [Case].Subs.Exceler8 can't break [Case].Subs.Exceler8.Data.
Position
Below the diagonal: [Case].Subs.Exceler8 uses a module listed above it, which is the healthy direction.
[Case].Subs.MultiViewDuplicate uses [Case].Subs.MultiViewDuplicate.Data, so a change to [Case].Subs.MultiViewDuplicate.Data can break [Case].Subs.MultiViewDuplicate, while a change to [Case].Subs.MultiViewDuplicate can't break [Case].Subs.MultiViewDuplicate.Data.
Position
Below the diagonal: [Case].Subs.MultiViewDuplicate uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 44% · Weak · gated by D2, D18, D17, X3 ·
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 category
Findings
Severity
A07:2025 — Authentication Failures
88
High / Critical
A05:2025 — Injection
78
Medium
A03:2025 — Software Supply Chain Failures
3
High / Critical
Roadmap
Immediately resolve the 88 leaked secrets, prioritizing REDACTED, REDACTED, and REDACTED, to eliminate critical security exposure. Establish a CI pipeline that builds on every push and integrates local security tooling, including the project's Roslyn analyzer and gitleaks, to prevent future regressions. Finally, address the 4,063 empty catch blocks, starting with clsSettings.vb, and clear the 8 write-only private fields in cmd.cs and app.cs to improve code quality and maintainability.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 88 Leaked secret finding(s) in Secret Scanning — start with REDACTED (57), REDACTED (25), REDACTED (4).
Run what this repository's stack ships: a Roslyn security analyzer package referenced from the project (the analyzer packages do analyse VB.NET), plus gitleaks for committed secrets — CodeQL has no VB.NET extractor, so its csharp pack would extract nothing from this tree and then report it clean — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
Resolve the 4 Solution references a project that does not exist finding(s) in Solution Shape — start with Case.Subs.Worksets.sln, Case.Subs.RoomsToMass.sln, Case.Subs.OpenNURBS.sln.
Per-file score 0–10 — a quality signature. Of 907 files carrying findings, judged against the Production bar: 42% slop · 47% mixed · 11% near-clean.
File
Score
Band
Worst signal
REDACTED
0.0
Slop
Secret Scanning: Leaked secret: REDACTED
REDACTED
0.0
Slop
Secret Scanning: Leaked secret: REDACTED
REDACTED
0.0
Slop
Secret Scanning: Leaked secret: REDACTED
REDACTED
0.0
Slop
Secret Scanning: Leaked secret: REDACTED
REDACTED
0.0
Slop
Secret Scanning: Leaked secret: REDACTED
REDACTED
0.0
Slop
Secret Scanning: Leaked secret: REDACTED
REDACTED
0.0
Slop
Secret Scanning: Leaked secret: REDACTED
REDACTED
0.0
Slop
Secret Scanning: Leaked secret: REDACTED
REDACTED
0.0
Slop
Secret Scanning: Leaked secret: REDACTED
REDACTED
0.0
Slop
Secret Scanning: Leaked secret: REDACTED
REDACTED
0.0
Slop
Secret Scanning: Leaked secret: REDACTED
REDACTED
0.0
Slop
Secret Scanning: Leaked secret: REDACTED
REDACTED
0.0
Slop
Secret Scanning: Leaked secret: REDACTED
REDACTED
0.0
Slop
Secret Scanning: Leaked secret: REDACTED
REDACTED
0.0
Slop
Secret Scanning: Leaked secret: REDACTED
REDACTED
0.0
Slop
Secret Scanning: Leaked secret: REDACTED
REDACTED
0.0
Slop
Secret Scanning: Leaked secret: REDACTED
REDACTED
0.0
Slop
Secret Scanning: Leaked secret: REDACTED
REDACTED
0.0
Slop
Secret Scanning: Leaked secret: REDACTED
REDACTED
0.0
Slop
Secret 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 — 4161
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 — 2289
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 — 92
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 6
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
Watchdog 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. 53 of 57 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 4 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three 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; ◐ Advisory — an LLM prose judgement. 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; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 57 dimensions across the health lenses
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
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, 6528 of 6542 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.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
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.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
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.
D11 Test Reliability — not measured this run — Watchdog 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 source is present (.vb) and it is .NET, which this analyzer re-runs through `dotnet test` — but the .NET workspace loaded none of this repository's test projects, so there was no suite to re-run and flakiness couldn't be assessed. The repository commits a project or solution file, so the load had something to read and still produced nothing: the remedy is the restore, the SDK band or the target resolution, not a new runner. Not scored — this is a gap on our side, not a finding about this repository.
D12 Dependency Hygiene — not measured this run — Watchdog 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.
D15 Churn × Complexity Hotspots — 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. Git history depth insufficient — this repository has 15 commit(s), too few for a reliable trend signal. The clone is complete, so there is no deeper history to fetch: the signal returns as the project accumulates history.
D16 Bus Factor — 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. Too few commits for a meaningful bus factor (15 commit(s) sampled, fewer than the 50 this dimension needs before a bus factor means anything).
D17 Explicit Debt — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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 '2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Case.Subs.Exceler8.vbproj' with message: The task "ResolveComReference" is not supported on the .NET Core version of MSBuild. Please use the .NET Framework version of MSBuild. See https://aka.ms/msbuild/MSB4803 for further details.
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 — Watchdog 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 (200,488 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. The solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan. 1 of 2 declared ecosystem(s) (nuget REDACTED) 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.
D34 Knowledge Freshness — 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. Too few commits to judge knowledge freshness (15 commit(s) sampled).
D35 Change Coupling — 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. Git history depth insufficient — this repository has 15 commit(s), too few for a reliable change-coupling signal. The clone is complete, so there is no deeper history to fetch: the signal returns as the project accumulates history.
D39 IL Efficiency — 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. `dotnet build` exited 1 with a compiler/MSBuild diagnostic, so there were no assemblies to read IL from. The build itself is D18's row, with the ask; nothing further is charged here.
D44 Platform End-of-Life — not measured this run — Watchdog 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. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
AXB1 Runtime evidence locked — no reproducible boot — not measured this run — Watchdog 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. Subject: a native UI project (2015/Case.Navis2BCF/Case.Navis2BCF/Navis2BCFWin.xaml). The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. Watchdog then boots it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
IC1 Incompleteness & stubs — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. 30 further occurrence(s) are not listed individually; the score already reflects all 70.
M3 Folder & project structure — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. Whether the tests sit apart from production code is not visible here, because the suite is not in a form this pass reads. The test-separation credit is granted rather than withheld: this is a gap in the analyzer's language coverage, not a finding about the repository's tests. You can widen what we reach: keep the test surface somewhere a reader can find it without opening a binary — an exported/checked-in test source tree beside the production code makes the suite reviewable, diffable and discoverable by tooling.
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.
X3 Exception handling — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. 219 further occurrence(s) are not listed individually; the score already reflects all 259.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does 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.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
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.
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.
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 is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D24 Comment Value: Comment value (WHY vs WHAT) is an LLM judgement over a bounded sample — it is advisory and cannot weigh a comment against the precise code change it was written to explain.
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.
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.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
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.
The LLM boundary
LLM-set scores this run (4): D19, D21, D24, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
+ 58 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 4 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with clsRvtCategoryData.GetAllPropertyValues (cyclomatic 91), clsRvtCategoryData.GetAllPropertyValues (cyclomatic 91), clsRvtCategoryData.GetAllPropertyValues (cyclomatic 91). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cyclomatic Complexity from 5.5 to about 6.1/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Stand up a CI pipeline, then gate Cyclomatic Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 139 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 569 bodies over 15 down to 15 or less in Cognitive Complexity — start with clsRvtCategoryData.GetAllPropertyValues (cognitive 329), clsRvtCategoryData.GetAllPropertyValues (cognitive 329), clsRvtCategoryData.GetAllPropertyValues (cognitive 329). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 569 together lifts Cognitive Complexity from 2.0 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Stand up a CI pipeline, then gate Cognitive Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.0 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 82 MethodTooLong finding(s) in God Classes — start with form_RoomMasses.vb (8), clsReportingData.vb (8), form_Sync.vb (8). — One of this dimension's main actionable groups (82 warning-level).
Resolve the 31 ClassTooLong finding(s) in God Classes — start with form_Sync.vb (4), clsReportingData.vb (4), RVTCurveUtils.vb (4). — One of this dimension's main actionable groups (31 warning-level).
Resolve the 19 FileTooLong finding(s) in God Classes — start with form_Sync.vb (4), clsReportingData.vb (4), RVTCurveUtils.vb (4). — One of this dimension's main actionable groups (19 warning-level).
Stand up a CI pipeline, then gate God Classes in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
749 duplicated block group(s) detected. A further 352 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
Members sharing a duplicated core (4 members, 50+ identical tokens) · ×2872015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsElementsByCategory.vb:63
Duplicated block (10 lines × 4) · ×24REDACTED:555
Duplicated block (12 lines × 4) · ×19REDACTED:508
Duplicated block (23 lines × 4) · ×18REDACTED:194
Duplicated block (19 lines × 4) · ×18REDACTED:301
+ 254 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 287 Members sharing a duplicated core (4 members, 50+ identical tokens) finding(s) in Code Duplication — start with clsSettings.vb (45), form_Main.vb (38), REDACTED (15). — One of this dimension's main actionable groups (287 warning-level).
Resolve the 24 Duplicated block (10 lines × 4) finding(s) in Code Duplication — start with form_Main.vb (5), clsRoomTagInfo.vb (3), clsParameter.vb (2). — One of this dimension's main actionable groups (24 warning-level).
Resolve the 19 Duplicated block (12 lines × 4) finding(s) in Code Duplication — start with clsSettings.vb (4), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (19 warning-level).
Stand up a CI pipeline, then gate Code Duplication in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling10.0 / 10Exemplary✓ 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.
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.
Resolve the 20 Low cohesion finding(s) in Cohesion (LCOM4) — start with form_DataManager.xaml.vb (4), clsAutomationTest.vb (4), form_PlacePoint.xaml.vb (4). — One of this dimension's main actionable groups (20 warning-level).
Stand up a CI pipeline, then gate Cohesion (LCOM4) in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
Resolve the 88 Leaked secret finding(s) in Secret Scanning — start with REDACTED (57), REDACTED (25), REDACTED (4). — One of this dimension's main actionable groups (88 issue-level).
Stand up a CI pipeline, then gate Secret Scanning in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
0 of 108 packages use a banned license. The depth of this set was not established for this repository: the graded packages are what this pass resolved, and no lockfile was read, so it is not certified to be the full transitive closure.
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.
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.
4093 deducted debt markers + unmeasured dead symbols across 200488 LoC in the .NET projects (20.1/KLoC) → score 0.0. Dead code not measured: the solution did not load cleanly, so the reference search was skipped.
Resolve the 4063 EmptyCatchBlock finding(s) in Explicit Debt — start with clsSettings.vb (724), form_Main.vb (518), REDACTED (171). — One of this dimension's main actionable groups (4063 issue-level).
Resolve the 8 WriteOnlyPrivateField finding(s) in Explicit Debt — start with cmd.cs (4), app.cs (4). — One of this dimension's main actionable groups (8 issue-level).
Resolve the 18 CommentedOutCode finding(s) in Explicit Debt — start with cmd.cs (12), IfcGuid.cs (4), REDACTED (2). — One of this dimension's main actionable groups (18 warning-level).
Stand up a CI pipeline, then gate Explicit Debt in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
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.
179 projects, 1478 source files, 201316 hand-written lines of code (200488 production / 828 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 71062 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 0 inter-project edges (build failed). Measured across 8 solutions loaded as one workspace: `Case.Apps.2015.sln`, `Case.Apps.2016.sln`, `Case.Apps.2017.sln`, `Case.Apps.2018.sln`, `2015/Case.Subs.Worksets/Case.Subs.Worksets.sln`, `2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass.sln`, `2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS.sln`, `2015/Case.Subs.SharedParameters/Case.Subs.SharedParameters.sln`.
Solution references a project that does not exist · ×42015/Case.Subs.Worksets/Case.Subs.Worksets.sln
Build failed
What to do
Resolve the 4 Solution references a project that does not exist finding(s) in Solution Shape — start with Case.Subs.Worksets.sln, Case.Subs.RoomsToMass.sln, Case.Subs.OpenNURBS.sln. — One of this dimension's main actionable groups (4 warning-level).
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.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.
The repository's root README is a clear overview of what CASE Apps is and its origins (a set of Autodesk Revit add-ins for BIM workflows), an installation link to releases, a brief structure section explaining the 2015/2016 projects organized by year/set, post-build copy rules, and pull-request guidance. It also thanks contributors Don Rudder, Matthew Nelson, Matteo Cominetti, and Kyle Morin. The body is clipped mid-Installation at '## Pull Requests' before covering installation, usage, contribution, or licence; the outline lists all these sections present in the document.
Resolve the 16 Low XML-doc coverage finding(s) in Documentation Quality — start with Case.ApplySysOrient.csproj (4), Case.ViewCreator.csproj (4), Case.Subs.KeyMatcher.csproj (4). — One of this dimension's main actionable groups (16 warning-level).
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.
6 naming inconsistencies across 200 sampled symbols.
Typo in method name: 'ChechHidden' appears to be a misspelling of 'CheckHidden'. While 'ShowMessage' is a different concept, the presence of a clear typo ('Chech') alongside correctly spelled verbs in similar contexts (e.g., 'ShowMessage', 'GetOriginalAngles') indicates a lack of consistency in spelling correctness within the codebase.
Inconsistent naming for local settings fields across different form classes. While '_s' is a common abbreviation, the codebase also uses more descriptive names like '_cmd' for command data and 'defaultInstance' for settings. However, since '_s' is used consistently across multiple forms for the same type (`clsSettings`), this is actually a consistent convention within the UI layer. No inconsistency found here as the pattern is uniform.
Consistent naming for Culture properties across all Resources classes. No inconsistency.
Consistent naming for ResourceManager fields. No inconsistency.
Inconsistent naming for the resource culture field/property. Some classes use a field named 'resourceCulture' (e.g., `UngroupAll`), while others use a property named 'Culture' (e.g., `ApplySysOrient`). These represent the same concept (the current culture for resource lookup) but are named differently.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 Typo in method name finding(s) in Naming Consistency. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 Inconsistent naming for local settings fields across different form… finding(s) in Naming Consistency. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 Consistent naming for Culture properties across all Resources classes.… finding(s) in Naming Consistency. — 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.
Do you agree with this assessment?
D24 · Comment ValueExemplary◐ Sampled · advisory
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Judged by language model at low temperature (0.0-0.1) on deterministically sampled inline comments with surrounding code; findings verified back to sampled comments by substring match. Advisory, sampled.
0 of 179 projects flagged as possibly oversized/incoherent.
✓ On the Gold path — maintain.
Detailed fixes: d26_recommendation.md.
Do you agree with this assessment?
D27 · Navigability8.5 / 10Strong✓ 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.
90 % of calls cross a namespace and 10 % 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.
What to do
Improve Navigability — currently 8.5/10. — 90 % of calls cross a namespace and 10 % 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.
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.
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).
Resolve the 78 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (50), REDACTED (20), REDACTED (4). — One of this dimension's main actionable groups (78 warning-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
3 finding(s): 0 critical, 2 high, 1 medium, 0 low. Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (nuget REDACTED), and the findings above are real and complete for them. nuget was not scanned (nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan), so this is not the whole dependency surface and the result is reported at reduced confidence.
REDACTED
REDACTED
What to do
Resolve the 2 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
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. Scored 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. SCORED, not informational.
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.
What to do
The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
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.
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.
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.
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. (×8) — 2015/Case.Navis2BCF/Case.Navis2BCF/Converters.cs:41, 2015/Case.Navis2BCF/Case.Navis2BCF/VisibConverter.cs:38, 2016/Case.Navis2BCF/Case.Navis2BCF/Converters.cs:41, …
What to do
Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
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.
`LogData` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. (×4) — 2015/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs:104, 2016/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs:104, 2017/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs:104, …
A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×34) — REDACTED:123, REDACTED:132, 2015/Case.ExportSharedParameters/Case.ExportSharedParameters/Classes/Entry/cmd.cs:42, …
13 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers). (×2) — 2015/Case.Navis2BCF/Case.Navis2BCF/IfcGuid.cs:167, 2016/Case.Navis2BCF/Case.Navis2BCF/IfcGuid.cs:167
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.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
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.
Add a README to the 179 of 179 project(s) that lack one — worth up to 2 pts.
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.
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.
Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.
What to do
Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
Do you agree with this assessment?
P1 · CI/CD gates0.0 / 10Critical✓ Tool-verified
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.
No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
Add a CI workflow that builds and runs the test suite on every push/PR.
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 a Roslyn security analyzer package referenced from the project (the analyzer packages do analyse VB.NET), plus gitleaks for committed secrets — CodeQL has no VB.NET extractor, so its csharp pack would extract nothing from this tree and then report it clean — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 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.
What to do
Run what this repository's stack ships: a Roslyn security analyzer package referenced from the project (the analyzer packages do analyse VB.NET), plus gitleaks for committed secrets — CodeQL has no VB.NET extractor, so its csharp pack would extract nothing from this tree and then report it clean — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
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.
No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
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.
Do you agree with this assessment?
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.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.
Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.
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.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
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.
`sr` is a `StreamReader`, which implements `IDisposable`, and it is created here (line 83). Every use of it in `GetPublicIp` 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 sr = …;`), which releases it at the end of the scope on every path including a throw. (×25) — REDACTED:83, REDACTED:83, REDACTED:83, …
`m_dlg` is a `form_Main`, which implements `IDisposable`, and it is created here (line 114). Every use of it in `Execute` 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 m_dlg = …;`), which releases it at the end of the scope on every path including a throw. (×4) — 2015/Case.ExportSharedParameters/Case.ExportSharedParameters/Classes/Entry/cmd.cs:114, 2016/Case.ExportSharedParameters/Case.ExportSharedParameters/Classes/Entry/cmd.cs:114, 2017/Case.ExportSharedParameters/Case.ExportSharedParameters/Classes/Entry/cmd.cs:114, …
`frm` is a `form_Main`, which implements `IDisposable`, and it is created here (line 40). Every use of it in `Execute` 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 frm = …;`), which releases it at the end of the scope on every path including a throw. (×4) — 2015/Case.ViewCreator/Case.ViewCreator/Classes/Entry/cmd.cs:40, 2016/Case.ViewCreator/Case.ViewCreator/Classes/Entry/cmd.cs:40, 2017/Case.ViewCreator/Case.ViewCreator/Classes/Entry/cmd.cs:40, …
`m_splash` is a `form_SplashScreen`, which implements `IDisposable`, and it is created here (line 47). Every use of it in `Execute` 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 m_splash = …;`), which releases it at the end of the scope on every path including a throw. (×4) — 2015/Case.ParallelWalls/Case.ParallelWalls/Entry/CmdMain.cs:47, 2016/Case.ParallelWalls/Case.ParallelWalls/Entry/CmdMain.cs:47, 2017/Case.ParallelWalls/Case.ParallelWalls/Entry/CmdMain.cs:47, …
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.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
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 controlled by an `if`, 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)`). Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.
Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. 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 `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
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.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
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.
Do you agree with this assessment?
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.
Do you agree with this assessment?
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.
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.
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. (×40) — REDACTED:40, REDACTED:93, REDACTED:147, …
What to do
Swallowed exception (empty catch)
Do you agree with this assessment?
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.
Do you agree with this assessment?
X32 · Type resolved by simple name across every loaded assembly10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a plugin lookup names the type it means — searching every assembly loaded into the process for a candidate whose SIMPLE name equals a string supplied at runtime, and taking the first one found, is decided by assembly LOAD ORDER rather than by this source, so the same name can resolve to a different type on the next run.
Method: Roslyn syntax only, no semantic model: every invocation of `First`/`FirstOrDefault`/`Single`/`SingleOrDefault` whose OWN expression subtree contains both a `GetAssemblies()` call and a `GetTypes()`/`GetExportedTypes()` call — a single-element pick out of every type loaded into the process. A nested selector in the same chain sees no `GetAssemblies()` in its own subtree and is outside the population, so one lookup counts once however many links its chain has. A finding additionally needs both remaining halves: the selector must be `First`/`FirstOrDefault` (`Single`/`SingleOrDefault` reports the ambiguity rather than resolving it, and is counted and never reported), and the chain must carry an `==` comparison of `<lambda parameter>.Name` against something that is not a literal. The receiver must be a plain identifier bound by one of the chain’s own lambdas, which places `assembly.GetName().Name == "X"` outside the rule by construction. One exemption: a `.Name` test joined by `&&` to a `FullName`/`AssemblyQualifiedName` test on the same identifier is spared; joined by `||` it is not. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. 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 `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
Do you agree with this assessment?
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.
Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Unscored — 2 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.
SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X10 Duplicated predicate — 17 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 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.
P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 58 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.
AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — no DI registrations detected
AX2 Stateful singletons — no singleton implementations detected
AX6 Interface segregation — no public interfaces
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
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.
C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
D10 Test Quality — ~828 lines of test source are present (.vb) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
D11 Test Reliability — Test reliability not included — the .NET workspace loaded no .vb test project
D12 Dependency Hygiene — Dependency hygiene not measured
D16 Bus Factor — too few commits for a meaningful bus factor
D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
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
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) — 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.
D34 Knowledge Freshness — too few commits to judge knowledge freshness
D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D39 IL Efficiency — IL not measured — the target did not build
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.
D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
D8 Code Coverage — Coverage NOT MEASURED: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect.
D9 Test Distribution — Test source is present (.vb) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
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 — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P12 CI test-gate honesty — no CI workflow found
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 — not applicable — this isn't a service/API/worker
P8 Schema migrations — no EF Core usage detected
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
PF2 Allocation hygiene — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
PF3 Async & latency hygiene — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
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.
X2 Cancellation propagation — no async method does work a token could cancel
X5 Nullable reference types — no NRT-eligible projects
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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.
EmptyCatchBlock REDACTED:40— 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 REDACTED:93— 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 REDACTED:147— 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 2015/Case.ApplySysOrient/Data/clsSettings.cs:27— 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 2015/Case.ApplySysOrient/Data/clsSettings.cs:40— 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 2015/Case.ApplySysOrient/Data/clsSettings.cs:53— 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 2015/Case.ApplySysOrient/Data/clsSettings.cs:65— 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 2015/Case.ApplySysOrient/Data/clsSettings.cs:93— 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 2015/Case.ApplySysOrient/Data/clsSettings.cs:161— 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 2015/Case.ApplySysOrient/Data/clsSettings.cs:177— 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 2015/Case.ApplySysOrient/Data/clsSettings.cs:237— 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 2015/Case.ApplySysOrient/Data/clsSettings.cs:240— 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 2015/Case.ApplySysOrient/Data/clsSettings.cs:287— 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 2015/Case.ApplySysOrient/Data/clsSettings.cs:302— 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 2015/Case.ApplySysOrient/Data/clsSettings.cs:352— 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 2015/Case.ApplySysOrient/Data/clsSettings.cs:368— 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 2015/Case.ApplySysOrient/Data/clsUtil.cs:78— 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 2015/Case.ApplySysOrient/UI/form_MaxSize.cs:57— 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 2015/Case.ApplySysOrient/UI/form_Orient.cs:34— 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 REDACTED:30— 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 REDACTED:79— 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 REDACTED:127— 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 2015/Case.BasicReporting/Case.BasicReporting/Data/clsHosts.vb:41— 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 2015/Case.BasicReporting/Case.BasicReporting/Data/clsHosts.vb:48— 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 2015/Case.BasicReporting/Case.BasicReporting/Data/clsHosts.vb:58— 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.
WriteOnlyPrivateField 2015/Case.ExportSharedParameters/Case.ExportSharedParameters/Classes/Entry/cmd.cs:20— private Dictionary<string, string> _sharedParams — 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 2016/Case.ExportSharedParameters/Case.ExportSharedParameters/Classes/Entry/cmd.cs:20— private Dictionary<string, string> _sharedParams — 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 2017/Case.ExportSharedParameters/Case.ExportSharedParameters/Classes/Entry/cmd.cs:20— private Dictionary<string, string> _sharedParams — 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 2018/Case.ExportSharedParameters/Case.ExportSharedParameters/Classes/Entry/cmd.cs:20— private Dictionary<string, string> _sharedParams — 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 2015/Case.ViewCreator/Case.ViewCreator/Classes/Entry/app.cs:25— private string ButtonIconsFolder — 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 2016/Case.ViewCreator/Case.ViewCreator/Classes/Entry/app.cs:25— private string ButtonIconsFolder — 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 2017/Case.ViewCreator/Case.ViewCreator/Classes/Entry/app.cs:25— private string ButtonIconsFolder — 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 2018/Case.ViewCreator/Case.ViewCreator/Classes/Entry/app.cs:25— private string ButtonIconsFolder — 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.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×287
Members sharing a duplicated core (4 members, 50+ identical tokens) 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsElementsByCategory.vb:63— 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsElementsByCategory.vb:63-79 | 2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsElementsByCategory.vb:63-79 | 2017/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsElementsByCategory.vb:63-79 | 2018/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsElementsByCategory.vb:63-79 — 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) 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsElementsByCategory.vb:90— 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsElementsByCategory.vb:90-122 | 2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsElementsByCategory.vb:90-122 | 2017/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsElementsByCategory.vb:90-122 | 2018/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsElementsByCategory.vb:90-122 — 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) 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSettings.vb:90— 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSettings.vb:90-141 | 2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSettings.vb:90-141 | 2017/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSettings.vb:90-141 | 2018/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSettings.vb:90-141 — 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) 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSettings.vb:152— 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSettings.vb:152-170 | 2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSettings.vb:152-170 | 2017/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSettings.vb:152-170 | 2018/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSettings.vb:152-170 — 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) 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:32— 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:32-47 | 2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:32-47 | 2017/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:32-47 | 2018/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:32-47 — 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) 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:57— 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:57-184 | 2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:57-184 | 2017/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:57-184 | 2018/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:57-184 — 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) 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:195— 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:195-246 | 2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:195-246 | 2017/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:195-246 | 2018/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:195-246 — 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) 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:266— 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:266-283 | 2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:266-283 | 2017/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:266-283 | 2018/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:266-283 — 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) 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:300— 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:300-312 | 2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:300-312 | 2017/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:300-312 | 2018/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:300-312 — 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) 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:382— 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:382-417 | 2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:382-417 | 2017/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:382-417 | 2018/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:382-417 — 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) 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:613— 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:613-632 | 2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:613-632 | 2017/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:613-632 | 2018/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:613-632 — 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) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb:41— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb:41-67 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb:41-67 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb:41-67 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb:41-67 — 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) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb:77— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb:77-93 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb:77-93 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb:77-93 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb:77-93 — 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) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb:103— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb:103-119 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb:103-119 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb:103-119 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb:103-119 — 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) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb:189— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb:189-230 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb:189-230 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb:189-230 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb:189-230 — 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) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:343— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:343-373 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:343-373 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:343-373 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:343-373 — 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) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsIoConfig.vb:62— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsIoConfig.vb:62-136 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsIoConfig.vb:62-136 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsIoConfig.vb:62-136 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsIoConfig.vb:62-136 — 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) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsIoConfig.vb:146— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsIoConfig.vb:146-168 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsIoConfig.vb:146-168 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsIoConfig.vb:146-168 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsIoConfig.vb:146-168 — 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) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:124— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:124-249 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:124-249 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:124-249 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:124-249 — 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) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:265— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:265-314 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:265-314 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:265-314 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:265-314 — 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) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:599— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:599-632 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:599-632 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:599-632 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:599-632 — 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) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:644— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:644-691 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:644-691 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:644-691 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:644-691 — 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) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:711— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:711-951 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:711-951 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:711-951 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:711-951 — 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) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:967— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:967-1008 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:967-1008 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:967-1008 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:967-1008 — 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) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtParameter.vb:161— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtParameter.vb:161-199 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtParameter.vb:161-199 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtParameter.vb:161-199 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtParameter.vb:161-199 — 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.
MethodTooLong: AppMain.LoadItemsOne Case.AppsRibbon.2017/Entry/AppMain.vb:592— MethodTooLong — LoadItemsOne runs 294 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 194 over it, 2.94× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AppMain.LoadItemsOne Case.AppsRibbon.2018/Entry/AppMain.vb:592— MethodTooLong — LoadItemsOne runs 294 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 194 over it, 2.94× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AppMain.LoadItemsOne Case.AppsRibbon/Entry/AppMain.vb:592— MethodTooLong — LoadItemsOne runs 294 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 194 over it, 2.94× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: clsRvtCategoryData.GetAllPropertyValues 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:387— MethodTooLong — GetAllPropertyValues runs 290 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 190 over it, 2.90× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: clsRvtCategoryData.GetAllPropertyValues 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:387— MethodTooLong — GetAllPropertyValues runs 290 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 190 over it, 2.90× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: clsRvtCategoryData.GetAllPropertyValues 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:387— MethodTooLong — GetAllPropertyValues runs 290 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 190 over it, 2.90× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: clsRvtCategoryData.GetAllPropertyValues 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:387— MethodTooLong — GetAllPropertyValues runs 290 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 190 over it, 2.90× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: form_RoomMasses.GenerateMasses 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:41— MethodTooLong — GenerateMasses runs 197 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 97 over it, 1.97× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: form_RoomMasses.GenerateMasses 2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:41— MethodTooLong — GenerateMasses runs 197 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 97 over it, 1.97× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: form_RoomMasses.GenerateMasses 2017/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:41— MethodTooLong — GenerateMasses runs 197 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 97 over it, 1.97× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: form_RoomMasses.GenerateMasses 2018/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:41— MethodTooLong — GenerateMasses runs 197 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 97 over it, 1.97× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: clsONSort.SortObjects 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/OpenNURBS/clsONSort.vb:56— MethodTooLong — SortObjects runs 181 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 81 over it, 1.81× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: clsONSort.SortObjects 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/OpenNURBS/clsONSort.vb:56— MethodTooLong — SortObjects runs 181 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 81 over it, 1.81× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: clsONSort.SortObjects 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/OpenNURBS/clsONSort.vb:56— MethodTooLong — SortObjects runs 181 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 81 over it, 1.81× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: clsONSort.SortObjects 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/OpenNURBS/clsONSort.vb:56— MethodTooLong — SortObjects runs 181 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 81 over it, 1.81× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AppMain.LoadItemsTwo Case.AppsRibbon.2017/Entry/AppMain.vb:394— MethodTooLong — LoadItemsTwo runs 164 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 64 over it, 1.64× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AppMain.LoadItemsTwo Case.AppsRibbon.2018/Entry/AppMain.vb:394— MethodTooLong — LoadItemsTwo runs 164 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 64 over it, 1.64× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AppMain.LoadItemsTwo Case.AppsRibbon/Entry/AppMain.vb:394— MethodTooLong — LoadItemsTwo runs 164 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 64 over it, 1.64× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Form_Main.TagElementsInViews 2015/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:326— MethodTooLong — TagElementsInViews runs 159 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 59 over it, 1.59× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Form_Main.TagElementsInViews 2016/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:326— MethodTooLong — TagElementsInViews runs 159 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 59 over it, 1.59× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Form_Main.TagElementsInViews 2017/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:326— MethodTooLong — TagElementsInViews runs 159 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 59 over it, 1.59× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Form_Main.TagElementsInViews 2018/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:326— MethodTooLong — TagElementsInViews runs 159 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 59 over it, 1.59× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: clsReportingData.New(…) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:309— MethodTooLong — New(…) runs 158 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 58 over it, 1.58× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: clsReportingData.New(…) 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:309— MethodTooLong — New(…) runs 158 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 58 over it, 1.58× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: clsReportingData.New(…) 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:309— MethodTooLong — New(…) runs 158 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 58 over it, 1.58× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Swallowed exception (empty catch) REDACTED:40— 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) REDACTED:93— 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) REDACTED:147— 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) 2015/Case.ApplySysOrient/Data/clsSettings.cs:27— 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) 2015/Case.ApplySysOrient/Data/clsSettings.cs:40— 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) 2015/Case.ApplySysOrient/Data/clsSettings.cs:53— 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) 2015/Case.ApplySysOrient/Data/clsSettings.cs:65— 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) 2015/Case.ApplySysOrient/Data/clsSettings.cs:93— 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) 2015/Case.ApplySysOrient/Data/clsSettings.cs:161— 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) 2015/Case.ApplySysOrient/Data/clsSettings.cs:177— 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) 2015/Case.ApplySysOrient/Data/clsSettings.cs:237— 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) 2015/Case.ApplySysOrient/Data/clsSettings.cs:240— 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) 2015/Case.ApplySysOrient/Data/clsSettings.cs:287— 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) 2015/Case.ApplySysOrient/Data/clsSettings.cs:302— 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) 2015/Case.ApplySysOrient/Data/clsSettings.cs:352— 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) 2015/Case.ApplySysOrient/Data/clsSettings.cs:368— 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) 2015/Case.ApplySysOrient/Data/clsUtil.cs:78— 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) 2015/Case.ApplySysOrient/UI/form_MaxSize.cs:57— 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) 2015/Case.ApplySysOrient/UI/form_Orient.cs:34— 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) 2015/Case.ExportSharedParameters/Case.ExportSharedParameters/Classes/Entry/cmd.cs:140— 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) 2015/Case.ExportSharedParameters/Case.ExportSharedParameters/Classes/Entry/cmd.cs:151— 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) 2015/Case.ExportSharedParameters/Case.ExportSharedParameters/UI/form_Main.cs:33— 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) REDACTED:40— 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) REDACTED:93— 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) REDACTED:147— 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.
+ 15 more in this group — see findings.md.
X18 · Disposal-pattern correctness· Disposable created and abandoned in the method that made it · ×37
Disposable created and abandoned in the method that made it REDACTED:83— `sr` is a `StreamReader`, which implements `IDisposable`, and it is created here (line 83). Every use of it in `GetPublicIp` 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 sr = …;`), 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 2015/Case.ExportSharedParameters/Case.ExportSharedParameters/Classes/Entry/cmd.cs:114— `m_dlg` is a `form_Main`, which implements `IDisposable`, and it is created here (line 114). Every use of it in `Execute` 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 m_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 REDACTED:83— `sr` is a `StreamReader`, which implements `IDisposable`, and it is created here (line 83). Every use of it in `GetPublicIp` 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 sr = …;`), 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:83— `sr` is a `StreamReader`, which implements `IDisposable`, and it is created here (line 83). Every use of it in `GetPublicIp` 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 sr = …;`), 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 2015/Case.ViewCreator/Case.ViewCreator/Classes/Entry/cmd.cs:40— `frm` is a `form_Main`, which implements `IDisposable`, and it is created here (line 40). Every use of it in `Execute` 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 frm = …;`), 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:83— `sr` is a `StreamReader`, which implements `IDisposable`, and it is created here (line 83). Every use of it in `GetPublicIp` 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 sr = …;`), 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:83— `sr` is a `StreamReader`, which implements `IDisposable`, and it is created here (line 83). Every use of it in `GetPublicIp` 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 sr = …;`), 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:83— `sr` is a `StreamReader`, which implements `IDisposable`, and it is created here (line 83). Every use of it in `GetPublicIp` 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 sr = …;`), 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 2015/Case.ParallelWalls/Case.ParallelWalls/Entry/CmdMain.cs:47— `m_splash` is a `form_SplashScreen`, which implements `IDisposable`, and it is created here (line 47). Every use of it in `Execute` 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 m_splash = …;`), 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:83— `sr` is a `StreamReader`, which implements `IDisposable`, and it is created here (line 83). Every use of it in `GetPublicIp` 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 sr = …;`), 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:83— `sr` is a `StreamReader`, which implements `IDisposable`, and it is created here (line 83). Every use of it in `GetPublicIp` 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 sr = …;`), 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:83— `sr` is a `StreamReader`, which implements `IDisposable`, and it is created here (line 83). Every use of it in `GetPublicIp` 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 sr = …;`), 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 2016/Case.ExportSharedParameters/Case.ExportSharedParameters/Classes/Entry/cmd.cs:114— `m_dlg` is a `form_Main`, which implements `IDisposable`, and it is created here (line 114). Every use of it in `Execute` 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 m_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 REDACTED:83— `sr` is a `StreamReader`, which implements `IDisposable`, and it is created here (line 83). Every use of it in `GetPublicIp` 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 sr = …;`), 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:83— `sr` is a `StreamReader`, which implements `IDisposable`, and it is created here (line 83). Every use of it in `GetPublicIp` 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 sr = …;`), 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 2016/Case.ViewCreator/Case.ViewCreator/Classes/Entry/cmd.cs:40— `frm` is a `form_Main`, which implements `IDisposable`, and it is created here (line 40). Every use of it in `Execute` 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 frm = …;`), 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:83— `sr` is a `StreamReader`, which implements `IDisposable`, and it is created here (line 83). Every use of it in `GetPublicIp` 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 sr = …;`), 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:83— `sr` is a `StreamReader`, which implements `IDisposable`, and it is created here (line 83). Every use of it in `GetPublicIp` 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 sr = …;`), 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:83— `sr` is a `StreamReader`, which implements `IDisposable`, and it is created here (line 83). Every use of it in `GetPublicIp` 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 sr = …;`), 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 2016/Case.ParallelWalls/Case.ParallelWalls/Entry/CmdMain.cs:47— `m_splash` is a `form_SplashScreen`, which implements `IDisposable`, and it is created here (line 47). Every use of it in `Execute` 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 m_splash = …;`), 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:83— `sr` is a `StreamReader`, which implements `IDisposable`, and it is created here (line 83). Every use of it in `GetPublicIp` 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 sr = …;`), 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:83— `sr` is a `StreamReader`, which implements `IDisposable`, and it is created here (line 83). Every use of it in `GetPublicIp` 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 sr = …;`), 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:83— `sr` is a `StreamReader`, which implements `IDisposable`, and it is created here (line 83). Every use of it in `GetPublicIp` 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 sr = …;`), 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 2017/Case.ExportSharedParameters/Case.ExportSharedParameters/Classes/Entry/cmd.cs:114— `m_dlg` is a `form_Main`, which implements `IDisposable`, and it is created here (line 114). Every use of it in `Execute` 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 m_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 REDACTED:83— `sr` is a `StreamReader`, which implements `IDisposable`, and it is created here (line 83). Every use of it in `GetPublicIp` 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 sr = …;`), which releases it at the end of the scope on every path including a throw.
ClassTooLong: AppMain Case.AppsRibbon.2017/Entry/AppMain.vb— ClassTooLong — 659 significant lines (blank, comment-only and punctuation-only lines excluded), 10 methods. The bar is 400 significant lines; this is 259 over it, 1.65× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: AppMain Case.AppsRibbon.2018/Entry/AppMain.vb— ClassTooLong — 659 significant lines (blank, comment-only and punctuation-only lines excluded), 10 methods. The bar is 400 significant lines; this is 259 over it, 1.65× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: AppMain Case.AppsRibbon/Entry/AppMain.vb— ClassTooLong — 659 significant lines (blank, comment-only and punctuation-only lines excluded), 10 methods. The bar is 400 significant lines; this is 259 over it, 1.65× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: form_Sync 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb— ClassTooLong — 552 significant lines (blank, comment-only and punctuation-only lines excluded), 18 methods. The bar is 400 significant lines; this is 152 over it, 1.38× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: form_Sync 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb— ClassTooLong — 552 significant lines (blank, comment-only and punctuation-only lines excluded), 18 methods. The bar is 400 significant lines; this is 152 over it, 1.38× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: form_Sync 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb— ClassTooLong — 552 significant lines (blank, comment-only and punctuation-only lines excluded), 18 methods. The bar is 400 significant lines; this is 152 over it, 1.38× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: form_Sync 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb— ClassTooLong — 552 significant lines (blank, comment-only and punctuation-only lines excluded), 18 methods. The bar is 400 significant lines; this is 152 over it, 1.38× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: clsReportingData 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb— ClassTooLong — 531 significant lines (blank, comment-only and punctuation-only lines excluded), 6 methods. The bar is 400 significant lines; this is 131 over it, 1.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: clsReportingData 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb— ClassTooLong — 531 significant lines (blank, comment-only and punctuation-only lines excluded), 6 methods. The bar is 400 significant lines; this is 131 over it, 1.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: clsReportingData 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb— ClassTooLong — 531 significant lines (blank, comment-only and punctuation-only lines excluded), 6 methods. The bar is 400 significant lines; this is 131 over it, 1.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: clsReportingData 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb— ClassTooLong — 531 significant lines (blank, comment-only and punctuation-only lines excluded), 6 methods. The bar is 400 significant lines; this is 131 over it, 1.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: RVTCurveUtils 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb— ClassTooLong — 527 significant lines (blank, comment-only and punctuation-only lines excluded), 10 methods. The bar is 400 significant lines; this is 127 over it, 1.32× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: RVTCurveUtils 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb— ClassTooLong — 527 significant lines (blank, comment-only and punctuation-only lines excluded), 10 methods. The bar is 400 significant lines; this is 127 over it, 1.32× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: RVTCurveUtils 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb— ClassTooLong — 527 significant lines (blank, comment-only and punctuation-only lines excluded), 10 methods. The bar is 400 significant lines; this is 127 over it, 1.32× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: RVTCurveUtils 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb— ClassTooLong — 527 significant lines (blank, comment-only and punctuation-only lines excluded), 10 methods. The bar is 400 significant lines; this is 127 over it, 1.32× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: clsExcel 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb— ClassTooLong — 514 significant lines (blank, comment-only and punctuation-only lines excluded), 13 methods. The bar is 400 significant lines; this is 114 over it, 1.29× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: clsExcel 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb— ClassTooLong — 514 significant lines (blank, comment-only and punctuation-only lines excluded), 13 methods. The bar is 400 significant lines; this is 114 over it, 1.29× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: clsExcel 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb— ClassTooLong — 514 significant lines (blank, comment-only and punctuation-only lines excluded), 13 methods. The bar is 400 significant lines; this is 114 over it, 1.29× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: clsExcel 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb— ClassTooLong — 514 significant lines (blank, comment-only and punctuation-only lines excluded), 13 methods. The bar is 400 significant lines; this is 114 over it, 1.29× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: clsRvtCategoryData 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb— ClassTooLong — 474 significant lines (blank, comment-only and punctuation-only lines excluded), 5 methods. The bar is 400 significant lines; this is 74 over it, 1.19× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: clsRvtCategoryData 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb— ClassTooLong — 474 significant lines (blank, comment-only and punctuation-only lines excluded), 5 methods. The bar is 400 significant lines; this is 74 over it, 1.19× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: clsRvtCategoryData 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb— ClassTooLong — 474 significant lines (blank, comment-only and punctuation-only lines excluded), 5 methods. The bar is 400 significant lines; this is 74 over it, 1.19× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: clsRvtCategoryData 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb— ClassTooLong — 474 significant lines (blank, comment-only and punctuation-only lines excluded), 5 methods. The bar is 400 significant lines; this is 74 over it, 1.19× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: form_Data 2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb— ClassTooLong — 460 significant lines (blank, comment-only and punctuation-only lines excluded), 20 methods. The bar is 400 significant lines; this is 60 over it, 1.15× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: form_Data 2016/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb— ClassTooLong — 460 significant lines (blank, comment-only and punctuation-only lines excluded), 20 methods. The bar is 400 significant lines; this is 60 over it, 1.15× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (10 lines × 4) REDACTED:555— REDACTED:555-564 | REDACTED:555-564 | REDACTED:555-564 | REDACTED:555-564 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 421 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:555` 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 (10 lines × 4) 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:452— 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:452-461 | 2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:452-461 | 2017/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:452-461 | 2018/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:452-461 — before extracting anything, compare `2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb` and `2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 323 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 × 4) 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:473— 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:473-482 | 2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:473-482 | 2017/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:473-482 | 2018/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:473-482 — before extracting anything, compare `2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb` and `2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 323 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 × 4) 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:536— 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:536-545 | 2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:536-545 | 2017/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:536-545 | 2018/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:536-545 — before extracting anything, compare `2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb` and `2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 323 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 × 4) 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:557— 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:557-566 | 2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:557-566 | 2017/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:557-566 | 2018/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:557-566 — before extracting anything, compare `2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb` and `2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 323 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 × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/Entry/E33AB788BB594985A6A437CEFC70F7C1.vb:25— 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/Entry/E33AB788BB594985A6A437CEFC70F7C1.vb:25-34 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/Entry/E33AB788BB594985A6A437CEFC70F7C1.vb:25-34 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/Entry/E33AB788BB594985A6A437CEFC70F7C1.vb:25-34 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/Entry/E33AB788BB594985A6A437CEFC70F7C1.vb:25-34 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/Entry/E33AB788BB594985A6A437CEFC70F7C1.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/Entry/E33AB788BB594985A6A437CEFC70F7C1.vb` 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.
Duplicated block (10 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/Entry/E33AB788BB594985A6A437CEFC70F7C2.vb:25— 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/Entry/E33AB788BB594985A6A437CEFC70F7C2.vb:25-34 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/Entry/E33AB788BB594985A6A437CEFC70F7C2.vb:25-34 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/Entry/E33AB788BB594985A6A437CEFC70F7C2.vb:25-34 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/Entry/E33AB788BB594985A6A437CEFC70F7C2.vb:25-34 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/Entry/E33AB788BB594985A6A437CEFC70F7C2.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/Entry/E33AB788BB594985A6A437CEFC70F7C2.vb` 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.
Duplicated block (10 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/Entry/E33AB788BB594985A6A437CEFC70F7C3.vb:25— 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/Entry/E33AB788BB594985A6A437CEFC70F7C3.vb:25-34 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/Entry/E33AB788BB594985A6A437CEFC70F7C3.vb:25-34 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/Entry/E33AB788BB594985A6A437CEFC70F7C3.vb:25-34 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/Entry/E33AB788BB594985A6A437CEFC70F7C3.vb:25-34 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/Entry/E33AB788BB594985A6A437CEFC70F7C3.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/Entry/E33AB788BB594985A6A437CEFC70F7C3.vb` 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.
Duplicated block (10 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/Entry/E33AB788BB594985A6A437CEFC70F7C4.vb:25— 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/Entry/E33AB788BB594985A6A437CEFC70F7C4.vb:25-34 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/Entry/E33AB788BB594985A6A437CEFC70F7C4.vb:25-34 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/Entry/E33AB788BB594985A6A437CEFC70F7C4.vb:25-34 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/Entry/E33AB788BB594985A6A437CEFC70F7C4.vb:25-34 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/Entry/E33AB788BB594985A6A437CEFC70F7C4.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/Entry/E33AB788BB594985A6A437CEFC70F7C4.vb` 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.
Duplicated block (10 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ParameterConfigurationManager.xaml.vb:30— 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ParameterConfigurationManager.xaml.vb:30-39 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ParameterConfigurationManager.xaml.vb:30-39 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ParameterConfigurationManager.xaml.vb:30-39 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ParameterConfigurationManager.xaml.vb:30-39 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ParameterConfigurationManager.xaml.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ParameterConfigurationManager.xaml.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 169 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 × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/Entry/E33AB788BB594985A6A437CEFC70F7C5.vb:25— 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/Entry/E33AB788BB594985A6A437CEFC70F7C5.vb:25-34 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/Entry/E33AB788BB594985A6A437CEFC70F7C5.vb:25-34 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/Entry/E33AB788BB594985A6A437CEFC70F7C5.vb:25-34 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/Entry/E33AB788BB594985A6A437CEFC70F7C5.vb:25-34 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/Entry/E33AB788BB594985A6A437CEFC70F7C5.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/Entry/E33AB788BB594985A6A437CEFC70F7C5.vb` 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.
Duplicated block (10 lines × 4) 2015/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Data/clsParameter.vb:93— 2015/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Data/clsParameter.vb:93-102 | 2016/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Data/clsParameter.vb:93-102 | 2017/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Data/clsParameter.vb:93-102 | 2018/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Data/clsParameter.vb:93-102 — before extracting anything, compare `2015/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Data/clsParameter.vb` and `2016/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Data/clsParameter.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 52 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 × 4) 2015/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Data/clsParameter.vb:121— 2015/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Data/clsParameter.vb:121-130 | 2016/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Data/clsParameter.vb:121-130 | 2017/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Data/clsParameter.vb:121-130 | 2018/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Data/clsParameter.vb:121-130 — before extracting anything, compare `2015/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Data/clsParameter.vb` and `2016/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Data/clsParameter.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 52 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 × 4) 2015/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsRoomTagInfo.vb:22— 2015/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsRoomTagInfo.vb:22-31 | 2016/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsRoomTagInfo.vb:22-31 | 2017/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsRoomTagInfo.vb:22-31 | 2018/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsRoomTagInfo.vb:22-31 — before extracting anything, compare `2015/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsRoomTagInfo.vb` and `2016/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsRoomTagInfo.vb` as WHOLE FILES: this scan already matched 5 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.
Duplicated block (10 lines × 4) 2015/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsRoomTagInfo.vb:43— 2015/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsRoomTagInfo.vb:43-52 | 2016/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsRoomTagInfo.vb:43-52 | 2017/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsRoomTagInfo.vb:43-52 | 2018/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsRoomTagInfo.vb:43-52 — before extracting anything, compare `2015/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsRoomTagInfo.vb` and `2016/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsRoomTagInfo.vb` as WHOLE FILES: this scan already matched 5 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.
Duplicated block (10 lines × 4) 2015/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsRoomTagInfo.vb:64— 2015/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsRoomTagInfo.vb:64-73 | 2016/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsRoomTagInfo.vb:64-73 | 2017/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsRoomTagInfo.vb:64-73 | 2018/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsRoomTagInfo.vb:64-73 — before extracting anything, compare `2015/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsRoomTagInfo.vb` and `2016/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsRoomTagInfo.vb` as WHOLE FILES: this scan already matched 5 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.
Duplicated block (10 lines × 4) 2015/Case.ViewTemplates/Case.ViewTemplates/UI/form_Main.vb:42— 2015/Case.ViewTemplates/Case.ViewTemplates/UI/form_Main.vb:42-51 | 2016/Case.ViewTemplates/Case.ViewTemplates/UI/form_Main.vb:42-51 | 2017/Case.ViewTemplates/Case.ViewTemplates/UI/form_Main.vb:42-51 | 2018/Case.ViewTemplates/Case.ViewTemplates/UI/form_Main.vb:42-51 — before extracting anything, compare `2015/Case.ViewTemplates/Case.ViewTemplates/UI/form_Main.vb` and `2016/Case.ViewTemplates/Case.ViewTemplates/UI/form_Main.vb` as WHOLE FILES: this scan already matched 4 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.
Duplicated block (10 lines × 4) 2015/Case.ObjectStyles/Case.ObjectStyles/Data/mnData.cs:85— 2015/Case.ObjectStyles/Case.ObjectStyles/Data/mnData.cs:85-94 | 2016/Case.ObjectStyles/Case.ObjectStyles/Data/mnData.cs:85-94 | 2017/Case.ObjectStyles/Case.ObjectStyles/Data/mnData.cs:85-94 | 2018/Case.ObjectStyles/Case.ObjectStyles/Data/mnData.cs:85-94 — before extracting anything, compare `2015/Case.ObjectStyles/Case.ObjectStyles/Data/mnData.cs` and `2016/Case.ObjectStyles/Case.ObjectStyles/Data/mnData.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. 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 × 4) 2015/Case.ObjectStyles/Case.ObjectStyles/Data/mnFamData.cs:58— 2015/Case.ObjectStyles/Case.ObjectStyles/Data/mnFamData.cs:58-67 | 2016/Case.ObjectStyles/Case.ObjectStyles/Data/mnFamData.cs:58-67 | 2017/Case.ObjectStyles/Case.ObjectStyles/Data/mnFamData.cs:58-67 | 2018/Case.ObjectStyles/Case.ObjectStyles/Data/mnFamData.cs:58-67 — before extracting anything, compare `2015/Case.ObjectStyles/Case.ObjectStyles/Data/mnFamData.cs` and `2016/Case.ObjectStyles/Case.ObjectStyles/Data/mnFamData.cs` as WHOLE FILES: this scan already matched 4 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. 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 × 4) 2015/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs:32— 2015/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs:32-41 | 2016/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs:32-41 | 2017/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs:32-41 | 2018/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs:32-41 — before extracting anything, compare `2015/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs` and `2016/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs` as WHOLE FILES: this scan already matched 6 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.
Duplicated block (10 lines × 4) 2015/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnFamData.cs:53— 2015/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnFamData.cs:53-62 | 2016/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnFamData.cs:53-62 | 2017/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnFamData.cs:53-62 | 2018/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnFamData.cs:53-62 — before extracting anything, compare `2015/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnFamData.cs` and `2016/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnFamData.cs` as WHOLE FILES: this scan already matched 4 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. 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 × 4) 2015/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnSettings.cs:28— 2015/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnSettings.cs:28-37 | 2016/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnSettings.cs:28-37 | 2017/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnSettings.cs:28-37 | 2018/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnSettings.cs:28-37 — before extracting anything, compare `2015/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnSettings.cs` and `2016/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnSettings.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. 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 × 4) 2015/Case.Subs.KeyMatcher/Utility/clsGlobals.cs:32— 2015/Case.Subs.KeyMatcher/Utility/clsGlobals.cs:32-41 | 2016/Case.Subs.KeyMatcher/Utility/clsGlobals.cs:32-41 | 2017/Case.Subs.KeyMatcher/Utility/clsGlobals.cs:32-41 | 2018/Case.Subs.KeyMatcher/Utility/clsGlobals.cs:32-41 — before extracting anything, compare `2015/Case.Subs.KeyMatcher/Utility/clsGlobals.cs` and `2016/Case.Subs.KeyMatcher/Utility/clsGlobals.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 115 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 × 4) 2015/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Events/clsDocs.vb:21— 2015/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Events/clsDocs.vb:21-30 | 2016/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Events/clsDocs.vb:21-30 | 2017/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Events/clsDocs.vb:21-30 | 2018/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Events/clsDocs.vb:21-30 — before extracting anything, compare `2015/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Events/clsDocs.vb` and `2016/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Events/clsDocs.vb` 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.
Low cohesion: form_DataManager (LCOM4 5) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:6— form_DataManager'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: clsAutomationTest (LCOM4 5) 2015/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/clsAutomationTest.vb:4— clsAutomationTest'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: form_DataManager (LCOM4 5) 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:6— form_DataManager'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: form_DataManager (LCOM4 5) 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:6— form_DataManager'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: form_DataManager (LCOM4 5) 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:6— form_DataManager'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: clsAutomationTest (LCOM4 5) 2016/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/clsAutomationTest.vb:4— clsAutomationTest'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: clsAutomationTest (LCOM4 5) 2017/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/clsAutomationTest.vb:4— clsAutomationTest'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: clsAutomationTest (LCOM4 5) 2018/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/clsAutomationTest.vb:4— clsAutomationTest'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: form_PlacePoint (LCOM4 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb:4— form_PlacePoint'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: form_PlacePointsFromFile (LCOM4 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb:5— form_PlacePointsFromFile'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: form_ExportPoints (LCOM4 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:4— form_ExportPoints'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: form_PlacePoint (LCOM4 4) 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb:4— form_PlacePoint'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: form_PlacePointsFromFile (LCOM4 4) 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb:5— form_PlacePointsFromFile'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: form_ExportPoints (LCOM4 4) 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:4— form_ExportPoints'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: form_PlacePoint (LCOM4 4) 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb:4— form_PlacePoint'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: form_PlacePointsFromFile (LCOM4 4) 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb:5— form_PlacePointsFromFile'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: form_ExportPoints (LCOM4 4) 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:4— form_ExportPoints'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: form_PlacePoint (LCOM4 4) 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb:4— form_PlacePoint'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: form_PlacePointsFromFile (LCOM4 4) 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb:5— form_PlacePointsFromFile'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: form_ExportPoints (LCOM4 4) 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:4— form_ExportPoints'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.
FileTooLong: Entry/AppMain.vb Case.AppsRibbon.2017/Entry/AppMain.vb— FileTooLong — 669 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 169 over it, 1.34× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Entry/AppMain.vb Case.AppsRibbon.2018/Entry/AppMain.vb— FileTooLong — 669 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 169 over it, 1.34× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Entry/AppMain.vb Case.AppsRibbon/Entry/AppMain.vb— FileTooLong — 669 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 169 over it, 1.34× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: UI/form_Sync.vb 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb— FileTooLong — 558 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 58 over it, 1.12× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: UI/form_Sync.vb 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb— FileTooLong — 558 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 58 over it, 1.12× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: UI/form_Sync.vb 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb— FileTooLong — 558 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 58 over it, 1.12× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: UI/form_Sync.vb 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb— FileTooLong — 558 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 58 over it, 1.12× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Classes/clsReportingData.vb 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb— FileTooLong — 533 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 33 over it, 1.07× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Classes/clsReportingData.vb 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb— FileTooLong — 533 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 33 over it, 1.07× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Classes/clsReportingData.vb 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb— FileTooLong — 533 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 33 over it, 1.07× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Classes/clsReportingData.vb 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb— FileTooLong — 533 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 33 over it, 1.07× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Translators/RVTCurveUtils.vb 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb— FileTooLong — 531 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 31 over it, 1.06× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Translators/RVTCurveUtils.vb 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb— FileTooLong — 531 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 31 over it, 1.06× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Translators/RVTCurveUtils.vb 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb— FileTooLong — 531 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 31 over it, 1.06× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Translators/RVTCurveUtils.vb 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb— FileTooLong — 531 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 31 over it, 1.06× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Data/clsExcel.vb 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb— FileTooLong — 522 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 22 over it, 1.04× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Data/clsExcel.vb 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb— FileTooLong — 522 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 22 over it, 1.04× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Data/clsExcel.vb 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb— FileTooLong — 522 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 22 over it, 1.04× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Data/clsExcel.vb 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb— FileTooLong — 522 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 22 over it, 1.04× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
Duplicated block (12 lines × 4) REDACTED:508— REDACTED:508-519 | REDACTED:508-519 | REDACTED:508-519 | REDACTED:508-519 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 421 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 (12 lines × 4) REDACTED:528— REDACTED:528-539 | REDACTED:528-539 | REDACTED:528-539 | REDACTED:528-539 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 421 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 (12 lines × 4) REDACTED:111— REDACTED:111-122 | REDACTED:111-122 | REDACTED:111-122 | REDACTED:111-122 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 147 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 (12 lines × 4) 2015/Case.ParallelWalls/Case.ParallelWalls/Data/clsVectors.cs:137— 2015/Case.ParallelWalls/Case.ParallelWalls/Data/clsVectors.cs:137-148 | 2016/Case.ParallelWalls/Case.ParallelWalls/Data/clsVectors.cs:137-148 | 2017/Case.ParallelWalls/Case.ParallelWalls/Data/clsVectors.cs:137-148 | 2018/Case.ParallelWalls/Case.ParallelWalls/Data/clsVectors.cs:132-143 — before extracting anything, compare `2015/Case.ParallelWalls/Case.ParallelWalls/Data/clsVectors.cs` and `2016/Case.ParallelWalls/Case.ParallelWalls/Data/clsVectors.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 55 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 (12 lines × 4) 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb:179— 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb:179-190 | 2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb:179-190 | 2017/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb:179-190 | 2018/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb:179-190 — before extracting anything, compare `2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb` and `2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 7 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. 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 (12 lines × 4) 2015/Case.Subs.SharedParameters/Case.Subs.SharedParameters/Data/clsSharedParameters.vb:258— 2015/Case.Subs.SharedParameters/Case.Subs.SharedParameters/Data/clsSharedParameters.vb:258-269 | 2016/Case.Subs.SharedParameters/Case.Subs.SharedParameters/Data/clsSharedParameters.vb:258-269 | 2017/Case.Subs.SharedParameters/Case.Subs.SharedParameters/Data/clsSharedParameters.vb:258-269 | 2018/Case.Subs.SharedParameters/Case.Subs.SharedParameters/Data/clsSharedParameters.vb:258-269 — before extracting anything, compare `2015/Case.Subs.SharedParameters/Case.Subs.SharedParameters/Data/clsSharedParameters.vb` and `2016/Case.Subs.SharedParameters/Case.Subs.SharedParameters/Data/clsSharedParameters.vb` 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. 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 (12 lines × 4) 2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:437— 2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:437-448 | 2016/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:437-448 | 2017/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:437-448 | 2018/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:437-448 — before extracting anything, compare `2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb` and `2016/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 323 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 (12 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsFamily.vb:15— 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsFamily.vb:15-26 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsFamily.vb:15-26 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsFamily.vb:15-26 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsFamily.vb:15-26 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsFamily.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsFamily.vb` 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 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.
Duplicated block (12 lines × 4) 2015/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:80— 2015/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:80-91 | 2016/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:80-91 | 2017/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:80-91 | 2018/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:80-91 — before extracting anything, compare `2015/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb` and `2016/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 173 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 (12 lines × 4) 2015/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/clsSettings.vb:99— 2015/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/clsSettings.vb:99-110 | 2016/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/clsSettings.vb:99-110 | 2017/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/clsSettings.vb:99-110 | 2018/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/clsSettings.vb:99-110 — before extracting anything, compare `2015/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/clsSettings.vb` and `2016/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/clsSettings.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 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 (12 lines × 4) 2015/Case.ExportSharedParameters/Case.ExportSharedParameters/UI/form_Main.cs:23— 2015/Case.ExportSharedParameters/Case.ExportSharedParameters/UI/form_Main.cs:23-34 | 2016/Case.ExportSharedParameters/Case.ExportSharedParameters/UI/form_Main.cs:23-34 | 2017/Case.ExportSharedParameters/Case.ExportSharedParameters/UI/form_Main.cs:23-34 | 2018/Case.ExportSharedParameters/Case.ExportSharedParameters/UI/form_Main.cs:23-34 — before extracting anything, compare `2015/Case.ExportSharedParameters/Case.ExportSharedParameters/UI/form_Main.cs` and `2016/Case.ExportSharedParameters/Case.ExportSharedParameters/UI/form_Main.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.
Duplicated block (12 lines × 4) 2015/Case.Navis2BCF/Case.Navis2BCF/Converters.cs:33— 2015/Case.Navis2BCF/Case.Navis2BCF/Converters.cs:33-44 | 2016/Case.Navis2BCF/Case.Navis2BCF/Converters.cs:33-44 | 2017/Case.Navis2BCF/Case.Navis2BCF/Converters.cs:33-44 | 2018/Case.Navis2BCF/Case.Navis2BCF/Converters.cs:33-44 — before extracting anything, compare `2015/Case.Navis2BCF/Case.Navis2BCF/Converters.cs` and `2016/Case.Navis2BCF/Case.Navis2BCF/Converters.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.
Duplicated block (12 lines × 4) 2015/Case.Subs.KeyMatcher/ViewModels/clsViewModelBase.cs:35— 2015/Case.Subs.KeyMatcher/ViewModels/clsViewModelBase.cs:35-46 | 2016/Case.Subs.KeyMatcher/ViewModels/clsViewModelBase.cs:35-46 | 2017/Case.Subs.KeyMatcher/ViewModels/clsViewModelBase.cs:35-46 | 2018/Case.Subs.KeyMatcher/ViewModels/clsViewModelBase.cs:35-46 — before extracting anything, compare `2015/Case.Subs.KeyMatcher/ViewModels/clsViewModelBase.cs` and `2016/Case.Subs.KeyMatcher/ViewModels/clsViewModelBase.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.
Duplicated block (12 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:488— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:488-499 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:488-499 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:488-499 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:488-499 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 422 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 (12 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:671— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:671-682 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:671-682 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:671-682 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:671-682 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 422 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 (12 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:230— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:230-241 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:230-241 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:230-241 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:230-241 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb` as WHOLE FILES: this scan already matched 10 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. 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 (12 lines × 4) 2015/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Forms/form_Main.vb:178— 2015/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Forms/form_Main.vb:178-189 | 2016/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Forms/form_Main.vb:178-189 | 2017/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Forms/form_Main.vb:178-189 | 2018/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Forms/form_Main.vb:178-189 — before extracting anything, compare `2015/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Forms/form_Main.vb` and `2016/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Forms/form_Main.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 137 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 (12 lines × 4) 2015/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb:231— 2015/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb:231-242 | 2016/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb:231-242 | 2017/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb:231-242 | 2018/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb:231-242 — before extracting anything, compare `2015/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb` and `2016/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 150 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 (12 lines × 4) 2015/Case.Subs.KeyMatcher/Utility/clsGlobals.cs:224— 2015/Case.Subs.KeyMatcher/Utility/clsGlobals.cs:224-235 | 2016/Case.Subs.KeyMatcher/Utility/clsGlobals.cs:224-235 | 2017/Case.Subs.KeyMatcher/Utility/clsGlobals.cs:224-235 | 2018/Case.Subs.KeyMatcher/Utility/clsGlobals.cs:224-235 — before extracting anything, compare `2015/Case.Subs.KeyMatcher/Utility/clsGlobals.cs` and `2016/Case.Subs.KeyMatcher/Utility/clsGlobals.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 115 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 (23 lines × 4) REDACTED:194— REDACTED:194-216 | REDACTED:194-216 | REDACTED:194-216 | REDACTED:194-216 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 421 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 (23 lines × 4) REDACTED:207— REDACTED:207-229 | REDACTED:207-229 | REDACTED:207-229 | REDACTED:207-229 — before extracting anything, compare `REDACTED` and `REDACTED` 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 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 (23 lines × 4) REDACTED:36— REDACTED:36-58 | REDACTED:36-58 | REDACTED:36-58 | REDACTED:36-58 — before extracting anything, compare `REDACTED` and `REDACTED` 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 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 (23 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsIoConfig.vb:146— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsIoConfig.vb:146-168 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsIoConfig.vb:146-168 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsIoConfig.vb:146-168 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsIoConfig.vb:146-168 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsIoConfig.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsIoConfig.vb` 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 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.
Duplicated block (23 lines × 4) 2015/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb:332— 2015/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb:332-354 | 2016/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb:332-354 | 2017/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb:332-354 | 2018/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb:332-354 — before extracting anything, compare `2015/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb` and `2016/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 215 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 (23 lines × 4) 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb:538— 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb:538-560 | 2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb:538-560 | 2017/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb:538-560 | 2018/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb:538-560 — before extracting anything, compare `2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb` and `2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 7 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. 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 (23 lines × 4) 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:423— 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:423-445 | 2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:423-445 | 2017/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:423-445 | 2018/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:423-445 — before extracting anything, compare `2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb` and `2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 500 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 (23 lines × 4) 2015/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:36— 2015/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:36-58 | 2016/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:36-58 | 2017/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:36-58 | 2018/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:36-58 — before extracting anything, compare `2015/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb` and `2016/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 201 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 (23 lines × 4) 2015/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:41— 2015/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:41-63 | 2016/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:41-63 | 2017/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:41-63 | 2018/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:41-63 — before extracting anything, compare `2015/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb` and `2016/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 264 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 (23 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:359— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:359-381 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:359-381 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:359-381 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:359-381 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 330 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 (23 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:443— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:443-465 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:443-465 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:443-465 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:443-465 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 330 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 (23 lines × 4) 2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:140— 2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:140-162 | 2016/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:140-162 | 2017/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:140-162 | 2018/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:140-162 — before extracting anything, compare `2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb` and `2016/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 373 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 (23 lines × 4) 2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:70— 2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:70-92 | 2016/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:70-92 | 2017/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:70-92 | 2018/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:70-92 — before extracting anything, compare `2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb` and `2016/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 323 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 (23 lines × 4) 2015/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb:98— 2015/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb:98-120 | 2016/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb:98-120 | 2017/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb:98-120 | 2018/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb:98-120 — before extracting anything, compare `2015/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb` and `2016/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 260 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 (23 lines × 4) 2015/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb:471— 2015/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb:471-493 | 2016/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb:471-493 | 2017/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb:471-493 | 2018/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb:471-493 — before extracting anything, compare `2015/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb` and `2016/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 191 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 (23 lines × 4) 2015/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Entry/app.vb:39— 2015/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Entry/app.vb:39-61 | 2016/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Entry/app.vb:39-61 | 2017/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Entry/app.vb:39-61 | 2018/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Entry/app.vb:39-61 — before extracting anything, compare `2015/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Entry/app.vb` and `2016/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Entry/app.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 93 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 (23 lines × 4) 2015/Case.ParallelWalls/Case.ParallelWalls/Data/clsReferenceFilter.cs:31— 2015/Case.ParallelWalls/Case.ParallelWalls/Data/clsReferenceFilter.cs:31-53 | 2016/Case.ParallelWalls/Case.ParallelWalls/Data/clsReferenceFilter.cs:31-53 | 2017/Case.ParallelWalls/Case.ParallelWalls/Data/clsReferenceFilter.cs:31-53 | 2018/Case.ParallelWalls/Case.ParallelWalls/Data/clsReferenceFilter.cs:26-48 — before extracting anything, compare `2015/Case.ParallelWalls/Case.ParallelWalls/Data/clsReferenceFilter.cs` and `2016/Case.ParallelWalls/Case.ParallelWalls/Data/clsReferenceFilter.cs` as WHOLE FILES: 97% 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 (23 lines × 4) 2015/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb:147— 2015/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb:147-169 | 2016/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb:147-169 | 2017/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb:147-169 | 2018/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb:147-169 — before extracting anything, compare `2015/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb` and `2016/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 260 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 (19 lines × 4) REDACTED:301— REDACTED:301-319 | REDACTED:301-319 | REDACTED:301-319 | REDACTED:301-319 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 421 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: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 (19 lines × 4) REDACTED:346— REDACTED:346-364 | REDACTED:346-364 | REDACTED:346-364 | REDACTED:346-364 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 421 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 (19 lines × 4) 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSettings.vb:152— 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSettings.vb:152-170 | 2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSettings.vb:152-170 | 2017/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSettings.vb:152-170 | 2018/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSettings.vb:152-170 — before extracting anything, compare `2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSettings.vb` and `2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 97 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 (19 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:509— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:509-527 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:509-527 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:509-527 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:509-527 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 422 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 (19 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:537— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:537-555 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:537-555 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:537-555 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:537-555 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 422 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 (19 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_ExportSchedule.vb:197— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_ExportSchedule.vb:197-215 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_ExportSchedule.vb:197-215 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_ExportSchedule.vb:197-215 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_ExportSchedule.vb:197-215 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_ExportSchedule.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_ExportSchedule.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 81 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 (19 lines × 4) 2015/Case.Subs.Linestyles/Case.Subs.Linestyles/UI/form_Main.vb:14— 2015/Case.Subs.Linestyles/Case.Subs.Linestyles/UI/form_Main.vb:14-32 | 2016/Case.Subs.Linestyles/Case.Subs.Linestyles/UI/form_Main.vb:14-32 | 2017/Case.Subs.Linestyles/Case.Subs.Linestyles/UI/form_Main.vb:14-32 | 2018/Case.Subs.Linestyles/Case.Subs.Linestyles/UI/form_Main.vb:14-32 — before extracting anything, compare `2015/Case.Subs.Linestyles/Case.Subs.Linestyles/UI/form_Main.vb` and `2016/Case.Subs.Linestyles/Case.Subs.Linestyles/UI/form_Main.vb` 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 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.
Duplicated block (19 lines × 4) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/clsFormUtil.vb:33— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/clsFormUtil.vb:33-51 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/clsFormUtil.vb:33-51 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/clsFormUtil.vb:33-51 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/clsFormUtil.vb:33-51 — before extracting anything, compare `2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/clsFormUtil.vb` and `2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/clsFormUtil.vb` 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 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.
Duplicated block (19 lines × 4) 2015/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb:267— 2015/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb:267-285 | 2016/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb:267-285 | 2017/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb:267-285 | 2018/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb:267-285 — before extracting anything, compare `2015/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb` and `2016/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 215 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 (19 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsSettings.vb:205— 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsSettings.vb:205-223 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsSettings.vb:205-223 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsSettings.vb:205-223 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsSettings.vb:205-223 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsSettings.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsSettings.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 175 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 (19 lines × 4) 2015/Case.Directionality/Case.Directionality/Data/clsParamItem.vb:25— 2015/Case.Directionality/Case.Directionality/Data/clsParamItem.vb:25-43 | 2016/Case.Directionality/Case.Directionality/Data/clsParamItem.vb:25-43 | 2017/Case.Directionality/Case.Directionality/Data/clsParamItem.vb:25-43 | 2018/Case.Directionality/Case.Directionality/Data/clsParamItem.vb:25-43 — before extracting anything, compare `2015/Case.Directionality/Case.Directionality/Data/clsParamItem.vb` and `2016/Case.Directionality/Case.Directionality/Data/clsParamItem.vb` 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.
Duplicated block (19 lines × 4) 2015/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb:181— 2015/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb:181-199 | 2016/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb:181-199 | 2017/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb:181-199 | 2018/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb:181-199 — before extracting anything, compare `2015/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb` and `2016/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 150 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 (19 lines × 4) 2015/Case.RoomSync/Case.RoomSync/UI/form_Sync.vb:45— 2015/Case.RoomSync/Case.RoomSync/UI/form_Sync.vb:45-63 | 2016/Case.RoomSync/Case.RoomSync/UI/form_Sync.vb:45-63 | 2017/Case.RoomSync/Case.RoomSync/UI/form_Sync.vb:45-63 | 2018/Case.RoomSync/Case.RoomSync/UI/form_Sync.vb:45-63 — before extracting anything, compare `2015/Case.RoomSync/Case.RoomSync/UI/form_Sync.vb` and `2016/Case.RoomSync/Case.RoomSync/UI/form_Sync.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 242 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 (19 lines × 4) 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSettings.vb:181— 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSettings.vb:181-199 | 2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSettings.vb:181-199 | 2017/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSettings.vb:181-199 | 2018/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSettings.vb:181-199 — before extracting anything, compare `2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSettings.vb` and `2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 97 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 (19 lines × 4) 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:456— 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:456-474 | 2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:456-474 | 2017/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:456-474 | 2018/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:456-474 — before extracting anything, compare `2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb` and `2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 500 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 (19 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_AddFamily.vb:84— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_AddFamily.vb:84-102 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_AddFamily.vb:84-102 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_AddFamily.vb:84-102 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_AddFamily.vb:84-102 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_AddFamily.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_AddFamily.vb` 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 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.
Duplicated block (19 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:385— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:385-403 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:385-403 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:385-403 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:385-403 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 330 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 (19 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb:111— 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb:111-129 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb:111-129 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb:111-129 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb:111-129 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 221 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 (16 lines × 4) 2015/Case.ReportGroupsByView/Case.ReportGroupsByView/Data/clsSettings.cs:25— 2015/Case.ReportGroupsByView/Case.ReportGroupsByView/Data/clsSettings.cs:25-40 | 2016/Case.ReportGroupsByView/Case.ReportGroupsByView/Data/clsSettings.cs:25-40 | 2017/Case.ReportGroupsByView/Case.ReportGroupsByView/Data/clsSettings.cs:25-40 | 2018/Case.ReportGroupsByView/Case.ReportGroupsByView/Data/clsSettings.cs:25-40 — before extracting anything, compare `2015/Case.ReportGroupsByView/Case.ReportGroupsByView/Data/clsSettings.cs` and `2016/Case.ReportGroupsByView/Case.ReportGroupsByView/Data/clsSettings.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 123 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 (16 lines × 4) 2015/Case.Subs.KeyMatcher/Utility/clsGlobals.cs:171— 2015/Case.Subs.KeyMatcher/Utility/clsGlobals.cs:171-186 | 2016/Case.Subs.KeyMatcher/Utility/clsGlobals.cs:171-186 | 2017/Case.Subs.KeyMatcher/Utility/clsGlobals.cs:171-186 | 2018/Case.Subs.KeyMatcher/Utility/clsGlobals.cs:171-186 — before extracting anything, compare `2015/Case.Subs.KeyMatcher/Utility/clsGlobals.cs` and `2016/Case.Subs.KeyMatcher/Utility/clsGlobals.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 115 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 (16 lines × 4) 2015/Case.Subs.KeyMatcher/Utility/clsGlobals.cs:196— 2015/Case.Subs.KeyMatcher/Utility/clsGlobals.cs:196-211 | 2016/Case.Subs.KeyMatcher/Utility/clsGlobals.cs:196-211 | 2017/Case.Subs.KeyMatcher/Utility/clsGlobals.cs:196-211 | 2018/Case.Subs.KeyMatcher/Utility/clsGlobals.cs:196-211 — before extracting anything, compare `2015/Case.Subs.KeyMatcher/Utility/clsGlobals.cs` and `2016/Case.Subs.KeyMatcher/Utility/clsGlobals.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 115 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 (16 lines × 4) 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:32— 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:32-47 | 2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:32-47 | 2017/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:32-47 | 2018/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:32-47 — before extracting anything, compare `2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb` and `2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 323 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 (16 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:566— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:566-581 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:566-581 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:566-581 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:566-581 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 422 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 (16 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSortableBindingList.vb:60— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSortableBindingList.vb:60-75 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSortableBindingList.vb:60-75 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSortableBindingList.vb:60-75 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSortableBindingList.vb:60-75 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSortableBindingList.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSortableBindingList.vb` 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 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.
Duplicated block (16 lines × 4) 2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/SplitContainerEx.vb:40— 2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/SplitContainerEx.vb:40-55 | 2016/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/SplitContainerEx.vb:40-55 | 2017/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/SplitContainerEx.vb:40-55 | 2018/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/SplitContainerEx.vb:40-55 — before extracting anything, compare `2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/SplitContainerEx.vb` and `2016/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/SplitContainerEx.vb` 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.
Duplicated block (16 lines × 4) 2015/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsRvtElemInst.vb:136— 2015/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsRvtElemInst.vb:136-151 | 2016/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsRvtElemInst.vb:136-151 | 2017/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsRvtElemInst.vb:136-151 | 2018/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsRvtElemInst.vb:136-151 — before extracting anything, compare `2015/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsRvtElemInst.vb` and `2016/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsRvtElemInst.vb` 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. 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 (16 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:340— 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:340-355 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:340-355 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:340-355 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:339-354 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 317 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 (16 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb:379— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb:379-394 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb:379-394 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb:379-394 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb:379-394 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 291 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 (16 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_ExportSchedule.vb:34— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_ExportSchedule.vb:34-49 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_ExportSchedule.vb:34-49 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_ExportSchedule.vb:34-49 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_ExportSchedule.vb:34-49 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_ExportSchedule.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_ExportSchedule.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 81 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 (16 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:382— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:382-397 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:382-397 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:382-397 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:382-397 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb` as WHOLE FILES: this scan already matched 10 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. 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 (16 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsViews.vb:129— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsViews.vb:129-144 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsViews.vb:129-144 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsViews.vb:129-144 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsViews.vb:129-144 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsViews.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsViews.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 68 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 (16 lines × 4) 2015/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Data/clsSettings.vb:240— 2015/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Data/clsSettings.vb:240-255 | 2016/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Data/clsSettings.vb:240-255 | 2017/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Data/clsSettings.vb:240-255 | 2018/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Data/clsSettings.vb:240-255 — before extracting anything, compare `2015/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Data/clsSettings.vb` and `2016/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 131 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 (16 lines × 4) 2015/Case.RoomSync/Case.RoomSync/Data/modGeneral.vb:51— 2015/Case.RoomSync/Case.RoomSync/Data/modGeneral.vb:51-66 | 2016/Case.RoomSync/Case.RoomSync/Data/modGeneral.vb:51-66 | 2017/Case.RoomSync/Case.RoomSync/Data/modGeneral.vb:51-66 | 2018/Case.RoomSync/Case.RoomSync/Data/modGeneral.vb:51-66 — before extracting anything, compare `2015/Case.RoomSync/Case.RoomSync/Data/modGeneral.vb` and `2016/Case.RoomSync/Case.RoomSync/Data/modGeneral.vb` as WHOLE FILES: this scan already matched 5 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.
Duplicated block (16 lines × 4) 2015/Case.RoomSync/Case.RoomSync/Data/modGeneral.vb:80— 2015/Case.RoomSync/Case.RoomSync/Data/modGeneral.vb:80-95 | 2016/Case.RoomSync/Case.RoomSync/Data/modGeneral.vb:80-95 | 2017/Case.RoomSync/Case.RoomSync/Data/modGeneral.vb:80-95 | 2018/Case.RoomSync/Case.RoomSync/Data/modGeneral.vb:80-95 — before extracting anything, compare `2015/Case.RoomSync/Case.RoomSync/Data/modGeneral.vb` and `2016/Case.RoomSync/Case.RoomSync/Data/modGeneral.vb` as WHOLE FILES: this scan already matched 5 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.
Duplicated block (16 lines × 4) 2015/Case.RoomSync/Case.RoomSync/Data/modGeneral.vb:109— 2015/Case.RoomSync/Case.RoomSync/Data/modGeneral.vb:109-124 | 2016/Case.RoomSync/Case.RoomSync/Data/modGeneral.vb:109-124 | 2017/Case.RoomSync/Case.RoomSync/Data/modGeneral.vb:109-124 | 2018/Case.RoomSync/Case.RoomSync/Data/modGeneral.vb:109-124 — before extracting anything, compare `2015/Case.RoomSync/Case.RoomSync/Data/modGeneral.vb` and `2016/Case.RoomSync/Case.RoomSync/Data/modGeneral.vb` as WHOLE FILES: this scan already matched 5 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.
Duplicated block (16 lines × 4) 2015/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/clsSettings.vb:35— 2015/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/clsSettings.vb:35-50 | 2016/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/clsSettings.vb:35-50 | 2017/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/clsSettings.vb:35-50 | 2018/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/clsSettings.vb:35-50 — before extracting anything, compare `2015/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/clsSettings.vb` and `2016/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/clsSettings.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 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 (9 lines × 4) 2015/Case.Navis2BCF/Case.Navis2BCF/IfcGuid.cs:135— 2015/Case.Navis2BCF/Case.Navis2BCF/IfcGuid.cs:135-143 | 2016/Case.Navis2BCF/Case.Navis2BCF/IfcGuid.cs:135-143 | 2017/Case.Navis2BCF/Case.Navis2BCF/IfcGuid.cs:135-143 | 2018/Case.Navis2BCF/Case.Navis2BCF/IfcGuid.cs:135-143 — before extracting anything, compare `2015/Case.Navis2BCF/Case.Navis2BCF/IfcGuid.cs` and `2016/Case.Navis2BCF/Case.Navis2BCF/IfcGuid.cs` as WHOLE FILES: this scan already matched 5 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. 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 (9 lines × 4) 2015/Case.ChangeReplaceFamTypeNames/Case.ChangeReplaceFamTypeNames/UI/form_Main.vb:33— 2015/Case.ChangeReplaceFamTypeNames/Case.ChangeReplaceFamTypeNames/UI/form_Main.vb:33-41 | 2016/Case.ChangeReplaceFamTypeNames/Case.ChangeReplaceFamTypeNames/UI/form_Main.vb:33-41 | 2017/Case.ChangeReplaceFamTypeNames/Case.ChangeReplaceFamTypeNames/UI/form_Main.vb:33-41 | 2018/Case.ChangeReplaceFamTypeNames/Case.ChangeReplaceFamTypeNames/UI/form_Main.vb:33-41 — before extracting anything, compare `2015/Case.ChangeReplaceFamTypeNames/Case.ChangeReplaceFamTypeNames/UI/form_Main.vb` and `2016/Case.ChangeReplaceFamTypeNames/Case.ChangeReplaceFamTypeNames/UI/form_Main.vb` 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 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.
Duplicated block (9 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:53— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:53-61 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:53-61 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:53-61 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:53-61 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb` as WHOLE FILES: this scan already matched 10 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. 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 (9 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:83— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:83-91 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:83-91 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:83-91 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:83-91 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb` as WHOLE FILES: this scan already matched 10 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. 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 (9 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSortableBindingList.vb:87— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSortableBindingList.vb:87-95 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSortableBindingList.vb:87-95 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSortableBindingList.vb:87-95 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSortableBindingList.vb:87-95 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSortableBindingList.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSortableBindingList.vb` 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 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.
Duplicated block (9 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:702— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:702-710 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:702-710 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:702-710 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:702-710 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 467 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 (9 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:714— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:714-722 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:714-722 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:714-722 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:714-722 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 467 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 (9 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:726— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:726-734 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:726-734 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:726-734 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:726-734 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 467 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 (9 lines × 4) 2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:55— 2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:55-63 | 2016/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:55-63 | 2017/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:55-63 | 2018/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:55-63 — before extracting anything, compare `2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb` and `2016/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 323 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 (9 lines × 4) 2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:415— 2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:415-423 | 2016/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:415-423 | 2017/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:415-423 | 2018/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:415-423 — before extracting anything, compare `2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb` and `2016/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 323 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 (9 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsConfiguration.vb:164— 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsConfiguration.vb:164-172 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsConfiguration.vb:164-172 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsConfiguration.vb:164-172 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsConfiguration.vb:164-172 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsConfiguration.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsConfiguration.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 115 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 (9 lines × 4) 2015/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb:426— 2015/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb:426-434 | 2016/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb:426-434 | 2017/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb:427-435 | 2018/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb:427-435 — before extracting anything, compare `2015/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb` and `2016/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 260 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 (9 lines × 4) 2015/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb:164— 2015/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb:164-172 | 2016/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb:164-172 | 2017/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb:164-172 | 2018/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb:164-172 — before extracting anything, compare `2015/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb` and `2016/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 150 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 (9 lines × 4) 2015/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb:390— 2015/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb:390-398 | 2016/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb:390-398 | 2017/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb:390-398 | 2018/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb:390-398 — before extracting anything, compare `2015/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb` and `2016/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 191 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 (9 lines × 4) 2015/Case.ViewportReporting/Case.ViewportReporting/Data/clsSettings.vb:63— 2015/Case.ViewportReporting/Case.ViewportReporting/Data/clsSettings.vb:63-71 | 2016/Case.ViewportReporting/Case.ViewportReporting/Data/clsSettings.vb:63-71 | 2017/Case.ViewportReporting/Case.ViewportReporting/Data/clsSettings.vb:63-71 | 2018/Case.ViewportReporting/Case.ViewportReporting/Data/clsSettings.vb:63-71 — before extracting anything, compare `2015/Case.ViewportReporting/Case.ViewportReporting/Data/clsSettings.vb` and `2016/Case.ViewportReporting/Case.ViewportReporting/Data/clsSettings.vb` 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 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.
Duplicated block (9 lines × 4) 2015/Case.ViewCreator/Case.ViewCreator/Classes/clsParameterData.cs:16— 2015/Case.ViewCreator/Case.ViewCreator/Classes/clsParameterData.cs:16-24 | 2016/Case.ViewCreator/Case.ViewCreator/Classes/clsParameterData.cs:16-24 | 2017/Case.ViewCreator/Case.ViewCreator/Classes/clsParameterData.cs:16-24 | 2018/Case.ViewCreator/Case.ViewCreator/Classes/clsParameterData.cs:16-24 — before extracting anything, compare `2015/Case.ViewCreator/Case.ViewCreator/Classes/clsParameterData.cs` and `2016/Case.ViewCreator/Case.ViewCreator/Classes/clsParameterData.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. 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 × 4) REDACTED:27— REDACTED:27-35 | REDACTED:27-35 | REDACTED:27-35 | REDACTED:22-30 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 123 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 × 4) 2015/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Entry/app.vb:124— 2015/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Entry/app.vb:124-132 | 2016/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Entry/app.vb:124-132 | 2017/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Entry/app.vb:124-132 | 2018/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Entry/app.vb:124-132 — before extracting anything, compare `2015/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Entry/app.vb` and `2016/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Entry/app.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 93 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 (20 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:388— 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:388-407 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:388-407 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:388-407 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:388-407 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 267 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 (20 lines × 4) 2015/Case.ReportGroupsByView/Case.ReportGroupsByView/UI/form_Main.cs:115— 2015/Case.ReportGroupsByView/Case.ReportGroupsByView/UI/form_Main.cs:115-134 | 2016/Case.ReportGroupsByView/Case.ReportGroupsByView/UI/form_Main.cs:115-134 | 2017/Case.ReportGroupsByView/Case.ReportGroupsByView/UI/form_Main.cs:115-134 | 2018/Case.ReportGroupsByView/Case.ReportGroupsByView/UI/form_Main.cs:115-134 — before extracting anything, compare `2015/Case.ReportGroupsByView/Case.ReportGroupsByView/UI/form_Main.cs` and `2016/Case.ReportGroupsByView/Case.ReportGroupsByView/UI/form_Main.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 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 (20 lines × 4) 2015/Case.Navis2BCF/Case.Navis2BCF/IfcGuid.cs:68— 2015/Case.Navis2BCF/Case.Navis2BCF/IfcGuid.cs:68-87 | 2016/Case.Navis2BCF/Case.Navis2BCF/IfcGuid.cs:68-87 | 2017/Case.Navis2BCF/Case.Navis2BCF/IfcGuid.cs:68-87 | 2018/Case.Navis2BCF/Case.Navis2BCF/IfcGuid.cs:68-87 — before extracting anything, compare `2015/Case.Navis2BCF/Case.Navis2BCF/IfcGuid.cs` and `2016/Case.Navis2BCF/Case.Navis2BCF/IfcGuid.cs` as WHOLE FILES: this scan already matched 5 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. 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 (20 lines × 4) 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:613— 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:613-632 | 2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:613-632 | 2017/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:613-632 | 2018/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:613-632 — before extracting anything, compare `2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb` and `2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 323 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 (20 lines × 4) 2015/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb:93— 2015/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb:93-112 | 2016/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb:93-112 | 2017/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb:93-112 | 2018/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb:93-112 — before extracting anything, compare `2015/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb` and `2016/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 215 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 (20 lines × 4) 2015/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:238— 2015/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:238-257 | 2016/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:238-257 | 2017/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:238-257 | 2018/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:238-257 — before extracting anything, compare `2015/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb` and `2016/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 264 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 (20 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:408— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:408-427 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:408-427 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:408-427 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:408-427 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb` as WHOLE FILES: this scan already matched 10 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. 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 (20 lines × 4) 2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:100— 2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:100-119 | 2016/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:100-119 | 2017/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:100-119 | 2018/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:100-119 — before extracting anything, compare `2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb` and `2016/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 323 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 (20 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ParameterConfigurationManager.xaml.vb:219— 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ParameterConfigurationManager.xaml.vb:219-238 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ParameterConfigurationManager.xaml.vb:219-238 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ParameterConfigurationManager.xaml.vb:219-238 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ParameterConfigurationManager.xaml.vb:219-238 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ParameterConfigurationManager.xaml.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ParameterConfigurationManager.xaml.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 169 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 (20 lines × 4) 2015/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Form/form_Main.vb:374— 2015/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Form/form_Main.vb:374-393 | 2016/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Form/form_Main.vb:374-393 | 2017/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Form/form_Main.vb:374-393 | 2018/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Form/form_Main.vb:374-393 — before extracting anything, compare `2015/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Form/form_Main.vb` and `2016/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Form/form_Main.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 215 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 (20 lines × 4) 2015/Case.Export.Families/Case.Export.Families/Forms/form_Familes.vb:234— 2015/Case.Export.Families/Case.Export.Families/Forms/form_Familes.vb:234-253 | 2016/Case.Export.Families/Case.Export.Families/Forms/form_Familes.vb:234-253 | 2017/Case.Export.Families/Case.Export.Families/Forms/form_Familes.vb:234-253 | 2018/Case.Export.Families/Case.Export.Families/Forms/form_Familes.vb:234-253 — before extracting anything, compare `2015/Case.Export.Families/Case.Export.Families/Forms/form_Familes.vb` and `2016/Case.Export.Families/Case.Export.Families/Forms/form_Familes.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 93 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 (20 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:956— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:956-975 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:956-975 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:956-975 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:956-975 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 281 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 (20 lines × 4) 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb:571— 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb:571-590 | 2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb:571-590 | 2017/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb:571-590 | 2018/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb:571-590 — before extracting anything, compare `2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb` and `2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 7 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. 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 (20 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:230— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:230-249 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:230-249 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:230-249 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:230-249 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 330 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 (20 lines × 4) 2015/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsDoors.vb:216— 2015/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsDoors.vb:216-235 | 2016/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsDoors.vb:216-235 | 2017/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsDoors.vb:216-235 | 2018/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsDoors.vb:216-235 — before extracting anything, compare `2015/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsDoors.vb` and `2016/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsDoors.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 70 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 (20 lines × 4) 2015/Case.ViewCreator/Case.ViewCreator/Classes/Entry/app.cs:90— 2015/Case.ViewCreator/Case.ViewCreator/Classes/Entry/app.cs:90-109 | 2016/Case.ViewCreator/Case.ViewCreator/Classes/Entry/app.cs:90-109 | 2017/Case.ViewCreator/Case.ViewCreator/Classes/Entry/app.cs:90-109 | 2018/Case.ViewCreator/Case.ViewCreator/Classes/Entry/app.cs:90-109 — before extracting anything, compare `2015/Case.ViewCreator/Case.ViewCreator/Classes/Entry/app.cs` and `2016/Case.ViewCreator/Case.ViewCreator/Classes/Entry/app.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 98 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 (20 lines × 4) 2015/Case.RoomSync/Case.RoomSync/UI/form_Sync.vb:296— 2015/Case.RoomSync/Case.RoomSync/UI/form_Sync.vb:296-315 | 2016/Case.RoomSync/Case.RoomSync/UI/form_Sync.vb:296-315 | 2017/Case.RoomSync/Case.RoomSync/UI/form_Sync.vb:296-315 | 2018/Case.RoomSync/Case.RoomSync/UI/form_Sync.vb:296-315 — before extracting anything, compare `2015/Case.RoomSync/Case.RoomSync/UI/form_Sync.vb` and `2016/Case.RoomSync/Case.RoomSync/UI/form_Sync.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 242 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 (17 lines × 4) REDACTED:167— REDACTED:167-183 | REDACTED:167-183 | REDACTED:167-183 | REDACTED:163-179 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 264 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 (17 lines × 4) 2015/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb:155— 2015/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb:155-171 | 2016/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb:155-171 | 2017/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb:155-171 | 2018/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb:156-172 — before extracting anything, compare `2015/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb` and `2016/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 364 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 (17 lines × 4) 2015/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs:157— 2015/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs:157-173 | 2016/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs:157-173 | 2017/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs:157-173 | 2018/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs:157-173 — before extracting anything, compare `2015/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs` and `2016/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs` as WHOLE FILES: this scan already matched 6 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.
Duplicated block (17 lines × 4) 2015/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnSettings.cs:57— 2015/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnSettings.cs:57-73 | 2016/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnSettings.cs:57-73 | 2017/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnSettings.cs:57-73 | 2018/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnSettings.cs:57-73 — before extracting anything, compare `2015/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnSettings.cs` and `2016/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnSettings.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. 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 × 4) 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsElementsByCategory.vb:63— 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsElementsByCategory.vb:63-79 | 2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsElementsByCategory.vb:63-79 | 2017/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsElementsByCategory.vb:63-79 | 2018/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsElementsByCategory.vb:63-79 — before extracting anything, compare `2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsElementsByCategory.vb` and `2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsElementsByCategory.vb` 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 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.
Duplicated block (17 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb:77— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb:77-93 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb:77-93 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb:77-93 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb:77-93 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 109 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 (17 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb:103— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb:103-119 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb:103-119 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb:103-119 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb:103-119 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 109 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 (17 lines × 4) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/OpenNURBS/clsONSort.vb:59— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/OpenNURBS/clsONSort.vb:59-75 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/OpenNURBS/clsONSort.vb:59-75 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/OpenNURBS/clsONSort.vb:59-75 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/OpenNURBS/clsONSort.vb:59-75 — before extracting anything, compare `2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/OpenNURBS/clsONSort.vb` and `2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/OpenNURBS/clsONSort.vb` 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 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.
Duplicated block (17 lines × 4) REDACTED:334— REDACTED:334-350 | REDACTED:334-350 | REDACTED:334-350 | REDACTED:330-346 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 264 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:334` 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 (17 lines × 4) 2015/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Entry/app.vb:183— 2015/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Entry/app.vb:183-199 | 2016/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Entry/app.vb:183-199 | 2017/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Entry/app.vb:183-199 | 2018/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Entry/app.vb:183-199 — before extracting anything, compare `2015/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Entry/app.vb` and `2016/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Entry/app.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 93 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 (17 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:98— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:98-114 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:98-114 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:98-114 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:98-114 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 402 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 (17 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb:454— 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb:454-470 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb:454-470 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb:454-470 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb:454-470 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 221 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 (17 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsFile.vb:32— 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsFile.vb:32-48 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsFile.vb:32-48 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsFile.vb:32-48 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsFile.vb:32-48 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsFile.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsFile.vb` as WHOLE FILES: this scan already matched 4 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. 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 (17 lines × 4) 2015/Case.RevClouds/Case.RevClouds/UI/form_RevisionClouds.vb:53— 2015/Case.RevClouds/Case.RevClouds/UI/form_RevisionClouds.vb:53-69 | 2016/Case.RevClouds/Case.RevClouds/UI/form_RevisionClouds.vb:53-69 | 2017/Case.RevClouds/Case.RevClouds/UI/form_RevisionClouds.vb:53-69 | 2018/Case.RevClouds/Case.RevClouds/UI/form_RevisionClouds.vb:53-69 — before extracting anything, compare `2015/Case.RevClouds/Case.RevClouds/UI/form_RevisionClouds.vb` and `2016/Case.RevClouds/Case.RevClouds/UI/form_RevisionClouds.vb` 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 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.
Duplicated block (17 lines × 4) 2015/Case.RoomSync/Case.RoomSync/Data/modGeneral.vb:192— 2015/Case.RoomSync/Case.RoomSync/Data/modGeneral.vb:192-208 | 2016/Case.RoomSync/Case.RoomSync/Data/modGeneral.vb:192-208 | 2017/Case.RoomSync/Case.RoomSync/Data/modGeneral.vb:192-208 | 2018/Case.RoomSync/Case.RoomSync/Data/modGeneral.vb:192-208 — before extracting anything, compare `2015/Case.RoomSync/Case.RoomSync/Data/modGeneral.vb` and `2016/Case.RoomSync/Case.RoomSync/Data/modGeneral.vb` as WHOLE FILES: this scan already matched 5 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.
D4 · Code Duplication· Members sharing a duplicated core (8 members, 50+ identical tokens) · ×14
Members sharing a duplicated core (8 members, 50+ identical tokens) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:169— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:169-202 | 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSettings.vb:136-169 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:169-202 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSettings.vb:136-169 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:169-202 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSettings.vb:136-169 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:169-202 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSettings.vb:136-169 — 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) 2015/Case.LineChanger/Case.LineChanger/Data/clsSettings.vb:132— 2015/Case.LineChanger/Case.LineChanger/Data/clsSettings.vb:132-186 | 2015/Case.Subs.Linestyles/Case.Subs.Linestyles/Data/clsSettings.vb:220-280 | 2016/Case.LineChanger/Case.LineChanger/Data/clsSettings.vb:132-186 | 2016/Case.Subs.Linestyles/Case.Subs.Linestyles/Data/clsSettings.vb:220-280 | 2017/Case.LineChanger/Case.LineChanger/Data/clsSettings.vb:132-186 | 2017/Case.Subs.Linestyles/Case.Subs.Linestyles/Data/clsSettings.vb:220-280 | 2018/Case.LineChanger/Case.LineChanger/Data/clsSettings.vb:132-186 | 2018/Case.Subs.Linestyles/Case.Subs.Linestyles/Data/clsSettings.vb:220-280 — 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) 2015/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Data/clsView.vb:93— 2015/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Data/clsView.vb:93-109 | 2015/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/Data/clsView.vb:81-97 | 2016/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Data/clsView.vb:93-109 | 2016/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/Data/clsView.vb:81-97 | 2017/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Data/clsView.vb:93-109 | 2017/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/Data/clsView.vb:81-97 | 2018/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Data/clsView.vb:93-109 | 2018/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/Data/clsView.vb:81-97 — 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) 2015/Case.MultiViewDuplicate/Case.MultiViewDuplicate/UI/form_Main.vb:69— 2015/Case.MultiViewDuplicate/Case.MultiViewDuplicate/UI/form_Main.vb:69-168 | 2015/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/UI/form_Main.vb:69-177 | 2016/Case.MultiViewDuplicate/Case.MultiViewDuplicate/UI/form_Main.vb:69-168 | 2016/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/UI/form_Main.vb:69-177 | 2017/Case.MultiViewDuplicate/Case.MultiViewDuplicate/UI/form_Main.vb:69-168 | 2017/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/UI/form_Main.vb:69-177 | 2018/Case.MultiViewDuplicate/Case.MultiViewDuplicate/UI/form_Main.vb:69-168 | 2018/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/UI/form_Main.vb:69-177 — 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) 2015/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsExcel.vb:287— 2015/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsExcel.vb:287-323 | 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb:286-407 | 2016/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsExcel.vb:287-323 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb:286-407 | 2017/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsExcel.vb:287-323 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb:286-407 | 2018/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsExcel.vb:287-323 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb:286-407 — 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) 2015/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:39— 2015/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:39-69 | 2015/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:184-226 | 2016/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:39-69 | 2016/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:184-226 | 2017/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:39-69 | 2017/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:184-226 | 2018/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:39-69 | 2018/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:184-226 — 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) 2015/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:396— 2015/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:396-425 | 2015/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:453-482 | 2016/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:396-425 | 2016/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:453-482 | 2017/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:396-425 | 2017/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:453-482 | 2018/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:391-420 | 2018/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:453-482 — 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) 2015/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsElement.vb:25— 2015/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsElement.vb:25-64 | 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsFamily.vb:38-49 | 2016/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsElement.vb:25-64 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsFamily.vb:38-49 | 2017/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsElement.vb:25-64 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsFamily.vb:38-49 | 2018/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsElement.vb:25-64 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsFamily.vb:38-49 — 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) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:440— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:440-496 | 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:509-574 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:440-496 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:509-574 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:440-496 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:509-574 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:440-496 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:509-574 — 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) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:57— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:57-94 | 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_ModifyViewReference.vb:36-59 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:57-94 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_ModifyViewReference.vb:36-59 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:57-94 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_ModifyViewReference.vb:36-59 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:57-94 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_ModifyViewReference.vb:36-59 — 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) 2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:591— 2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:591-633 | 2015/Case.ViewTemplates/Case.ViewTemplates/UI/form_Main.vb:199-241 | 2016/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:591-633 | 2016/Case.ViewTemplates/Case.ViewTemplates/UI/form_Main.vb:199-241 | 2017/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:591-633 | 2017/Case.ViewTemplates/Case.ViewTemplates/UI/form_Main.vb:199-241 | 2018/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:591-633 | 2018/Case.ViewTemplates/Case.ViewTemplates/UI/form_Main.vb:199-241 — 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) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb:118— 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb:118-200 | 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb:213-298 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb:118-200 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb:213-298 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb:118-200 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb:213-298 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb:118-200 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb:213-298 — 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) 2015/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnFamData.cs:126— 2015/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnFamData.cs:126-151 | 2015/Case.ObjectStyles/Case.ObjectStyles/Data/mnFamData.cs:132-157 | 2016/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnFamData.cs:126-151 | 2016/Case.ObjectStyles/Case.ObjectStyles/Data/mnFamData.cs:132-157 | 2017/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnFamData.cs:126-151 | 2017/Case.ObjectStyles/Case.ObjectStyles/Data/mnFamData.cs:132-157 | 2018/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnFamData.cs:126-151 | 2018/Case.ObjectStyles/Case.ObjectStyles/Data/mnFamData.cs:132-157 — 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) 2015/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:245— 2015/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:245-303 | 2015/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:360-421 | 2016/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:245-303 | 2016/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:360-421 | 2017/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:245-303 | 2017/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:360-421 | 2018/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:245-303 | 2018/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:360-421 — 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.
Duplicated block (22 lines × 4) 2015/Case.ApplySysOrient/Data/clsSettings.cs:77— 2015/Case.ApplySysOrient/Data/clsSettings.cs:77-98 | 2016/Case.ApplySysOrient/Data/clsSettings.cs:77-98 | 2017/Case.ApplySysOrient/Data/clsSettings.cs:77-98 | 2018/Case.ApplySysOrient/Data/clsSettings.cs:77-98 — before extracting anything, compare `2015/Case.ApplySysOrient/Data/clsSettings.cs` and `2016/Case.ApplySysOrient/Data/clsSettings.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 288 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 (22 lines × 4) REDACTED:25— REDACTED:25-46 | REDACTED:25-46 | REDACTED:25-46 | REDACTED:24-45 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 264 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 (22 lines × 4) REDACTED:131— REDACTED:131-152 | REDACTED:131-152 | REDACTED:131-152 | REDACTED:131-152 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 421 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 (22 lines × 4) 2015/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs:182— 2015/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs:182-203 | 2016/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs:182-203 | 2017/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs:182-203 | 2018/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs:182-203 — before extracting anything, compare `2015/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs` and `2016/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs` as WHOLE FILES: this scan already matched 6 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.
Duplicated block (22 lines × 4) 2015/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs:211— 2015/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs:211-232 | 2016/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs:211-232 | 2017/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs:211-232 | 2018/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs:211-232 — before extracting anything, compare `2015/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs` and `2016/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs` as WHOLE FILES: this scan already matched 6 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.
Duplicated block (22 lines × 4) REDACTED:131— REDACTED:131-152 | REDACTED:131-152 | REDACTED:131-152 | REDACTED:131-152 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 147 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 (22 lines × 4) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:149— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:149-170 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:149-170 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:149-170 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:149-170 — before extracting anything, compare `2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb` and `2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 383 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 (22 lines × 4) 2015/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsSettings.vb:149— 2015/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsSettings.vb:149-170 | 2016/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsSettings.vb:149-170 | 2017/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsSettings.vb:149-170 | 2018/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsSettings.vb:149-170 — before extracting anything, compare `2015/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsSettings.vb` and `2016/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 149 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 (22 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:32— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:32-53 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:32-53 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:32-53 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:32-53 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 467 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 (22 lines × 4) 2015/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb:358— 2015/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb:358-379 | 2016/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb:358-379 | 2017/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb:358-379 | 2018/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb:358-379 — before extracting anything, compare `2015/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb` and `2016/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 260 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 (22 lines × 4) 2015/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb:390— 2015/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb:390-411 | 2016/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb:390-411 | 2017/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb:390-411 | 2018/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb:390-411 — before extracting anything, compare `2015/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb` and `2016/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 260 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 (22 lines × 4) 2015/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb:511— 2015/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb:511-532 | 2016/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb:511-532 | 2017/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb:511-532 | 2018/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb:511-532 — before extracting anything, compare `2015/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb` and `2016/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 260 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 (22 lines × 4) 2015/Case.RoomInsertionPoint/Case.RoomInsertionPoint/UI/form_Progress.vb:11— 2015/Case.RoomInsertionPoint/Case.RoomInsertionPoint/UI/form_Progress.vb:11-32 | 2016/Case.RoomInsertionPoint/Case.RoomInsertionPoint/UI/form_Progress.vb:11-32 | 2017/Case.RoomInsertionPoint/Case.RoomInsertionPoint/UI/form_Progress.vb:11-32 | 2018/Case.RoomInsertionPoint/Case.RoomInsertionPoint/UI/form_Progress.vb:11-32 — before extracting anything, compare `2015/Case.RoomInsertionPoint/Case.RoomInsertionPoint/UI/form_Progress.vb` and `2016/Case.RoomInsertionPoint/Case.RoomInsertionPoint/UI/form_Progress.vb` 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.
Duplicated block (22 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSharedParameters.vb:34— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSharedParameters.vb:34-55 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSharedParameters.vb:34-55 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSharedParameters.vb:34-55 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSharedParameters.vb:34-55 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSharedParameters.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSharedParameters.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 110 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 (11 lines × 4) 2015/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb:211— 2015/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb:211-221 | 2016/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb:211-221 | 2017/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb:211-221 | 2018/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb:211-221 — before extracting anything, compare `2015/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb` and `2016/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 215 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 (11 lines × 4) 2015/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb:231— 2015/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb:231-241 | 2016/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb:231-241 | 2017/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb:231-241 | 2018/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb:231-241 — before extracting anything, compare `2015/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb` and `2016/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 215 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 (11 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:33— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:33-43 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:33-43 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:33-43 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:33-43 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 330 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 (11 lines × 4) 2015/Case.Export.Families/Case.Export.Families/Forms/form_Familes.vb:178— 2015/Case.Export.Families/Case.Export.Families/Forms/form_Familes.vb:178-188 | 2016/Case.Export.Families/Case.Export.Families/Forms/form_Familes.vb:178-188 | 2017/Case.Export.Families/Case.Export.Families/Forms/form_Familes.vb:178-188 | 2018/Case.Export.Families/Case.Export.Families/Forms/form_Familes.vb:178-188 — before extracting anything, compare `2015/Case.Export.Families/Case.Export.Families/Forms/form_Familes.vb` and `2016/Case.Export.Families/Case.Export.Families/Forms/form_Familes.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 93 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 (11 lines × 4) 2015/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs:11— 2015/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs:11-21 | 2016/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs:11-21 | 2017/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs:11-21 | 2018/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs:11-21 — before extracting anything, compare `2015/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs` and `2016/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs` as WHOLE FILES: this scan already matched 6 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 `2015/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.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 (11 lines × 4) 2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:614— 2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:614-624 | 2016/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:614-624 | 2017/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:614-624 | 2018/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:614-624 — before extracting anything, compare `2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb` and `2016/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb` as WHOLE FILES: this scan already matched 5 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. 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 (11 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsParamMap.vb:28— 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsParamMap.vb:28-38 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsParamMap.vb:28-38 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsParamMap.vb:28-38 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsParamMap.vb:28-38 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsParamMap.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsParamMap.vb` 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.
Duplicated block (11 lines × 4) 2015/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb:32— 2015/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb:32-42 | 2016/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb:32-42 | 2017/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb:33-43 | 2018/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb:33-43 — before extracting anything, compare `2015/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb` and `2016/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 260 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 (11 lines × 4) 2015/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb:59— 2015/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb:59-69 | 2016/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb:59-69 | 2017/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb:60-70 | 2018/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb:60-70 — before extracting anything, compare `2015/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb` and `2016/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 260 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 (11 lines × 4) 2015/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Form/form_Main.vb:45— 2015/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Form/form_Main.vb:45-55 | 2016/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Form/form_Main.vb:45-55 | 2017/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Form/form_Main.vb:45-55 | 2018/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Form/form_Main.vb:45-55 — before extracting anything, compare `2015/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Form/form_Main.vb` and `2016/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Form/form_Main.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 215 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 (11 lines × 4) 2015/Case.ImageToDraftingView/Case.ImageToDraftingView/Forms/form_Main.vb:45— 2015/Case.ImageToDraftingView/Case.ImageToDraftingView/Forms/form_Main.vb:45-55 | 2016/Case.ImageToDraftingView/Case.ImageToDraftingView/Forms/form_Main.vb:45-55 | 2017/Case.ImageToDraftingView/Case.ImageToDraftingView/Forms/form_Main.vb:45-55 | 2018/Case.ImageToDraftingView/Case.ImageToDraftingView/Forms/form_Main.vb:45-55 — before extracting anything, compare `2015/Case.ImageToDraftingView/Case.ImageToDraftingView/Forms/form_Main.vb` and `2016/Case.ImageToDraftingView/Case.ImageToDraftingView/Forms/form_Main.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 155 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 (11 lines × 4) 2015/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb:210— 2015/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb:210-220 | 2016/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb:210-220 | 2017/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb:210-220 | 2018/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb:210-220 — before extracting anything, compare `2015/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb` and `2016/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 150 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 (11 lines × 4) 2015/Case.ViewCreator/Case.ViewCreator/Classes/Entry/app.cs:72— 2015/Case.ViewCreator/Case.ViewCreator/Classes/Entry/app.cs:72-82 | 2016/Case.ViewCreator/Case.ViewCreator/Classes/Entry/app.cs:72-82 | 2017/Case.ViewCreator/Case.ViewCreator/Classes/Entry/app.cs:72-82 | 2018/Case.ViewCreator/Case.ViewCreator/Classes/Entry/app.cs:72-82 — before extracting anything, compare `2015/Case.ViewCreator/Case.ViewCreator/Classes/Entry/app.cs` and `2016/Case.ViewCreator/Case.ViewCreator/Classes/Entry/app.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 98 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:192— REDACTED:192-202 | REDACTED:192-202 | REDACTED:192-202 | REDACTED:188-198 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 264 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 × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSharedParameters.vb:196— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSharedParameters.vb:196-202 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSharedParameters.vb:196-202 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSharedParameters.vb:196-202 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSharedParameters.vb:196-202 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSharedParameters.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSharedParameters.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 110 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 (7 lines × 4) 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSettings.vb:71— 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSettings.vb:71-77 | 2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSettings.vb:71-77 | 2017/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSettings.vb:71-77 | 2018/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSettings.vb:71-77 — before extracting anything, compare `2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSettings.vb` and `2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 97 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 (7 lines × 4) 2015/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsFamilyType.vb:130— 2015/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsFamilyType.vb:130-136 | 2016/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsFamilyType.vb:130-136 | 2017/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsFamilyType.vb:130-136 | 2018/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsFamilyType.vb:130-136 — before extracting anything, compare `2015/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsFamilyType.vb` and `2016/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsFamilyType.vb` 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 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.
Duplicated block (7 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2512.vb:294— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2512.vb:294-300 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2512.vb:294-300 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2512.vb:294-300 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2512.vb:294-300 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2512.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2512.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 283 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 (7 lines × 4) 2015/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsRvtElemInst.vb:98— 2015/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsRvtElemInst.vb:98-104 | 2016/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsRvtElemInst.vb:98-104 | 2017/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsRvtElemInst.vb:98-104 | 2018/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsRvtElemInst.vb:98-104 — before extracting anything, compare `2015/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsRvtElemInst.vb` and `2016/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsRvtElemInst.vb` 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. 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 (7 lines × 4) 2015/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsRvtElemInst.vb:116— 2015/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsRvtElemInst.vb:116-122 | 2016/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsRvtElemInst.vb:116-122 | 2017/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsRvtElemInst.vb:116-122 | 2018/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsRvtElemInst.vb:116-122 — before extracting anything, compare `2015/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsRvtElemInst.vb` and `2016/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsRvtElemInst.vb` 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. 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 (7 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:110— 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:110-116 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:110-116 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:110-116 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:110-116 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 317 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 (7 lines × 4) 2015/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Data/clsCategory.vb:37— 2015/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Data/clsCategory.vb:37-43 | 2016/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Data/clsCategory.vb:37-43 | 2017/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Data/clsCategory.vb:37-43 | 2018/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Data/clsCategory.vb:37-43 — before extracting anything, compare `2015/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Data/clsCategory.vb` and `2016/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Data/clsCategory.vb` 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 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.
Duplicated block (7 lines × 4) 2015/Case.ParallelWalls/Case.ParallelWalls/Data/clsVectors.cs:155— 2015/Case.ParallelWalls/Case.ParallelWalls/Data/clsVectors.cs:155-161 | 2016/Case.ParallelWalls/Case.ParallelWalls/Data/clsVectors.cs:155-161 | 2017/Case.ParallelWalls/Case.ParallelWalls/Data/clsVectors.cs:155-161 | 2018/Case.ParallelWalls/Case.ParallelWalls/Data/clsVectors.cs:150-156 — before extracting anything, compare `2015/Case.ParallelWalls/Case.ParallelWalls/Data/clsVectors.cs` and `2016/Case.ParallelWalls/Case.ParallelWalls/Data/clsVectors.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 55 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 × 4) 2015/Case.ParallelWalls/Case.ParallelWalls/Data/clsWallTransform.cs:166— 2015/Case.ParallelWalls/Case.ParallelWalls/Data/clsWallTransform.cs:166-172 | 2016/Case.ParallelWalls/Case.ParallelWalls/Data/clsWallTransform.cs:166-172 | 2017/Case.ParallelWalls/Case.ParallelWalls/Data/clsWallTransform.cs:166-172 | 2018/Case.ParallelWalls/Case.ParallelWalls/Data/clsWallTransform.cs:161-167 — before extracting anything, compare `2015/Case.ParallelWalls/Case.ParallelWalls/Data/clsWallTransform.cs` and `2016/Case.ParallelWalls/Case.ParallelWalls/Data/clsWallTransform.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 56 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 × 4) 2015/Case.Subs.KeyMatcher/Utility/clsGlobals.cs:52— 2015/Case.Subs.KeyMatcher/Utility/clsGlobals.cs:52-58 | 2016/Case.Subs.KeyMatcher/Utility/clsGlobals.cs:52-58 | 2017/Case.Subs.KeyMatcher/Utility/clsGlobals.cs:52-58 | 2018/Case.Subs.KeyMatcher/Utility/clsGlobals.cs:52-58 — before extracting anything, compare `2015/Case.Subs.KeyMatcher/Utility/clsGlobals.cs` and `2016/Case.Subs.KeyMatcher/Utility/clsGlobals.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 115 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 × 4) 2015/Case.Subs.KeyMatcher/Utility/clsGlobals.cs:69— 2015/Case.Subs.KeyMatcher/Utility/clsGlobals.cs:69-75 | 2016/Case.Subs.KeyMatcher/Utility/clsGlobals.cs:69-75 | 2017/Case.Subs.KeyMatcher/Utility/clsGlobals.cs:69-75 | 2018/Case.Subs.KeyMatcher/Utility/clsGlobals.cs:69-75 — before extracting anything, compare `2015/Case.Subs.KeyMatcher/Utility/clsGlobals.cs` and `2016/Case.Subs.KeyMatcher/Utility/clsGlobals.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 115 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 × 4) 2015/Case.DimensionOverrides/Case.DimensionOverrides/Data/clsSettings.cs:93— 2015/Case.DimensionOverrides/Case.DimensionOverrides/Data/clsSettings.cs:93-99 | 2016/Case.DimensionOverrides/Case.DimensionOverrides/Data/clsSettings.cs:93-99 | 2017/Case.DimensionOverrides/Case.DimensionOverrides/Data/clsSettings.cs:93-99 | 2018/Case.DimensionOverrides/Case.DimensionOverrides/Data/clsSettings.cs:88-94 — before extracting anything, compare `2015/Case.DimensionOverrides/Case.DimensionOverrides/Data/clsSettings.cs` and `2016/Case.DimensionOverrides/Case.DimensionOverrides/Data/clsSettings.cs` as WHOLE FILES: 98% 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 (7 lines × 4) 2015/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/clsSettings.vb:120— 2015/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/clsSettings.vb:120-126 | 2016/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/clsSettings.vb:120-126 | 2017/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/clsSettings.vb:120-126 | 2018/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/clsSettings.vb:120-126 — before extracting anything, compare `2015/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/clsSettings.vb` and `2016/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/clsSettings.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 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 (24 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:360— 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:360-383 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:360-383 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:360-383 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:360-383 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 267 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 (24 lines × 4) REDACTED:378— REDACTED:378-401 | REDACTED:378-401 | REDACTED:378-401 | REDACTED:378-401 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 421 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 (24 lines × 4) 2015/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs:125— 2015/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs:125-148 | 2016/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs:125-148 | 2017/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs:125-148 | 2018/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs:125-148 — before extracting anything, compare `2015/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs` and `2016/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs` as WHOLE FILES: this scan already matched 6 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.
Duplicated block (24 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtSchedule.vb:154— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtSchedule.vb:154-177 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtSchedule.vb:154-177 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtSchedule.vb:154-177 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtSchedule.vb:154-177 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtSchedule.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtSchedule.vb` 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 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.
Duplicated block (24 lines × 4) 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:490— 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:490-513 | 2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:490-513 | 2017/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:490-513 | 2018/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:490-513 — before extracting anything, compare `2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb` and `2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 500 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 (24 lines × 4) 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:531— 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:531-554 | 2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:531-554 | 2017/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:531-554 | 2018/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:531-554 — before extracting anything, compare `2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb` and `2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 500 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 (24 lines × 4) 2015/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsSettings.vb:116— 2015/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsSettings.vb:116-139 | 2016/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsSettings.vb:116-139 | 2017/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsSettings.vb:116-139 | 2018/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsSettings.vb:116-139 — before extracting anything, compare `2015/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsSettings.vb` and `2016/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 149 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 (24 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSharedParameters.vb:259— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSharedParameters.vb:259-282 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSharedParameters.vb:259-282 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSharedParameters.vb:259-282 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSharedParameters.vb:259-282 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSharedParameters.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSharedParameters.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 110 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 (24 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_AddFamily.vb:35— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_AddFamily.vb:35-58 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_AddFamily.vb:35-58 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_AddFamily.vb:35-58 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_AddFamily.vb:35-58 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_AddFamily.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_AddFamily.vb` 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 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.
Duplicated block (24 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_ModifyViewReference.vb:36— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_ModifyViewReference.vb:36-59 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_ModifyViewReference.vb:36-59 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_ModifyViewReference.vb:36-59 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_ModifyViewReference.vb:36-59 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_ModifyViewReference.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_ModifyViewReference.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 62 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 (24 lines × 4) 2015/Case.ParallelWalls/Case.ParallelWalls/Data/clsWallFilter.cs:12— 2015/Case.ParallelWalls/Case.ParallelWalls/Data/clsWallFilter.cs:12-35 | 2016/Case.ParallelWalls/Case.ParallelWalls/Data/clsWallFilter.cs:12-35 | 2017/Case.ParallelWalls/Case.ParallelWalls/Data/clsWallFilter.cs:12-35 | 2018/Case.ParallelWalls/Case.ParallelWalls/Data/clsWallFilter.cs:12-35 — before extracting anything, compare `2015/Case.ParallelWalls/Case.ParallelWalls/Data/clsWallFilter.cs` and `2016/Case.ParallelWalls/Case.ParallelWalls/Data/clsWallFilter.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.
Duplicated block (24 lines × 4) 2015/Case.LineChanger/Case.LineChanger/Data/clsSettings.vb:95— 2015/Case.LineChanger/Case.LineChanger/Data/clsSettings.vb:95-118 | 2016/Case.LineChanger/Case.LineChanger/Data/clsSettings.vb:95-118 | 2017/Case.LineChanger/Case.LineChanger/Data/clsSettings.vb:95-118 | 2018/Case.LineChanger/Case.LineChanger/Data/clsSettings.vb:95-118 — before extracting anything, compare `2015/Case.LineChanger/Case.LineChanger/Data/clsSettings.vb` and `2016/Case.LineChanger/Case.LineChanger/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 126 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 (24 lines × 4) 2015/Case.ModeledRoomTags/Case.ModeledRoomTags/UI/form_Main.vb:33— 2015/Case.ModeledRoomTags/Case.ModeledRoomTags/UI/form_Main.vb:33-56 | 2016/Case.ModeledRoomTags/Case.ModeledRoomTags/UI/form_Main.vb:33-56 | 2017/Case.ModeledRoomTags/Case.ModeledRoomTags/UI/form_Main.vb:33-56 | 2018/Case.ModeledRoomTags/Case.ModeledRoomTags/UI/form_Main.vb:33-56 — before extracting anything, compare `2015/Case.ModeledRoomTags/Case.ModeledRoomTags/UI/form_Main.vb` and `2016/Case.ModeledRoomTags/Case.ModeledRoomTags/UI/form_Main.vb` as WHOLE FILES: this scan already matched 3 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. 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 (26 lines × 4) 2015/Case.ReportGroupsByView/Case.ReportGroupsByView/Data/clsSettings.cs:206— 2015/Case.ReportGroupsByView/Case.ReportGroupsByView/Data/clsSettings.cs:206-231 | 2016/Case.ReportGroupsByView/Case.ReportGroupsByView/Data/clsSettings.cs:206-231 | 2017/Case.ReportGroupsByView/Case.ReportGroupsByView/Data/clsSettings.cs:206-231 | 2018/Case.ReportGroupsByView/Case.ReportGroupsByView/Data/clsSettings.cs:206-231 — before extracting anything, compare `2015/Case.ReportGroupsByView/Case.ReportGroupsByView/Data/clsSettings.cs` and `2016/Case.ReportGroupsByView/Case.ReportGroupsByView/Data/clsSettings.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 123 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 (26 lines × 4) 2015/Case.ViewCreator/Case.ViewCreator/Classes/Entry/app.cs:38— 2015/Case.ViewCreator/Case.ViewCreator/Classes/Entry/app.cs:38-63 | 2016/Case.ViewCreator/Case.ViewCreator/Classes/Entry/app.cs:38-63 | 2017/Case.ViewCreator/Case.ViewCreator/Classes/Entry/app.cs:38-63 | 2018/Case.ViewCreator/Case.ViewCreator/Classes/Entry/app.cs:38-63 — before extracting anything, compare `2015/Case.ViewCreator/Case.ViewCreator/Classes/Entry/app.cs` and `2016/Case.ViewCreator/Case.ViewCreator/Classes/Entry/app.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 98 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 (26 lines × 4) 2015/Case.Subs.KeyMatcher/Utility/clsGlobals.cs:136— 2015/Case.Subs.KeyMatcher/Utility/clsGlobals.cs:136-161 | 2016/Case.Subs.KeyMatcher/Utility/clsGlobals.cs:136-161 | 2017/Case.Subs.KeyMatcher/Utility/clsGlobals.cs:136-161 | 2018/Case.Subs.KeyMatcher/Utility/clsGlobals.cs:136-161 — before extracting anything, compare `2015/Case.Subs.KeyMatcher/Utility/clsGlobals.cs` and `2016/Case.Subs.KeyMatcher/Utility/clsGlobals.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 115 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 (26 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:735— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:735-760 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:735-760 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:735-760 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:735-760 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 281 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 (26 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb:421— 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb:421-446 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb:421-446 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb:421-446 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb:421-446 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 221 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 `2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb:421` 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 (26 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:207— 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:207-232 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:207-232 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:207-232 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:207-232 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 267 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 (26 lines × 4) 2015/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Data/clsCategory.vb:94— 2015/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Data/clsCategory.vb:94-119 | 2016/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Data/clsCategory.vb:94-119 | 2017/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Data/clsCategory.vb:94-119 | 2018/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Data/clsCategory.vb:94-119 — before extracting anything, compare `2015/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Data/clsCategory.vb` and `2016/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Data/clsCategory.vb` 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 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.
Duplicated block (26 lines × 4) 2015/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:213— 2015/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:213-238 | 2016/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:213-238 | 2017/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:213-238 | 2018/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:208-233 — before extracting anything, compare `2015/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb` and `2016/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 173 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 (26 lines × 4) 2015/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:200— 2015/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:200-225 | 2016/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:200-225 | 2017/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:200-225 | 2018/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:200-225 — before extracting anything, compare `2015/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb` and `2016/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 245 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 (26 lines × 4) 2015/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Entry/app.vb:146— 2015/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Entry/app.vb:146-171 | 2016/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Entry/app.vb:146-171 | 2017/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Entry/app.vb:146-171 | 2018/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Entry/app.vb:146-171 — before extracting anything, compare `2015/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Entry/app.vb` and `2016/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Entry/app.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 93 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 (26 lines × 4) 2015/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Entry/cmd.vb:22— 2015/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Entry/cmd.vb:22-47 | 2016/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Entry/cmd.vb:22-47 | 2017/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Entry/cmd.vb:22-47 | 2018/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Entry/cmd.vb:22-47 — before extracting anything, compare `2015/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Entry/cmd.vb` and `2016/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Entry/cmd.vb` 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.
Duplicated block (26 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Progress.vb:14— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Progress.vb:14-39 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Progress.vb:14-39 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Progress.vb:14-39 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Progress.vb:14-39 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Progress.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Progress.vb` 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.
Duplicated block (26 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_ModifyViewReference.vb:70— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_ModifyViewReference.vb:70-95 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_ModifyViewReference.vb:70-95 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_ModifyViewReference.vb:70-95 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_ModifyViewReference.vb:70-95 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_ModifyViewReference.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_ModifyViewReference.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 62 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 (30 lines × 4) REDACTED:67— REDACTED:67-96 | REDACTED:67-96 | REDACTED:67-96 | REDACTED:66-95 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 264 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: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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `REDACTED:99` calls `RecordUsage` and `REDACTED:97` 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 (30 lines × 4) 2015/Case.ApplySysOrient/Data/clsUtil.cs:54— 2015/Case.ApplySysOrient/Data/clsUtil.cs:54-83 | 2016/Case.ApplySysOrient/Data/clsUtil.cs:54-83 | 2017/Case.ApplySysOrient/Data/clsUtil.cs:54-83 | 2018/Case.ApplySysOrient/Data/clsUtil.cs:54-83 — before extracting anything, compare `2015/Case.ApplySysOrient/Data/clsUtil.cs` and `2016/Case.ApplySysOrient/Data/clsUtil.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. 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 (30 lines × 4) 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb:327— 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb:327-356 | 2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb:327-356 | 2017/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb:327-356 | 2018/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb:327-356 — before extracting anything, compare `2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb` and `2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 7 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. 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 (30 lines × 4) 2015/Case.Subs.Worksets/Case.Subs.Worksets/Entry/CEB749CFCF844AE8B76F40E3EBAA2FF7.vb:37— 2015/Case.Subs.Worksets/Case.Subs.Worksets/Entry/CEB749CFCF844AE8B76F40E3EBAA2FF7.vb:37-66 | 2016/Case.Subs.Worksets/Case.Subs.Worksets/Entry/CEB749CFCF844AE8B76F40E3EBAA2FF7.vb:37-66 | 2017/Case.Subs.Worksets/Case.Subs.Worksets/Entry/CEB749CFCF844AE8B76F40E3EBAA2FF7.vb:37-66 | 2018/Case.Subs.Worksets/Case.Subs.Worksets/Entry/CEB749CFCF844AE8B76F40E3EBAA2FF7.vb:37-66 — before extracting anything, compare `2015/Case.Subs.Worksets/Case.Subs.Worksets/Entry/CEB749CFCF844AE8B76F40E3EBAA2FF7.vb` and `2016/Case.Subs.Worksets/Case.Subs.Worksets/Entry/CEB749CFCF844AE8B76F40E3EBAA2FF7.vb` as WHOLE FILES: 96% 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. Read the line range as the matched WINDOW rather than a finished unit: at `2015/Case.Subs.Worksets/Case.Subs.Worksets/Entry/CEB749CFCF844AE8B76F40E3EBAA2FF7.vb:37` 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 (30 lines × 4) 2015/Case.BasicReporting/Case.BasicReporting/Entry/CmdMain.vb:27— 2015/Case.BasicReporting/Case.BasicReporting/Entry/CmdMain.vb:27-56 | 2015/Case.ChangeReplaceFamTypeNames/Case.ChangeReplaceFamTypeNames/Entry/CmdMain.vb:28-57 | 2015/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Entry/CmdMain.vb:27-56 | 2015/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Entry/CmdMain.vb:28-57 — before extracting anything, compare `2015/Case.BasicReporting/Case.BasicReporting/Entry/CmdMain.vb` and `2015/Case.ChangeReplaceFamTypeNames/Case.ChangeReplaceFamTypeNames/Entry/CmdMain.vb` 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 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.
Duplicated block (30 lines × 4) 2015/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/UI/form_Main.vb:68— 2015/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/UI/form_Main.vb:68-97 | 2016/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/UI/form_Main.vb:68-97 | 2017/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/UI/form_Main.vb:68-97 | 2018/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/UI/form_Main.vb:68-97 — before extracting anything, compare `2015/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/UI/form_Main.vb` and `2016/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/UI/form_Main.vb` as WHOLE FILES: this scan already matched 3 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. 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 (30 lines × 4) 2015/Case.RoomSync/Case.RoomSync/UI/form_Sync.vb:255— 2015/Case.RoomSync/Case.RoomSync/UI/form_Sync.vb:255-284 | 2016/Case.RoomSync/Case.RoomSync/UI/form_Sync.vb:255-284 | 2017/Case.RoomSync/Case.RoomSync/UI/form_Sync.vb:255-284 | 2018/Case.RoomSync/Case.RoomSync/UI/form_Sync.vb:255-284 — before extracting anything, compare `2015/Case.RoomSync/Case.RoomSync/UI/form_Sync.vb` and `2016/Case.RoomSync/Case.RoomSync/UI/form_Sync.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 242 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 (30 lines × 4) 2016/Case.BasicReporting/Case.BasicReporting/Entry/CmdMain.vb:27— 2016/Case.BasicReporting/Case.BasicReporting/Entry/CmdMain.vb:27-56 | 2016/Case.ChangeReplaceFamTypeNames/Case.ChangeReplaceFamTypeNames/Entry/CmdMain.vb:28-57 | 2016/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Entry/CmdMain.vb:27-56 | 2016/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Entry/CmdMain.vb:28-57 — before extracting anything, compare `2016/Case.BasicReporting/Case.BasicReporting/Entry/CmdMain.vb` and `2016/Case.ChangeReplaceFamTypeNames/Case.ChangeReplaceFamTypeNames/Entry/CmdMain.vb` 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 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.
Duplicated block (30 lines × 4) 2017/Case.BasicReporting/Case.BasicReporting/Entry/CmdMain.vb:27— 2017/Case.BasicReporting/Case.BasicReporting/Entry/CmdMain.vb:27-56 | 2017/Case.ChangeReplaceFamTypeNames/Case.ChangeReplaceFamTypeNames/Entry/CmdMain.vb:28-57 | 2017/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Entry/CmdMain.vb:27-56 | 2017/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Entry/CmdMain.vb:28-57 — before extracting anything, compare `2017/Case.BasicReporting/Case.BasicReporting/Entry/CmdMain.vb` and `2017/Case.ChangeReplaceFamTypeNames/Case.ChangeReplaceFamTypeNames/Entry/CmdMain.vb` 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 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.
Duplicated block (30 lines × 4) 2018/Case.BasicReporting/Case.BasicReporting/Entry/CmdMain.vb:27— 2018/Case.BasicReporting/Case.BasicReporting/Entry/CmdMain.vb:27-56 | 2018/Case.ChangeReplaceFamTypeNames/Case.ChangeReplaceFamTypeNames/Entry/CmdMain.vb:28-57 | 2018/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Entry/CmdMain.vb:27-56 | 2018/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Entry/CmdMain.vb:28-57 — before extracting anything, compare `2018/Case.BasicReporting/Case.BasicReporting/Entry/CmdMain.vb` and `2018/Case.ChangeReplaceFamTypeNames/Case.ChangeReplaceFamTypeNames/Entry/CmdMain.vb` 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 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.
Duplicated block (30 lines × 4) REDACTED:25— REDACTED:25-54 | REDACTED:25-54 | REDACTED:25-54 | REDACTED:25-54 — before extracting anything, compare `REDACTED` and `REDACTED` 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.
Duplicated block (25 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_ExportSchedule.vb:267— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_ExportSchedule.vb:267-291 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_ExportSchedule.vb:267-291 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_ExportSchedule.vb:267-291 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_ExportSchedule.vb:267-291 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_ExportSchedule.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_ExportSchedule.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 81 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 (25 lines × 4) 2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:414— 2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:414-438 | 2016/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:414-438 | 2017/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:414-438 | 2018/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:414-438 — before extracting anything, compare `2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb` and `2016/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 373 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 (25 lines × 4) 2015/Case.Navis2BCF/Case.Navis2BCF/IfcGuid.cs:101— 2015/Case.Navis2BCF/Case.Navis2BCF/IfcGuid.cs:101-125 | 2016/Case.Navis2BCF/Case.Navis2BCF/IfcGuid.cs:101-125 | 2017/Case.Navis2BCF/Case.Navis2BCF/IfcGuid.cs:101-125 | 2018/Case.Navis2BCF/Case.Navis2BCF/IfcGuid.cs:101-125 — before extracting anything, compare `2015/Case.Navis2BCF/Case.Navis2BCF/IfcGuid.cs` and `2016/Case.Navis2BCF/Case.Navis2BCF/IfcGuid.cs` as WHOLE FILES: this scan already matched 5 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. 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 (25 lines × 4) REDACTED:160— REDACTED:160-184 | REDACTED:160-184 | REDACTED:160-184 | REDACTED:160-184 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 147 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 (25 lines × 4) 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:647— 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:647-671 | 2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:647-671 | 2017/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:647-671 | 2018/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:647-671 — before extracting anything, compare `2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb` and `2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 500 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 (25 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSettings.vb:279— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSettings.vb:279-303 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSettings.vb:279-303 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSettings.vb:279-303 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSettings.vb:279-303 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSettings.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 5 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. 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 (25 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsPara.vb:84— 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsPara.vb:84-108 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsPara.vb:84-108 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsPara.vb:84-108 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsPara.vb:84-108 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsPara.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsPara.vb` 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 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.
Duplicated block (25 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ParameterConfigurationManager.xaml.vb:182— 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ParameterConfigurationManager.xaml.vb:182-206 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ParameterConfigurationManager.xaml.vb:182-206 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ParameterConfigurationManager.xaml.vb:182-206 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ParameterConfigurationManager.xaml.vb:182-206 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ParameterConfigurationManager.xaml.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ParameterConfigurationManager.xaml.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 169 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 (25 lines × 4) 2015/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Progress.vb:13— 2015/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Progress.vb:13-37 | 2016/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Progress.vb:13-37 | 2017/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Progress.vb:13-37 | 2018/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Progress.vb:13-37 — before extracting anything, compare `2015/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Progress.vb` and `2016/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Progress.vb` 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.
Duplicated block (25 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:291— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:291-315 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:291-315 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:291-315 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:291-315 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 422 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 (25 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:701— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:701-725 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:701-725 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:701-725 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:701-725 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 422 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 (18 lines × 4) 2015/Case.ReportGroupsByView/Case.ReportGroupsByView/Data/clsSettings.cs:104— 2015/Case.ReportGroupsByView/Case.ReportGroupsByView/Data/clsSettings.cs:104-121 | 2016/Case.ReportGroupsByView/Case.ReportGroupsByView/Data/clsSettings.cs:104-121 | 2017/Case.ReportGroupsByView/Case.ReportGroupsByView/Data/clsSettings.cs:104-121 | 2018/Case.ReportGroupsByView/Case.ReportGroupsByView/Data/clsSettings.cs:104-121 — before extracting anything, compare `2015/Case.ReportGroupsByView/Case.ReportGroupsByView/Data/clsSettings.cs` and `2016/Case.ReportGroupsByView/Case.ReportGroupsByView/Data/clsSettings.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 123 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 (18 lines × 4) 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:266— 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:266-283 | 2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:266-283 | 2017/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:266-283 | 2018/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:266-283 — before extracting anything, compare `2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb` and `2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 323 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 (18 lines × 4) 2015/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:301— 2015/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:301-318 | 2016/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:301-318 | 2017/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:301-318 | 2018/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:301-318 — before extracting anything, compare `2015/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb` and `2016/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 264 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 (18 lines × 4) 2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:370— 2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:370-387 | 2016/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:370-387 | 2017/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:370-387 | 2018/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:370-387 — before extracting anything, compare `2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb` and `2016/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 373 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 (18 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb:15— 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb:15-32 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb:15-32 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb:15-32 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb:15-32 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 274 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 (18 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsSettings.vb:357— 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsSettings.vb:357-374 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsSettings.vb:357-374 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsSettings.vb:357-374 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsSettings.vb:357-374 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsSettings.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsSettings.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 175 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 (18 lines × 4) 2015/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Data/clsSettings.vb:212— 2015/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Data/clsSettings.vb:212-229 | 2016/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Data/clsSettings.vb:212-229 | 2017/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Data/clsSettings.vb:212-229 | 2018/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Data/clsSettings.vb:212-229 — before extracting anything, compare `2015/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Data/clsSettings.vb` and `2016/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 131 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 (18 lines × 4) 2015/Case.ViewportReporting/Case.ViewportReporting/Data/clsSettings.vb:21— 2015/Case.ViewportReporting/Case.ViewportReporting/Data/clsSettings.vb:21-38 | 2016/Case.ViewportReporting/Case.ViewportReporting/Data/clsSettings.vb:21-38 | 2017/Case.ViewportReporting/Case.ViewportReporting/Data/clsSettings.vb:21-38 | 2018/Case.ViewportReporting/Case.ViewportReporting/Data/clsSettings.vb:21-38 — before extracting anything, compare `2015/Case.ViewportReporting/Case.ViewportReporting/Data/clsSettings.vb` and `2016/Case.ViewportReporting/Case.ViewportReporting/Data/clsSettings.vb` 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 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.
Duplicated block (18 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:413— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:413-430 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:413-430 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:413-430 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:413-430 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 610 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 (18 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Tag.vb:113— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Tag.vb:113-130 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Tag.vb:113-130 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Tag.vb:113-130 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Tag.vb:113-130 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Tag.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Tag.vb` 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 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.
Duplicated block (18 lines × 4) 2015/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Entry/app.vb:75— 2015/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Entry/app.vb:75-92 | 2016/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Entry/app.vb:75-92 | 2017/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Entry/app.vb:75-92 | 2018/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Entry/app.vb:75-92 — before extracting anything, compare `2015/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Entry/app.vb` and `2016/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Entry/app.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 93 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 (13 lines × 4) 2015/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnSettings.cs:83— 2015/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnSettings.cs:83-95 | 2016/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnSettings.cs:83-95 | 2017/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnSettings.cs:83-95 | 2018/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnSettings.cs:83-95 — before extracting anything, compare `2015/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnSettings.cs` and `2016/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnSettings.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. 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 (13 lines × 4) 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:300— 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:300-312 | 2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:300-312 | 2017/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:300-312 | 2018/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:300-312 — before extracting anything, compare `2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb` and `2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 323 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 (13 lines × 4) 2015/Case.Subs.SharedParameters/Case.Subs.SharedParameters/Data/clsSharedParameters.vb:161— 2015/Case.Subs.SharedParameters/Case.Subs.SharedParameters/Data/clsSharedParameters.vb:161-173 | 2016/Case.Subs.SharedParameters/Case.Subs.SharedParameters/Data/clsSharedParameters.vb:161-173 | 2017/Case.Subs.SharedParameters/Case.Subs.SharedParameters/Data/clsSharedParameters.vb:161-173 | 2018/Case.Subs.SharedParameters/Case.Subs.SharedParameters/Data/clsSharedParameters.vb:161-173 — before extracting anything, compare `2015/Case.Subs.SharedParameters/Case.Subs.SharedParameters/Data/clsSharedParameters.vb` and `2016/Case.Subs.SharedParameters/Case.Subs.SharedParameters/Data/clsSharedParameters.vb` 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. 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 (13 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsFile.vb:61— 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsFile.vb:61-73 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsFile.vb:61-73 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsFile.vb:61-73 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsFile.vb:61-73 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsFile.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsFile.vb` as WHOLE FILES: this scan already matched 4 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. 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 `2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsFile.vb:61` 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 × 4) 2015/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Data/clsSettings.vb:99— 2015/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Data/clsSettings.vb:99-111 | 2016/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Data/clsSettings.vb:99-111 | 2017/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Data/clsSettings.vb:99-111 | 2018/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Data/clsSettings.vb:99-111 — before extracting anything, compare `2015/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Data/clsSettings.vb` and `2016/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Data/clsSettings.vb` 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.
Duplicated block (13 lines × 4) 2015/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/UI/form_Main.vb:272— 2015/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/UI/form_Main.vb:272-284 | 2016/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/UI/form_Main.vb:272-284 | 2017/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/UI/form_Main.vb:272-284 | 2018/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/UI/form_Main.vb:272-284 — before extracting anything, compare `2015/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/UI/form_Main.vb` and `2016/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/UI/form_Main.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 214 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 (13 lines × 4) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/UI/form_ImportMain.xaml.vb:371— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/UI/form_ImportMain.xaml.vb:371-383 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/UI/form_ImportMain.xaml.vb:371-383 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/UI/form_ImportMain.xaml.vb:371-383 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/UI/form_ImportMain.xaml.vb:371-383 — before extracting anything, compare `2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/UI/form_ImportMain.xaml.vb` and `2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/UI/form_ImportMain.xaml.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 299 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 (13 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSettings.vb:253— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSettings.vb:253-265 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSettings.vb:253-265 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSettings.vb:253-265 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSettings.vb:253-265 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSettings.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 5 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. 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 (13 lines × 4) 2015/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb:35— 2015/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb:35-47 | 2016/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb:35-47 | 2017/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb:35-47 | 2018/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb:35-47 — before extracting anything, compare `2015/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb` and `2016/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 191 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 (13 lines × 4) 2015/Case.ObjectStyles/Case.ObjectStyles/Data/mnFamData.cs:78— 2015/Case.ObjectStyles/Case.ObjectStyles/Data/mnFamData.cs:78-90 | 2016/Case.ObjectStyles/Case.ObjectStyles/Data/mnFamData.cs:78-90 | 2017/Case.ObjectStyles/Case.ObjectStyles/Data/mnFamData.cs:78-90 | 2018/Case.ObjectStyles/Case.ObjectStyles/Data/mnFamData.cs:78-90 — before extracting anything, compare `2015/Case.ObjectStyles/Case.ObjectStyles/Data/mnFamData.cs` and `2016/Case.ObjectStyles/Case.ObjectStyles/Data/mnFamData.cs` as WHOLE FILES: this scan already matched 4 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. 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 (13 lines × 4) 2015/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnFamData.cs:73— 2015/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnFamData.cs:73-85 | 2016/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnFamData.cs:73-85 | 2017/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnFamData.cs:73-85 | 2018/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnFamData.cs:73-85 — before extracting anything, compare `2015/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnFamData.cs` and `2016/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnFamData.cs` as WHOLE FILES: this scan already matched 4 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. 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 (52 lines × 4) REDACTED:65— REDACTED:65-116 | REDACTED:65-116 | REDACTED:65-116 | REDACTED:65-116 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 421 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 (52 lines × 4) 2015/Case.ReportGroupsByView/Case.ReportGroupsByView/UI/form_Main.cs:38— 2015/Case.ReportGroupsByView/Case.ReportGroupsByView/UI/form_Main.cs:38-89 | 2016/Case.ReportGroupsByView/Case.ReportGroupsByView/UI/form_Main.cs:38-89 | 2017/Case.ReportGroupsByView/Case.ReportGroupsByView/UI/form_Main.cs:38-89 | 2018/Case.ReportGroupsByView/Case.ReportGroupsByView/UI/form_Main.cs:38-89 — before extracting anything, compare `2015/Case.ReportGroupsByView/Case.ReportGroupsByView/UI/form_Main.cs` and `2016/Case.ReportGroupsByView/Case.ReportGroupsByView/UI/form_Main.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 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 (52 lines × 4) 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSettings.vb:90— 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSettings.vb:90-141 | 2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSettings.vb:90-141 | 2017/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSettings.vb:90-141 | 2018/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSettings.vb:90-141 — before extracting anything, compare `2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSettings.vb` and `2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 97 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 (52 lines × 4) 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:195— 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:195-246 | 2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:195-246 | 2017/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:195-246 | 2018/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:195-246 — before extracting anything, compare `2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb` and `2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 323 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 (52 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:642— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:642-693 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:642-693 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:642-693 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:642-693 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 467 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 (52 lines × 4) 2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:366— 2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:366-417 | 2016/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:366-417 | 2017/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:366-417 | 2018/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:366-417 — before extracting anything, compare `2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb` and `2016/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb` as WHOLE FILES: this scan already matched 5 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. 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 (52 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:143— 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:143-194 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:143-194 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:143-194 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:143-194 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 267 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 (52 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ParameterConfigurationManager.xaml.vb:53— 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ParameterConfigurationManager.xaml.vb:53-104 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ParameterConfigurationManager.xaml.vb:53-104 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ParameterConfigurationManager.xaml.vb:53-104 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ParameterConfigurationManager.xaml.vb:53-104 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ParameterConfigurationManager.xaml.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ParameterConfigurationManager.xaml.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 169 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 (52 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsSettings.vb:412— 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsSettings.vb:412-463 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsSettings.vb:412-463 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsSettings.vb:412-463 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsSettings.vb:412-463 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsSettings.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsSettings.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 175 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 (52 lines × 4) 2015/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Form/form_Main.vb:216— 2015/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Form/form_Main.vb:216-267 | 2016/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Form/form_Main.vb:216-267 | 2017/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Form/form_Main.vb:216-267 | 2018/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Form/form_Main.vb:216-267 — before extracting anything, compare `2015/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Form/form_Main.vb` and `2016/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Form/form_Main.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 215 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 (35 lines × 4) 2015/Case.DimensionOverrides/Case.DimensionOverrides/Data/clsSettings.cs:55— 2015/Case.DimensionOverrides/Case.DimensionOverrides/Data/clsSettings.cs:55-89 | 2016/Case.DimensionOverrides/Case.DimensionOverrides/Data/clsSettings.cs:55-89 | 2017/Case.DimensionOverrides/Case.DimensionOverrides/Data/clsSettings.cs:55-89 | 2018/Case.DimensionOverrides/Case.DimensionOverrides/Data/clsSettings.cs:50-84 — before extracting anything, compare `2015/Case.DimensionOverrides/Case.DimensionOverrides/Data/clsSettings.cs` and `2016/Case.DimensionOverrides/Case.DimensionOverrides/Data/clsSettings.cs` as WHOLE FILES: 98% 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 (35 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F2.vb:44— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F2.vb:44-78 | 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F4.vb:42-76 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F2.vb:44-78 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F4.vb:42-76 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F2.vb` and `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F4.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 123 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the 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 (35 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F1.vb:40— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F1.vb:40-74 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F1.vb:40-74 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F1.vb:40-74 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F1.vb:40-74 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F1.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F1.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 76 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 (35 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb:463— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb:463-497 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb:463-497 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb:463-497 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb:463-497 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 291 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 (35 lines × 4) 2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Entry/CEB749CFCF844AE8B76F40E3EBAA2FF7.vb:35— 2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Entry/CEB749CFCF844AE8B76F40E3EBAA2FF7.vb:35-69 | 2016/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Entry/CEB749CFCF844AE8B76F40E3EBAA2FF7.vb:35-69 | 2017/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Entry/CEB749CFCF844AE8B76F40E3EBAA2FF7.vb:35-69 | 2018/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Entry/CEB749CFCF844AE8B76F40E3EBAA2FF7.vb:35-69 — before extracting anything, compare `2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Entry/CEB749CFCF844AE8B76F40E3EBAA2FF7.vb` and `2016/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Entry/CEB749CFCF844AE8B76F40E3EBAA2FF7.vb` as WHOLE FILES: 96% 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. Read the line range as the matched WINDOW rather than a finished unit: at `2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Entry/CEB749CFCF844AE8B76F40E3EBAA2FF7.vb:35` 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 (35 lines × 4) 2015/Case.Export.Families/Case.Export.Families/Forms/form_Familes.vb:53— 2015/Case.Export.Families/Case.Export.Families/Forms/form_Familes.vb:53-87 | 2016/Case.Export.Families/Case.Export.Families/Forms/form_Familes.vb:53-87 | 2017/Case.Export.Families/Case.Export.Families/Forms/form_Familes.vb:53-87 | 2018/Case.Export.Families/Case.Export.Families/Forms/form_Familes.vb:53-87 — before extracting anything, compare `2015/Case.Export.Families/Case.Export.Families/Forms/form_Familes.vb` and `2016/Case.Export.Families/Case.Export.Families/Forms/form_Familes.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 93 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 `2015/Case.Export.Families/Case.Export.Families/Forms/form_Familes.vb: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.
Duplicated block (35 lines × 4) 2015/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb:448— 2015/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb:448-482 | 2016/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb:448-482 | 2017/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb:448-482 | 2018/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb:449-483 — before extracting anything, compare `2015/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb` and `2016/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 364 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 (35 lines × 4) 2015/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:313— 2015/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:313-347 | 2016/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:313-347 | 2017/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:313-347 | 2018/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:313-347 — before extracting anything, compare `2015/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb` and `2016/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 245 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 (35 lines × 4) 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F2.vb:44— 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F2.vb:44-78 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F4.vb:42-76 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F2.vb:44-78 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F4.vb:42-76 — before extracting anything, compare `2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F2.vb` and `2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F4.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 123 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the 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 (35 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategory.vb:27— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategory.vb:27-61 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategory.vb:27-61 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategory.vb:27-61 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategory.vb:27-61 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategory.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategory.vb` 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.
Duplicated block (31 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F4.vb:66— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F4.vb:66-96 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F4.vb:66-96 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F4.vb:66-96 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F4.vb:66-96 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F4.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F4.vb` as WHOLE FILES: this scan already matched 4 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.
Duplicated block (31 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:343— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:343-373 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:343-373 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:343-373 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:343-373 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 402 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 (31 lines × 4) 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb:286— 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb:286-316 | 2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb:286-316 | 2017/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb:286-316 | 2018/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb:286-316 — before extracting anything, compare `2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb` and `2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 7 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. 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 (31 lines × 4) 2015/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:275— 2015/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:275-305 | 2016/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:275-305 | 2017/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:275-305 | 2018/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:275-305 — before extracting anything, compare `2015/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb` and `2016/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 201 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 (31 lines × 4) 2015/Case.BasicReporting/Case.BasicReporting/Data/clsHosts.vb:31— 2015/Case.BasicReporting/Case.BasicReporting/Data/clsHosts.vb:31-61 | 2016/Case.BasicReporting/Case.BasicReporting/Data/clsHosts.vb:31-61 | 2017/Case.BasicReporting/Case.BasicReporting/Data/clsHosts.vb:31-61 | 2018/Case.BasicReporting/Case.BasicReporting/Data/clsHosts.vb:31-61 — before extracting anything, compare `2015/Case.BasicReporting/Case.BasicReporting/Data/clsHosts.vb` and `2016/Case.BasicReporting/Case.BasicReporting/Data/clsHosts.vb` 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 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.
Duplicated block (31 lines × 4) 2015/Case.Directionality/Case.Directionality/Data/clsExternalWalls.vb:88— 2015/Case.Directionality/Case.Directionality/Data/clsExternalWalls.vb:88-118 | 2016/Case.Directionality/Case.Directionality/Data/clsExternalWalls.vb:88-118 | 2017/Case.Directionality/Case.Directionality/Data/clsExternalWalls.vb:88-118 | 2018/Case.Directionality/Case.Directionality/Data/clsExternalWalls.vb:88-118 — before extracting anything, compare `2015/Case.Directionality/Case.Directionality/Data/clsExternalWalls.vb` and `2016/Case.Directionality/Case.Directionality/Data/clsExternalWalls.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 252 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 (31 lines × 4) 2015/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Entry/CmdMain.vb:36— 2015/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Entry/CmdMain.vb:36-66 | 2016/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Entry/CmdMain.vb:36-66 | 2017/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Entry/CmdMain.vb:36-66 | 2018/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Entry/CmdMain.vb:36-66 — before extracting anything, compare `2015/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Entry/CmdMain.vb` and `2016/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Entry/CmdMain.vb` as WHOLE FILES: 96% 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. Read the line range as the matched WINDOW rather than a finished unit: at `2015/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Entry/CmdMain.vb:36` 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 (31 lines × 4) 2015/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:39— 2015/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:39-69 | 2016/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:39-69 | 2017/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:39-69 | 2018/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:39-69 — before extracting anything, compare `2015/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb` and `2016/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 173 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 (31 lines × 4) 2015/Case.ParallelWalls/Case.ParallelWalls/Data/clsVectors.cs:77— 2015/Case.ParallelWalls/Case.ParallelWalls/Data/clsVectors.cs:77-107 | 2016/Case.ParallelWalls/Case.ParallelWalls/Data/clsVectors.cs:77-107 | 2017/Case.ParallelWalls/Case.ParallelWalls/Data/clsVectors.cs:77-107 | 2018/Case.ParallelWalls/Case.ParallelWalls/Data/clsVectors.cs:72-102 — before extracting anything, compare `2015/Case.ParallelWalls/Case.ParallelWalls/Data/clsVectors.cs` and `2016/Case.ParallelWalls/Case.ParallelWalls/Data/clsVectors.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 55 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 (31 lines × 4) 2015/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Events/clsSWC.vb:25— 2015/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Events/clsSWC.vb:25-55 | 2016/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Events/clsSWC.vb:25-55 | 2017/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Events/clsSWC.vb:25-55 | 2018/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Events/clsSWC.vb:25-55 — before extracting anything, compare `2015/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Events/clsSWC.vb` and `2016/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/Events/clsSWC.vb` 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.
Duplicated block (14 lines × 4) REDACTED:146— REDACTED:146-159 | REDACTED:146-159 | REDACTED:146-159 | REDACTED:142-155 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 264 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 (14 lines × 4) 2015/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb:117— 2015/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb:117-130 | 2016/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb:117-130 | 2017/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb:117-130 | 2018/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb:117-130 — before extracting anything, compare `2015/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb` and `2016/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 364 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 (14 lines × 4) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/OpenNURBS/clsONSort.vb:324— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/OpenNURBS/clsONSort.vb:324-337 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/OpenNURBS/clsONSort.vb:324-337 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/OpenNURBS/clsONSort.vb:324-337 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/OpenNURBS/clsONSort.vb:324-337 — before extracting anything, compare `2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/OpenNURBS/clsONSort.vb` and `2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/OpenNURBS/clsONSort.vb` 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 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.
Duplicated block (14 lines × 4) 2015/Case.Export.Families/Case.Export.Families/Forms/form_Familes.vb:205— 2015/Case.Export.Families/Case.Export.Families/Forms/form_Familes.vb:205-218 | 2016/Case.Export.Families/Case.Export.Families/Forms/form_Familes.vb:205-218 | 2017/Case.Export.Families/Case.Export.Families/Forms/form_Familes.vb:205-218 | 2018/Case.Export.Families/Case.Export.Families/Forms/form_Familes.vb:205-218 — before extracting anything, compare `2015/Case.Export.Families/Case.Export.Families/Forms/form_Familes.vb` and `2016/Case.Export.Families/Case.Export.Families/Forms/form_Familes.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 93 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 (14 lines × 4) 2015/Case.Navis2BCF/Case.Navis2BCF/CASERibbon.cs:10— 2015/Case.Navis2BCF/Case.Navis2BCF/CASERibbon.cs:10-23 | 2016/Case.Navis2BCF/Case.Navis2BCF/CASERibbon.cs:10-23 | 2017/Case.Navis2BCF/Case.Navis2BCF/CASERibbon.cs:10-23 | 2018/Case.Navis2BCF/Case.Navis2BCF/CASERibbon.cs:10-23 — before extracting anything, compare `2015/Case.Navis2BCF/Case.Navis2BCF/CASERibbon.cs` and `2016/Case.Navis2BCF/Case.Navis2BCF/CASERibbon.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 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. Read the line range as the matched WINDOW rather than a finished unit: at `2015/Case.Navis2BCF/Case.Navis2BCF/CASERibbon.cs:10` 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) 2015/Case.Navis2BCF/Case.Navis2BCF/IfcGuid.cs:144— 2015/Case.Navis2BCF/Case.Navis2BCF/IfcGuid.cs:144-157 | 2016/Case.Navis2BCF/Case.Navis2BCF/IfcGuid.cs:144-157 | 2017/Case.Navis2BCF/Case.Navis2BCF/IfcGuid.cs:144-157 | 2018/Case.Navis2BCF/Case.Navis2BCF/IfcGuid.cs:144-157 — before extracting anything, compare `2015/Case.Navis2BCF/Case.Navis2BCF/IfcGuid.cs` and `2016/Case.Navis2BCF/Case.Navis2BCF/IfcGuid.cs` as WHOLE FILES: this scan already matched 5 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. 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 `2015/Case.Navis2BCF/Case.Navis2BCF/IfcGuid.cs:144` 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 (14 lines × 4) 2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:127— 2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:127-140 | 2016/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:127-140 | 2017/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:127-140 | 2018/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:127-140 — before extracting anything, compare `2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb` and `2016/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 323 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 (14 lines × 4) 2015/Case.Directionality/Case.Directionality/UI/form_Main.vb:19— 2015/Case.Directionality/Case.Directionality/UI/form_Main.vb:19-32 | 2016/Case.Directionality/Case.Directionality/UI/form_Main.vb:19-32 | 2017/Case.Directionality/Case.Directionality/UI/form_Main.vb:19-32 | 2018/Case.Directionality/Case.Directionality/UI/form_Main.vb:19-32 — before extracting anything, compare `2015/Case.Directionality/Case.Directionality/UI/form_Main.vb` and `2016/Case.Directionality/Case.Directionality/UI/form_Main.vb` 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 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.
Duplicated block (14 lines × 4) 2015/Case.ModeledRoomTags/Case.ModeledRoomTags/UI/form_Main.vb:74— 2015/Case.ModeledRoomTags/Case.ModeledRoomTags/UI/form_Main.vb:74-87 | 2016/Case.ModeledRoomTags/Case.ModeledRoomTags/UI/form_Main.vb:74-87 | 2017/Case.ModeledRoomTags/Case.ModeledRoomTags/UI/form_Main.vb:74-87 | 2018/Case.ModeledRoomTags/Case.ModeledRoomTags/UI/form_Main.vb:74-87 — before extracting anything, compare `2015/Case.ModeledRoomTags/Case.ModeledRoomTags/UI/form_Main.vb` and `2016/Case.ModeledRoomTags/Case.ModeledRoomTags/UI/form_Main.vb` as WHOLE FILES: this scan already matched 3 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. 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 (14 lines × 4) 2015/Case.RevClouds/Case.RevClouds/Data/clsSettings.vb:36— 2015/Case.RevClouds/Case.RevClouds/Data/clsSettings.vb:36-49 | 2016/Case.RevClouds/Case.RevClouds/Data/clsSettings.vb:36-49 | 2017/Case.RevClouds/Case.RevClouds/Data/clsSettings.vb:36-49 | 2018/Case.RevClouds/Case.RevClouds/Data/clsSettings.vb:36-49 — before extracting anything, compare `2015/Case.RevClouds/Case.RevClouds/Data/clsSettings.vb` and `2016/Case.RevClouds/Case.RevClouds/Data/clsSettings.vb` 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 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.
Duplicated block (5 lines × 4) REDACTED:550— REDACTED:550-554 | REDACTED:550-554 | REDACTED:550-554 | REDACTED:550-554 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 421 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:550` 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 (5 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:472— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:472-476 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:472-476 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:472-476 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:472-476 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 610 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 (5 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:454— 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:454-458 | 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:468-472 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:454-458 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:468-472 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 267 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 (5 lines × 4) 2015/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb:16— 2015/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb:16-20 | 2016/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb:16-20 | 2017/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb:16-20 | 2018/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb:16-20 — before extracting anything, compare `2015/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb` and `2016/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 150 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 (5 lines × 4) 2015/Case.ObjectStyles/Case.ObjectStyles/Data/mnData.cs:38— 2015/Case.ObjectStyles/Case.ObjectStyles/Data/mnData.cs:38-42 | 2016/Case.ObjectStyles/Case.ObjectStyles/Data/mnData.cs:38-42 | 2017/Case.ObjectStyles/Case.ObjectStyles/Data/mnData.cs:38-42 | 2018/Case.ObjectStyles/Case.ObjectStyles/Data/mnData.cs:38-42 — before extracting anything, compare `2015/Case.ObjectStyles/Case.ObjectStyles/Data/mnData.cs` and `2016/Case.ObjectStyles/Case.ObjectStyles/Data/mnData.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. 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) REDACTED:99— REDACTED:99-103 | REDACTED:99-103 | REDACTED:99-103 | REDACTED:99-103 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 147 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) REDACTED:274— REDACTED:274-278 | REDACTED:274-278 | REDACTED:274-278 | REDACTED:274-278 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 147 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) 2015/Case.ParallelWalls/Case.ParallelWalls/Data/clsVectors.cs:177— 2015/Case.ParallelWalls/Case.ParallelWalls/Data/clsVectors.cs:177-181 | 2016/Case.ParallelWalls/Case.ParallelWalls/Data/clsVectors.cs:177-181 | 2017/Case.ParallelWalls/Case.ParallelWalls/Data/clsVectors.cs:177-181 | 2018/Case.ParallelWalls/Case.ParallelWalls/Data/clsVectors.cs:172-176 — before extracting anything, compare `2015/Case.ParallelWalls/Case.ParallelWalls/Data/clsVectors.cs` and `2016/Case.ParallelWalls/Case.ParallelWalls/Data/clsVectors.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 55 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 (5 lines × 4) 2015/Case.Subs.KeyMatcher/Utility/clsGlobals.cs:83— 2015/Case.Subs.KeyMatcher/Utility/clsGlobals.cs:83-87 | 2016/Case.Subs.KeyMatcher/Utility/clsGlobals.cs:83-87 | 2017/Case.Subs.KeyMatcher/Utility/clsGlobals.cs:83-87 | 2018/Case.Subs.KeyMatcher/Utility/clsGlobals.cs:83-87 — before extracting anything, compare `2015/Case.Subs.KeyMatcher/Utility/clsGlobals.cs` and `2016/Case.Subs.KeyMatcher/Utility/clsGlobals.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 115 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 (5 lines × 4) 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:454— 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:454-458 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:468-472 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:454-458 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:468-472 — before extracting anything, compare `2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb` and `2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 267 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 (49 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb:655— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb:655-703 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb:655-703 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb:655-703 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb:655-703 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 291 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 (49 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:774— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:774-822 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:774-822 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:774-822 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:774-822 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 281 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 (49 lines × 4) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:189— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:189-237 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:189-237 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:189-237 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:189-237 — before extracting anything, compare `2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb` and `2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 257 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 (49 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSettings.vb:453— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSettings.vb:453-501 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSettings.vb:453-501 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSettings.vb:453-501 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSettings.vb:453-501 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSettings.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 5 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. 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 (49 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb:47— 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb:47-95 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb:47-95 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb:47-95 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb:47-95 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 274 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 (49 lines × 4) 2015/Case.ImageToDraftingView/Case.ImageToDraftingView/Forms/form_Main.vb:149— 2015/Case.ImageToDraftingView/Case.ImageToDraftingView/Forms/form_Main.vb:149-197 | 2016/Case.ImageToDraftingView/Case.ImageToDraftingView/Forms/form_Main.vb:149-197 | 2017/Case.ImageToDraftingView/Case.ImageToDraftingView/Forms/form_Main.vb:149-197 | 2018/Case.ImageToDraftingView/Case.ImageToDraftingView/Forms/form_Main.vb:149-197 — before extracting anything, compare `2015/Case.ImageToDraftingView/Case.ImageToDraftingView/Forms/form_Main.vb` and `2016/Case.ImageToDraftingView/Case.ImageToDraftingView/Forms/form_Main.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 155 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 (49 lines × 4) 2015/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb:29— 2015/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb:29-77 | 2016/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb:29-77 | 2017/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb:29-77 | 2018/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb:29-77 — before extracting anything, compare `2015/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb` and `2016/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 150 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 (49 lines × 4) 2015/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb:411— 2015/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb:411-459 | 2016/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb:411-459 | 2017/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb:411-459 | 2018/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb:411-459 — before extracting anything, compare `2015/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb` and `2016/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 191 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 (49 lines × 4) 2015/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsRoomTagInfo.vb:232— 2015/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsRoomTagInfo.vb:232-280 | 2016/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsRoomTagInfo.vb:232-280 | 2017/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsRoomTagInfo.vb:232-280 | 2018/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsRoomTagInfo.vb:232-280 — before extracting anything, compare `2015/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsRoomTagInfo.vb` and `2016/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsRoomTagInfo.vb` as WHOLE FILES: this scan already matched 5 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.
Duplicated block (33 lines × 4) 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsElementsByCategory.vb:90— 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsElementsByCategory.vb:90-122 | 2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsElementsByCategory.vb:90-122 | 2017/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsElementsByCategory.vb:90-122 | 2018/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsElementsByCategory.vb:90-122 — before extracting anything, compare `2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsElementsByCategory.vb` and `2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsElementsByCategory.vb` 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 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.
Duplicated block (33 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb:285— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb:285-317 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb:285-317 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb:285-317 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb:285-317 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 291 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 (33 lines × 4) 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_Parameters.vb:111— 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_Parameters.vb:111-143 | 2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_Parameters.vb:111-143 | 2017/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_Parameters.vb:111-143 | 2018/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_Parameters.vb:111-143 — before extracting anything, compare `2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_Parameters.vb` and `2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_Parameters.vb` 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 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.
Duplicated block (33 lines × 4) 2015/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsSettings.vb:262— 2015/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsSettings.vb:262-294 | 2016/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsSettings.vb:262-294 | 2017/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsSettings.vb:262-294 | 2018/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsSettings.vb:262-294 — before extracting anything, compare `2015/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsSettings.vb` and `2016/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 149 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 (33 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:254— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:254-286 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:254-286 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:254-286 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:254-286 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 330 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 (33 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:323— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:323-355 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:323-355 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:323-355 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:323-355 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 330 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 (33 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:407— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:407-439 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:407-439 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:407-439 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:407-439 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 330 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 (33 lines × 4) 2015/Case.ApplySysOrient/UI/form_Orient.cs:23— 2015/Case.ApplySysOrient/UI/form_Orient.cs:23-55 | 2016/Case.ApplySysOrient/UI/form_Orient.cs:23-55 | 2017/Case.ApplySysOrient/UI/form_Orient.cs:23-55 | 2018/Case.ApplySysOrient/UI/form_Orient.cs:23-55 — before extracting anything, compare `2015/Case.ApplySysOrient/UI/form_Orient.cs` and `2016/Case.ApplySysOrient/UI/form_Orient.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.
Duplicated block (33 lines × 4) 2015/Case.Subs.KeyMatcher/Data/clsSettings.cs:40— 2015/Case.Subs.KeyMatcher/Data/clsSettings.cs:40-72 | 2016/Case.Subs.KeyMatcher/Data/clsSettings.cs:40-72 | 2017/Case.Subs.KeyMatcher/Data/clsSettings.cs:40-72 | 2018/Case.Subs.KeyMatcher/Data/clsSettings.cs:40-72 — before extracting anything, compare `2015/Case.Subs.KeyMatcher/Data/clsSettings.cs` and `2016/Case.Subs.KeyMatcher/Data/clsSettings.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.
Duplicated block (28 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:291— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:291-318 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:291-318 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:291-318 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:291-318 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 330 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 (28 lines × 4) 2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:728— 2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:728-755 | 2016/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:728-755 | 2017/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:728-755 | 2018/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:728-755 — before extracting anything, compare `2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb` and `2016/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb` as WHOLE FILES: this scan already matched 5 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. 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 (28 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsConfiguration.vb:183— 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsConfiguration.vb:183-210 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsConfiguration.vb:183-210 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsConfiguration.vb:183-210 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsConfiguration.vb:183-210 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsConfiguration.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsConfiguration.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 115 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 (28 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb:55— 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb:55-82 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb:55-82 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb:55-82 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb:55-82 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 221 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 (28 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsFile.vb:132— 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsFile.vb:132-159 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsFile.vb:132-159 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsFile.vb:132-159 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsFile.vb:132-159 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsFile.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsFile.vb` as WHOLE FILES: this scan already matched 4 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. 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 (28 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:74— 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:74-101 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:74-101 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:74-101 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:74-101 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 317 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 (28 lines × 4) 2015/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Forms/form_Main.vb:240— 2015/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Forms/form_Main.vb:240-267 | 2016/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Forms/form_Main.vb:240-267 | 2017/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Forms/form_Main.vb:240-267 | 2018/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Forms/form_Main.vb:237-264 — before extracting anything, compare `2015/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Forms/form_Main.vb` and `2016/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Forms/form_Main.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 137 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `2015/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Forms/form_Main.vb:238` calls `RecordUsage` and `2018/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Forms/form_Main.vb:235` 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 (28 lines × 4) 2015/Case.LineChanger/Case.LineChanger/Forms/form_Main.vb:32— 2015/Case.LineChanger/Case.LineChanger/Forms/form_Main.vb:32-59 | 2016/Case.LineChanger/Case.LineChanger/Forms/form_Main.vb:32-59 | 2017/Case.LineChanger/Case.LineChanger/Forms/form_Main.vb:32-59 | 2018/Case.LineChanger/Case.LineChanger/Forms/form_Main.vb:32-59 — before extracting anything, compare `2015/Case.LineChanger/Case.LineChanger/Forms/form_Main.vb` and `2016/Case.LineChanger/Case.LineChanger/Forms/form_Main.vb` 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 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.
Duplicated block (28 lines × 4) 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsViewType.vb:53— 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsViewType.vb:53-80 | 2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsViewType.vb:53-80 | 2017/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsViewType.vb:53-80 | 2018/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsViewType.vb:53-80 — before extracting anything, compare `2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsViewType.vb` and `2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsViewType.vb` 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.
Duplicated block (15 lines × 4) 2015/Case.Navis2BCF/Case.Navis2BCF/IfcGuid.cs:42— 2015/Case.Navis2BCF/Case.Navis2BCF/IfcGuid.cs:42-56 | 2016/Case.Navis2BCF/Case.Navis2BCF/IfcGuid.cs:42-56 | 2017/Case.Navis2BCF/Case.Navis2BCF/IfcGuid.cs:42-56 | 2018/Case.Navis2BCF/Case.Navis2BCF/IfcGuid.cs:42-56 — before extracting anything, compare `2015/Case.Navis2BCF/Case.Navis2BCF/IfcGuid.cs` and `2016/Case.Navis2BCF/Case.Navis2BCF/IfcGuid.cs` as WHOLE FILES: this scan already matched 5 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. 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 (15 lines × 4) REDACTED:172— REDACTED:172-186 | REDACTED:172-186 | REDACTED:172-186 | REDACTED:172-186 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 421 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 (15 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb:51— 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb:51-65 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb:51-65 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb:51-65 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb:51-65 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 149 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 (15 lines × 4) REDACTED:24— REDACTED:24-38 | REDACTED:24-38 | REDACTED:24-38 | REDACTED:24-38 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 421 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:24` 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 × 4) 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_Parameters.vb:154— 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_Parameters.vb:154-168 | 2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_Parameters.vb:154-168 | 2017/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_Parameters.vb:154-168 | 2018/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_Parameters.vb:154-168 — before extracting anything, compare `2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_Parameters.vb` and `2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_Parameters.vb` 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 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.
Duplicated block (15 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:202— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:202-216 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:202-216 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:202-216 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:202-216 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb` as WHOLE FILES: this scan already matched 10 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. 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 (15 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:438— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:438-452 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:438-452 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:438-452 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:438-452 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb` as WHOLE FILES: this scan already matched 10 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. 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 (15 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsViews.vb:155— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsViews.vb:155-169 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsViews.vb:155-169 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsViews.vb:155-169 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsViews.vb:155-169 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsViews.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsViews.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 68 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 (15 lines × 4) 2015/Case.ParallelWalls/Case.ParallelWalls/Data/clsWallTransform.cs:65— 2015/Case.ParallelWalls/Case.ParallelWalls/Data/clsWallTransform.cs:65-79 | 2016/Case.ParallelWalls/Case.ParallelWalls/Data/clsWallTransform.cs:65-79 | 2017/Case.ParallelWalls/Case.ParallelWalls/Data/clsWallTransform.cs:65-79 | 2018/Case.ParallelWalls/Case.ParallelWalls/Data/clsWallTransform.cs:60-74 — before extracting anything, compare `2015/Case.ParallelWalls/Case.ParallelWalls/Data/clsWallTransform.cs` and `2016/Case.ParallelWalls/Case.ParallelWalls/Data/clsWallTransform.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 56 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.
form_Main.RefreshViewList (cyclomatic 20) 2015/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/UI/form_Main.vb:185— form_Main.RefreshViewList has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Main.RefreshViewList (cyclomatic 20) 2015/Case.MultiViewDuplicate/Case.MultiViewDuplicate/UI/form_Main.vb:176— form_Main.RefreshViewList has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Main.RefreshViewList (cyclomatic 20) 2016/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/UI/form_Main.vb:185— form_Main.RefreshViewList has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Main.RefreshViewList (cyclomatic 20) 2016/Case.MultiViewDuplicate/Case.MultiViewDuplicate/UI/form_Main.vb:176— form_Main.RefreshViewList has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Main.RefreshViewList (cyclomatic 20) 2017/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/UI/form_Main.vb:185— form_Main.RefreshViewList has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Main.RefreshViewList (cyclomatic 20) 2017/Case.MultiViewDuplicate/Case.MultiViewDuplicate/UI/form_Main.vb:176— form_Main.RefreshViewList has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Main.RefreshViewList (cyclomatic 20) 2018/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/UI/form_Main.vb:185— form_Main.RefreshViewList has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Main.RefreshViewList (cyclomatic 20) 2018/Case.MultiViewDuplicate/Case.MultiViewDuplicate/UI/form_Main.vb:176— form_Main.RefreshViewList has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsSettings.ChangeIfMatch (cyclomatic 17) 2015/Case.Subs.Linestyles/Case.Subs.Linestyles/Data/clsSettings.vb:125— clsSettings.ChangeIfMatch has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsSettings.ChangeIfMatch (cyclomatic 17) 2015/Case.LineChanger/Case.LineChanger/Data/clsSettings.vb:197— clsSettings.ChangeIfMatch has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsSettings.ChangeIfMatch (cyclomatic 17) 2016/Case.Subs.Linestyles/Case.Subs.Linestyles/Data/clsSettings.vb:125— clsSettings.ChangeIfMatch has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsSettings.ChangeIfMatch (cyclomatic 17) 2016/Case.LineChanger/Case.LineChanger/Data/clsSettings.vb:197— clsSettings.ChangeIfMatch has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsSettings.ChangeIfMatch (cyclomatic 17) 2017/Case.Subs.Linestyles/Case.Subs.Linestyles/Data/clsSettings.vb:125— clsSettings.ChangeIfMatch has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsSettings.ChangeIfMatch (cyclomatic 17) 2017/Case.LineChanger/Case.LineChanger/Data/clsSettings.vb:197— clsSettings.ChangeIfMatch has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsSettings.ChangeIfMatch (cyclomatic 17) 2018/Case.Subs.Linestyles/Case.Subs.Linestyles/Data/clsSettings.vb:125— clsSettings.ChangeIfMatch has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsSettings.ChangeIfMatch (cyclomatic 17) 2018/Case.LineChanger/Case.LineChanger/Data/clsSettings.vb:197— clsSettings.ChangeIfMatch has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Main.RefreshViewList (cognitive 44) 2015/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/UI/form_Main.vb:185— form_Main.RefreshViewList has cognitive complexity 44 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.RefreshViewList (cognitive 44) 2015/Case.MultiViewDuplicate/Case.MultiViewDuplicate/UI/form_Main.vb:176— form_Main.RefreshViewList has cognitive complexity 44 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.RefreshViewList (cognitive 44) 2016/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/UI/form_Main.vb:185— form_Main.RefreshViewList has cognitive complexity 44 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.RefreshViewList (cognitive 44) 2016/Case.MultiViewDuplicate/Case.MultiViewDuplicate/UI/form_Main.vb:176— form_Main.RefreshViewList has cognitive complexity 44 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.RefreshViewList (cognitive 44) 2017/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/UI/form_Main.vb:185— form_Main.RefreshViewList has cognitive complexity 44 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.RefreshViewList (cognitive 44) 2017/Case.MultiViewDuplicate/Case.MultiViewDuplicate/UI/form_Main.vb:176— form_Main.RefreshViewList has cognitive complexity 44 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.RefreshViewList (cognitive 44) 2018/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/UI/form_Main.vb:185— form_Main.RefreshViewList has cognitive complexity 44 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.RefreshViewList (cognitive 44) 2018/Case.MultiViewDuplicate/Case.MultiViewDuplicate/UI/form_Main.vb:176— form_Main.RefreshViewList has cognitive complexity 44 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.ChangeIfMatch (cognitive 24) 2015/Case.Subs.Linestyles/Case.Subs.Linestyles/Data/clsSettings.vb:125— clsSettings.ChangeIfMatch has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.ChangeIfMatch (cognitive 24) 2015/Case.LineChanger/Case.LineChanger/Data/clsSettings.vb:197— clsSettings.ChangeIfMatch has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.ChangeIfMatch (cognitive 24) 2016/Case.Subs.Linestyles/Case.Subs.Linestyles/Data/clsSettings.vb:125— clsSettings.ChangeIfMatch has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.ChangeIfMatch (cognitive 24) 2016/Case.LineChanger/Case.LineChanger/Data/clsSettings.vb:197— clsSettings.ChangeIfMatch has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.ChangeIfMatch (cognitive 24) 2017/Case.Subs.Linestyles/Case.Subs.Linestyles/Data/clsSettings.vb:125— clsSettings.ChangeIfMatch has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.ChangeIfMatch (cognitive 24) 2017/Case.LineChanger/Case.LineChanger/Data/clsSettings.vb:197— clsSettings.ChangeIfMatch has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.ChangeIfMatch (cognitive 24) 2018/Case.Subs.Linestyles/Case.Subs.Linestyles/Data/clsSettings.vb:125— clsSettings.ChangeIfMatch has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.ChangeIfMatch (cognitive 24) 2018/Case.LineChanger/Case.LineChanger/Data/clsSettings.vb:197— clsSettings.ChangeIfMatch has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Duplicated block (43 lines × 4) REDACTED:68— REDACTED:68-110 | REDACTED:68-110 | REDACTED:68-110 | REDACTED:63-105 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 123 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:68` 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 (43 lines × 4) 2015/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsExcel.vb:339— 2015/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsExcel.vb:339-381 | 2016/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsExcel.vb:339-381 | 2017/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsExcel.vb:339-381 | 2018/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsExcel.vb:339-381 — before extracting anything, compare `2015/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsExcel.vb` and `2016/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsExcel.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 187 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 `2015/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsExcel.vb:339` 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 (43 lines × 4) 2015/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:184— 2015/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:184-226 | 2016/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:184-226 | 2017/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:184-226 | 2018/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:184-226 — before extracting anything, compare `2015/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb` and `2016/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 201 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 (43 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb:219— 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb:219-261 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb:219-261 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb:219-261 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb:219-261 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 149 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 (43 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsSettings.vb:96— 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsSettings.vb:96-138 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsSettings.vb:96-138 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsSettings.vb:96-138 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsSettings.vb:96-138 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsSettings.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsSettings.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 175 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 (43 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsSettings.vb:152— 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsSettings.vb:152-194 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsSettings.vb:152-194 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsSettings.vb:152-194 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsSettings.vb:152-194 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsSettings.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsSettings.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 175 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 (43 lines × 4) 2015/Case.RevClouds/Case.RevClouds/UI/form_RevisionClouds.vb:97— 2015/Case.RevClouds/Case.RevClouds/UI/form_RevisionClouds.vb:97-139 | 2016/Case.RevClouds/Case.RevClouds/UI/form_RevisionClouds.vb:97-139 | 2017/Case.RevClouds/Case.RevClouds/UI/form_RevisionClouds.vb:97-139 | 2018/Case.RevClouds/Case.RevClouds/UI/form_RevisionClouds.vb:92-134 — before extracting anything, compare `2015/Case.RevClouds/Case.RevClouds/UI/form_RevisionClouds.vb` and `2016/Case.RevClouds/Case.RevClouds/UI/form_RevisionClouds.vb` 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 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.
Duplicated block (43 lines × 4) REDACTED:372— REDACTED:372-414 | REDACTED:372-414 | REDACTED:372-414 | REDACTED:368-410 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 264 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:372` 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. 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 (42 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb:189— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb:189-230 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb:189-230 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb:189-230 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb:189-230 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 109 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 (42 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:967— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:967-1008 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:967-1008 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:967-1008 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:967-1008 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 610 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 `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:967` 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 (42 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:422— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:422-463 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:422-463 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:422-463 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:422-463 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 422 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 (42 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb:509— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb:509-550 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb:509-550 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb:509-550 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb:509-550 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 291 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 (42 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:506— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:506-547 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:506-547 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:506-547 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:506-547 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb` as WHOLE FILES: this scan already matched 10 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. 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 (42 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsFile.vb:76— 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsFile.vb:76-117 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsFile.vb:76-117 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsFile.vb:76-117 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsFile.vb:76-117 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsFile.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsFile.vb` as WHOLE FILES: this scan already matched 4 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. 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 `2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsFile.vb:76` 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 (42 lines × 4) 2015/Case.SharedParameters/Case.SharedParameters/Data/clsSharedParameters.vb:132— 2015/Case.SharedParameters/Case.SharedParameters/Data/clsSharedParameters.vb:132-173 | 2016/Case.SharedParameters/Case.SharedParameters/Data/clsSharedParameters.vb:132-173 | 2017/Case.SharedParameters/Case.SharedParameters/Data/clsSharedParameters.vb:132-173 | 2018/Case.SharedParameters/Case.SharedParameters/Data/clsSharedParameters.vb:132-173 — before extracting anything, compare `2015/Case.SharedParameters/Case.SharedParameters/Data/clsSharedParameters.vb` and `2016/Case.SharedParameters/Case.SharedParameters/Data/clsSharedParameters.vb` 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 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.
Duplicated block (42 lines × 4) 2015/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:123— 2015/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:123-164 | 2016/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:123-164 | 2017/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:123-164 | 2018/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:123-164 — before extracting anything, compare `2015/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb` and `2016/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 245 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 (39 lines × 4) REDACTED:411— REDACTED:411-449 | REDACTED:411-449 | REDACTED:411-449 | REDACTED:411-449 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 421 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:411` 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 (39 lines × 4) 2015/Case.ParallelWalls/Case.ParallelWalls/Entry/CmdMain.cs:35— 2015/Case.ParallelWalls/Case.ParallelWalls/Entry/CmdMain.cs:35-73 | 2016/Case.ParallelWalls/Case.ParallelWalls/Entry/CmdMain.cs:35-73 | 2017/Case.ParallelWalls/Case.ParallelWalls/Entry/CmdMain.cs:35-73 | 2018/Case.ParallelWalls/Case.ParallelWalls/Entry/CmdMain.cs:35-73 — before extracting anything, compare `2015/Case.ParallelWalls/Case.ParallelWalls/Entry/CmdMain.cs` and `2016/Case.ParallelWalls/Case.ParallelWalls/Entry/CmdMain.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. Read the line range as the matched WINDOW rather than a finished unit: at `2015/Case.ParallelWalls/Case.ParallelWalls/Entry/CmdMain.cs:35` 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 (39 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtParameter.vb:161— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtParameter.vb:161-199 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtParameter.vb:161-199 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtParameter.vb:161-199 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtParameter.vb:161-199 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtParameter.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtParameter.vb` 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.
Duplicated block (39 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsIoIni.vb:207— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsIoIni.vb:207-245 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsIoIni.vb:207-245 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsIoIni.vb:207-245 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsIoIni.vb:207-245 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsIoIni.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsIoIni.vb` 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.
Duplicated block (39 lines × 4) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:205— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:205-243 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:205-243 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:205-243 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:205-243 — before extracting anything, compare `2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb` and `2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 383 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 (39 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:591— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:591-629 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:591-629 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:591-629 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:591-629 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 467 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 (39 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:146— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:146-184 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:146-184 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:146-184 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:146-184 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 330 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 (39 lines × 4) 2015/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Data/clsSettings.vb:93— 2015/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Data/clsSettings.vb:93-131 | 2016/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Data/clsSettings.vb:93-131 | 2017/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Data/clsSettings.vb:93-131 | 2018/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Data/clsSettings.vb:93-131 — before extracting anything, compare `2015/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Data/clsSettings.vb` and `2016/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 131 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 (37 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:319— 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:319-355 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:319-355 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:319-355 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:319-355 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 267 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 (37 lines × 4) 2015/Case.Navis2BCF/Case.Navis2BCF/CASERibbon.cs:82— 2015/Case.Navis2BCF/Case.Navis2BCF/CASERibbon.cs:82-118 | 2016/Case.Navis2BCF/Case.Navis2BCF/CASERibbon.cs:82-118 | 2017/Case.Navis2BCF/Case.Navis2BCF/CASERibbon.cs:82-118 | 2018/Case.Navis2BCF/Case.Navis2BCF/CASERibbon.cs:82-118 — before extracting anything, compare `2015/Case.Navis2BCF/Case.Navis2BCF/CASERibbon.cs` and `2016/Case.Navis2BCF/Case.Navis2BCF/CASERibbon.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 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 (37 lines × 4) 2015/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsExcel.vb:287— 2015/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsExcel.vb:287-323 | 2016/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsExcel.vb:287-323 | 2017/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsExcel.vb:287-323 | 2018/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsExcel.vb:287-323 — before extracting anything, compare `2015/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsExcel.vb` and `2016/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsExcel.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 187 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 (37 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsViews.vb:81— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsViews.vb:81-117 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsViews.vb:81-117 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsViews.vb:81-117 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsViews.vb:81-117 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsViews.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsViews.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 68 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 (37 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Modules/mod1.vb:9— 2015/Case.Subs.Xyz/Case.Subs.Xyz/Modules/mod1.vb:9-45 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/Modules/mod1.vb:9-45 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/Modules/mod1.vb:9-45 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/Modules/mod1.vb:9-45 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/Modules/mod1.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/Modules/mod1.vb` 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.
Duplicated block (37 lines × 4) 2015/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Entry/CmdMain.vb:39— 2015/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Entry/CmdMain.vb:39-75 | 2016/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Entry/CmdMain.vb:39-75 | 2017/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Entry/CmdMain.vb:39-75 | 2018/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Entry/CmdMain.vb:39-75 — before extracting anything, compare `2015/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Entry/CmdMain.vb` and `2016/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Entry/CmdMain.vb` as WHOLE FILES: 96% 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. Read the line range as the matched WINDOW rather than a finished unit: at `2015/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Entry/CmdMain.vb:39` 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 (37 lines × 4) 2015/Case.LightingLayout/Case.LightingLayout/Entry/CmdMain.vb:37— 2015/Case.LightingLayout/Case.LightingLayout/Entry/CmdMain.vb:37-73 | 2016/Case.LightingLayout/Case.LightingLayout/Entry/CmdMain.vb:37-73 | 2017/Case.LightingLayout/Case.LightingLayout/Entry/CmdMain.vb:37-73 | 2018/Case.LightingLayout/Case.LightingLayout/Entry/CmdMain.vb:37-73 — before extracting anything, compare `2015/Case.LightingLayout/Case.LightingLayout/Entry/CmdMain.vb` and `2016/Case.LightingLayout/Case.LightingLayout/Entry/CmdMain.vb` as WHOLE FILES: 97% 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. Read the line range as the matched WINDOW rather than a finished unit: at `2015/Case.LightingLayout/Case.LightingLayout/Entry/CmdMain.vb:37` 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 (37 lines × 4) 2015/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsSettings.vb:239— 2015/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsSettings.vb:239-275 | 2016/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsSettings.vb:239-275 | 2017/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsSettings.vb:239-275 | 2018/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsSettings.vb:239-275 — before extracting anything, compare `2015/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsSettings.vb` and `2016/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 114 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 (8 lines × 4) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:192— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:192-199 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:192-199 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:192-199 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:192-199 — before extracting anything, compare `2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb` and `2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 383 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 (8 lines × 4) 2015/Case.Navis2BCF/Case.Navis2BCF/Plugin.cs:33— 2015/Case.Navis2BCF/Case.Navis2BCF/Plugin.cs:33-40 | 2016/Case.Navis2BCF/Case.Navis2BCF/Plugin.cs:33-40 | 2017/Case.Navis2BCF/Case.Navis2BCF/Plugin.cs:33-40 | 2018/Case.Navis2BCF/Case.Navis2BCF/Plugin.cs:33-40 — before extracting anything, compare `2015/Case.Navis2BCF/Case.Navis2BCF/Plugin.cs` and `2016/Case.Navis2BCF/Case.Navis2BCF/Plugin.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.
Duplicated block (8 lines × 4) 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb:601— 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb:601-608 | 2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb:601-608 | 2017/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb:601-608 | 2018/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb:601-608 — before extracting anything, compare `2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb` and `2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 7 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. 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 (8 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ParameterConfigurationManager.xaml.vb:251— 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ParameterConfigurationManager.xaml.vb:251-258 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ParameterConfigurationManager.xaml.vb:251-258 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ParameterConfigurationManager.xaml.vb:251-258 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ParameterConfigurationManager.xaml.vb:251-258 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ParameterConfigurationManager.xaml.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ParameterConfigurationManager.xaml.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 169 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 (8 lines × 4) 2015/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/UI/form_Main.vb:37— 2015/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/UI/form_Main.vb:37-44 | 2016/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/UI/form_Main.vb:37-44 | 2017/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/UI/form_Main.vb:37-44 | 2018/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/UI/form_Main.vb:37-44 — before extracting anything, compare `2015/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/UI/form_Main.vb` and `2016/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/UI/form_Main.vb` as WHOLE FILES: this scan already matched 3 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. 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 (8 lines × 4) REDACTED:46— REDACTED:46-53 | REDACTED:46-53 | REDACTED:46-53 | REDACTED:46-53 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 421 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) 2015/Case.Subs.KeyMatcher/Utility/clsGlobals.cs:117— 2015/Case.Subs.KeyMatcher/Utility/clsGlobals.cs:117-124 | 2016/Case.Subs.KeyMatcher/Utility/clsGlobals.cs:117-124 | 2017/Case.Subs.KeyMatcher/Utility/clsGlobals.cs:117-124 | 2018/Case.Subs.KeyMatcher/Utility/clsGlobals.cs:117-124 — before extracting anything, compare `2015/Case.Subs.KeyMatcher/Utility/clsGlobals.cs` and `2016/Case.Subs.KeyMatcher/Utility/clsGlobals.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 115 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) 2015/Case.Subs.KeyMatcher/Utility/clsGlobals.cs:276— 2015/Case.Subs.KeyMatcher/Utility/clsGlobals.cs:276-283 | 2016/Case.Subs.KeyMatcher/Utility/clsGlobals.cs:276-283 | 2017/Case.Subs.KeyMatcher/Utility/clsGlobals.cs:276-283 | 2018/Case.Subs.KeyMatcher/Utility/clsGlobals.cs:276-283 — before extracting anything, compare `2015/Case.Subs.KeyMatcher/Utility/clsGlobals.cs` and `2016/Case.Subs.KeyMatcher/Utility/clsGlobals.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 115 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.
Unfinished stub — throws NotImplementedException 2015/Case.Navis2BCF/Case.Navis2BCF/Converters.cs:41— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException 2015/Case.Navis2BCF/Case.Navis2BCF/VisibConverter.cs:38— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException 2016/Case.Navis2BCF/Case.Navis2BCF/Converters.cs:41— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException 2016/Case.Navis2BCF/Case.Navis2BCF/VisibConverter.cs:38— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException 2017/Case.Navis2BCF/Case.Navis2BCF/Converters.cs:41— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException 2017/Case.Navis2BCF/Case.Navis2BCF/VisibConverter.cs:38— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException 2018/Case.Navis2BCF/Case.Navis2BCF/Converters.cs:41— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException 2018/Case.Navis2BCF/Case.Navis2BCF/VisibConverter.cs:38— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Duplicated block (83 lines × 4) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:348— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:348-430 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:348-430 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:348-430 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:348-430 — before extracting anything, compare `2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb` and `2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 383 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 (83 lines × 4) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:431— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:431-513 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:431-513 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:431-513 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:431-513 — before extracting anything, compare `2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb` and `2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 685 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 (83 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb:118— 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb:118-200 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb:118-200 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb:118-200 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb:118-200 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 274 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 (83 lines × 4) 2015/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb:334— 2015/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb:334-416 | 2016/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb:334-416 | 2017/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb:335-417 | 2018/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb:335-417 — before extracting anything, compare `2015/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb` and `2016/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 260 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 (83 lines × 4) 2015/Case.ChangeReplaceFamTypeNames/Case.ChangeReplaceFamTypeNames/Data/clsSettings.vb:23— 2015/Case.ChangeReplaceFamTypeNames/Case.ChangeReplaceFamTypeNames/Data/clsSettings.vb:23-105 | 2016/Case.ChangeReplaceFamTypeNames/Case.ChangeReplaceFamTypeNames/Data/clsSettings.vb:23-105 | 2017/Case.ChangeReplaceFamTypeNames/Case.ChangeReplaceFamTypeNames/Data/clsSettings.vb:23-105 | 2018/Case.ChangeReplaceFamTypeNames/Case.ChangeReplaceFamTypeNames/Data/clsSettings.vb:23-105 — before extracting anything, compare `2015/Case.ChangeReplaceFamTypeNames/Case.ChangeReplaceFamTypeNames/Data/clsSettings.vb` and `2016/Case.ChangeReplaceFamTypeNames/Case.ChangeReplaceFamTypeNames/Data/clsSettings.vb` 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.
Duplicated block (83 lines × 4) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/clsSettings.vb:18— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/clsSettings.vb:18-100 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/clsSettings.vb:18-100 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/clsSettings.vb:18-100 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/clsSettings.vb:18-100 — before extracting anything, compare `2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/clsSettings.vb` and `2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/clsSettings.vb` 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.
Duplicated block (83 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsFam.vb:30— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsFam.vb:30-112 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsFam.vb:30-112 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsFam.vb:30-112 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsFam.vb:30-112 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsFam.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsFam.vb` 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.
Duplicated block (51 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtSchedule.vb:93— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtSchedule.vb:93-143 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtSchedule.vb:93-143 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtSchedule.vb:93-143 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtSchedule.vb:93-143 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtSchedule.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtSchedule.vb` 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 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.
Duplicated block (51 lines × 4) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:38— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:38-88 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:38-88 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:38-88 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:38-88 — before extracting anything, compare `2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb` and `2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 383 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 (51 lines × 4) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/UI/form_ImportMain.xaml.vb:243— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/UI/form_ImportMain.xaml.vb:243-293 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/UI/form_ImportMain.xaml.vb:243-293 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/UI/form_ImportMain.xaml.vb:243-293 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/UI/form_ImportMain.xaml.vb:243-293 — before extracting anything, compare `2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/UI/form_ImportMain.xaml.vb` and `2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/UI/form_ImportMain.xaml.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 299 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 (51 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsVP.vb:78— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsVP.vb:78-128 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsVP.vb:78-128 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsVP.vb:78-128 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsVP.vb:78-128 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsVP.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsVP.vb` 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 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.
Duplicated block (51 lines × 4) REDACTED:142— REDACTED:142-192 | REDACTED:140-190 | REDACTED:140-190 | REDACTED:135-185 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 123 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:142` 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 (51 lines × 4) 2015/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsSettings.vb:25— 2015/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsSettings.vb:25-75 | 2016/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsSettings.vb:25-75 | 2017/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsSettings.vb:25-75 | 2018/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsSettings.vb:25-75 — before extracting anything, compare `2015/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsSettings.vb` and `2016/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsSettings.vb` 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.
Duplicated block (51 lines × 4) 2015/Case.Navis2BCF/Case.Navis2BCF/ObservableCollections.cs:24— 2015/Case.Navis2BCF/Case.Navis2BCF/ObservableCollections.cs:24-74 | 2016/Case.Navis2BCF/Case.Navis2BCF/ObservableCollections.cs:24-74 | 2017/Case.Navis2BCF/Case.Navis2BCF/ObservableCollections.cs:24-74 | 2018/Case.Navis2BCF/Case.Navis2BCF/ObservableCollections.cs:24-74 — before extracting anything, compare `2015/Case.Navis2BCF/Case.Navis2BCF/ObservableCollections.cs` and `2016/Case.Navis2BCF/Case.Navis2BCF/ObservableCollections.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. Read the line range as the matched WINDOW rather than a finished unit: at `2015/Case.Navis2BCF/Case.Navis2BCF/ObservableCollections.cs:24` 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 (38 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F2.vb:68— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F2.vb:68-105 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F2.vb:68-105 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F2.vb:68-105 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F2.vb:68-105 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F2.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F2.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 113 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 (38 lines × 4) 2015/Case.ApplySysOrient/Entry/CmdMain.cs:38— 2015/Case.ApplySysOrient/Entry/CmdMain.cs:38-75 | 2016/Case.ApplySysOrient/Entry/CmdMain.cs:38-75 | 2017/Case.ApplySysOrient/Entry/CmdMain.cs:38-75 | 2018/Case.ApplySysOrient/Entry/CmdMain.cs:38-75 — before extracting anything, compare `2015/Case.ApplySysOrient/Entry/CmdMain.cs` and `2016/Case.ApplySysOrient/Entry/CmdMain.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. Read the line range as the matched WINDOW rather than a finished unit: at `2015/Case.ApplySysOrient/Entry/CmdMain.cs:38` 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 (38 lines × 4) REDACTED:197— REDACTED:197-234 | REDACTED:197-234 | REDACTED:197-234 | REDACTED:197-234 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 147 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 (38 lines × 4) 2015/Case.UngroupAll/Case.UngroupAll/Entry/CmdMain.cs:37— 2015/Case.UngroupAll/Case.UngroupAll/Entry/CmdMain.cs:37-74 | 2016/Case.UngroupAll/Case.UngroupAll/Entry/CmdMain.cs:37-74 | 2017/Case.UngroupAll/Case.UngroupAll/Entry/CmdMain.cs:37-74 | 2018/Case.UngroupAll/Case.UngroupAll/Entry/CmdMain.cs:37-74 — before extracting anything, compare `2015/Case.UngroupAll/Case.UngroupAll/Entry/CmdMain.cs` and `2016/Case.UngroupAll/Case.UngroupAll/Entry/CmdMain.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. Read the line range as the matched WINDOW rather than a finished unit: at `2015/Case.UngroupAll/Case.UngroupAll/Entry/CmdMain.cs:37` 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 (38 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb:412— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb:412-449 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb:412-449 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb:412-449 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb:412-449 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 291 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 (38 lines × 4) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:100— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:100-137 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:100-137 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:100-137 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:100-137 — before extracting anything, compare `2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb` and `2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 383 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 (38 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:57— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:57-94 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:57-94 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:57-94 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:57-94 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 330 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 (29 lines × 4) 2015/Case.UngroupAll/Case.UngroupAll/Data/clsSettings.cs:60— 2015/Case.UngroupAll/Case.UngroupAll/Data/clsSettings.cs:60-88 | 2016/Case.UngroupAll/Case.UngroupAll/Data/clsSettings.cs:60-88 | 2017/Case.UngroupAll/Case.UngroupAll/Data/clsSettings.cs:60-88 | 2018/Case.UngroupAll/Case.UngroupAll/Data/clsSettings.cs:60-88 — before extracting anything, compare `2015/Case.UngroupAll/Case.UngroupAll/Data/clsSettings.cs` and `2016/Case.UngroupAll/Case.UngroupAll/Data/clsSettings.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. 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 (29 lines × 4) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:308— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:308-336 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:308-336 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:308-336 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:308-336 — before extracting anything, compare `2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb` and `2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 383 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 (29 lines × 4) 2015/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:75— 2015/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:75-103 | 2016/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:75-103 | 2017/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:75-103 | 2018/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:75-103 — before extracting anything, compare `2015/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb` and `2016/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 264 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 (29 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:467— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:467-495 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:467-495 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:467-495 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:467-495 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb` as WHOLE FILES: this scan already matched 10 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. 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 (29 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:303— 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:303-331 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:303-331 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:303-331 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:302-330 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 317 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 (29 lines × 4) 2015/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsDoors.vb:178— 2015/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsDoors.vb:178-206 | 2016/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsDoors.vb:178-206 | 2017/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsDoors.vb:178-206 | 2018/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsDoors.vb:178-206 — before extracting anything, compare `2015/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsDoors.vb` and `2016/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsDoors.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 70 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 (29 lines × 4) 2015/Case.SharedParameters/Case.SharedParameters/Entry/CmdMain.vb:36— 2015/Case.SharedParameters/Case.SharedParameters/Entry/CmdMain.vb:36-64 | 2016/Case.SharedParameters/Case.SharedParameters/Entry/CmdMain.vb:36-64 | 2017/Case.SharedParameters/Case.SharedParameters/Entry/CmdMain.vb:36-64 | 2018/Case.SharedParameters/Case.SharedParameters/Entry/CmdMain.vb:36-64 — before extracting anything, compare `2015/Case.SharedParameters/Case.SharedParameters/Entry/CmdMain.vb` and `2016/Case.SharedParameters/Case.SharedParameters/Entry/CmdMain.vb` as WHOLE FILES: 96% 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. Read the line range as the matched WINDOW rather than a finished unit: at `2015/Case.SharedParameters/Case.SharedParameters/Entry/CmdMain.vb:36` 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 (21 lines × 4) 2015/Case.Subs.Linestyles/Case.Subs.Linestyles/UI/form_Main.vb:101— 2015/Case.Subs.Linestyles/Case.Subs.Linestyles/UI/form_Main.vb:101-121 | 2016/Case.Subs.Linestyles/Case.Subs.Linestyles/UI/form_Main.vb:101-121 | 2017/Case.Subs.Linestyles/Case.Subs.Linestyles/UI/form_Main.vb:101-121 | 2018/Case.Subs.Linestyles/Case.Subs.Linestyles/UI/form_Main.vb:101-121 — before extracting anything, compare `2015/Case.Subs.Linestyles/Case.Subs.Linestyles/UI/form_Main.vb` and `2016/Case.Subs.Linestyles/Case.Subs.Linestyles/UI/form_Main.vb` 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 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.
Duplicated block (21 lines × 4) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/OpenNURBS/clsONGet.vb:17— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/OpenNURBS/clsONGet.vb:17-37 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/OpenNURBS/clsONGet.vb:17-37 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/OpenNURBS/clsONGet.vb:17-37 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/OpenNURBS/clsONGet.vb:17-37 — before extracting anything, compare `2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/OpenNURBS/clsONGet.vb` and `2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/OpenNURBS/clsONGet.vb` 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.
Duplicated block (21 lines × 4) 2015/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsDoors.vb:145— 2015/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsDoors.vb:145-165 | 2016/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsDoors.vb:145-165 | 2017/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsDoors.vb:145-165 | 2018/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsDoors.vb:145-165 — before extracting anything, compare `2015/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsDoors.vb` and `2016/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsDoors.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 70 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 (21 lines × 4) 2015/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb:248— 2015/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb:248-268 | 2016/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb:248-268 | 2017/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb:248-268 | 2018/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb:248-268 — before extracting anything, compare `2015/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb` and `2016/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 191 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 (21 lines × 4) 2015/Case.RoomSync/Case.RoomSync/Data/clsRoom.vb:49— 2015/Case.RoomSync/Case.RoomSync/Data/clsRoom.vb:49-69 | 2016/Case.RoomSync/Case.RoomSync/Data/clsRoom.vb:49-69 | 2017/Case.RoomSync/Case.RoomSync/Data/clsRoom.vb:49-69 | 2018/Case.RoomSync/Case.RoomSync/Data/clsRoom.vb:49-69 — before extracting anything, compare `2015/Case.RoomSync/Case.RoomSync/Data/clsRoom.vb` and `2016/Case.RoomSync/Case.RoomSync/Data/clsRoom.vb` 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 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.
Duplicated block (21 lines × 4) 2015/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsPropertyComparer.vb:18— 2015/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsPropertyComparer.vb:18-38 | 2016/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsPropertyComparer.vb:18-38 | 2017/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsPropertyComparer.vb:18-38 | 2018/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsPropertyComparer.vb:18-38 — before extracting anything, compare `2015/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsPropertyComparer.vb` and `2016/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsPropertyComparer.vb` 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.
Duplicated block (21 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_ExportSchedule.vb:60— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_ExportSchedule.vb:60-80 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_ExportSchedule.vb:60-80 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_ExportSchedule.vb:60-80 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_ExportSchedule.vb:60-80 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_ExportSchedule.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_ExportSchedule.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 81 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 (48 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:644— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:644-691 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:644-691 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:644-691 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:644-691 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 610 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 (48 lines × 4) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/UI/form_ImportMain.xaml.vb:304— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/UI/form_ImportMain.xaml.vb:304-351 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/UI/form_ImportMain.xaml.vb:304-351 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/UI/form_ImportMain.xaml.vb:304-351 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/UI/form_ImportMain.xaml.vb:304-351 — before extracting anything, compare `2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/UI/form_ImportMain.xaml.vb` and `2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/UI/form_ImportMain.xaml.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 299 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 (48 lines × 4) 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb:228— 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb:228-275 | 2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb:228-275 | 2017/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb:228-275 | 2018/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb:228-275 — before extracting anything, compare `2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb` and `2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 7 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. 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 (48 lines × 4) 2015/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Form/form_Main.vb:158— 2015/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Form/form_Main.vb:158-205 | 2016/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Form/form_Main.vb:158-205 | 2017/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Form/form_Main.vb:158-205 | 2018/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Form/form_Main.vb:158-205 — before extracting anything, compare `2015/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Form/form_Main.vb` and `2016/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Form/form_Main.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 215 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 (48 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Progress.vb:12— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Progress.vb:12-59 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Progress.vb:12-59 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Progress.vb:12-59 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Progress.vb:12-59 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Progress.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Progress.vb` 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.
Duplicated block (48 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsLevel.vb:17— 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsLevel.vb:17-64 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsLevel.vb:17-64 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsLevel.vb:17-64 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsLevel.vb:17-64 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsLevel.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsLevel.vb` 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.
Duplicated block (41 lines × 4) 2015/Case.ViewCreator/Case.ViewCreator/Classes/Entry/app.cs:134— 2015/Case.ViewCreator/Case.ViewCreator/Classes/Entry/app.cs:134-174 | 2016/Case.ViewCreator/Case.ViewCreator/Classes/Entry/app.cs:134-174 | 2017/Case.ViewCreator/Case.ViewCreator/Classes/Entry/app.cs:134-174 | 2018/Case.ViewCreator/Case.ViewCreator/Classes/Entry/app.cs:134-174 — before extracting anything, compare `2015/Case.ViewCreator/Case.ViewCreator/Classes/Entry/app.cs` and `2016/Case.ViewCreator/Case.ViewCreator/Classes/Entry/app.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 98 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 (41 lines × 4) REDACTED:567— REDACTED:567-607 | REDACTED:567-607 | REDACTED:567-607 | REDACTED:567-607 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 421 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 (41 lines × 4) 2015/Case.Directionality/Case.Directionality/Data/clsExternalWalls.vb:27— 2015/Case.Directionality/Case.Directionality/Data/clsExternalWalls.vb:27-67 | 2016/Case.Directionality/Case.Directionality/Data/clsExternalWalls.vb:27-67 | 2017/Case.Directionality/Case.Directionality/Data/clsExternalWalls.vb:27-67 | 2018/Case.Directionality/Case.Directionality/Data/clsExternalWalls.vb:27-67 — before extracting anything, compare `2015/Case.Directionality/Case.Directionality/Data/clsExternalWalls.vb` and `2016/Case.Directionality/Case.Directionality/Data/clsExternalWalls.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 252 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 (41 lines × 4) 2015/Case.RoomSync/Case.RoomSync/Data/modGeneral.vb:138— 2015/Case.RoomSync/Case.RoomSync/Data/modGeneral.vb:138-178 | 2016/Case.RoomSync/Case.RoomSync/Data/modGeneral.vb:138-178 | 2017/Case.RoomSync/Case.RoomSync/Data/modGeneral.vb:138-178 | 2018/Case.RoomSync/Case.RoomSync/Data/modGeneral.vb:138-178 — before extracting anything, compare `2015/Case.RoomSync/Case.RoomSync/Data/modGeneral.vb` and `2016/Case.RoomSync/Case.RoomSync/Data/modGeneral.vb` as WHOLE FILES: this scan already matched 5 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.
Duplicated block (41 lines × 4) 2015/Case.FreeBenchmarking/Case.FreeBenchmarking/Modules/LogData.vb:20— 2015/Case.FreeBenchmarking/Case.FreeBenchmarking/Modules/LogData.vb:20-60 | 2016/Case.FreeBenchmarking/Case.FreeBenchmarking/Modules/LogData.vb:20-60 | 2017/Case.FreeBenchmarking/Case.FreeBenchmarking/Modules/LogData.vb:20-60 | 2018/Case.FreeBenchmarking/Case.FreeBenchmarking/Modules/LogData.vb:20-60 — before extracting anything, compare `2015/Case.FreeBenchmarking/Case.FreeBenchmarking/Modules/LogData.vb` and `2016/Case.FreeBenchmarking/Case.FreeBenchmarking/Modules/LogData.vb` 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.
Duplicated block (41 lines × 4) 2015/Case.ParallelWalls/Case.ParallelWalls/Data/clsElementSelection.cs:56— 2015/Case.ParallelWalls/Case.ParallelWalls/Data/clsElementSelection.cs:56-96 | 2016/Case.ParallelWalls/Case.ParallelWalls/Data/clsElementSelection.cs:56-96 | 2017/Case.ParallelWalls/Case.ParallelWalls/Data/clsElementSelection.cs:56-96 | 2018/Case.ParallelWalls/Case.ParallelWalls/Data/clsElementSelection.cs:51-91 — before extracting anything, compare `2015/Case.ParallelWalls/Case.ParallelWalls/Data/clsElementSelection.cs` and `2016/Case.ParallelWalls/Case.ParallelWalls/Data/clsElementSelection.cs` as WHOLE FILES: 98% 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 (36 lines × 4) 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:382— 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:382-417 | 2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:382-417 | 2017/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:382-417 | 2018/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:382-417 — before extracting anything, compare `2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb` and `2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 323 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 (36 lines × 4) 2015/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsElement.vb:25— 2015/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsElement.vb:25-60 | 2016/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsElement.vb:25-60 | 2017/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsElement.vb:25-60 | 2018/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsElement.vb:25-60 — before extracting anything, compare `2015/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsElement.vb` and `2016/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsElement.vb` 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 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.
Duplicated block (36 lines × 4) 2015/Case.BasicReporting/Case.BasicReporting/Data/clsHosts.vb:74— 2015/Case.BasicReporting/Case.BasicReporting/Data/clsHosts.vb:74-109 | 2016/Case.BasicReporting/Case.BasicReporting/Data/clsHosts.vb:74-109 | 2017/Case.BasicReporting/Case.BasicReporting/Data/clsHosts.vb:74-109 | 2018/Case.BasicReporting/Case.BasicReporting/Data/clsHosts.vb:74-109 — before extracting anything, compare `2015/Case.BasicReporting/Case.BasicReporting/Data/clsHosts.vb` and `2016/Case.BasicReporting/Case.BasicReporting/Data/clsHosts.vb` 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 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.
Duplicated block (36 lines × 4) 2015/Case.Directionality/Case.Directionality/Data/clsExternalWalls.vb:131— 2015/Case.Directionality/Case.Directionality/Data/clsExternalWalls.vb:131-166 | 2016/Case.Directionality/Case.Directionality/Data/clsExternalWalls.vb:131-166 | 2017/Case.Directionality/Case.Directionality/Data/clsExternalWalls.vb:131-166 | 2018/Case.Directionality/Case.Directionality/Data/clsExternalWalls.vb:131-166 — before extracting anything, compare `2015/Case.Directionality/Case.Directionality/Data/clsExternalWalls.vb` and `2016/Case.Directionality/Case.Directionality/Data/clsExternalWalls.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 252 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 (36 lines × 4) REDACTED:455— REDACTED:455-490 | REDACTED:455-490 | REDACTED:455-490 | REDACTED:455-490 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 421 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:455` 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 (36 lines × 4) 2015/Case.BasicReporting/Case.BasicReporting/Data/clsFormulas.vb:15— 2015/Case.BasicReporting/Case.BasicReporting/Data/clsFormulas.vb:15-50 | 2016/Case.BasicReporting/Case.BasicReporting/Data/clsFormulas.vb:15-50 | 2017/Case.BasicReporting/Case.BasicReporting/Data/clsFormulas.vb:15-50 | 2018/Case.BasicReporting/Case.BasicReporting/Data/clsFormulas.vb:15-50 — before extracting anything, compare `2015/Case.BasicReporting/Case.BasicReporting/Data/clsFormulas.vb` and `2016/Case.BasicReporting/Case.BasicReporting/Data/clsFormulas.vb` 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.
Duplicated block (34 lines × 4) 2015/Case.ParallelWalls/Case.ParallelWalls/Data/clsWallTransform.cs:91— 2015/Case.ParallelWalls/Case.ParallelWalls/Data/clsWallTransform.cs:91-124 | 2016/Case.ParallelWalls/Case.ParallelWalls/Data/clsWallTransform.cs:91-124 | 2017/Case.ParallelWalls/Case.ParallelWalls/Data/clsWallTransform.cs:91-124 | 2018/Case.ParallelWalls/Case.ParallelWalls/Data/clsWallTransform.cs:86-119 — before extracting anything, compare `2015/Case.ParallelWalls/Case.ParallelWalls/Data/clsWallTransform.cs` and `2016/Case.ParallelWalls/Case.ParallelWalls/Data/clsWallTransform.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 56 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 (34 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F3.vb:40— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F3.vb:40-73 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F3.vb:40-73 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F3.vb:40-73 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F3.vb:40-73 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F3.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F3.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 75 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 × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:599— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:599-632 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:599-632 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:599-632 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:599-632 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 610 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 × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Tag.vb:33— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Tag.vb:33-66 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Tag.vb:33-66 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Tag.vb:33-66 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Tag.vb:33-66 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Tag.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Tag.vb` 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 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.
Duplicated block (34 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:682— 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:682-715 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:682-715 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:682-715 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:682-715 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 604 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 × 4) 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsLinks.vb:15— 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsLinks.vb:15-48 | 2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsLinks.vb:15-48 | 2017/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsLinks.vb:15-48 | 2018/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsLinks.vb:15-48 — before extracting anything, compare `2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsLinks.vb` and `2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsLinks.vb` 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.
Duplicated block (10 lines × 2) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:246— 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:246-255 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:246-255 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 267 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 × 2) 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:246— 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:246-255 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:246-255 — before extracting anything, compare `2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb` and `2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 267 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 × 2) 2015/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:418— 2015/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:418-427 | 2016/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:418-427 — before extracting anything, compare `2015/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb` and `2016/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 201 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 × 2) 2015/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:351— 2015/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:351-360 | 2016/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:351-360 — before extracting anything, compare `2015/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb` and `2016/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 173 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 × 2) 2017/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:418— 2017/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:418-427 | 2018/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:418-427 — before extracting anything, compare `2017/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb` and `2018/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 201 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 × 2) 2017/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:351— 2017/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:351-360 | 2018/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:346-355 — before extracting anything, compare `2017/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb` and `2018/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 173 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 (78 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb:39— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb:39-116 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb:39-116 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb:39-116 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb:39-116 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 291 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 (78 lines × 4) 2015/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsFamilyType.vb:150— 2015/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsFamilyType.vb:150-227 | 2016/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsFamilyType.vb:150-227 | 2017/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsFamilyType.vb:150-227 | 2018/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsFamilyType.vb:150-227 — before extracting anything, compare `2015/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsFamilyType.vb` and `2016/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsFamilyType.vb` 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 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.
Duplicated block (78 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsConfiguration.vb:71— 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsConfiguration.vb:71-148 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsConfiguration.vb:71-148 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsConfiguration.vb:71-148 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsConfiguration.vb:71-148 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsConfiguration.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsConfiguration.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 115 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 (78 lines × 4) 2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/clsViewTemplates.vb:27— 2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/clsViewTemplates.vb:27-104 | 2016/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/clsViewTemplates.vb:27-104 | 2017/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/clsViewTemplates.vb:27-104 | 2018/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/clsViewTemplates.vb:27-104 — before extracting anything, compare `2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/clsViewTemplates.vb` and `2016/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/clsViewTemplates.vb` 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.
Duplicated block (78 lines × 4) 2015/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb:367— 2015/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb:367-444 | 2016/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb:367-444 | 2017/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb:367-444 | 2018/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb:367-444 — before extracting anything, compare `2015/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb` and `2016/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 215 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 (58 lines × 4) 2015/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/UI/form_Main.vb:188— 2015/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/UI/form_Main.vb:188-245 | 2016/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/UI/form_Main.vb:188-245 | 2017/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/UI/form_Main.vb:188-245 | 2018/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/UI/form_Main.vb:188-245 — before extracting anything, compare `2015/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/UI/form_Main.vb` and `2016/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/UI/form_Main.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 214 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 (58 lines × 4) 2015/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Data/clsSettings.vb:144— 2015/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Data/clsSettings.vb:144-201 | 2016/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Data/clsSettings.vb:144-201 | 2017/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Data/clsSettings.vb:144-201 | 2018/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Data/clsSettings.vb:144-201 — before extracting anything, compare `2015/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Data/clsSettings.vb` and `2016/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 131 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 (58 lines × 4) 2015/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb:286— 2015/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb:286-343 | 2016/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb:286-343 | 2017/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb:286-343 | 2018/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb:286-343 — before extracting anything, compare `2015/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb` and `2016/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 260 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 (58 lines × 4) 2015/Case.MultiViewDuplicate/Case.MultiViewDuplicate/UI/form_Main.vb:179— 2015/Case.MultiViewDuplicate/Case.MultiViewDuplicate/UI/form_Main.vb:179-236 | 2016/Case.MultiViewDuplicate/Case.MultiViewDuplicate/UI/form_Main.vb:179-236 | 2017/Case.MultiViewDuplicate/Case.MultiViewDuplicate/UI/form_Main.vb:179-236 | 2018/Case.MultiViewDuplicate/Case.MultiViewDuplicate/UI/form_Main.vb:179-236 — before extracting anything, compare `2015/Case.MultiViewDuplicate/Case.MultiViewDuplicate/UI/form_Main.vb` and `2016/Case.MultiViewDuplicate/Case.MultiViewDuplicate/UI/form_Main.vb` as WHOLE FILES: this scan already matched 3 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. 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 (58 lines × 4) 2015/Case.ImageToDraftingView/Case.ImageToDraftingView/Data/clsPara.vb:15— 2015/Case.ImageToDraftingView/Case.ImageToDraftingView/Data/clsPara.vb:15-72 | 2016/Case.ImageToDraftingView/Case.ImageToDraftingView/Data/clsPara.vb:15-72 | 2017/Case.ImageToDraftingView/Case.ImageToDraftingView/Data/clsPara.vb:15-72 | 2018/Case.ImageToDraftingView/Case.ImageToDraftingView/Data/clsPara.vb:15-72 — before extracting anything, compare `2015/Case.ImageToDraftingView/Case.ImageToDraftingView/Data/clsPara.vb` and `2016/Case.ImageToDraftingView/Case.ImageToDraftingView/Data/clsPara.vb` 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.
clsRvtCategoryData.GetAllPropertyValues (cyclomatic 91) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:387— clsRvtCategoryData.GetAllPropertyValues has cyclomatic complexity 91 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsRvtCategoryData.GetAllPropertyValues (cyclomatic 91) 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:387— clsRvtCategoryData.GetAllPropertyValues has cyclomatic complexity 91 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsRvtCategoryData.GetAllPropertyValues (cyclomatic 91) 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:387— clsRvtCategoryData.GetAllPropertyValues has cyclomatic complexity 91 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsRvtCategoryData.GetAllPropertyValues (cyclomatic 91) 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:387— clsRvtCategoryData.GetAllPropertyValues has cyclomatic complexity 91 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsSettings.ScanCategories (cyclomatic 58) 2015/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsSettings.vb:179— clsSettings.ScanCategories has cyclomatic complexity 58 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsSettings.ScanCategories (cyclomatic 58) 2016/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsSettings.vb:179— clsSettings.ScanCategories has cyclomatic complexity 58 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsSettings.ScanCategories (cyclomatic 58) 2017/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsSettings.vb:179— clsSettings.ScanCategories has cyclomatic complexity 58 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsSettings.ScanCategories (cyclomatic 58) 2018/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsSettings.vb:179— clsSettings.ScanCategories has cyclomatic complexity 58 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsSettings.GetSymbolNames (cyclomatic 50) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsSettings.vb:254— clsSettings.GetSymbolNames has cyclomatic complexity 50 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsSettings.GetSymbolNames (cyclomatic 50) 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsSettings.vb:254— clsSettings.GetSymbolNames has cyclomatic complexity 50 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsSettings.GetSymbolNames (cyclomatic 50) 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsSettings.vb:254— clsSettings.GetSymbolNames has cyclomatic complexity 50 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsSettings.GetSymbolNames (cyclomatic 50) 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsSettings.vb:254— clsSettings.GetSymbolNames has cyclomatic complexity 50 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_ExportPoints.New.ctor (cyclomatic 47) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:13— form_ExportPoints.New.ctor has cyclomatic complexity 47 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_ExportPoints.New.ctor (cyclomatic 47) 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:13— form_ExportPoints.New.ctor has cyclomatic complexity 47 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_ExportPoints.New.ctor (cyclomatic 47) 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:13— form_ExportPoints.New.ctor has cyclomatic complexity 47 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_ExportPoints.New.ctor (cyclomatic 47) 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:13— form_ExportPoints.New.ctor has cyclomatic complexity 47 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Sync.UpdateElementData (cyclomatic 46) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:299— form_Sync.UpdateElementData has cyclomatic complexity 46 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Sync.UpdateElementData (cyclomatic 46) 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:299— form_Sync.UpdateElementData has cyclomatic complexity 46 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Sync.UpdateElementData (cyclomatic 46) 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:299— form_Sync.UpdateElementData has cyclomatic complexity 46 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Sync.UpdateElementData (cyclomatic 46) 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:299— form_Sync.UpdateElementData has cyclomatic complexity 46 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_RoomMasses.GenerateMasses (cyclomatic 45) 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:41— form_RoomMasses.GenerateMasses has cyclomatic complexity 45 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_RoomMasses.GenerateMasses (cyclomatic 45) 2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:41— form_RoomMasses.GenerateMasses has cyclomatic complexity 45 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_RoomMasses.GenerateMasses (cyclomatic 45) 2017/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:41— form_RoomMasses.GenerateMasses has cyclomatic complexity 45 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_RoomMasses.GenerateMasses (cyclomatic 45) 2018/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:41— form_RoomMasses.GenerateMasses has cyclomatic complexity 45 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsONSort.SortObjects (cyclomatic 44) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/OpenNURBS/clsONSort.vb:56— clsONSort.SortObjects has cyclomatic complexity 44 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsONSort.SortObjects (cyclomatic 44) 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/OpenNURBS/clsONSort.vb:56— clsONSort.SortObjects has cyclomatic complexity 44 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsONSort.SortObjects (cyclomatic 44) 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/OpenNURBS/clsONSort.vb:56— clsONSort.SortObjects has cyclomatic complexity 44 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsONSort.SortObjects (cyclomatic 44) 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/OpenNURBS/clsONSort.vb:56— clsONSort.SortObjects has cyclomatic complexity 44 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Form_Main.TagElementsInViews (cyclomatic 40) 2015/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:326— Form_Main.TagElementsInViews has cyclomatic complexity 40 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Form_Main.TagElementsInViews (cyclomatic 40) 2016/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:326— Form_Main.TagElementsInViews has cyclomatic complexity 40 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Form_Main.TagElementsInViews (cyclomatic 40) 2017/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:326— Form_Main.TagElementsInViews has cyclomatic complexity 40 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Form_Main.TagElementsInViews (cyclomatic 40) 2018/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:326— Form_Main.TagElementsInViews has cyclomatic complexity 40 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsReportingData.New.ctor (cyclomatic 37) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:309— clsReportingData.New.ctor has cyclomatic complexity 37 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsReportingData.New.ctor (cyclomatic 37) 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:309— clsReportingData.New.ctor has cyclomatic complexity 37 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsReportingData.New.ctor (cyclomatic 37) 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:309— clsReportingData.New.ctor has cyclomatic complexity 37 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsReportingData.New.ctor (cyclomatic 37) 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:309— clsReportingData.New.ctor has cyclomatic complexity 37 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
MultiSelectTreeview.OnKeyDown (cyclomatic 36) 2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:165— MultiSelectTreeview.OnKeyDown has cyclomatic complexity 36 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
MultiSelectTreeview.OnKeyDown (cyclomatic 36) 2016/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:165— MultiSelectTreeview.OnKeyDown has cyclomatic complexity 36 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
MultiSelectTreeview.OnKeyDown (cyclomatic 36) 2017/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:165— MultiSelectTreeview.OnKeyDown has cyclomatic complexity 36 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
MultiSelectTreeview.OnKeyDown (cyclomatic 36) 2018/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:165— MultiSelectTreeview.OnKeyDown has cyclomatic complexity 36 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Sync.SyncRooms (cyclomatic 35) 2015/Case.RoomSync/Case.RoomSync/UI/form_Sync.vb:43— form_Sync.SyncRooms has cyclomatic complexity 35 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Sync.SyncRooms (cyclomatic 35) 2016/Case.RoomSync/Case.RoomSync/UI/form_Sync.vb:43— form_Sync.SyncRooms has cyclomatic complexity 35 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Sync.SyncRooms (cyclomatic 35) 2017/Case.RoomSync/Case.RoomSync/UI/form_Sync.vb:43— form_Sync.SyncRooms has cyclomatic complexity 35 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Sync.SyncRooms (cyclomatic 35) 2018/Case.RoomSync/Case.RoomSync/UI/form_Sync.vb:43— form_Sync.SyncRooms has cyclomatic complexity 35 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsExcel.UpdateWorksheetFromArray (cyclomatic 33) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:704— clsExcel.UpdateWorksheetFromArray has cyclomatic complexity 33 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsExcel.UpdateWorksheetFromArray (cyclomatic 33) 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:704— clsExcel.UpdateWorksheetFromArray has cyclomatic complexity 33 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsExcel.UpdateWorksheetFromArray (cyclomatic 33) 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:704— clsExcel.UpdateWorksheetFromArray has cyclomatic complexity 33 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsExcel.UpdateWorksheetFromArray (cyclomatic 33) 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:704— clsExcel.UpdateWorksheetFromArray has cyclomatic complexity 33 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsSettings.UpdateElementValues (cyclomatic 32) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:738— clsSettings.UpdateElementValues has cyclomatic complexity 32 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsSettings.UpdateElementValues (cyclomatic 32) 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:738— clsSettings.UpdateElementValues has cyclomatic complexity 32 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsSettings.UpdateElementValues (cyclomatic 32) 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:738— clsSettings.UpdateElementValues has cyclomatic complexity 32 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsSettings.UpdateElementValues (cyclomatic 32) 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:738— clsSettings.UpdateElementValues has cyclomatic complexity 32 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_PlacePointsFromFile.PlacePoints (cyclomatic 32) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb:48— form_PlacePointsFromFile.PlacePoints has cyclomatic complexity 32 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_PlacePointsFromFile.PlacePoints (cyclomatic 32) 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb:48— form_PlacePointsFromFile.PlacePoints has cyclomatic complexity 32 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_PlacePointsFromFile.PlacePoints (cyclomatic 32) 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb:48— form_PlacePointsFromFile.PlacePoints has cyclomatic complexity 32 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_PlacePointsFromFile.PlacePoints (cyclomatic 32) 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb:48— form_PlacePointsFromFile.PlacePoints has cyclomatic complexity 32 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Main.CalculatePoints (cyclomatic 32) 2015/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb:32— form_Main.CalculatePoints has cyclomatic complexity 32 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Main.CalculatePoints (cyclomatic 32) 2016/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb:32— form_Main.CalculatePoints has cyclomatic complexity 32 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Main.CalculatePoints (cyclomatic 32) 2017/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb:32— form_Main.CalculatePoints has cyclomatic complexity 32 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Main.CalculatePoints (cyclomatic 32) 2018/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb:32— form_Main.CalculatePoints has cyclomatic complexity 32 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Form_Main.UpdateFamiliesList (cyclomatic 30) 2015/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:111— Form_Main.UpdateFamiliesList has cyclomatic complexity 30 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Form_Main.UpdateFamiliesList (cyclomatic 30) 2016/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:111— Form_Main.UpdateFamiliesList has cyclomatic complexity 30 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Form_Main.UpdateFamiliesList (cyclomatic 30) 2017/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:111— Form_Main.UpdateFamiliesList has cyclomatic complexity 30 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Form_Main.UpdateFamiliesList (cyclomatic 30) 2018/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:111— Form_Main.UpdateFamiliesList has cyclomatic complexity 30 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsExcel.FillExcelWorksheetFromDataTable (cyclomatic 30) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb:283— clsExcel.FillExcelWorksheetFromDataTable has cyclomatic complexity 30 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsExcel.FillExcelWorksheetFromDataTable (cyclomatic 30) 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb:283— clsExcel.FillExcelWorksheetFromDataTable has cyclomatic complexity 30 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsExcel.FillExcelWorksheetFromDataTable (cyclomatic 30) 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb:283— clsExcel.FillExcelWorksheetFromDataTable has cyclomatic complexity 30 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsExcel.FillExcelWorksheetFromDataTable (cyclomatic 30) 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb:283— clsExcel.FillExcelWorksheetFromDataTable has cyclomatic complexity 30 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsReportingData.New.ctor (cyclomatic 30) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:157— clsReportingData.New.ctor has cyclomatic complexity 30 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsReportingData.New.ctor (cyclomatic 30) 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:157— clsReportingData.New.ctor has cyclomatic complexity 30 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsReportingData.New.ctor (cyclomatic 30) 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:157— clsReportingData.New.ctor has cyclomatic complexity 30 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsReportingData.New.ctor (cyclomatic 30) 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:157— clsReportingData.New.ctor has cyclomatic complexity 30 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_DataManager.UpdatePoints (cyclomatic 30) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:37— form_DataManager.UpdatePoints has cyclomatic complexity 30 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_DataManager.UpdatePoints (cyclomatic 30) 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:37— form_DataManager.UpdatePoints has cyclomatic complexity 30 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_DataManager.UpdatePoints (cyclomatic 30) 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:37— form_DataManager.UpdatePoints has cyclomatic complexity 30 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_DataManager.UpdatePoints (cyclomatic 30) 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:37— form_DataManager.UpdatePoints has cyclomatic complexity 30 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsRvtCategoryData.GetPropertyNames (cyclomatic 29) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:178— clsRvtCategoryData.GetPropertyNames has cyclomatic complexity 29 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsRvtCategoryData.GetPropertyNames (cyclomatic 29) 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:178— clsRvtCategoryData.GetPropertyNames has cyclomatic complexity 29 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsRvtCategoryData.GetPropertyNames (cyclomatic 29) 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:178— clsRvtCategoryData.GetPropertyNames has cyclomatic complexity 29 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsRvtCategoryData.GetPropertyNames (cyclomatic 29) 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:178— clsRvtCategoryData.GetPropertyNames has cyclomatic complexity 29 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_RoomMasses.GenerateMasses (cyclomatic 26) 2015/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb:193— form_RoomMasses.GenerateMasses has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_RoomMasses.GenerateMasses (cyclomatic 26) 2016/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb:193— form_RoomMasses.GenerateMasses has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_RoomMasses.GenerateMasses (cyclomatic 26) 2017/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb:193— form_RoomMasses.GenerateMasses has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_RoomMasses.GenerateMasses (cyclomatic 26) 2018/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb:194— form_RoomMasses.GenerateMasses has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Sync.SyncExcelAndRevit (cyclomatic 25) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:108— form_Sync.SyncExcelAndRevit has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Sync.SyncExcelAndRevit (cyclomatic 25) 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:108— form_Sync.SyncExcelAndRevit has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Sync.SyncExcelAndRevit (cyclomatic 25) 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:108— form_Sync.SyncExcelAndRevit has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Sync.SyncExcelAndRevit (cyclomatic 25) 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:108— form_Sync.SyncExcelAndRevit has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D9B42C3FEA6F4F9E8E1B62E993AA2512.Execute (cyclomatic 25) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2512.vb:28— D9B42C3FEA6F4F9E8E1B62E993AA2512.Execute has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D9B42C3FEA6F4F9E8E1B62E993AA2512.Execute (cyclomatic 25) 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2512.vb:28— D9B42C3FEA6F4F9E8E1B62E993AA2512.Execute has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D9B42C3FEA6F4F9E8E1B62E993AA2512.Execute (cyclomatic 25) 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2512.vb:28— D9B42C3FEA6F4F9E8E1B62E993AA2512.Execute has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D9B42C3FEA6F4F9E8E1B62E993AA2512.Execute (cyclomatic 25) 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2512.vb:28— D9B42C3FEA6F4F9E8E1B62E993AA2512.Execute has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
MultiSelectTreeview.SelectNode (cyclomatic 25) 2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:299— MultiSelectTreeview.SelectNode has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
MultiSelectTreeview.SelectNode (cyclomatic 25) 2016/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:299— MultiSelectTreeview.SelectNode has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
MultiSelectTreeview.SelectNode (cyclomatic 25) 2017/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:299— MultiSelectTreeview.SelectNode has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
MultiSelectTreeview.SelectNode (cyclomatic 25) 2018/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:299— MultiSelectTreeview.SelectNode has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsReportingData.New.ctor (cyclomatic 25) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:52— clsReportingData.New.ctor has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsReportingData.New.ctor (cyclomatic 25) 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:52— clsReportingData.New.ctor has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsReportingData.New.ctor (cyclomatic 25) 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:52— clsReportingData.New.ctor has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsReportingData.New.ctor (cyclomatic 25) 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:52— clsReportingData.New.ctor has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_ExportPoints.LoadPreviewData (cyclomatic 25) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:151— form_ExportPoints.LoadPreviewData has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_ExportPoints.LoadPreviewData (cyclomatic 25) 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:151— form_ExportPoints.LoadPreviewData has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_ExportPoints.LoadPreviewData (cyclomatic 25) 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:151— form_ExportPoints.LoadPreviewData has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_ExportPoints.LoadPreviewData (cyclomatic 25) 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:151— form_ExportPoints.LoadPreviewData has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Main.form_Main_Shown (cyclomatic 24) 2015/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb:245— form_Main.form_Main_Shown has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Main.form_Main_Shown (cyclomatic 24) 2016/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb:245— form_Main.form_Main_Shown has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Main.form_Main_Shown (cyclomatic 24) 2017/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb:245— form_Main.form_Main_Shown has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Main.form_Main_Shown (cyclomatic 24) 2018/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb:245— form_Main.form_Main_Shown has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsSettings.doSetup (cyclomatic 23) 2015/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Data/clsSettings.vb:103— clsSettings.doSetup has cyclomatic complexity 23 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsSettings.doSetup (cyclomatic 23) 2016/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Data/clsSettings.vb:103— clsSettings.doSetup has cyclomatic complexity 23 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsSettings.doSetup (cyclomatic 23) 2017/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Data/clsSettings.vb:103— clsSettings.doSetup has cyclomatic complexity 23 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsSettings.doSetup (cyclomatic 23) 2018/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Data/clsSettings.vb:103— clsSettings.doSetup has cyclomatic complexity 23 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Main.RenumberDoors (cyclomatic 22) 2015/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Form/form_Main.vb:66— form_Main.RenumberDoors has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Main.RenumberDoors (cyclomatic 22) 2016/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Form/form_Main.vb:66— form_Main.RenumberDoors has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Main.RenumberDoors (cyclomatic 22) 2017/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Form/form_Main.vb:66— form_Main.RenumberDoors has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Main.RenumberDoors (cyclomatic 22) 2018/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Form/form_Main.vb:66— form_Main.RenumberDoors has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsAutomationTest.Test1 (cyclomatic 22) 2015/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/clsAutomationTest.vb:22— clsAutomationTest.Test1 has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsAutomationTest.Test1 (cyclomatic 22) 2016/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/clsAutomationTest.vb:22— clsAutomationTest.Test1 has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsAutomationTest.Test1 (cyclomatic 22) 2017/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/clsAutomationTest.vb:22— clsAutomationTest.Test1 has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsAutomationTest.Test1 (cyclomatic 22) 2018/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/clsAutomationTest.vb:22— clsAutomationTest.Test1 has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsExcel.GetHeaderData (cyclomatic 21) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:469— clsExcel.GetHeaderData has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsExcel.GetHeaderData (cyclomatic 21) 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:469— clsExcel.GetHeaderData has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsExcel.GetHeaderData (cyclomatic 21) 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:469— clsExcel.GetHeaderData has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsExcel.GetHeaderData (cyclomatic 21) 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:469— clsExcel.GetHeaderData has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsSettings.UpdateMassParameters (cyclomatic 21) 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb:369— clsSettings.UpdateMassParameters has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsSettings.UpdateMassParameters (cyclomatic 21) 2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb:369— clsSettings.UpdateMassParameters has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsSettings.UpdateMassParameters (cyclomatic 21) 2017/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb:369— clsSettings.UpdateMassParameters has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsSettings.UpdateMassParameters (cyclomatic 21) 2018/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb:369— clsSettings.UpdateMassParameters has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsExternalWalls.GetFacingDirection (cyclomatic 21) 2015/Case.Directionality/Case.Directionality/Data/clsExternalWalls.vb:174— clsExternalWalls.GetFacingDirection has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsExternalWalls.GetFacingDirection (cyclomatic 21) 2016/Case.Directionality/Case.Directionality/Data/clsExternalWalls.vb:174— clsExternalWalls.GetFacingDirection has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsExternalWalls.GetFacingDirection (cyclomatic 21) 2017/Case.Directionality/Case.Directionality/Data/clsExternalWalls.vb:174— clsExternalWalls.GetFacingDirection has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsExternalWalls.GetFacingDirection (cyclomatic 21) 2018/Case.Directionality/Case.Directionality/Data/clsExternalWalls.vb:174— clsExternalWalls.GetFacingDirection has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Main.DisplayDoorItems (cyclomatic 21) 2015/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Form/form_Main.vb:275— form_Main.DisplayDoorItems has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Main.DisplayDoorItems (cyclomatic 21) 2016/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Form/form_Main.vb:275— form_Main.DisplayDoorItems has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Main.DisplayDoorItems (cyclomatic 21) 2017/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Form/form_Main.vb:275— form_Main.DisplayDoorItems has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Main.DisplayDoorItems (cyclomatic 21) 2018/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Form/form_Main.vb:275— form_Main.DisplayDoorItems has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
UnitConversion.CalculateDoubleLength (cyclomatic 21) 2015/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb:28— UnitConversion.CalculateDoubleLength has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
UnitConversion.CalculateDoubleLength (cyclomatic 21) 2016/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb:28— UnitConversion.CalculateDoubleLength has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
UnitConversion.CalculateDoubleLength (cyclomatic 21) 2017/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb:28— UnitConversion.CalculateDoubleLength has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
UnitConversion.CalculateDoubleLength (cyclomatic 21) 2018/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb:28— UnitConversion.CalculateDoubleLength has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Main.ProcessData (cyclomatic 21) REDACTED:38— form_Main.ProcessData has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Main.ProcessData (cyclomatic 21) REDACTED:38— form_Main.ProcessData has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Main.ProcessData (cyclomatic 21) REDACTED:38— form_Main.ProcessData has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Main.ProcessData (cyclomatic 21) REDACTED:38— form_Main.ProcessData has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsIoConfig.ReadData (cyclomatic 20) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsIoConfig.vb:60— clsIoConfig.ReadData has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsIoConfig.ReadData (cyclomatic 20) 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsIoConfig.vb:60— clsIoConfig.ReadData has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsIoConfig.ReadData (cyclomatic 20) 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsIoConfig.vb:60— clsIoConfig.ReadData has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsIoConfig.ReadData (cyclomatic 20) 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsIoConfig.vb:60— clsIoConfig.ReadData has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsIoIni.Setup (cyclomatic 20) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsIoIni.vb:44— clsIoIni.Setup has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsIoIni.Setup (cyclomatic 20) 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsIoIni.vb:44— clsIoIni.Setup has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsIoIni.Setup (cyclomatic 20) 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsIoIni.vb:44— clsIoIni.Setup has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsIoIni.Setup (cyclomatic 20) 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsIoIni.vb:44— clsIoIni.Setup has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Sync.UpdateWorksheetData (cyclomatic 20) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:581— form_Sync.UpdateWorksheetData has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Sync.UpdateWorksheetData (cyclomatic 20) 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:581— form_Sync.UpdateWorksheetData has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Sync.UpdateWorksheetData (cyclomatic 20) 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:581— form_Sync.UpdateWorksheetData has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Sync.UpdateWorksheetData (cyclomatic 20) 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:581— form_Sync.UpdateWorksheetData has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D9B42C3FEA6F4F9E8E1B62E993AA2513.Execute (cyclomatic 20) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2513.vb:25— D9B42C3FEA6F4F9E8E1B62E993AA2513.Execute has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D9B42C3FEA6F4F9E8E1B62E993AA2513.Execute (cyclomatic 20) 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2513.vb:25— D9B42C3FEA6F4F9E8E1B62E993AA2513.Execute has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D9B42C3FEA6F4F9E8E1B62E993AA2513.Execute (cyclomatic 20) 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2513.vb:25— D9B42C3FEA6F4F9E8E1B62E993AA2513.Execute has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D9B42C3FEA6F4F9E8E1B62E993AA2513.Execute (cyclomatic 20) 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2513.vb:25— D9B42C3FEA6F4F9E8E1B62E993AA2513.Execute has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Main.LoadViews (cyclomatic 20) 2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:227— form_Main.LoadViews has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Main.LoadViews (cyclomatic 20) 2016/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:227— form_Main.LoadViews has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Main.LoadViews (cyclomatic 20) 2017/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:227— form_Main.LoadViews has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Main.LoadViews (cyclomatic 20) 2018/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:227— form_Main.LoadViews has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Main.makeViews (cyclomatic 20) REDACTED:237— form_Main.makeViews has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
form_Main.makeViews (cyclomatic 20) REDACTED:237— form_Main.makeViews has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
form_Main.makeViews (cyclomatic 20) REDACTED:237— form_Main.makeViews has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
form_Main.makeViews (cyclomatic 20) REDACTED:233— form_Main.makeViews has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
form_Main.DeleteSelections (cyclomatic 19) 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:55— form_Main.DeleteSelections has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Main.DeleteSelections (cyclomatic 19) 2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:55— form_Main.DeleteSelections has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Main.DeleteSelections (cyclomatic 19) 2017/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:55— form_Main.DeleteSelections has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Main.DeleteSelections (cyclomatic 19) 2018/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:55— form_Main.DeleteSelections has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Export.ExportData (cyclomatic 19) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb:36— form_Export.ExportData has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Export.ExportData (cyclomatic 19) 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb:36— form_Export.ExportData has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Export.ExportData (cyclomatic 19) 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb:36— form_Export.ExportData has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Export.ExportData (cyclomatic 19) 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb:36— form_Export.ExportData has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Main.DuplicateViews (cyclomatic 19) 2015/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/UI/form_Main.vb:66— form_Main.DuplicateViews has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Main.DuplicateViews (cyclomatic 19) 2016/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/UI/form_Main.vb:66— form_Main.DuplicateViews has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Main.DuplicateViews (cyclomatic 19) 2017/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/UI/form_Main.vb:66— form_Main.DuplicateViews has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Main.DuplicateViews (cyclomatic 19) 2018/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/UI/form_Main.vb:66— form_Main.DuplicateViews has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_ImportMain.Button_Import_Click (cyclomatic 19) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/UI/form_ImportMain.xaml.vb:47— form_ImportMain.Button_Import_Click has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_ImportMain.Button_Import_Click (cyclomatic 19) 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/UI/form_ImportMain.xaml.vb:47— form_ImportMain.Button_Import_Click has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_ImportMain.Button_Import_Click (cyclomatic 19) 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/UI/form_ImportMain.xaml.vb:47— form_ImportMain.Button_Import_Click has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_ImportMain.Button_Import_Click (cyclomatic 19) 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/UI/form_ImportMain.xaml.vb:47— form_ImportMain.Button_Import_Click has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Parameters.LoadDatagrid (cyclomatic 19) 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_Parameters.vb:51— form_Parameters.LoadDatagrid has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Parameters.LoadDatagrid (cyclomatic 19) 2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_Parameters.vb:51— form_Parameters.LoadDatagrid has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Parameters.LoadDatagrid (cyclomatic 19) 2017/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_Parameters.vb:51— form_Parameters.LoadDatagrid has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Parameters.LoadDatagrid (cyclomatic 19) 2018/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_Parameters.vb:51— form_Parameters.LoadDatagrid has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Data.ShowAsCategoryBasic (cyclomatic 19) 2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:36— form_Data.ShowAsCategoryBasic has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Data.ShowAsCategoryBasic (cyclomatic 19) 2016/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:36— form_Data.ShowAsCategoryBasic has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Data.ShowAsCategoryBasic (cyclomatic 19) 2017/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:36— form_Data.ShowAsCategoryBasic has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Data.ShowAsCategoryBasic (cyclomatic 19) 2018/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:36— form_Data.ShowAsCategoryBasic has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsConfiguration.ReadFile (cyclomatic 19) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsConfiguration.vb:68— clsConfiguration.ReadFile has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsConfiguration.ReadFile (cyclomatic 19) 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsConfiguration.vb:68— clsConfiguration.ReadFile has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsConfiguration.ReadFile (cyclomatic 19) 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsConfiguration.vb:68— clsConfiguration.ReadFile has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsConfiguration.ReadFile (cyclomatic 19) 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsConfiguration.vb:68— clsConfiguration.ReadFile has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Data.ButtonSelect_Click (cyclomatic 18) 2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:611— form_Data.ButtonSelect_Click has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Data.ButtonSelect_Click (cyclomatic 18) 2016/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:611— form_Data.ButtonSelect_Click has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Data.ButtonSelect_Click (cyclomatic 18) 2017/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:611— form_Data.ButtonSelect_Click has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Data.ButtonSelect_Click (cyclomatic 18) 2018/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:611— form_Data.ButtonSelect_Click has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Main.LoadSharedParameters (cyclomatic 17) 2015/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:84— form_Main.LoadSharedParameters has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Main.LoadSharedParameters (cyclomatic 17) 2016/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:84— form_Main.LoadSharedParameters has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Main.LoadSharedParameters (cyclomatic 17) 2017/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:84— form_Main.LoadSharedParameters has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Main.LoadSharedParameters (cyclomatic 17) 2018/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:84— form_Main.LoadSharedParameters has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsSettings.GetViews (cyclomatic 17) 2015/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsSettings.vb:259— clsSettings.GetViews has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsSettings.GetViews (cyclomatic 17) 2016/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsSettings.vb:259— clsSettings.GetViews has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsSettings.GetViews (cyclomatic 17) 2017/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsSettings.vb:259— clsSettings.GetViews has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsSettings.GetViews (cyclomatic 17) 2018/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsSettings.vb:259— clsSettings.GetViews has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Main.DuplicateViews (cyclomatic 17) 2015/Case.MultiViewDuplicate/Case.MultiViewDuplicate/UI/form_Main.vb:66— form_Main.DuplicateViews has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Main.DuplicateViews (cyclomatic 17) 2016/Case.MultiViewDuplicate/Case.MultiViewDuplicate/UI/form_Main.vb:66— form_Main.DuplicateViews has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Main.DuplicateViews (cyclomatic 17) 2017/Case.MultiViewDuplicate/Case.MultiViewDuplicate/UI/form_Main.vb:66— form_Main.DuplicateViews has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Main.DuplicateViews (cyclomatic 17) 2018/Case.MultiViewDuplicate/Case.MultiViewDuplicate/UI/form_Main.vb:66— form_Main.DuplicateViews has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsSettings.Setup (cyclomatic 17) 2015/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:84— clsSettings.Setup has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsSettings.Setup (cyclomatic 17) 2016/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:84— clsSettings.Setup has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsSettings.Setup (cyclomatic 17) 2017/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:84— clsSettings.Setup has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsSettings.Setup (cyclomatic 17) 2018/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:84— clsSettings.Setup has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsExcel.FillDataTableFromExcelWorksheet (cyclomatic 16) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb:169— clsExcel.FillDataTableFromExcelWorksheet has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsExcel.FillDataTableFromExcelWorksheet (cyclomatic 16) 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb:169— clsExcel.FillDataTableFromExcelWorksheet has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsExcel.FillDataTableFromExcelWorksheet (cyclomatic 16) 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb:169— clsExcel.FillDataTableFromExcelWorksheet has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
clsExcel.FillDataTableFromExcelWorksheet (cyclomatic 16) 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb:169— clsExcel.FillDataTableFromExcelWorksheet has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Families.doExport (cyclomatic 16) 2015/Case.Export.Families/Case.Export.Families/Forms/form_Familes.vb:50— form_Families.doExport has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Families.doExport (cyclomatic 16) 2016/Case.Export.Families/Case.Export.Families/Forms/form_Familes.vb:50— form_Families.doExport has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Families.doExport (cyclomatic 16) 2017/Case.Export.Families/Case.Export.Families/Forms/form_Familes.vb:50— form_Families.doExport has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Families.doExport (cyclomatic 16) 2018/Case.Export.Families/Case.Export.Families/Forms/form_Familes.vb:50— form_Families.doExport has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TodoComment 2015/Case.ViewCreator/Case.ViewCreator/Classes/Entry/app.cs:74— //TODO: add you code below. — 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 2016/Case.ViewCreator/Case.ViewCreator/Classes/Entry/app.cs:74— //TODO: add you code below. — 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 2017/Case.ViewCreator/Case.ViewCreator/Classes/Entry/app.cs:74— //TODO: add you code below. — 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 2018/Case.ViewCreator/Case.ViewCreator/Classes/Entry/app.cs:74— //TODO: add you code below. — 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.
D18 · Solution Shape· Solution references a project that does not exist · ×4
Solution references a project that does not exist 2015/Case.Subs.Worksets/Case.Subs.Worksets.sln— `2015/Case.Subs.Worksets/Case.Subs.Worksets.sln` declares 1 project file(s) that are missing from the tree (`Case.Lic.Com/Case.Lic.Com/Case.Lic.Com.vbproj`). A solution-level restore or build fails on a dangling reference, so anyone building the solution rather than an individual project is blocked. Delete the stale entry from the solution, or restore the missing project file.
Solution references a project that does not exist 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass.sln— `2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass.sln` declares 1 project file(s) that are missing from the tree (`Case.Lic/Case.Lic/Case.Lic.vbproj`). A solution-level restore or build fails on a dangling reference, so anyone building the solution rather than an individual project is blocked. Delete the stale entry from the solution, or restore the missing project file.
Solution references a project that does not exist 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS.sln— `2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS.sln` declares 1 project file(s) that are missing from the tree (`Case.Lic.Com/Case.Lic.Com/Case.Lic.Com.vbproj`). A solution-level restore or build fails on a dangling reference, so anyone building the solution rather than an individual project is blocked. Delete the stale entry from the solution, or restore the missing project file.
Solution references a project that does not exist 2015/Case.Subs.SharedParameters/Case.Subs.SharedParameters.sln— `2015/Case.Subs.SharedParameters/Case.Subs.SharedParameters.sln` declares 1 project file(s) that are missing from the tree (`Case.Lic.vbproj`). A solution-level restore or build fails on a dangling reference, so anyone building the solution rather than an individual project is blocked. Delete the stale entry from the solution, or restore the missing project file.
clsRvtCategoryData.GetAllPropertyValues (cognitive 329) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:387— clsRvtCategoryData.GetAllPropertyValues has cognitive complexity 329 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsRvtCategoryData.GetAllPropertyValues (cognitive 329) 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:387— clsRvtCategoryData.GetAllPropertyValues has cognitive complexity 329 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsRvtCategoryData.GetAllPropertyValues (cognitive 329) 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:387— clsRvtCategoryData.GetAllPropertyValues has cognitive complexity 329 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsRvtCategoryData.GetAllPropertyValues (cognitive 329) 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:387— clsRvtCategoryData.GetAllPropertyValues has cognitive complexity 329 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsONSort.SortObjects (cognitive 229) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/OpenNURBS/clsONSort.vb:56— clsONSort.SortObjects has cognitive complexity 229 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsONSort.SortObjects (cognitive 229) 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/OpenNURBS/clsONSort.vb:56— clsONSort.SortObjects has cognitive complexity 229 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsONSort.SortObjects (cognitive 229) 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/OpenNURBS/clsONSort.vb:56— clsONSort.SortObjects has cognitive complexity 229 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsONSort.SortObjects (cognitive 229) 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/OpenNURBS/clsONSort.vb:56— clsONSort.SortObjects has cognitive complexity 229 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.UpdateElementValues (cognitive 192) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:738— clsSettings.UpdateElementValues has cognitive complexity 192 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.UpdateElementValues (cognitive 192) 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:738— clsSettings.UpdateElementValues has cognitive complexity 192 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.UpdateElementValues (cognitive 192) 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:738— clsSettings.UpdateElementValues has cognitive complexity 192 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.UpdateElementValues (cognitive 192) 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:738— clsSettings.UpdateElementValues has cognitive complexity 192 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_RoomMasses.GenerateMasses (cognitive 161) 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:41— form_RoomMasses.GenerateMasses has cognitive complexity 161 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_RoomMasses.GenerateMasses (cognitive 161) 2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:41— form_RoomMasses.GenerateMasses has cognitive complexity 161 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_RoomMasses.GenerateMasses (cognitive 161) 2017/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:41— form_RoomMasses.GenerateMasses has cognitive complexity 161 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_RoomMasses.GenerateMasses (cognitive 161) 2018/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:41— form_RoomMasses.GenerateMasses has cognitive complexity 161 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Sync.UpdateElementData (cognitive 157) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:299— form_Sync.UpdateElementData has cognitive complexity 157 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Sync.UpdateElementData (cognitive 157) 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:299— form_Sync.UpdateElementData has cognitive complexity 157 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Sync.UpdateElementData (cognitive 157) 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:299— form_Sync.UpdateElementData has cognitive complexity 157 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Sync.UpdateElementData (cognitive 157) 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:299— form_Sync.UpdateElementData has cognitive complexity 157 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.GetSymbolNames (cognitive 137) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsSettings.vb:254— clsSettings.GetSymbolNames has cognitive complexity 137 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.GetSymbolNames (cognitive 137) 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsSettings.vb:254— clsSettings.GetSymbolNames has cognitive complexity 137 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.GetSymbolNames (cognitive 137) 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsSettings.vb:254— clsSettings.GetSymbolNames has cognitive complexity 137 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.GetSymbolNames (cognitive 137) 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsSettings.vb:254— clsSettings.GetSymbolNames has cognitive complexity 137 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Form_Main.TagElementsInViews (cognitive 133) 2015/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:326— Form_Main.TagElementsInViews has cognitive complexity 133 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Form_Main.TagElementsInViews (cognitive 133) 2016/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:326— Form_Main.TagElementsInViews has cognitive complexity 133 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Form_Main.TagElementsInViews (cognitive 133) 2017/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:326— Form_Main.TagElementsInViews has cognitive complexity 133 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Form_Main.TagElementsInViews (cognitive 133) 2018/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:326— Form_Main.TagElementsInViews has cognitive complexity 133 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsRvtCategoryData.GetPropertyNames (cognitive 123) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:178— clsRvtCategoryData.GetPropertyNames has cognitive complexity 123 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsRvtCategoryData.GetPropertyNames (cognitive 123) 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:178— clsRvtCategoryData.GetPropertyNames has cognitive complexity 123 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsRvtCategoryData.GetPropertyNames (cognitive 123) 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:178— clsRvtCategoryData.GetPropertyNames has cognitive complexity 123 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsRvtCategoryData.GetPropertyNames (cognitive 123) 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:178— clsRvtCategoryData.GetPropertyNames has cognitive complexity 123 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.ScanCategories (cognitive 113) 2015/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsSettings.vb:179— clsSettings.ScanCategories has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.ScanCategories (cognitive 113) 2016/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsSettings.vb:179— clsSettings.ScanCategories has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.ScanCategories (cognitive 113) 2017/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsSettings.vb:179— clsSettings.ScanCategories has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.ScanCategories (cognitive 113) 2018/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsSettings.vb:179— clsSettings.ScanCategories has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Sync.SyncRooms (cognitive 109) 2015/Case.RoomSync/Case.RoomSync/UI/form_Sync.vb:43— form_Sync.SyncRooms has cognitive complexity 109 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Sync.SyncRooms (cognitive 109) 2016/Case.RoomSync/Case.RoomSync/UI/form_Sync.vb:43— form_Sync.SyncRooms has cognitive complexity 109 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Sync.SyncRooms (cognitive 109) 2017/Case.RoomSync/Case.RoomSync/UI/form_Sync.vb:43— form_Sync.SyncRooms has cognitive complexity 109 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Sync.SyncRooms (cognitive 109) 2018/Case.RoomSync/Case.RoomSync/UI/form_Sync.vb:43— form_Sync.SyncRooms has cognitive complexity 109 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.CalculatePoints (cognitive 106) 2015/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb:32— form_Main.CalculatePoints has cognitive complexity 106 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.CalculatePoints (cognitive 106) 2016/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb:32— form_Main.CalculatePoints has cognitive complexity 106 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.CalculatePoints (cognitive 106) 2017/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb:32— form_Main.CalculatePoints has cognitive complexity 106 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.CalculatePoints (cognitive 106) 2018/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb:32— form_Main.CalculatePoints has cognitive complexity 106 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Form_Main.UpdateFamiliesList (cognitive 101) 2015/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:111— Form_Main.UpdateFamiliesList has cognitive complexity 101 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Form_Main.UpdateFamiliesList (cognitive 101) 2016/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:111— Form_Main.UpdateFamiliesList has cognitive complexity 101 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Form_Main.UpdateFamiliesList (cognitive 101) 2017/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:111— Form_Main.UpdateFamiliesList has cognitive complexity 101 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Form_Main.UpdateFamiliesList (cognitive 101) 2018/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:111— Form_Main.UpdateFamiliesList has cognitive complexity 101 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsExcel.GetHeaderData (cognitive 93) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:469— clsExcel.GetHeaderData has cognitive complexity 93 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsExcel.GetHeaderData (cognitive 93) 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:469— clsExcel.GetHeaderData has cognitive complexity 93 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsExcel.GetHeaderData (cognitive 93) 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:469— clsExcel.GetHeaderData has cognitive complexity 93 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsExcel.GetHeaderData (cognitive 93) 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:469— clsExcel.GetHeaderData has cognitive complexity 93 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D9B42C3FEA6F4F9E8E1B62E993AA2512.Execute (cognitive 93) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2512.vb:28— D9B42C3FEA6F4F9E8E1B62E993AA2512.Execute has cognitive complexity 93 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D9B42C3FEA6F4F9E8E1B62E993AA2512.Execute (cognitive 93) 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2512.vb:28— D9B42C3FEA6F4F9E8E1B62E993AA2512.Execute has cognitive complexity 93 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D9B42C3FEA6F4F9E8E1B62E993AA2512.Execute (cognitive 93) 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2512.vb:28— D9B42C3FEA6F4F9E8E1B62E993AA2512.Execute has cognitive complexity 93 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D9B42C3FEA6F4F9E8E1B62E993AA2512.Execute (cognitive 93) 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2512.vb:28— D9B42C3FEA6F4F9E8E1B62E993AA2512.Execute has cognitive complexity 93 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_PlacePointsFromFile.PlacePoints (cognitive 93) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb:48— form_PlacePointsFromFile.PlacePoints has cognitive complexity 93 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_PlacePointsFromFile.PlacePoints (cognitive 93) 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb:48— form_PlacePointsFromFile.PlacePoints has cognitive complexity 93 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_PlacePointsFromFile.PlacePoints (cognitive 93) 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb:48— form_PlacePointsFromFile.PlacePoints has cognitive complexity 93 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_PlacePointsFromFile.PlacePoints (cognitive 93) 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb:48— form_PlacePointsFromFile.PlacePoints has cognitive complexity 93 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_ExportPoints.New.ctor (cognitive 90) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:13— form_ExportPoints.New.ctor has cognitive complexity 90 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_ExportPoints.New.ctor (cognitive 90) 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:13— form_ExportPoints.New.ctor has cognitive complexity 90 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_ExportPoints.New.ctor (cognitive 90) 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:13— form_ExportPoints.New.ctor has cognitive complexity 90 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_ExportPoints.New.ctor (cognitive 90) 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:13— form_ExportPoints.New.ctor has cognitive complexity 90 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
MultiSelectTreeview.SelectNode (cognitive 89) 2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:299— MultiSelectTreeview.SelectNode has cognitive complexity 89 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
MultiSelectTreeview.SelectNode (cognitive 89) 2016/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:299— MultiSelectTreeview.SelectNode has cognitive complexity 89 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
MultiSelectTreeview.SelectNode (cognitive 89) 2017/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:299— MultiSelectTreeview.SelectNode has cognitive complexity 89 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
MultiSelectTreeview.SelectNode (cognitive 89) 2018/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:299— MultiSelectTreeview.SelectNode has cognitive complexity 89 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsReportingData.New.ctor (cognitive 87) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:309— clsReportingData.New.ctor has cognitive complexity 87 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsReportingData.New.ctor (cognitive 87) 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:309— clsReportingData.New.ctor has cognitive complexity 87 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsReportingData.New.ctor (cognitive 87) 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:309— clsReportingData.New.ctor has cognitive complexity 87 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsReportingData.New.ctor (cognitive 87) 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:309— clsReportingData.New.ctor has cognitive complexity 87 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_RoomMasses.GenerateMasses (cognitive 83) 2015/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb:193— form_RoomMasses.GenerateMasses has cognitive complexity 83 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_RoomMasses.GenerateMasses (cognitive 83) 2016/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb:193— form_RoomMasses.GenerateMasses has cognitive complexity 83 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_RoomMasses.GenerateMasses (cognitive 83) 2017/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb:193— form_RoomMasses.GenerateMasses has cognitive complexity 83 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_RoomMasses.GenerateMasses (cognitive 83) 2018/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb:194— form_RoomMasses.GenerateMasses has cognitive complexity 83 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.DisplayDoorItems (cognitive 81) 2015/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Form/form_Main.vb:275— form_Main.DisplayDoorItems has cognitive complexity 81 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.DisplayDoorItems (cognitive 81) 2016/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Form/form_Main.vb:275— form_Main.DisplayDoorItems has cognitive complexity 81 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.DisplayDoorItems (cognitive 81) 2017/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Form/form_Main.vb:275— form_Main.DisplayDoorItems has cognitive complexity 81 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.DisplayDoorItems (cognitive 81) 2018/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Form/form_Main.vb:275— form_Main.DisplayDoorItems has cognitive complexity 81 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.DuplicateViews (cognitive 80) 2015/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/UI/form_Main.vb:66— form_Main.DuplicateViews has cognitive complexity 80 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.DuplicateViews (cognitive 80) 2016/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/UI/form_Main.vb:66— form_Main.DuplicateViews has cognitive complexity 80 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.DuplicateViews (cognitive 80) 2017/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/UI/form_Main.vb:66— form_Main.DuplicateViews has cognitive complexity 80 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.DuplicateViews (cognitive 80) 2018/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/UI/form_Main.vb:66— form_Main.DuplicateViews has cognitive complexity 80 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_DataManager.UpdatePoints (cognitive 80) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:37— form_DataManager.UpdatePoints has cognitive complexity 80 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_DataManager.UpdatePoints (cognitive 80) 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:37— form_DataManager.UpdatePoints has cognitive complexity 80 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_DataManager.UpdatePoints (cognitive 80) 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:37— form_DataManager.UpdatePoints has cognitive complexity 80 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_DataManager.UpdatePoints (cognitive 80) 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:37— form_DataManager.UpdatePoints has cognitive complexity 80 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.ProcessData (cognitive 79) REDACTED:38— form_Main.ProcessData has cognitive complexity 79 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.ProcessData (cognitive 79) REDACTED:38— form_Main.ProcessData has cognitive complexity 79 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.ProcessData (cognitive 79) REDACTED:38— form_Main.ProcessData has cognitive complexity 79 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.ProcessData (cognitive 79) REDACTED:38— form_Main.ProcessData has cognitive complexity 79 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsExcel.UpdateWorksheetFromArray (cognitive 77) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:704— clsExcel.UpdateWorksheetFromArray has cognitive complexity 77 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsExcel.UpdateWorksheetFromArray (cognitive 77) 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:704— clsExcel.UpdateWorksheetFromArray has cognitive complexity 77 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsExcel.UpdateWorksheetFromArray (cognitive 77) 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:704— clsExcel.UpdateWorksheetFromArray has cognitive complexity 77 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsExcel.UpdateWorksheetFromArray (cognitive 77) 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:704— clsExcel.UpdateWorksheetFromArray has cognitive complexity 77 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsIoIni.Setup (cognitive 75) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsIoIni.vb:44— clsIoIni.Setup has cognitive complexity 75 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsIoIni.Setup (cognitive 75) 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsIoIni.vb:44— clsIoIni.Setup has cognitive complexity 75 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsIoIni.Setup (cognitive 75) 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsIoIni.vb:44— clsIoIni.Setup has cognitive complexity 75 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsIoIni.Setup (cognitive 75) 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsIoIni.vb:44— clsIoIni.Setup has cognitive complexity 75 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsExcel.FillExcelWorksheetFromDataTable (cognitive 74) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb:283— clsExcel.FillExcelWorksheetFromDataTable has cognitive complexity 74 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsExcel.FillExcelWorksheetFromDataTable (cognitive 74) 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb:283— clsExcel.FillExcelWorksheetFromDataTable has cognitive complexity 74 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsExcel.FillExcelWorksheetFromDataTable (cognitive 74) 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb:283— clsExcel.FillExcelWorksheetFromDataTable has cognitive complexity 74 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsExcel.FillExcelWorksheetFromDataTable (cognitive 74) 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb:283— clsExcel.FillExcelWorksheetFromDataTable has cognitive complexity 74 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D9B42C3FEA6F4F9E8E1B62E993AA2513.Execute (cognitive 73) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2513.vb:25— D9B42C3FEA6F4F9E8E1B62E993AA2513.Execute has cognitive complexity 73 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D9B42C3FEA6F4F9E8E1B62E993AA2513.Execute (cognitive 73) 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2513.vb:25— D9B42C3FEA6F4F9E8E1B62E993AA2513.Execute has cognitive complexity 73 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D9B42C3FEA6F4F9E8E1B62E993AA2513.Execute (cognitive 73) 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2513.vb:25— D9B42C3FEA6F4F9E8E1B62E993AA2513.Execute has cognitive complexity 73 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D9B42C3FEA6F4F9E8E1B62E993AA2513.Execute (cognitive 73) 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2513.vb:25— D9B42C3FEA6F4F9E8E1B62E993AA2513.Execute has cognitive complexity 73 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.UpdateMassParameters (cognitive 70) 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb:369— clsSettings.UpdateMassParameters has cognitive complexity 70 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.UpdateMassParameters (cognitive 70) 2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb:369— clsSettings.UpdateMassParameters has cognitive complexity 70 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.UpdateMassParameters (cognitive 70) 2017/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb:369— clsSettings.UpdateMassParameters has cognitive complexity 70 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.UpdateMassParameters (cognitive 70) 2018/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb:369— clsSettings.UpdateMassParameters has cognitive complexity 70 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
MultiSelectTreeview.OnKeyDown (cognitive 69) 2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:165— MultiSelectTreeview.OnKeyDown has cognitive complexity 69 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
MultiSelectTreeview.OnKeyDown (cognitive 69) 2016/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:165— MultiSelectTreeview.OnKeyDown has cognitive complexity 69 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
MultiSelectTreeview.OnKeyDown (cognitive 69) 2017/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:165— MultiSelectTreeview.OnKeyDown has cognitive complexity 69 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
MultiSelectTreeview.OnKeyDown (cognitive 69) 2018/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:165— MultiSelectTreeview.OnKeyDown has cognitive complexity 69 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsReportingData.New.ctor (cognitive 68) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:157— clsReportingData.New.ctor has cognitive complexity 68 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsReportingData.New.ctor (cognitive 68) 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:157— clsReportingData.New.ctor has cognitive complexity 68 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsReportingData.New.ctor (cognitive 68) 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:157— clsReportingData.New.ctor has cognitive complexity 68 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsReportingData.New.ctor (cognitive 68) 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:157— clsReportingData.New.ctor has cognitive complexity 68 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_ImportMain.Button_Import_Click (cognitive 65) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/UI/form_ImportMain.xaml.vb:47— form_ImportMain.Button_Import_Click has cognitive complexity 65 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_ImportMain.Button_Import_Click (cognitive 65) 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/UI/form_ImportMain.xaml.vb:47— form_ImportMain.Button_Import_Click has cognitive complexity 65 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_ImportMain.Button_Import_Click (cognitive 65) 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/UI/form_ImportMain.xaml.vb:47— form_ImportMain.Button_Import_Click has cognitive complexity 65 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_ImportMain.Button_Import_Click (cognitive 65) 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/UI/form_ImportMain.xaml.vb:47— form_ImportMain.Button_Import_Click has cognitive complexity 65 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.RenumberDoors (cognitive 65) 2015/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Form/form_Main.vb:66— form_Main.RenumberDoors has cognitive complexity 65 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.RenumberDoors (cognitive 65) 2016/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Form/form_Main.vb:66— form_Main.RenumberDoors has cognitive complexity 65 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.RenumberDoors (cognitive 65) 2017/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Form/form_Main.vb:66— form_Main.RenumberDoors has cognitive complexity 65 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.RenumberDoors (cognitive 65) 2018/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Form/form_Main.vb:66— form_Main.RenumberDoors has cognitive complexity 65 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.form_Main_Shown (cognitive 63) 2015/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb:245— form_Main.form_Main_Shown has cognitive complexity 63 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.form_Main_Shown (cognitive 63) 2016/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb:245— form_Main.form_Main_Shown has cognitive complexity 63 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.form_Main_Shown (cognitive 63) 2017/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb:245— form_Main.form_Main_Shown has cognitive complexity 63 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.form_Main_Shown (cognitive 63) 2018/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb:245— form_Main.form_Main_Shown has cognitive complexity 63 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsReportingData.New.ctor (cognitive 60) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:52— clsReportingData.New.ctor has cognitive complexity 60 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsReportingData.New.ctor (cognitive 60) 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:52— clsReportingData.New.ctor has cognitive complexity 60 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsReportingData.New.ctor (cognitive 60) 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:52— clsReportingData.New.ctor has cognitive complexity 60 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsReportingData.New.ctor (cognitive 60) 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:52— clsReportingData.New.ctor has cognitive complexity 60 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Sync.SyncExcelAndRevit (cognitive 59) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:108— form_Sync.SyncExcelAndRevit has cognitive complexity 59 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Sync.SyncExcelAndRevit (cognitive 59) 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:108— form_Sync.SyncExcelAndRevit has cognitive complexity 59 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Sync.SyncExcelAndRevit (cognitive 59) 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:108— form_Sync.SyncExcelAndRevit has cognitive complexity 59 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Sync.SyncExcelAndRevit (cognitive 59) 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:108— form_Sync.SyncExcelAndRevit has cognitive complexity 59 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.DuplicateViews (cognitive 58) 2015/Case.MultiViewDuplicate/Case.MultiViewDuplicate/UI/form_Main.vb:66— form_Main.DuplicateViews has cognitive complexity 58 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.DuplicateViews (cognitive 58) 2016/Case.MultiViewDuplicate/Case.MultiViewDuplicate/UI/form_Main.vb:66— form_Main.DuplicateViews has cognitive complexity 58 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.DuplicateViews (cognitive 58) 2017/Case.MultiViewDuplicate/Case.MultiViewDuplicate/UI/form_Main.vb:66— form_Main.DuplicateViews has cognitive complexity 58 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.DuplicateViews (cognitive 58) 2018/Case.MultiViewDuplicate/Case.MultiViewDuplicate/UI/form_Main.vb:66— form_Main.DuplicateViews has cognitive complexity 58 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.LoadSharedParameters (cognitive 57) 2015/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:84— form_Main.LoadSharedParameters has cognitive complexity 57 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.LoadSharedParameters (cognitive 57) 2016/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:84— form_Main.LoadSharedParameters has cognitive complexity 57 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.LoadSharedParameters (cognitive 57) 2017/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:84— form_Main.LoadSharedParameters has cognitive complexity 57 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.LoadSharedParameters (cognitive 57) 2018/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:84— form_Main.LoadSharedParameters has cognitive complexity 57 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Export.ButtonOk_Click (cognitive 55) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb:648— form_Export.ButtonOk_Click has cognitive complexity 55 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Export.ButtonOk_Click (cognitive 55) 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb:648— form_Export.ButtonOk_Click has cognitive complexity 55 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Export.ButtonOk_Click (cognitive 55) 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb:648— form_Export.ButtonOk_Click has cognitive complexity 55 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Export.ButtonOk_Click (cognitive 55) 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb:648— form_Export.ButtonOk_Click has cognitive complexity 55 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.makeViews (cognitive 52) REDACTED:237— form_Main.makeViews has cognitive complexity 52 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.makeViews (cognitive 52) REDACTED:237— form_Main.makeViews has cognitive complexity 52 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.makeViews (cognitive 52) REDACTED:237— form_Main.makeViews has cognitive complexity 52 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.makeViews (cognitive 52) REDACTED:233— form_Main.makeViews has cognitive complexity 52 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Parameters.LoadDatagrid (cognitive 51) 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_Parameters.vb:51— form_Parameters.LoadDatagrid has cognitive complexity 51 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Parameters.LoadDatagrid (cognitive 51) 2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_Parameters.vb:51— form_Parameters.LoadDatagrid has cognitive complexity 51 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Parameters.LoadDatagrid (cognitive 51) 2017/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_Parameters.vb:51— form_Parameters.LoadDatagrid has cognitive complexity 51 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Parameters.LoadDatagrid (cognitive 51) 2018/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_Parameters.vb:51— form_Parameters.LoadDatagrid has cognitive complexity 51 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsIoConfig.ReadData (cognitive 50) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsIoConfig.vb:60— clsIoConfig.ReadData has cognitive complexity 50 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsIoConfig.ReadData (cognitive 50) 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsIoConfig.vb:60— clsIoConfig.ReadData has cognitive complexity 50 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsIoConfig.ReadData (cognitive 50) 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsIoConfig.vb:60— clsIoConfig.ReadData has cognitive complexity 50 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsIoConfig.ReadData (cognitive 50) 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsIoConfig.vb:60— clsIoConfig.ReadData has cognitive complexity 50 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Data.ShowAsCategoryBasic (cognitive 48) 2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:36— form_Data.ShowAsCategoryBasic has cognitive complexity 48 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Data.ShowAsCategoryBasic (cognitive 48) 2016/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:36— form_Data.ShowAsCategoryBasic has cognitive complexity 48 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Data.ShowAsCategoryBasic (cognitive 48) 2017/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:36— form_Data.ShowAsCategoryBasic has cognitive complexity 48 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Data.ShowAsCategoryBasic (cognitive 48) 2018/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:36— form_Data.ShowAsCategoryBasic has cognitive complexity 48 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Data.ButtonSelect_Click (cognitive 48) 2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:611— form_Data.ButtonSelect_Click has cognitive complexity 48 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Data.ButtonSelect_Click (cognitive 48) 2016/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:611— form_Data.ButtonSelect_Click has cognitive complexity 48 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Data.ButtonSelect_Click (cognitive 48) 2017/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:611— form_Data.ButtonSelect_Click has cognitive complexity 48 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Data.ButtonSelect_Click (cognitive 48) 2018/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:611— form_Data.ButtonSelect_Click has cognitive complexity 48 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_ExportPoints.LoadPreviewData (cognitive 48) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:151— form_ExportPoints.LoadPreviewData has cognitive complexity 48 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_ExportPoints.LoadPreviewData (cognitive 48) 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:151— form_ExportPoints.LoadPreviewData has cognitive complexity 48 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_ExportPoints.LoadPreviewData (cognitive 48) 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:151— form_ExportPoints.LoadPreviewData has cognitive complexity 48 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_ExportPoints.LoadPreviewData (cognitive 48) 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:151— form_ExportPoints.LoadPreviewData has cognitive complexity 48 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.GetViews (cognitive 45) 2015/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsSettings.vb:259— clsSettings.GetViews has cognitive complexity 45 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.GetViews (cognitive 45) 2016/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsSettings.vb:259— clsSettings.GetViews has cognitive complexity 45 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.GetViews (cognitive 45) 2017/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsSettings.vb:259— clsSettings.GetViews has cognitive complexity 45 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.GetViews (cognitive 45) 2018/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsSettings.vb:259— clsSettings.GetViews has cognitive complexity 45 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.doSetup (cognitive 44) 2015/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Data/clsSettings.vb:103— clsSettings.doSetup has cognitive complexity 44 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.doSetup (cognitive 44) 2016/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Data/clsSettings.vb:103— clsSettings.doSetup has cognitive complexity 44 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.doSetup (cognitive 44) 2017/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Data/clsSettings.vb:103— clsSettings.doSetup has cognitive complexity 44 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.doSetup (cognitive 44) 2018/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Data/clsSettings.vb:103— clsSettings.doSetup has cognitive complexity 44 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.GetWalls (cognitive 43) 2015/Case.Directionality/Case.Directionality/Data/clsSettings.vb:78— clsSettings.GetWalls has cognitive complexity 43 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.GetWalls (cognitive 43) 2016/Case.Directionality/Case.Directionality/Data/clsSettings.vb:78— clsSettings.GetWalls has cognitive complexity 43 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.GetWalls (cognitive 43) 2017/Case.Directionality/Case.Directionality/Data/clsSettings.vb:78— clsSettings.GetWalls has cognitive complexity 43 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.GetWalls (cognitive 43) 2018/Case.Directionality/Case.Directionality/Data/clsSettings.vb:78— clsSettings.GetWalls has cognitive complexity 43 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Families.doExport (cognitive 42) 2015/Case.Export.Families/Case.Export.Families/Forms/form_Familes.vb:50— form_Families.doExport has cognitive complexity 42 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Families.doExport (cognitive 42) 2016/Case.Export.Families/Case.Export.Families/Forms/form_Familes.vb:50— form_Families.doExport has cognitive complexity 42 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Families.doExport (cognitive 42) 2017/Case.Export.Families/Case.Export.Families/Forms/form_Familes.vb:50— form_Families.doExport has cognitive complexity 42 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Families.doExport (cognitive 42) 2018/Case.Export.Families/Case.Export.Families/Forms/form_Familes.vb:50— form_Families.doExport has cognitive complexity 42 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.RenameStuff (cognitive 41) 2015/Case.ChangeReplaceFamTypeNames/Case.ChangeReplaceFamTypeNames/UI/form_Main.vb:49— form_Main.RenameStuff has cognitive complexity 41 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.RenameStuff (cognitive 41) 2016/Case.ChangeReplaceFamTypeNames/Case.ChangeReplaceFamTypeNames/UI/form_Main.vb:49— form_Main.RenameStuff has cognitive complexity 41 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.RenameStuff (cognitive 41) 2017/Case.ChangeReplaceFamTypeNames/Case.ChangeReplaceFamTypeNames/UI/form_Main.vb:49— form_Main.RenameStuff has cognitive complexity 41 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.RenameStuff (cognitive 41) 2018/Case.ChangeReplaceFamTypeNames/Case.ChangeReplaceFamTypeNames/UI/form_Main.vb:49— form_Main.RenameStuff has cognitive complexity 41 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.LoadSharedParameters (cognitive 39) 2015/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:117— form_Main.LoadSharedParameters has cognitive complexity 39 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.LoadSharedParameters (cognitive 39) 2016/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:117— form_Main.LoadSharedParameters has cognitive complexity 39 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.LoadSharedParameters (cognitive 39) 2017/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:117— form_Main.LoadSharedParameters has cognitive complexity 39 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.LoadSharedParameters (cognitive 39) 2018/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:117— form_Main.LoadSharedParameters has cognitive complexity 39 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.GetViews (cognitive 38) 2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/clsSettings.vb:103— clsSettings.GetViews has cognitive complexity 38 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.GetViews (cognitive 38) 2016/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/clsSettings.vb:103— clsSettings.GetViews has cognitive complexity 38 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.GetViews (cognitive 38) 2017/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/clsSettings.vb:103— clsSettings.GetViews has cognitive complexity 38 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.GetViews (cognitive 38) 2018/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/clsSettings.vb:103— clsSettings.GetViews has cognitive complexity 38 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.DeleteCheckedItems (cognitive 37) 2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:32— form_Main.DeleteCheckedItems has cognitive complexity 37 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.DeleteCheckedItems (cognitive 37) 2016/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:32— form_Main.DeleteCheckedItems has cognitive complexity 37 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.DeleteCheckedItems (cognitive 37) 2017/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:32— form_Main.DeleteCheckedItems has cognitive complexity 37 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.DeleteCheckedItems (cognitive 37) 2018/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:32— form_Main.DeleteCheckedItems has cognitive complexity 37 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsConfiguration.ReadFile (cognitive 37) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsConfiguration.vb:68— clsConfiguration.ReadFile has cognitive complexity 37 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsConfiguration.ReadFile (cognitive 37) 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsConfiguration.vb:68— clsConfiguration.ReadFile has cognitive complexity 37 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsConfiguration.ReadFile (cognitive 37) 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsConfiguration.vb:68— clsConfiguration.ReadFile has cognitive complexity 37 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsConfiguration.ReadFile (cognitive 37) 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsConfiguration.vb:68— clsConfiguration.ReadFile has cognitive complexity 37 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsExcel.FillDataTableFromExcelWorksheet (cognitive 37) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb:169— clsExcel.FillDataTableFromExcelWorksheet has cognitive complexity 37 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsExcel.FillDataTableFromExcelWorksheet (cognitive 37) 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb:169— clsExcel.FillDataTableFromExcelWorksheet has cognitive complexity 37 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsExcel.FillDataTableFromExcelWorksheet (cognitive 37) 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb:169— clsExcel.FillDataTableFromExcelWorksheet has cognitive complexity 37 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsExcel.FillDataTableFromExcelWorksheet (cognitive 37) 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb:169— clsExcel.FillDataTableFromExcelWorksheet has cognitive complexity 37 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsAutomationTest.Test1 (cognitive 37) 2015/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/clsAutomationTest.vb:22— clsAutomationTest.Test1 has cognitive complexity 37 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsAutomationTest.Test1 (cognitive 37) 2016/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/clsAutomationTest.vb:22— clsAutomationTest.Test1 has cognitive complexity 37 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsAutomationTest.Test1 (cognitive 37) 2017/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/clsAutomationTest.vb:22— clsAutomationTest.Test1 has cognitive complexity 37 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsAutomationTest.Test1 (cognitive 37) 2018/Case.FreeBenchmarking/Case.FreeBenchmarking/Classes/clsAutomationTest.vb:22— clsAutomationTest.Test1 has cognitive complexity 37 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.DeleteSelections (cognitive 36) 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:55— form_Main.DeleteSelections has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.DeleteSelections (cognitive 36) 2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:55— form_Main.DeleteSelections has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.DeleteSelections (cognitive 36) 2017/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:55— form_Main.DeleteSelections has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.DeleteSelections (cognitive 36) 2018/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:55— form_Main.DeleteSelections has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Sync.UpdateWorksheetData (cognitive 36) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:581— form_Sync.UpdateWorksheetData has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Sync.UpdateWorksheetData (cognitive 36) 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:581— form_Sync.UpdateWorksheetData has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Sync.UpdateWorksheetData (cognitive 36) 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:581— form_Sync.UpdateWorksheetData has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Sync.UpdateWorksheetData (cognitive 36) 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:581— form_Sync.UpdateWorksheetData has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.UpdateAll (cognitive 36) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSettings.vb:311— clsSettings.UpdateAll has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.UpdateAll (cognitive 36) 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSettings.vb:311— clsSettings.UpdateAll has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.UpdateAll (cognitive 36) 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSettings.vb:311— clsSettings.UpdateAll has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.UpdateAll (cognitive 36) 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSettings.vb:311— clsSettings.UpdateAll has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Data.ShowAsWorksetsBasic (cognitive 36) 2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:163— form_Data.ShowAsWorksetsBasic has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Data.ShowAsWorksetsBasic (cognitive 36) 2016/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:163— form_Data.ShowAsWorksetsBasic has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Data.ShowAsWorksetsBasic (cognitive 36) 2017/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:163— form_Data.ShowAsWorksetsBasic has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Data.ShowAsWorksetsBasic (cognitive 36) 2018/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:163— form_Data.ShowAsWorksetsBasic has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.ScanCategories (cognitive 36) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsSettings.vb:149— clsSettings.ScanCategories has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.ScanCategories (cognitive 36) 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsSettings.vb:149— clsSettings.ScanCategories has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.ScanCategories (cognitive 36) 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsSettings.vb:149— clsSettings.ScanCategories has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.ScanCategories (cognitive 36) 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsSettings.vb:149— clsSettings.ScanCategories has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsExternalWalls.GetFacingDirection (cognitive 36) 2015/Case.Directionality/Case.Directionality/Data/clsExternalWalls.vb:174— clsExternalWalls.GetFacingDirection has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsExternalWalls.GetFacingDirection (cognitive 36) 2016/Case.Directionality/Case.Directionality/Data/clsExternalWalls.vb:174— clsExternalWalls.GetFacingDirection has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsExternalWalls.GetFacingDirection (cognitive 36) 2017/Case.Directionality/Case.Directionality/Data/clsExternalWalls.vb:174— clsExternalWalls.GetFacingDirection has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsExternalWalls.GetFacingDirection (cognitive 36) 2018/Case.Directionality/Case.Directionality/Data/clsExternalWalls.vb:174— clsExternalWalls.GetFacingDirection has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.ReplaceStyles (cognitive 35) 2015/Case.Subs.Linestyles/Case.Subs.Linestyles/Data/clsSettings.vb:216— clsSettings.ReplaceStyles has cognitive complexity 35 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.ReplaceStyles (cognitive 35) 2016/Case.Subs.Linestyles/Case.Subs.Linestyles/Data/clsSettings.vb:216— clsSettings.ReplaceStyles has cognitive complexity 35 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.ReplaceStyles (cognitive 35) 2017/Case.Subs.Linestyles/Case.Subs.Linestyles/Data/clsSettings.vb:216— clsSettings.ReplaceStyles has cognitive complexity 35 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.ReplaceStyles (cognitive 35) 2018/Case.Subs.Linestyles/Case.Subs.Linestyles/Data/clsSettings.vb:216— clsSettings.ReplaceStyles has cognitive complexity 35 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.LoadViews (cognitive 35) 2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:227— form_Main.LoadViews has cognitive complexity 35 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.LoadViews (cognitive 35) 2016/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:227— form_Main.LoadViews has cognitive complexity 35 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.LoadViews (cognitive 35) 2017/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:227— form_Main.LoadViews has cognitive complexity 35 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.LoadViews (cognitive 35) 2018/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:227— form_Main.LoadViews has cognitive complexity 35 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.PlaceFixtures (cognitive 35) 2015/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb:549— clsSettings.PlaceFixtures has cognitive complexity 35 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.PlaceFixtures (cognitive 35) 2016/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb:549— clsSettings.PlaceFixtures has cognitive complexity 35 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.PlaceFixtures (cognitive 35) 2017/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb:549— clsSettings.PlaceFixtures has cognitive complexity 35 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.PlaceFixtures (cognitive 35) 2018/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb:549— clsSettings.PlaceFixtures has cognitive complexity 35 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Rename.UpdateTypesListing (cognitive 34) 2015/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb:122— form_Rename.UpdateTypesListing has cognitive complexity 34 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Rename.UpdateTypesListing (cognitive 34) 2016/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb:122— form_Rename.UpdateTypesListing has cognitive complexity 34 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Rename.UpdateTypesListing (cognitive 34) 2017/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb:122— form_Rename.UpdateTypesListing has cognitive complexity 34 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Rename.UpdateTypesListing (cognitive 34) 2018/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb:122— form_Rename.UpdateTypesListing has cognitive complexity 34 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_PlacePoint.ButtonBasepointBySymbol_Click (cognitive 34) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb:210— form_PlacePoint.ButtonBasepointBySymbol_Click has cognitive complexity 34 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_PlacePoint.ButtonBasepointBySymbol_Click (cognitive 34) 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb:210— form_PlacePoint.ButtonBasepointBySymbol_Click has cognitive complexity 34 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_PlacePoint.ButtonBasepointBySymbol_Click (cognitive 34) 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb:210— form_PlacePoint.ButtonBasepointBySymbol_Click has cognitive complexity 34 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_PlacePoint.ButtonBasepointBySymbol_Click (cognitive 34) 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb:210— form_PlacePoint.ButtonBasepointBySymbol_Click has cognitive complexity 34 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Export.ExportData (cognitive 33) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb:36— form_Export.ExportData has cognitive complexity 33 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Export.ExportData (cognitive 33) 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb:36— form_Export.ExportData has cognitive complexity 33 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Export.ExportData (cognitive 33) 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb:36— form_Export.ExportData has cognitive complexity 33 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Export.ExportData (cognitive 33) 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb:36— form_Export.ExportData has cognitive complexity 33 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Rename.ButtonRename_Click (cognitive 33) 2015/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb:264— form_Rename.ButtonRename_Click has cognitive complexity 33 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Rename.ButtonRename_Click (cognitive 33) 2016/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb:264— form_Rename.ButtonRename_Click has cognitive complexity 33 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Rename.ButtonRename_Click (cognitive 33) 2017/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb:264— form_Rename.ButtonRename_Click has cognitive complexity 33 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Rename.ButtonRename_Click (cognitive 33) 2018/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb:264— form_Rename.ButtonRename_Click has cognitive complexity 33 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsFamilyType.RenameElement (cognitive 32) 2015/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsFamilyType.vb:147— clsFamilyType.RenameElement has cognitive complexity 32 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsFamilyType.RenameElement (cognitive 32) 2016/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsFamilyType.vb:147— clsFamilyType.RenameElement has cognitive complexity 32 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsFamilyType.RenameElement (cognitive 32) 2017/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsFamilyType.vb:147— clsFamilyType.RenameElement has cognitive complexity 32 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsFamilyType.RenameElement (cognitive 32) 2018/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsFamilyType.vb:147— clsFamilyType.RenameElement has cognitive complexity 32 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_DataManager.ButtonBrowse_Click (cognitive 31) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:301— form_DataManager.ButtonBrowse_Click has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_DataManager.ButtonBrowse_Click (cognitive 31) 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:301— form_DataManager.ButtonBrowse_Click has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_DataManager.ButtonBrowse_Click (cognitive 31) 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:301— form_DataManager.ButtonBrowse_Click has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_DataManager.ButtonBrowse_Click (cognitive 31) 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:301— form_DataManager.ButtonBrowse_Click has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.Setup (cognitive 30) 2015/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/Data/clsSettings.vb:123— clsSettings.Setup has cognitive complexity 30 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.Setup (cognitive 30) 2016/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/Data/clsSettings.vb:123— clsSettings.Setup has cognitive complexity 30 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.Setup (cognitive 30) 2017/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/Data/clsSettings.vb:123— clsSettings.Setup has cognitive complexity 30 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.Setup (cognitive 30) 2018/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/Data/clsSettings.vb:123— clsSettings.Setup has cognitive complexity 30 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsRoom.ExtractBoundaryPointsFromRoom (cognitive 30) 2015/Case.LightingLayout/Case.LightingLayout/Data/clsRoom.vb:174— clsRoom.ExtractBoundaryPointsFromRoom has cognitive complexity 30 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsRoom.ExtractBoundaryPointsFromRoom (cognitive 30) 2016/Case.LightingLayout/Case.LightingLayout/Data/clsRoom.vb:174— clsRoom.ExtractBoundaryPointsFromRoom has cognitive complexity 30 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsRoom.ExtractBoundaryPointsFromRoom (cognitive 30) 2017/Case.LightingLayout/Case.LightingLayout/Data/clsRoom.vb:174— clsRoom.ExtractBoundaryPointsFromRoom has cognitive complexity 30 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsRoom.ExtractBoundaryPointsFromRoom (cognitive 30) 2018/Case.LightingLayout/Case.LightingLayout/Data/clsRoom.vb:174— clsRoom.ExtractBoundaryPointsFromRoom has cognitive complexity 30 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSpace.ExtractBoundaryPointsFromSpace (cognitive 30) 2015/Case.LightingLayout/Case.LightingLayout/Data/clsSpace.vb:174— clsSpace.ExtractBoundaryPointsFromSpace has cognitive complexity 30 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSpace.ExtractBoundaryPointsFromSpace (cognitive 30) 2016/Case.LightingLayout/Case.LightingLayout/Data/clsSpace.vb:174— clsSpace.ExtractBoundaryPointsFromSpace has cognitive complexity 30 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSpace.ExtractBoundaryPointsFromSpace (cognitive 30) 2017/Case.LightingLayout/Case.LightingLayout/Data/clsSpace.vb:174— clsSpace.ExtractBoundaryPointsFromSpace has cognitive complexity 30 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSpace.ExtractBoundaryPointsFromSpace (cognitive 30) 2018/Case.LightingLayout/Case.LightingLayout/Data/clsSpace.vb:174— clsSpace.ExtractBoundaryPointsFromSpace has cognitive complexity 30 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsExcel._GetSelectedSyncHeaderColumns (cognitive 29) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:324— clsExcel._GetSelectedSyncHeaderColumns has cognitive complexity 29 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsExcel._GetSelectedSyncHeaderColumns (cognitive 29) 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:324— clsExcel._GetSelectedSyncHeaderColumns has cognitive complexity 29 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsExcel._GetSelectedSyncHeaderColumns (cognitive 29) 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:324— clsExcel._GetSelectedSyncHeaderColumns has cognitive complexity 29 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsExcel._GetSelectedSyncHeaderColumns (cognitive 29) 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:324— clsExcel._GetSelectedSyncHeaderColumns has cognitive complexity 29 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Sync.GetCategoryAndKeys (cognitive 29) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:38— form_Sync.GetCategoryAndKeys has cognitive complexity 29 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Sync.GetCategoryAndKeys (cognitive 29) 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:38— form_Sync.GetCategoryAndKeys has cognitive complexity 29 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Sync.GetCategoryAndKeys (cognitive 29) 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:38— form_Sync.GetCategoryAndKeys has cognitive complexity 29 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Sync.GetCategoryAndKeys (cognitive 29) 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:38— form_Sync.GetCategoryAndKeys has cognitive complexity 29 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.Setup (cognitive 29) 2015/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:84— clsSettings.Setup has cognitive complexity 29 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.Setup (cognitive 29) 2016/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:84— clsSettings.Setup has cognitive complexity 29 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.Setup (cognitive 29) 2017/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:84— clsSettings.Setup has cognitive complexity 29 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.Setup (cognitive 29) 2018/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:84— clsSettings.Setup has cognitive complexity 29 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.GetInstances (cognitive 28) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSettings.vb:509— clsSettings.GetInstances has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.GetInstances (cognitive 28) 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSettings.vb:509— clsSettings.GetInstances has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.GetInstances (cognitive 28) 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSettings.vb:509— clsSettings.GetInstances has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.GetInstances (cognitive 28) 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSettings.vb:509— clsSettings.GetInstances has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Data.ShowAsKindsBasic (cognitive 28) 2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:268— form_Data.ShowAsKindsBasic has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Data.ShowAsKindsBasic (cognitive 28) 2016/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:268— form_Data.ShowAsKindsBasic has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Data.ShowAsKindsBasic (cognitive 28) 2017/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:268— form_Data.ShowAsKindsBasic has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Data.ShowAsKindsBasic (cognitive 28) 2018/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:268— form_Data.ShowAsKindsBasic has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_PlacePoint.ButtonBasepointByCategory_Click (cognitive 28) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb:115— form_PlacePoint.ButtonBasepointByCategory_Click has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_PlacePoint.ButtonBasepointByCategory_Click (cognitive 28) 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb:115— form_PlacePoint.ButtonBasepointByCategory_Click has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_PlacePoint.ButtonBasepointByCategory_Click (cognitive 28) 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb:115— form_PlacePoint.ButtonBasepointByCategory_Click has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_PlacePoint.ButtonBasepointByCategory_Click (cognitive 28) 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb:115— form_PlacePoint.ButtonBasepointByCategory_Click has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.GetViews (cognitive 28) 2015/Case.ViewTemplates/Case.ViewTemplates/Data/clsSettings.vb:92— clsSettings.GetViews has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.GetViews (cognitive 28) 2016/Case.ViewTemplates/Case.ViewTemplates/Data/clsSettings.vb:92— clsSettings.GetViews has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.GetViews (cognitive 28) 2017/Case.ViewTemplates/Case.ViewTemplates/Data/clsSettings.vb:92— clsSettings.GetViews has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.GetViews (cognitive 28) 2018/Case.ViewTemplates/Case.ViewTemplates/Data/clsSettings.vb:92— clsSettings.GetViews has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_ExportSchedule.ExportSchedules (cognitive 27) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_ExportSchedule.vb:58— form_ExportSchedule.ExportSchedules has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_ExportSchedule.ExportSchedules (cognitive 27) 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_ExportSchedule.vb:58— form_ExportSchedule.ExportSchedules has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_ExportSchedule.ExportSchedules (cognitive 27) 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_ExportSchedule.vb:58— form_ExportSchedule.ExportSchedules has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_ExportSchedule.ExportSchedules (cognitive 27) 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_ExportSchedule.vb:58— form_ExportSchedule.ExportSchedules has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsExcel.Setup (cognitive 26) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:122— clsExcel.Setup has cognitive complexity 26 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsExcel.Setup (cognitive 26) 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:122— clsExcel.Setup has cognitive complexity 26 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsExcel.Setup (cognitive 26) 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:122— clsExcel.Setup has cognitive complexity 26 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsExcel.Setup (cognitive 26) 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:122— clsExcel.Setup has cognitive complexity 26 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSharedParameters.BindDefinitionsToCategories (cognitive 26) 2015/Case.Subs.SharedParameters/Case.Subs.SharedParameters/Data/clsSharedParameters.vb:155— clsSharedParameters.BindDefinitionsToCategories has cognitive complexity 26 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSharedParameters.BindDefinitionsToCategories (cognitive 26) 2016/Case.Subs.SharedParameters/Case.Subs.SharedParameters/Data/clsSharedParameters.vb:155— clsSharedParameters.BindDefinitionsToCategories has cognitive complexity 26 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSharedParameters.BindDefinitionsToCategories (cognitive 26) 2017/Case.Subs.SharedParameters/Case.Subs.SharedParameters/Data/clsSharedParameters.vb:155— clsSharedParameters.BindDefinitionsToCategories has cognitive complexity 26 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSharedParameters.BindDefinitionsToCategories (cognitive 26) 2018/Case.Subs.SharedParameters/Case.Subs.SharedParameters/Data/clsSharedParameters.vb:155— clsSharedParameters.BindDefinitionsToCategories has cognitive complexity 26 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsRvtScheduleData.WriteSectionRowHtml (cognitive 25) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb:259— clsRvtScheduleData.WriteSectionRowHtml has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsRvtScheduleData.WriteSectionRowHtml (cognitive 25) 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb:259— clsRvtScheduleData.WriteSectionRowHtml has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsRvtScheduleData.WriteSectionRowHtml (cognitive 25) 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb:259— clsRvtScheduleData.WriteSectionRowHtml has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsRvtScheduleData.WriteSectionRowHtml (cognitive 25) 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb:259— clsRvtScheduleData.WriteSectionRowHtml has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Rename.Setup (cognitive 25) 2015/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb:30— form_Rename.Setup has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Rename.Setup (cognitive 25) 2016/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb:30— form_Rename.Setup has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Rename.Setup (cognitive 25) 2017/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb:30— form_Rename.Setup has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Rename.Setup (cognitive 25) 2018/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb:30— form_Rename.Setup has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
RVTFamilyMassUtils.RVTTrimSurface (cognitive 24) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:313— RVTFamilyMassUtils.RVTTrimSurface has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
RVTFamilyMassUtils.RVTTrimSurface (cognitive 24) 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:313— RVTFamilyMassUtils.RVTTrimSurface has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
RVTFamilyMassUtils.RVTTrimSurface (cognitive 24) 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:313— RVTFamilyMassUtils.RVTTrimSurface has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
RVTFamilyMassUtils.RVTTrimSurface (cognitive 24) 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:313— RVTFamilyMassUtils.RVTTrimSurface has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.ImportData (cognitive 24) 2015/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsSettings.vb:143— clsSettings.ImportData has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.ImportData (cognitive 24) 2016/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsSettings.vb:143— clsSettings.ImportData has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.ImportData (cognitive 24) 2017/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsSettings.vb:143— clsSettings.ImportData has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.ImportData (cognitive 24) 2018/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsSettings.vb:143— clsSettings.ImportData has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Tag.LoadViewports (cognitive 24) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Tag.vb:30— form_Tag.LoadViewports has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Tag.LoadViewports (cognitive 24) 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Tag.vb:30— form_Tag.LoadViewports has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Tag.LoadViewports (cognitive 24) 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Tag.vb:30— form_Tag.LoadViewports has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Tag.LoadViewports (cognitive 24) 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Tag.vb:30— form_Tag.LoadViewports has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_ParameterConfigurationManager.ButtonSave_Click (cognitive 24) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ParameterConfigurationManager.xaml.vb:114— form_ParameterConfigurationManager.ButtonSave_Click has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_ParameterConfigurationManager.ButtonSave_Click (cognitive 24) 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ParameterConfigurationManager.xaml.vb:114— form_ParameterConfigurationManager.ButtonSave_Click has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_ParameterConfigurationManager.ButtonSave_Click (cognitive 24) 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ParameterConfigurationManager.xaml.vb:114— form_ParameterConfigurationManager.ButtonSave_Click has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_ParameterConfigurationManager.ButtonSave_Click (cognitive 24) 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ParameterConfigurationManager.xaml.vb:114— form_ParameterConfigurationManager.ButtonSave_Click has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.LevelHosting (cognitive 24) 2015/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb:250— form_Main.LevelHosting has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.LevelHosting (cognitive 24) 2016/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb:250— form_Main.LevelHosting has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.LevelHosting (cognitive 24) 2017/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb:251— form_Main.LevelHosting has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.LevelHosting (cognitive 24) 2018/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb:251— form_Main.LevelHosting has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.buttonOk_Click (cognitive 24) REDACTED:75— form_Main.buttonOk_Click has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.buttonOk_Click (cognitive 24) REDACTED:75— form_Main.buttonOk_Click has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.buttonOk_Click (cognitive 24) REDACTED:75— form_Main.buttonOk_Click has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.buttonOk_Click (cognitive 24) REDACTED:75— form_Main.buttonOk_Click has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Find.FilterListings (cognitive 23) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:102— form_Find.FilterListings has cognitive complexity 23 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Find.FilterListings (cognitive 23) 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:102— form_Find.FilterListings has cognitive complexity 23 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Find.FilterListings (cognitive 23) 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:102— form_Find.FilterListings has cognitive complexity 23 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Find.FilterListings (cognitive 23) 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:102— form_Find.FilterListings has cognitive complexity 23 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.ReplaceStyles (cognitive 23) 2015/Case.LineChanger/Case.LineChanger/Data/clsSettings.vb:128— clsSettings.ReplaceStyles has cognitive complexity 23 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.ReplaceStyles (cognitive 23) 2016/Case.LineChanger/Case.LineChanger/Data/clsSettings.vb:128— clsSettings.ReplaceStyles has cognitive complexity 23 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.ReplaceStyles (cognitive 23) 2017/Case.LineChanger/Case.LineChanger/Data/clsSettings.vb:128— clsSettings.ReplaceStyles has cognitive complexity 23 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.ReplaceStyles (cognitive 23) 2018/Case.LineChanger/Case.LineChanger/Data/clsSettings.vb:128— clsSettings.ReplaceStyles has cognitive complexity 23 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D9B42C3FEA6F4F9E8E1B62E993AA2514.Execute (cognitive 22) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2514.vb:25— D9B42C3FEA6F4F9E8E1B62E993AA2514.Execute has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D9B42C3FEA6F4F9E8E1B62E993AA2514.Execute (cognitive 22) 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2514.vb:25— D9B42C3FEA6F4F9E8E1B62E993AA2514.Execute has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D9B42C3FEA6F4F9E8E1B62E993AA2514.Execute (cognitive 22) 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2514.vb:25— D9B42C3FEA6F4F9E8E1B62E993AA2514.Execute has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D9B42C3FEA6F4F9E8E1B62E993AA2514.Execute (cognitive 22) 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2514.vb:25— D9B42C3FEA6F4F9E8E1B62E993AA2514.Execute has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_ParameterConfigurationManager.ComboBoxCategory_SelectionChanged (cognitive 22) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ParameterConfigurationManager.xaml.vb:51— form_ParameterConfigurationManager.ComboBoxCategory_SelectionChanged has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_ParameterConfigurationManager.ComboBoxCategory_SelectionChanged (cognitive 22) 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ParameterConfigurationManager.xaml.vb:51— form_ParameterConfigurationManager.ComboBoxCategory_SelectionChanged has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_ParameterConfigurationManager.ComboBoxCategory_SelectionChanged (cognitive 22) 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ParameterConfigurationManager.xaml.vb:51— form_ParameterConfigurationManager.ComboBoxCategory_SelectionChanged has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_ParameterConfigurationManager.ComboBoxCategory_SelectionChanged (cognitive 22) 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ParameterConfigurationManager.xaml.vb:51— form_ParameterConfigurationManager.ComboBoxCategory_SelectionChanged has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.ProcessData (cognitive 22) 2015/Case.ReportGroupsByView/Case.ReportGroupsByView/UI/form_Main.cs:36— form_Main.ProcessData has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
form_Main.ProcessData (cognitive 22) 2016/Case.ReportGroupsByView/Case.ReportGroupsByView/UI/form_Main.cs:36— form_Main.ProcessData has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
form_Main.ProcessData (cognitive 22) 2017/Case.ReportGroupsByView/Case.ReportGroupsByView/UI/form_Main.cs:36— form_Main.ProcessData has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
form_Main.ProcessData (cognitive 22) 2018/Case.ReportGroupsByView/Case.ReportGroupsByView/UI/form_Main.cs:36— form_Main.ProcessData has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
clsSettings.SetComplexDataValue (cognitive 21) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:592— clsSettings.SetComplexDataValue has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.SetComplexDataValue (cognitive 21) 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:592— clsSettings.SetComplexDataValue has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.SetComplexDataValue (cognitive 21) 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:592— clsSettings.SetComplexDataValue has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.SetComplexDataValue (cognitive 21) 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:592— clsSettings.SetComplexDataValue has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
RVTCurveUtils.RVTNurbsCrv (cognitive 21) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:522— RVTCurveUtils.RVTNurbsCrv has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
RVTCurveUtils.RVTNurbsCrv (cognitive 21) 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:522— RVTCurveUtils.RVTNurbsCrv has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
RVTCurveUtils.RVTNurbsCrv (cognitive 21) 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:522— RVTCurveUtils.RVTNurbsCrv has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
RVTCurveUtils.RVTNurbsCrv (cognitive 21) 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:522— RVTCurveUtils.RVTNurbsCrv has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSharedParameters.BindDefinitionsToCategories (cognitive 21) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSharedParameters.vb:191— clsSharedParameters.BindDefinitionsToCategories has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSharedParameters.BindDefinitionsToCategories (cognitive 21) 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSharedParameters.vb:191— clsSharedParameters.BindDefinitionsToCategories has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSharedParameters.BindDefinitionsToCategories (cognitive 21) 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSharedParameters.vb:191— clsSharedParameters.BindDefinitionsToCategories has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSharedParameters.BindDefinitionsToCategories (cognitive 21) 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSharedParameters.vb:191— clsSharedParameters.BindDefinitionsToCategories has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.DeleteViews (cognitive 21) 2015/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Data/clsSettings.vb:141— clsSettings.DeleteViews has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.DeleteViews (cognitive 21) 2016/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Data/clsSettings.vb:141— clsSettings.DeleteViews has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.DeleteViews (cognitive 21) 2017/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Data/clsSettings.vb:141— clsSettings.DeleteViews has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.DeleteViews (cognitive 21) 2018/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Data/clsSettings.vb:141— clsSettings.DeleteViews has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Config.ButtonFamilyRemove_Click (cognitive 20) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:639— form_Config.ButtonFamilyRemove_Click has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Config.ButtonFamilyRemove_Click (cognitive 20) 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:639— form_Config.ButtonFamilyRemove_Click has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Config.ButtonFamilyRemove_Click (cognitive 20) 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:639— form_Config.ButtonFamilyRemove_Click has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Config.ButtonFamilyRemove_Click (cognitive 20) 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:639— form_Config.ButtonFamilyRemove_Click has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsReportingData.GetElementData (cognitive 20) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:515— clsReportingData.GetElementData has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsReportingData.GetElementData (cognitive 20) 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:515— clsReportingData.GetElementData has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsReportingData.GetElementData (cognitive 20) 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:515— clsReportingData.GetElementData has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsReportingData.GetElementData (cognitive 20) 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:515— clsReportingData.GetElementData has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
RVTBrepEdgeUtils.RVTCurveByPoints (cognitive 19) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:346— RVTBrepEdgeUtils.RVTCurveByPoints has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
RVTBrepEdgeUtils.RVTCurveByPoints (cognitive 19) 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:346— RVTBrepEdgeUtils.RVTCurveByPoints has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
RVTBrepEdgeUtils.RVTCurveByPoints (cognitive 19) 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:346— RVTBrepEdgeUtils.RVTCurveByPoints has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
RVTBrepEdgeUtils.RVTCurveByPoints (cognitive 19) 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:346— RVTBrepEdgeUtils.RVTCurveByPoints has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
RVTCurveUtils.RVTCurveByPoints (cognitive 19) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:796— RVTCurveUtils.RVTCurveByPoints has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
RVTCurveUtils.RVTCurveByPoints (cognitive 19) 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:796— RVTCurveUtils.RVTCurveByPoints has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
RVTCurveUtils.RVTCurveByPoints (cognitive 19) 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:796— RVTCurveUtils.RVTCurveByPoints has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
RVTCurveUtils.RVTCurveByPoints (cognitive 19) 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:796— RVTCurveUtils.RVTCurveByPoints has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.GetMassParameters (cognitive 19) 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb:283— clsSettings.GetMassParameters has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.GetMassParameters (cognitive 19) 2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb:283— clsSettings.GetMassParameters has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.GetMassParameters (cognitive 19) 2017/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb:283— clsSettings.GetMassParameters has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.GetMassParameters (cognitive 19) 2018/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb:283— clsSettings.GetMassParameters has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.GetViewports (cognitive 19) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSettings.vb:450— clsSettings.GetViewports has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.GetViewports (cognitive 19) 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSettings.vb:450— clsSettings.GetViewports has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.GetViewports (cognitive 19) 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSettings.vb:450— clsSettings.GetViewports has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.GetViewports (cognitive 19) 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSettings.vb:450— clsSettings.GetViewports has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsCategory.GetParameters (cognitive 19) 2015/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Data/clsCategory.vb:51— clsCategory.GetParameters has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsCategory.GetParameters (cognitive 19) 2016/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Data/clsCategory.vb:51— clsCategory.GetParameters has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsCategory.GetParameters (cognitive 19) 2017/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Data/clsCategory.vb:51— clsCategory.GetParameters has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsCategory.GetParameters (cognitive 19) 2018/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Data/clsCategory.vb:51— clsCategory.GetParameters has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Export.ButtonRemove_Click (cognitive 18) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb:507— form_Export.ButtonRemove_Click has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Export.ButtonRemove_Click (cognitive 18) 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb:507— form_Export.ButtonRemove_Click has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Export.ButtonRemove_Click (cognitive 18) 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb:507— form_Export.ButtonRemove_Click has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Export.ButtonRemove_Click (cognitive 18) 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Export.vb:507— form_Export.ButtonRemove_Click has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsModCharts.QueryCategories (cognitive 18) 2015/Case.Subs.Worksets/Case.Subs.Worksets/Charts/clsModCharts.vb:53— clsModCharts.QueryCategories has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsModCharts.QueryCategories (cognitive 18) 2016/Case.Subs.Worksets/Case.Subs.Worksets/Charts/clsModCharts.vb:53— clsModCharts.QueryCategories has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsModCharts.QueryCategories (cognitive 18) 2017/Case.Subs.Worksets/Case.Subs.Worksets/Charts/clsModCharts.vb:53— clsModCharts.QueryCategories has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsModCharts.QueryCategories (cognitive 18) 2018/Case.Subs.Worksets/Case.Subs.Worksets/Charts/clsModCharts.vb:53— clsModCharts.QueryCategories has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Data.MultiSelectTreeview1_AfterExpand (cognitive 18) 2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:725— form_Data.MultiSelectTreeview1_AfterExpand has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Data.MultiSelectTreeview1_AfterExpand (cognitive 18) 2016/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:725— form_Data.MultiSelectTreeview1_AfterExpand has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Data.MultiSelectTreeview1_AfterExpand (cognitive 18) 2017/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:725— form_Data.MultiSelectTreeview1_AfterExpand has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Data.MultiSelectTreeview1_AfterExpand (cognitive 18) 2018/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:725— form_Data.MultiSelectTreeview1_AfterExpand has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.GetAllFamilyInstanceHosts (cognitive 18) 2015/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb:176— form_Main.GetAllFamilyInstanceHosts has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.GetAllFamilyInstanceHosts (cognitive 18) 2016/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb:176— form_Main.GetAllFamilyInstanceHosts has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.GetAllFamilyInstanceHosts (cognitive 18) 2017/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb:177— form_Main.GetAllFamilyInstanceHosts has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.GetAllFamilyInstanceHosts (cognitive 18) 2018/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb:177— form_Main.GetAllFamilyInstanceHosts has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.GetRevisionItemData (cognitive 18) 2015/Case.RevClouds/Case.RevClouds/Data/clsSettings.vb:78— clsSettings.GetRevisionItemData has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.GetRevisionItemData (cognitive 18) 2016/Case.RevClouds/Case.RevClouds/Data/clsSettings.vb:78— clsSettings.GetRevisionItemData has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.GetRevisionItemData (cognitive 18) 2017/Case.RevClouds/Case.RevClouds/Data/clsSettings.vb:78— clsSettings.GetRevisionItemData has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.GetRevisionItemData (cognitive 18) 2018/Case.RevClouds/Case.RevClouds/Data/clsSettings.vb:78— clsSettings.GetRevisionItemData has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.LoadViews (cognitive 18) 2015/Case.ViewTemplates/Case.ViewTemplates/UI/form_Main.vb:61— form_Main.LoadViews has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.LoadViews (cognitive 18) 2016/Case.ViewTemplates/Case.ViewTemplates/UI/form_Main.vb:61— form_Main.LoadViews has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.LoadViews (cognitive 18) 2017/Case.ViewTemplates/Case.ViewTemplates/UI/form_Main.vb:61— form_Main.LoadViews has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.LoadViews (cognitive 18) 2018/Case.ViewTemplates/Case.ViewTemplates/UI/form_Main.vb:61— form_Main.LoadViews has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsRvtSchedule.Setup (cognitive 17) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtSchedule.vb:90— clsRvtSchedule.Setup has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsRvtSchedule.Setup (cognitive 17) 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtSchedule.vb:90— clsRvtSchedule.Setup has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsRvtSchedule.Setup (cognitive 17) 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtSchedule.vb:90— clsRvtSchedule.Setup has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsRvtSchedule.Setup (cognitive 17) 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtSchedule.vb:90— clsRvtSchedule.Setup has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsConfig.AddIniParameter (cognitive 17) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:318— clsConfig.AddIniParameter has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsConfig.AddIniParameter (cognitive 17) 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:318— clsConfig.AddIniParameter has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsConfig.AddIniParameter (cognitive 17) 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:318— clsConfig.AddIniParameter has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsConfig.AddIniParameter (cognitive 17) 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:318— clsConfig.AddIniParameter has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Config.form_Config_Shown (cognitive 17) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:261— form_Config.form_Config_Shown has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Config.form_Config_Shown (cognitive 17) 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:261— form_Config.form_Config_Shown has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Config.form_Config_Shown (cognitive 17) 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:261— form_Config.form_Config_Shown has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Config.form_Config_Shown (cognitive 17) 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:261— form_Config.form_Config_Shown has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_ExportPoints.ButtonExport_Click (cognitive 17) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:387— form_ExportPoints.ButtonExport_Click has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_ExportPoints.ButtonExport_Click (cognitive 17) 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:387— form_ExportPoints.ButtonExport_Click has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_ExportPoints.ButtonExport_Click (cognitive 17) 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:387— form_ExportPoints.ButtonExport_Click has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_ExportPoints.ButtonExport_Click (cognitive 17) 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:386— form_ExportPoints.ButtonExport_Click has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.ImportImages (cognitive 17) 2015/Case.ImageToDraftingView/Case.ImageToDraftingView/Forms/form_Main.vb:64— form_Main.ImportImages has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.ImportImages (cognitive 17) 2016/Case.ImageToDraftingView/Case.ImageToDraftingView/Forms/form_Main.vb:64— form_Main.ImportImages has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.ImportImages (cognitive 17) 2017/Case.ImageToDraftingView/Case.ImageToDraftingView/Forms/form_Main.vb:64— form_Main.ImportImages has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.ImportImages (cognitive 17) 2018/Case.ImageToDraftingView/Case.ImageToDraftingView/Forms/form_Main.vb:64— form_Main.ImportImages has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.ImportJPG (cognitive 17) 2015/Case.ImageToDraftingView/Case.ImageToDraftingView/Forms/form_Main.vb:146— form_Main.ImportJPG has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.ImportJPG (cognitive 17) 2016/Case.ImageToDraftingView/Case.ImageToDraftingView/Forms/form_Main.vb:146— form_Main.ImportJPG has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.ImportJPG (cognitive 17) 2017/Case.ImageToDraftingView/Case.ImageToDraftingView/Forms/form_Main.vb:146— form_Main.ImportJPG has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.ImportJPG (cognitive 17) 2018/Case.ImageToDraftingView/Case.ImageToDraftingView/Forms/form_Main.vb:146— form_Main.ImportJPG has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.GetIntersectionHeight (cognitive 17) 2015/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb:182— clsSettings.GetIntersectionHeight has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.GetIntersectionHeight (cognitive 17) 2016/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb:182— clsSettings.GetIntersectionHeight has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.GetIntersectionHeight (cognitive 17) 2017/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb:182— clsSettings.GetIntersectionHeight has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.GetIntersectionHeight (cognitive 17) 2018/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb:182— clsSettings.GetIntersectionHeight has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.Get3dView (cognitive 17) 2015/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb:283— clsSettings.Get3dView has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.Get3dView (cognitive 17) 2016/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb:283— clsSettings.Get3dView has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.Get3dView (cognitive 17) 2017/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb:283— clsSettings.Get3dView has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.Get3dView (cognitive 17) 2018/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb:283— clsSettings.Get3dView has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.GetReferencePlanes (cognitive 17) 2015/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb:462— clsSettings.GetReferencePlanes has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.GetReferencePlanes (cognitive 17) 2016/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb:462— clsSettings.GetReferencePlanes has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.GetReferencePlanes (cognitive 17) 2017/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb:462— clsSettings.GetReferencePlanes has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.GetReferencePlanes (cognitive 17) 2018/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb:462— clsSettings.GetReferencePlanes has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
UnitConversion.CalculateDoubleLength (cognitive 17) 2015/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb:28— UnitConversion.CalculateDoubleLength has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
UnitConversion.CalculateDoubleLength (cognitive 17) 2016/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb:28— UnitConversion.CalculateDoubleLength has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
UnitConversion.CalculateDoubleLength (cognitive 17) 2017/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb:28— UnitConversion.CalculateDoubleLength has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
UnitConversion.CalculateDoubleLength (cognitive 17) 2018/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb:28— UnitConversion.CalculateDoubleLength has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.PlaceTags (cognitive 17) 2015/Case.ModeledRoomTags/Case.ModeledRoomTags/UI/form_Main.vb:97— form_Main.PlaceTags has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.PlaceTags (cognitive 17) 2016/Case.ModeledRoomTags/Case.ModeledRoomTags/UI/form_Main.vb:97— form_Main.PlaceTags has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.PlaceTags (cognitive 17) 2017/Case.ModeledRoomTags/Case.ModeledRoomTags/UI/form_Main.vb:97— form_Main.PlaceTags has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.PlaceTags (cognitive 17) 2018/Case.ModeledRoomTags/Case.ModeledRoomTags/UI/form_Main.vb:97— form_Main.PlaceTags has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.DeleteUnusedTypes (cognitive 16) 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:192— form_Main.DeleteUnusedTypes has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.DeleteUnusedTypes (cognitive 16) 2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:192— form_Main.DeleteUnusedTypes has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.DeleteUnusedTypes (cognitive 16) 2017/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:192— form_Main.DeleteUnusedTypes has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.DeleteUnusedTypes (cognitive 16) 2018/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:192— form_Main.DeleteUnusedTypes has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.GetRoomParameters (cognitive 16) 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb:324— clsSettings.GetRoomParameters has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.GetRoomParameters (cognitive 16) 2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb:324— clsSettings.GetRoomParameters has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.GetRoomParameters (cognitive 16) 2017/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb:324— clsSettings.GetRoomParameters has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
clsSettings.GetRoomParameters (cognitive 16) 2018/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSettings.vb:324— clsSettings.GetRoomParameters has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Form_Main.UpdateViews (cognitive 16) 2015/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:265— Form_Main.UpdateViews has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Form_Main.UpdateViews (cognitive 16) 2016/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:265— Form_Main.UpdateViews has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Form_Main.UpdateViews (cognitive 16) 2017/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:265— Form_Main.UpdateViews has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Form_Main.UpdateViews (cognitive 16) 2018/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:265— Form_Main.UpdateViews has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Config.SetFormControlsFromConfig (cognitive 16) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:61— form_Config.SetFormControlsFromConfig has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Config.SetFormControlsFromConfig (cognitive 16) 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:61— form_Config.SetFormControlsFromConfig has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Config.SetFormControlsFromConfig (cognitive 16) 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:61— form_Config.SetFormControlsFromConfig has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Config.SetFormControlsFromConfig (cognitive 16) 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:61— form_Config.SetFormControlsFromConfig has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Find.ChangeViewReferenceFind_Click (cognitive 16) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:253— form_Find.ChangeViewReferenceFind_Click has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 2 other methods here (form_Find.ChooseViewReferenceNull_Click, form_Find.ToolStripOrphModify_Click) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
form_Find.ChangeViewReferenceFind_Click (cognitive 16) 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:253— form_Find.ChangeViewReferenceFind_Click has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 2 other methods here (form_Find.ChooseViewReferenceNull_Click, form_Find.ToolStripOrphModify_Click) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
form_Find.ChangeViewReferenceFind_Click (cognitive 16) 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:253— form_Find.ChangeViewReferenceFind_Click has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 2 other methods here (form_Find.ChooseViewReferenceNull_Click, form_Find.ToolStripOrphModify_Click) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
form_Find.ChangeViewReferenceFind_Click (cognitive 16) 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:253— form_Find.ChangeViewReferenceFind_Click has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 2 other methods here (form_Find.ChooseViewReferenceNull_Click, form_Find.ToolStripOrphModify_Click) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
form_Find.ChooseViewReferenceNull_Click (cognitive 16) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:322— form_Find.ChooseViewReferenceNull_Click has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 2 other methods here (form_Find.ChangeViewReferenceFind_Click, form_Find.ToolStripOrphModify_Click) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
form_Find.ChooseViewReferenceNull_Click (cognitive 16) 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:322— form_Find.ChooseViewReferenceNull_Click has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 2 other methods here (form_Find.ChangeViewReferenceFind_Click, form_Find.ToolStripOrphModify_Click) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
form_Find.ChooseViewReferenceNull_Click (cognitive 16) 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:322— form_Find.ChooseViewReferenceNull_Click has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 2 other methods here (form_Find.ChangeViewReferenceFind_Click, form_Find.ToolStripOrphModify_Click) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
form_Find.ChooseViewReferenceNull_Click (cognitive 16) 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:322— form_Find.ChooseViewReferenceNull_Click has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 2 other methods here (form_Find.ChangeViewReferenceFind_Click, form_Find.ToolStripOrphModify_Click) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
form_Find.ToolStripOrphModify_Click (cognitive 16) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:406— form_Find.ToolStripOrphModify_Click has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 2 other methods here (form_Find.ChangeViewReferenceFind_Click, form_Find.ChooseViewReferenceNull_Click) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
form_Find.ToolStripOrphModify_Click (cognitive 16) 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:406— form_Find.ToolStripOrphModify_Click has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 2 other methods here (form_Find.ChangeViewReferenceFind_Click, form_Find.ChooseViewReferenceNull_Click) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
form_Find.ToolStripOrphModify_Click (cognitive 16) 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:406— form_Find.ToolStripOrphModify_Click has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 2 other methods here (form_Find.ChangeViewReferenceFind_Click, form_Find.ChooseViewReferenceNull_Click) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
form_Find.ToolStripOrphModify_Click (cognitive 16) 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:406— form_Find.ToolStripOrphModify_Click has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 2 other methods here (form_Find.ChangeViewReferenceFind_Click, form_Find.ChooseViewReferenceNull_Click) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
form_Main.GetAllFamilyFormulas (cognitive 16) 2015/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb:119— form_Main.GetAllFamilyFormulas has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.GetAllFamilyFormulas (cognitive 16) 2016/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb:119— form_Main.GetAllFamilyFormulas has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.GetAllFamilyFormulas (cognitive 16) 2017/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb:120— form_Main.GetAllFamilyFormulas has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.GetAllFamilyFormulas (cognitive 16) 2018/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb:120— form_Main.GetAllFamilyFormulas has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Navis2JiraWin.worker_DoWork (cognitive 16) REDACTED:222— Navis2JiraWin.worker_DoWork has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Navis2JiraWin.worker_DoWork (cognitive 16) REDACTED:222— Navis2JiraWin.worker_DoWork has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Navis2JiraWin.worker_DoWork (cognitive 16) REDACTED:222— Navis2JiraWin.worker_DoWork has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Navis2JiraWin.worker_DoWork (cognitive 16) REDACTED:222— Navis2JiraWin.worker_DoWork has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D4 · Code Duplication· Members sharing a duplicated core (7 members, 50+ identical tokens) · ×4
Members sharing a duplicated core (7 members, 50+ identical tokens) 2015/Case.BasicReporting/Case.BasicReporting/Entry/CmdMain.vb:24— 2015/Case.BasicReporting/Case.BasicReporting/Entry/CmdMain.vb:24-56 | 2015/Case.ChangeReplaceFamTypeNames/Case.ChangeReplaceFamTypeNames/Entry/CmdMain.vb:25-57 | 2015/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Entry/CmdMain.vb:24-56 | 2015/Case.Directionality/Case.Directionality/Entry/CmdMain.vb:24-56 | 2015/Case.ImageToDraftingView/Case.ImageToDraftingView/Entry/CmdMain.vb:23-55 | 2015/Case.LineChanger/Case.LineChanger/Entry/CmdMain.vb:17-49 | 2015/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Entry/CmdMain.vb:25-57 — 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) 2016/Case.BasicReporting/Case.BasicReporting/Entry/CmdMain.vb:24— 2016/Case.BasicReporting/Case.BasicReporting/Entry/CmdMain.vb:24-56 | 2016/Case.ChangeReplaceFamTypeNames/Case.ChangeReplaceFamTypeNames/Entry/CmdMain.vb:25-57 | 2016/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Entry/CmdMain.vb:24-56 | 2016/Case.Directionality/Case.Directionality/Entry/CmdMain.vb:24-56 | 2016/Case.ImageToDraftingView/Case.ImageToDraftingView/Entry/CmdMain.vb:23-55 | 2016/Case.LineChanger/Case.LineChanger/Entry/CmdMain.vb:17-49 | 2016/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Entry/CmdMain.vb:25-57 — 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) 2017/Case.BasicReporting/Case.BasicReporting/Entry/CmdMain.vb:24— 2017/Case.BasicReporting/Case.BasicReporting/Entry/CmdMain.vb:24-56 | 2017/Case.ChangeReplaceFamTypeNames/Case.ChangeReplaceFamTypeNames/Entry/CmdMain.vb:25-57 | 2017/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Entry/CmdMain.vb:24-56 | 2017/Case.Directionality/Case.Directionality/Entry/CmdMain.vb:24-56 | 2017/Case.ImageToDraftingView/Case.ImageToDraftingView/Entry/CmdMain.vb:23-55 | 2017/Case.LineChanger/Case.LineChanger/Entry/CmdMain.vb:17-49 | 2017/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Entry/CmdMain.vb:25-57 — 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) 2018/Case.BasicReporting/Case.BasicReporting/Entry/CmdMain.vb:24— 2018/Case.BasicReporting/Case.BasicReporting/Entry/CmdMain.vb:24-56 | 2018/Case.ChangeReplaceFamTypeNames/Case.ChangeReplaceFamTypeNames/Entry/CmdMain.vb:25-57 | 2018/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Entry/CmdMain.vb:24-56 | 2018/Case.Directionality/Case.Directionality/Entry/CmdMain.vb:24-56 | 2018/Case.ImageToDraftingView/Case.ImageToDraftingView/Entry/CmdMain.vb:23-55 | 2018/Case.LineChanger/Case.LineChanger/Entry/CmdMain.vb:17-49 | 2018/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Entry/CmdMain.vb:25-57 — 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.
Duplicated block (85 lines × 4) REDACTED:240— REDACTED:240-324 | REDACTED:240-324 | REDACTED:240-324 | REDACTED:236-320 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 264 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:240` 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 (85 lines × 4) REDACTED:78— REDACTED:78-162 | REDACTED:78-162 | REDACTED:78-162 | REDACTED:78-162 — before extracting anything, compare `REDACTED` and `REDACTED` 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 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 (85 lines × 4) 2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/clsViews.vb:25— 2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/clsViews.vb:25-109 | 2016/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/clsViews.vb:25-109 | 2017/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/clsViews.vb:25-109 | 2018/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/clsViews.vb:25-109 — before extracting anything, compare `2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/clsViews.vb` and `2016/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/clsViews.vb` 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.
Duplicated block (85 lines × 4) 2015/Case.ViewTemplates/Case.ViewTemplates/Data/clsViews.vb:25— 2015/Case.ViewTemplates/Case.ViewTemplates/Data/clsViews.vb:25-109 | 2016/Case.ViewTemplates/Case.ViewTemplates/Data/clsViews.vb:25-109 | 2017/Case.ViewTemplates/Case.ViewTemplates/Data/clsViews.vb:25-109 | 2018/Case.ViewTemplates/Case.ViewTemplates/Data/clsViews.vb:25-109 — before extracting anything, compare `2015/Case.ViewTemplates/Case.ViewTemplates/Data/clsViews.vb` and `2016/Case.ViewTemplates/Case.ViewTemplates/Data/clsViews.vb` 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.
Duplicated block (66 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:509— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:509-574 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:509-574 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:509-574 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:509-574 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 467 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 (66 lines × 4) 2015/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Forms/form_Main.vb:31— 2015/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Forms/form_Main.vb:31-96 | 2016/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Forms/form_Main.vb:31-96 | 2017/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Forms/form_Main.vb:31-96 | 2018/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Forms/form_Main.vb:31-96 — before extracting anything, compare `2015/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Forms/form_Main.vb` and `2016/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Forms/form_Main.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 137 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 (66 lines × 4) 2015/Case.Export.Families/Case.Export.Families/Data/clsSettings.vb:22— 2015/Case.Export.Families/Case.Export.Families/Data/clsSettings.vb:22-87 | 2016/Case.Export.Families/Case.Export.Families/Data/clsSettings.vb:22-87 | 2017/Case.Export.Families/Case.Export.Families/Data/clsSettings.vb:22-87 | 2018/Case.Export.Families/Case.Export.Families/Data/clsSettings.vb:22-87 — before extracting anything, compare `2015/Case.Export.Families/Case.Export.Families/Data/clsSettings.vb` and `2016/Case.Export.Families/Case.Export.Families/Data/clsSettings.vb` 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.
Duplicated block (66 lines × 4) 2015/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsView.vb:27— 2015/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsView.vb:27-92 | 2016/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsView.vb:27-92 | 2017/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsView.vb:27-92 | 2018/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsView.vb:27-92 — before extracting anything, compare `2015/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsView.vb` and `2016/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsView.vb` 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.
Duplicated block (60 lines × 4) 2015/Case.ApplySysOrient/Data/clsSettings.cs:311— 2015/Case.ApplySysOrient/Data/clsSettings.cs:311-370 | 2016/Case.ApplySysOrient/Data/clsSettings.cs:311-370 | 2017/Case.ApplySysOrient/Data/clsSettings.cs:311-370 | 2018/Case.ApplySysOrient/Data/clsSettings.cs:311-370 — before extracting anything, compare `2015/Case.ApplySysOrient/Data/clsSettings.cs` and `2016/Case.ApplySysOrient/Data/clsSettings.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 288 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 (60 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:41— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:41-100 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:41-100 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:41-100 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:41-100 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 281 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 (60 lines × 4) 2015/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:329— 2015/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:329-388 | 2016/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:329-388 | 2017/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:329-388 | 2018/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:329-388 — before extracting anything, compare `2015/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb` and `2016/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 264 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 (60 lines × 4) 2015/Case.ViewTemplates/Case.ViewTemplates/Data/clsSettings.vb:25— 2015/Case.ViewTemplates/Case.ViewTemplates/Data/clsSettings.vb:25-84 | 2016/Case.ViewTemplates/Case.ViewTemplates/Data/clsSettings.vb:25-84 | 2017/Case.ViewTemplates/Case.ViewTemplates/Data/clsSettings.vb:25-84 | 2018/Case.ViewTemplates/Case.ViewTemplates/Data/clsSettings.vb:25-84 — before extracting anything, compare `2015/Case.ViewTemplates/Case.ViewTemplates/Data/clsSettings.vb` and `2016/Case.ViewTemplates/Case.ViewTemplates/Data/clsSettings.vb` 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.
Duplicated block (59 lines × 4) 2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:428— 2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:428-486 | 2016/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:428-486 | 2017/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:428-486 | 2018/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:428-486 — before extracting anything, compare `2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb` and `2016/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb` as WHOLE FILES: this scan already matched 5 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. 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 (59 lines × 4) 2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:497— 2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:497-555 | 2016/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:497-555 | 2017/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:497-555 | 2018/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb:497-555 — before extracting anything, compare `2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb` and `2016/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Data.vb` as WHOLE FILES: this scan already matched 5 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. 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 (59 lines × 4) 2015/Case.ModeledRoomTags/Case.ModeledRoomTags/Entry/CmdMain.vb:38— 2015/Case.ModeledRoomTags/Case.ModeledRoomTags/Entry/CmdMain.vb:38-96 | 2016/Case.ModeledRoomTags/Case.ModeledRoomTags/Entry/CmdMain.vb:38-96 | 2017/Case.ModeledRoomTags/Case.ModeledRoomTags/Entry/CmdMain.vb:38-96 | 2018/Case.ModeledRoomTags/Case.ModeledRoomTags/Entry/CmdMain.vb:38-96 — before extracting anything, compare `2015/Case.ModeledRoomTags/Case.ModeledRoomTags/Entry/CmdMain.vb` and `2016/Case.ModeledRoomTags/Case.ModeledRoomTags/Entry/CmdMain.vb` as WHOLE FILES: 97% 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. Read the line range as the matched WINDOW rather than a finished unit: at `2015/Case.ModeledRoomTags/Case.ModeledRoomTags/Entry/CmdMain.vb:38` 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 (59 lines × 4) 2015/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:245— 2015/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:245-303 | 2016/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:245-303 | 2017/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:245-303 | 2018/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:245-303 — before extracting anything, compare `2015/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb` and `2016/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 245 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 (57 lines × 4) 2015/Case.ApplySysOrient/Data/clsSettings.cs:123— 2015/Case.ApplySysOrient/Data/clsSettings.cs:123-179 | 2016/Case.ApplySysOrient/Data/clsSettings.cs:123-179 | 2017/Case.ApplySysOrient/Data/clsSettings.cs:123-179 | 2018/Case.ApplySysOrient/Data/clsSettings.cs:123-179 — before extracting anything, compare `2015/Case.ApplySysOrient/Data/clsSettings.cs` and `2016/Case.ApplySysOrient/Data/clsSettings.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 288 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 (57 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSharedParameters.vb:124— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSharedParameters.vb:124-180 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSharedParameters.vb:124-180 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSharedParameters.vb:124-180 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSharedParameters.vb:124-180 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSharedParameters.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSharedParameters.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 110 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 (57 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:440— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:440-496 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:440-496 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:440-496 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:440-496 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 467 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 (57 lines × 4) 2015/Case.BasicReporting/Case.BasicReporting/Data/clsSettings.vb:22— 2015/Case.BasicReporting/Case.BasicReporting/Data/clsSettings.vb:22-78 | 2016/Case.BasicReporting/Case.BasicReporting/Data/clsSettings.vb:22-78 | 2017/Case.BasicReporting/Case.BasicReporting/Data/clsSettings.vb:22-78 | 2018/Case.BasicReporting/Case.BasicReporting/Data/clsSettings.vb:22-78 — before extracting anything, compare `2015/Case.BasicReporting/Case.BasicReporting/Data/clsSettings.vb` and `2016/Case.BasicReporting/Case.BasicReporting/Data/clsSettings.vb` 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.
Duplicated block (55 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:327— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:327-381 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:327-381 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:327-381 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:327-381 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 422 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 (55 lines × 4) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:249— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:249-303 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:249-303 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:249-303 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:249-303 — before extracting anything, compare `2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb` and `2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 257 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 (55 lines × 4) 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:569— 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:569-623 | 2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:569-623 | 2017/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:569-623 | 2018/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:569-623 — before extracting anything, compare `2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb` and `2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 500 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 (55 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ItemSelection.xaml.vb:13— 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ItemSelection.xaml.vb:13-67 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ItemSelection.xaml.vb:13-67 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ItemSelection.xaml.vb:13-67 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ItemSelection.xaml.vb:13-67 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ItemSelection.xaml.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ItemSelection.xaml.vb` 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.
Duplicated block (50 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:265— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:265-314 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:265-314 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:265-314 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:265-314 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 610 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 (50 lines × 4) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:190— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:190-239 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:190-239 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:190-239 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:190-239 — before extracting anything, compare `2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb` and `2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 685 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 (50 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:258— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:258-307 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:258-307 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:258-307 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb:258-307 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsConfig.vb` as WHOLE FILES: this scan already matched 10 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. 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 (50 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:524— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:524-573 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:524-573 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:524-573 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:524-573 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 281 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 (45 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb:412— 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb:412-456 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb:412-456 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb:412-456 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb:412-456 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 149 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 (45 lines × 4) 2015/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb:89— 2015/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb:89-133 | 2016/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb:89-133 | 2017/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb:89-133 | 2018/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb:89-133 — before extracting anything, compare `2015/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb` and `2016/Case.LightingLayout/Case.LightingLayout/Data/UnitConversion.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 150 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 (45 lines × 4) 2015/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsSettings.vb:124— 2015/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsSettings.vb:124-168 | 2016/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsSettings.vb:124-168 | 2017/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsSettings.vb:124-168 | 2018/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsSettings.vb:124-168 — before extracting anything, compare `2015/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsSettings.vb` and `2016/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 114 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 (45 lines × 4) 2015/Case.RevClouds/Case.RevClouds/Data/clsRevcloud.vb:118— 2015/Case.RevClouds/Case.RevClouds/Data/clsRevcloud.vb:118-162 | 2016/Case.RevClouds/Case.RevClouds/Data/clsRevcloud.vb:118-162 | 2017/Case.RevClouds/Case.RevClouds/Data/clsRevcloud.vb:118-162 | 2018/Case.RevClouds/Case.RevClouds/Data/clsRevcloud.vb:118-162 — before extracting anything, compare `2015/Case.RevClouds/Case.RevClouds/Data/clsRevcloud.vb` and `2016/Case.RevClouds/Case.RevClouds/Data/clsRevcloud.vb` 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.
Duplicated block (44 lines × 4) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:54— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:54-97 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:54-97 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:54-97 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:54-97 — before extracting anything, compare `2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb` and `2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 257 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 (44 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:380— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:380-423 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:380-423 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:380-423 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:380-423 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 467 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 (44 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:628— 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:628-671 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:628-671 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:628-671 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:628-671 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 604 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 (44 lines × 4) 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSheets.vb:15— 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSheets.vb:15-58 | 2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSheets.vb:15-58 | 2017/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSheets.vb:15-58 | 2018/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSheets.vb:15-58 — before extracting anything, compare `2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSheets.vb` and `2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSheets.vb` 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.
Duplicated block (24–27 lines × 3) 2015/Case.Directionality/Case.Directionality/Entry/CmdMain.vb:27— 2015/Case.Directionality/Case.Directionality/Entry/CmdMain.vb:27-50 | 2015/Case.ImageToDraftingView/Case.ImageToDraftingView/Entry/CmdMain.vb:26-49 | 2015/Case.LineChanger/Case.LineChanger/Entry/CmdMain.vb:20-46 — before extracting anything, compare `2015/Case.Directionality/Case.Directionality/Entry/CmdMain.vb` and `2015/Case.ImageToDraftingView/Case.ImageToDraftingView/Entry/CmdMain.vb` as WHOLE FILES: 97% 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. 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 (24–27 lines × 3) 2016/Case.Directionality/Case.Directionality/Entry/CmdMain.vb:27— 2016/Case.Directionality/Case.Directionality/Entry/CmdMain.vb:27-50 | 2016/Case.ImageToDraftingView/Case.ImageToDraftingView/Entry/CmdMain.vb:26-49 | 2016/Case.LineChanger/Case.LineChanger/Entry/CmdMain.vb:20-46 — before extracting anything, compare `2016/Case.Directionality/Case.Directionality/Entry/CmdMain.vb` and `2016/Case.ImageToDraftingView/Case.ImageToDraftingView/Entry/CmdMain.vb` as WHOLE FILES: 97% 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. 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 (24–27 lines × 3) 2017/Case.Directionality/Case.Directionality/Entry/CmdMain.vb:27— 2017/Case.Directionality/Case.Directionality/Entry/CmdMain.vb:27-50 | 2017/Case.ImageToDraftingView/Case.ImageToDraftingView/Entry/CmdMain.vb:26-49 | 2017/Case.LineChanger/Case.LineChanger/Entry/CmdMain.vb:20-46 — before extracting anything, compare `2017/Case.Directionality/Case.Directionality/Entry/CmdMain.vb` and `2017/Case.ImageToDraftingView/Case.ImageToDraftingView/Entry/CmdMain.vb` as WHOLE FILES: 97% 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. 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 (24–27 lines × 3) 2018/Case.Directionality/Case.Directionality/Entry/CmdMain.vb:27— 2018/Case.Directionality/Case.Directionality/Entry/CmdMain.vb:27-50 | 2018/Case.ImageToDraftingView/Case.ImageToDraftingView/Entry/CmdMain.vb:26-49 | 2018/Case.LineChanger/Case.LineChanger/Entry/CmdMain.vb:20-46 — before extracting anything, compare `2018/Case.Directionality/Case.Directionality/Entry/CmdMain.vb` and `2018/Case.ImageToDraftingView/Case.ImageToDraftingView/Entry/CmdMain.vb` as WHOLE FILES: 97% 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. 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 (19 lines × 3) 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2512.vb:32— 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2512.vb:32-50 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2513.vb:29-47 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2514.vb:29-47 — before extracting anything, compare `2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2512.vb` and `2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2513.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the 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 (19 lines × 3) 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Entry/AF73BA45B4B94C7585CB3E425D423F5E.vb:39— 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Entry/AF73BA45B4B94C7585CB3E425D423F5E.vb:39-58 | 2015/Case.Subs.SuperTag/Case.Subs.SuperTag/Entry/A01A0A226EBE4CD89D655C55B997650F.vb:28-46 | 2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Entry/CEB749CFCF844AE8B76F40E3EBAA2FF7.vb:25-43 — 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 (19 lines × 3) 2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Entry/AF73BA45B4B94C7585CB3E425D423F5E.vb:39— 2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Entry/AF73BA45B4B94C7585CB3E425D423F5E.vb:39-58 | 2016/Case.Subs.SuperTag/Case.Subs.SuperTag/Entry/A01A0A226EBE4CD89D655C55B997650F.vb:28-46 | 2016/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Entry/CEB749CFCF844AE8B76F40E3EBAA2FF7.vb:25-43 — 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 (19 lines × 3) 2017/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Entry/AF73BA45B4B94C7585CB3E425D423F5E.vb:39— 2017/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Entry/AF73BA45B4B94C7585CB3E425D423F5E.vb:39-58 | 2017/Case.Subs.SuperTag/Case.Subs.SuperTag/Entry/A01A0A226EBE4CD89D655C55B997650F.vb:28-46 | 2017/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Entry/CEB749CFCF844AE8B76F40E3EBAA2FF7.vb:25-43 — 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 (19 lines × 7) 2015/Case.BasicReporting/Case.BasicReporting/Entry/CmdMain.vb:24— 2015/Case.BasicReporting/Case.BasicReporting/Entry/CmdMain.vb:24-42 | 2015/Case.ChangeReplaceFamTypeNames/Case.ChangeReplaceFamTypeNames/Entry/CmdMain.vb:25-43 | 2015/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Entry/CmdMain.vb:24-42 | 2015/Case.Directionality/Case.Directionality/Entry/CmdMain.vb:24-42 | 2015/Case.ImageToDraftingView/Case.ImageToDraftingView/Entry/CmdMain.vb:23-41 | 2015/Case.LineChanger/Case.LineChanger/Entry/CmdMain.vb:17-35 | 2015/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Entry/CmdMain.vb:25-43 — before extracting anything, compare `2015/Case.BasicReporting/Case.BasicReporting/Entry/CmdMain.vb` and `2015/Case.ChangeReplaceFamTypeNames/Case.ChangeReplaceFamTypeNames/Entry/CmdMain.vb` 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 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.
Duplicated block (19 lines × 7) 2016/Case.BasicReporting/Case.BasicReporting/Entry/CmdMain.vb:24— 2016/Case.BasicReporting/Case.BasicReporting/Entry/CmdMain.vb:24-42 | 2016/Case.ChangeReplaceFamTypeNames/Case.ChangeReplaceFamTypeNames/Entry/CmdMain.vb:25-43 | 2016/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Entry/CmdMain.vb:24-42 | 2016/Case.Directionality/Case.Directionality/Entry/CmdMain.vb:24-42 | 2016/Case.ImageToDraftingView/Case.ImageToDraftingView/Entry/CmdMain.vb:23-41 | 2016/Case.LineChanger/Case.LineChanger/Entry/CmdMain.vb:17-35 | 2016/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Entry/CmdMain.vb:25-43 — before extracting anything, compare `2016/Case.BasicReporting/Case.BasicReporting/Entry/CmdMain.vb` and `2016/Case.ChangeReplaceFamTypeNames/Case.ChangeReplaceFamTypeNames/Entry/CmdMain.vb` 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 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.
Duplicated block (19 lines × 7) 2017/Case.BasicReporting/Case.BasicReporting/Entry/CmdMain.vb:24— 2017/Case.BasicReporting/Case.BasicReporting/Entry/CmdMain.vb:24-42 | 2017/Case.ChangeReplaceFamTypeNames/Case.ChangeReplaceFamTypeNames/Entry/CmdMain.vb:25-43 | 2017/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Entry/CmdMain.vb:24-42 | 2017/Case.Directionality/Case.Directionality/Entry/CmdMain.vb:24-42 | 2017/Case.ImageToDraftingView/Case.ImageToDraftingView/Entry/CmdMain.vb:23-41 | 2017/Case.LineChanger/Case.LineChanger/Entry/CmdMain.vb:17-35 | 2017/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Entry/CmdMain.vb:25-43 — before extracting anything, compare `2017/Case.BasicReporting/Case.BasicReporting/Entry/CmdMain.vb` and `2017/Case.ChangeReplaceFamTypeNames/Case.ChangeReplaceFamTypeNames/Entry/CmdMain.vb` 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 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.
Duplicated block (19 lines × 7) 2018/Case.BasicReporting/Case.BasicReporting/Entry/CmdMain.vb:24— 2018/Case.BasicReporting/Case.BasicReporting/Entry/CmdMain.vb:24-42 | 2018/Case.ChangeReplaceFamTypeNames/Case.ChangeReplaceFamTypeNames/Entry/CmdMain.vb:25-43 | 2018/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Entry/CmdMain.vb:24-42 | 2018/Case.Directionality/Case.Directionality/Entry/CmdMain.vb:24-42 | 2018/Case.ImageToDraftingView/Case.ImageToDraftingView/Entry/CmdMain.vb:23-41 | 2018/Case.LineChanger/Case.LineChanger/Entry/CmdMain.vb:17-35 | 2018/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Entry/CmdMain.vb:25-43 — before extracting anything, compare `2018/Case.BasicReporting/Case.BasicReporting/Entry/CmdMain.vb` and `2018/Case.ChangeReplaceFamTypeNames/Case.ChangeReplaceFamTypeNames/Entry/CmdMain.vb` 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 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.
Duplicated block (19–20 lines × 6) 2015/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Entry/CmdMain.vb:25— 2015/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Entry/CmdMain.vb:25-44 | 2015/Case.LightingLayout/Case.LightingLayout/Entry/CmdMain.vb:26-45 | 2015/Case.ModeledRoomTags/Case.ModeledRoomTags/Entry/CmdMain.vb:27-46 | 2015/Case.SharedParameters/Case.SharedParameters/Entry/CmdMain.vb:25-44 | 2015/Case.Subs.Worksets/Case.Subs.Worksets/Entry/CEB749CFCF844AE8B76F40E3EBAA2FF7.vb:26-44 | 2015/Case.ViewTemplates/Case.ViewTemplates/Entry/CmdMain.vb:26-45 — before extracting anything, compare `2015/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Entry/CmdMain.vb` and `2015/Case.SharedParameters/Case.SharedParameters/Entry/CmdMain.vb` 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.
Duplicated block (19–20 lines × 6) 2016/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Entry/CmdMain.vb:25— 2016/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Entry/CmdMain.vb:25-44 | 2016/Case.LightingLayout/Case.LightingLayout/Entry/CmdMain.vb:26-45 | 2016/Case.ModeledRoomTags/Case.ModeledRoomTags/Entry/CmdMain.vb:27-46 | 2016/Case.SharedParameters/Case.SharedParameters/Entry/CmdMain.vb:25-44 | 2016/Case.Subs.Worksets/Case.Subs.Worksets/Entry/CEB749CFCF844AE8B76F40E3EBAA2FF7.vb:26-44 | 2016/Case.ViewTemplates/Case.ViewTemplates/Entry/CmdMain.vb:26-45 — before extracting anything, compare `2016/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Entry/CmdMain.vb` and `2016/Case.SharedParameters/Case.SharedParameters/Entry/CmdMain.vb` 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.
Duplicated block (19–20 lines × 6) 2017/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Entry/CmdMain.vb:25— 2017/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Entry/CmdMain.vb:25-44 | 2017/Case.LightingLayout/Case.LightingLayout/Entry/CmdMain.vb:26-45 | 2017/Case.ModeledRoomTags/Case.ModeledRoomTags/Entry/CmdMain.vb:27-46 | 2017/Case.SharedParameters/Case.SharedParameters/Entry/CmdMain.vb:25-44 | 2017/Case.Subs.Worksets/Case.Subs.Worksets/Entry/CEB749CFCF844AE8B76F40E3EBAA2FF7.vb:26-44 | 2017/Case.ViewTemplates/Case.ViewTemplates/Entry/CmdMain.vb:26-45 — before extracting anything, compare `2017/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Entry/CmdMain.vb` and `2017/Case.SharedParameters/Case.SharedParameters/Entry/CmdMain.vb` 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.
Duplicated block (19–20 lines × 6) 2018/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Entry/CmdMain.vb:25— 2018/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Entry/CmdMain.vb:25-44 | 2018/Case.LightingLayout/Case.LightingLayout/Entry/CmdMain.vb:26-45 | 2018/Case.ModeledRoomTags/Case.ModeledRoomTags/Entry/CmdMain.vb:27-46 | 2018/Case.SharedParameters/Case.SharedParameters/Entry/CmdMain.vb:25-44 | 2018/Case.Subs.Worksets/Case.Subs.Worksets/Entry/CEB749CFCF844AE8B76F40E3EBAA2FF7.vb:26-44 | 2018/Case.ViewTemplates/Case.ViewTemplates/Entry/CmdMain.vb:26-45 — before extracting anything, compare `2018/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Entry/CmdMain.vb` and `2018/Case.SharedParameters/Case.SharedParameters/Entry/CmdMain.vb` 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.
Duplicated block (19 lines × 2) 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:441— 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:441-459 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:441-459 — before extracting anything, compare `2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb` and `2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 610 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 (19 lines × 2) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:441— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:441-459 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:441-459 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 610 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 (19 lines × 2) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb:303— 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb:303-321 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb:303-321 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 149 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 (19 lines × 2) 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb:303— 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb:303-321 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb:303-321 — before extracting anything, compare `2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb` and `2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 149 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 (30 lines × 2) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Name.vb:12— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Name.vb:12-41 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Name.vb:12-41 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Name.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Name.vb` 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.
Duplicated block (30 lines × 2) 2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Progress.vb:12— 2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Progress.vb:12-41 | 2016/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Progress.vb:12-41 — before extracting anything, compare `2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Progress.vb` and `2016/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Progress.vb` 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.
Duplicated block (30 lines × 2) 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Name.vb:14— 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Name.vb:14-43 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Name.vb:14-43 — before extracting anything, compare `2017/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Name.vb` and `2018/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Name.vb` 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.
Duplicated block (30 lines × 2) 2017/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Progress.vb:12— 2017/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Progress.vb:12-41 | 2018/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Progress.vb:12-41 — before extracting anything, compare `2017/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Progress.vb` and `2018/Case.Subs.Worksets/Case.Subs.Worksets/UI/form_Progress.vb` 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.
Duplicated block (11 lines × 2) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/UI/form_ImportMain.xaml.vb:27— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/UI/form_ImportMain.xaml.vb:27-37 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/UI/form_ImportMain.xaml.vb:27-37 — before extracting anything, compare `2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/UI/form_ImportMain.xaml.vb` and `2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/UI/form_ImportMain.xaml.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 299 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 (11 lines × 2) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:19— 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:19-29 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:19-29 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 267 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 (11 lines × 2) 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/UI/form_ImportMain.xaml.vb:27— 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/UI/form_ImportMain.xaml.vb:27-37 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/UI/form_ImportMain.xaml.vb:27-37 — before extracting anything, compare `2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/UI/form_ImportMain.xaml.vb` and `2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/UI/form_ImportMain.xaml.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 299 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 (11 lines × 2) 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:19— 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:19-29 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:19-29 — before extracting anything, compare `2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb` and `2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 267 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 (13 lines × 8) 2015/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:251— 2015/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:251-263 | 2015/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:318-330 | 2016/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:251-263 | 2016/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:318-330 | 2017/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:251-263 | 2017/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:318-330 | 2018/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:246-258 | 2018/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:318-330 — before extracting anything, compare `2015/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb` and `2015/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb` 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.
Duplicated block (13 lines × 8) 2015/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:276— 2015/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:276-288 | 2015/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:343-355 | 2016/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:276-288 | 2016/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:343-355 | 2017/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:276-288 | 2017/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:343-355 | 2018/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:271-283 | 2018/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:343-355 — before extracting anything, compare `2015/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb` and `2015/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb` 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.
Duplicated block (13 lines × 8) 2015/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:301— 2015/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:301-313 | 2015/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:368-380 | 2016/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:301-313 | 2016/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:368-380 | 2017/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:301-313 | 2017/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:368-380 | 2018/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:296-308 | 2018/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:368-380 — before extracting anything, compare `2015/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb` and `2015/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb` 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.
Duplicated block (13 lines × 8) 2015/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:326— 2015/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:326-338 | 2015/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:393-405 | 2016/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:326-338 | 2016/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:393-405 | 2017/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:326-338 | 2017/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:393-405 | 2018/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:321-333 | 2018/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:393-405 — before extracting anything, compare `2015/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb` and `2015/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb` 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.
IC1 · Incompleteness & stubs· Empty method body · ×4
Empty method body — does nothing with its inputs 2015/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs:104— `LogData` 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 2016/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs:104— `LogData` 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 2017/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs:104— `LogData` 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 2018/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs:104— `LogData` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
AppMain.LoadItemsOne (cyclomatic 31) Case.AppsRibbon/Entry/AppMain.vb:592— AppMain.LoadItemsOne has cyclomatic complexity 31 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
AppMain.LoadItemsOne (cyclomatic 31) Case.AppsRibbon.2017/Entry/AppMain.vb:592— AppMain.LoadItemsOne has cyclomatic complexity 31 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
AppMain.LoadItemsOne (cyclomatic 31) Case.AppsRibbon.2018/Entry/AppMain.vb:592— AppMain.LoadItemsOne has cyclomatic complexity 31 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Main.buttonOk_Click (cyclomatic 22) REDACTED:66— form_Main.buttonOk_Click has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
form_Main.buttonOk_Click (cyclomatic 22) REDACTED:66— form_Main.buttonOk_Click has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
form_Main.buttonOk_Click (cyclomatic 22) REDACTED:61— form_Main.buttonOk_Click has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AppMain.AddAsStackedAndButtons (cyclomatic 18) Case.AppsRibbon/Entry/AppMain.vb:144— AppMain.AddAsStackedAndButtons has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
AppMain.AddAsStackedAndButtons (cyclomatic 18) Case.AppsRibbon.2017/Entry/AppMain.vb:144— AppMain.AddAsStackedAndButtons has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
AppMain.AddAsStackedAndButtons (cyclomatic 18) Case.AppsRibbon.2018/Entry/AppMain.vb:144— AppMain.AddAsStackedAndButtons has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
AppMain.LoadItemsTwo (cyclomatic 18) Case.AppsRibbon/Entry/AppMain.vb:394— AppMain.LoadItemsTwo has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
AppMain.LoadItemsTwo (cyclomatic 18) Case.AppsRibbon.2017/Entry/AppMain.vb:394— AppMain.LoadItemsTwo has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
AppMain.LoadItemsTwo (cyclomatic 18) Case.AppsRibbon.2018/Entry/AppMain.vb:394— AppMain.LoadItemsTwo has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
form_Main.buttonOk_Click (cognitive 78) REDACTED:66— form_Main.buttonOk_Click has cognitive complexity 78 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
form_Main.buttonOk_Click (cognitive 78) REDACTED:66— form_Main.buttonOk_Click has cognitive complexity 78 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
form_Main.buttonOk_Click (cognitive 78) REDACTED:61— form_Main.buttonOk_Click has cognitive complexity 78 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppMain.LoadItemsOne (cognitive 31) Case.AppsRibbon/Entry/AppMain.vb:592— AppMain.LoadItemsOne has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
AppMain.LoadItemsOne (cognitive 31) Case.AppsRibbon.2017/Entry/AppMain.vb:592— AppMain.LoadItemsOne has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
AppMain.LoadItemsOne (cognitive 31) Case.AppsRibbon.2018/Entry/AppMain.vb:592— AppMain.LoadItemsOne has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.ButtonOk_Click (cognitive 30) 2015/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/UI/form_Main.vb:107— form_Main.ButtonOk_Click has cognitive complexity 30 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.ButtonOk_Click (cognitive 30) 2016/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/UI/form_Main.vb:107— form_Main.ButtonOk_Click has cognitive complexity 30 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_Main.ButtonOk_Click (cognitive 30) 2017/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/UI/form_Main.vb:107— form_Main.ButtonOk_Click has cognitive complexity 30 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
AppMain.LoadItemsTwo (cognitive 19) Case.AppsRibbon/Entry/AppMain.vb:394— AppMain.LoadItemsTwo has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
AppMain.LoadItemsTwo (cognitive 19) Case.AppsRibbon.2017/Entry/AppMain.vb:394— AppMain.LoadItemsTwo has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
AppMain.LoadItemsTwo (cognitive 19) Case.AppsRibbon.2018/Entry/AppMain.vb:394— AppMain.LoadItemsTwo has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
CmdMain.Execute (cognitive 17) 2015/Case.RoomInsertionPoint/Case.RoomInsertionPoint/Entry/CmdMain.vb:23— CmdMain.Execute has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
CmdMain.Execute (cognitive 17) 2016/Case.RoomInsertionPoint/Case.RoomInsertionPoint/Entry/CmdMain.vb:23— CmdMain.Execute has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
CmdMain.Execute (cognitive 17) 2017/Case.RoomInsertionPoint/Case.RoomInsertionPoint/Entry/CmdMain.vb:23— CmdMain.Execute has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_RevisionClouds.ButtonExport_Click (cognitive 16) 2015/Case.RevClouds/Case.RevClouds/UI/form_RevisionClouds.vb:89— form_RevisionClouds.ButtonExport_Click has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_RevisionClouds.ButtonExport_Click (cognitive 16) 2016/Case.RevClouds/Case.RevClouds/UI/form_RevisionClouds.vb:89— form_RevisionClouds.ButtonExport_Click has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
form_RevisionClouds.ButtonExport_Click (cognitive 16) 2017/Case.RevClouds/Case.RevClouds/UI/form_RevisionClouds.vb:89— form_RevisionClouds.ButtonExport_Click has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D4 · Code Duplication· Members sharing a duplicated core (57 members, 50+ identical tokens) · ×3
Members sharing a duplicated core (57 members, 50+ identical tokens) REDACTED:15— REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 — These 57 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 57 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 57 times.
Members sharing a duplicated core (57 members, 50+ identical tokens) REDACTED:62— REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 — These 57 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 57 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 57 times.
Members sharing a duplicated core (57 members, 50+ identical tokens) REDACTED:99— REDACTED:99-129 | REDACTED:99-129 | REDACTED:99-129 | REDACTED:99-129 | REDACTED:99-129 | REDACTED:99-129 | REDACTED:99-129 | REDACTED:99-129 | REDACTED:99-129 | REDACTED:99-129 | REDACTED:99-129 | REDACTED:99-129 | REDACTED:99-129 | REDACTED:99-129 | REDACTED:99-129 | REDACTED:99-129 | REDACTED:99-129 | REDACTED:99-135 | REDACTED:99-129 | REDACTED:99-129 | REDACTED:99-129 | REDACTED:99-129 | REDACTED:99-129 | REDACTED:99-129 | REDACTED:99-129 | REDACTED:99-129 | REDACTED:99-129 | REDACTED:99-129 | REDACTED:99-129 | REDACTED:99-129 | REDACTED:99-129 | REDACTED:99-129 | REDACTED:99-129 | REDACTED:99-129 | REDACTED:99-129 | REDACTED:99-129 | REDACTED:99-135 | REDACTED:99-129 | REDACTED:99-129 | REDACTED:99-129 | REDACTED:99-129 | REDACTED:99-129 | REDACTED:99-129 | REDACTED:99-129 | REDACTED:99-129 | REDACTED:99-129 | REDACTED:99-129 | REDACTED:99-129 | REDACTED:99-129 | REDACTED:99-129 | REDACTED:99-129 | REDACTED:99-129 | REDACTED:99-129 | REDACTED:99-129 | REDACTED:99-129 | REDACTED:99-135 | REDACTED:99-129 — These 57 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 57 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 57 times.
D4 · Code Duplication· Members sharing a duplicated core (12 members, 50+ identical tokens) · ×3
Members sharing a duplicated core (12 members, 50+ identical tokens) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:254— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:254-286 | 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:323-355 | 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:407-439 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:254-286 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:323-355 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:407-439 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:254-286 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:323-355 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:407-439 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:254-286 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:323-355 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:407-439 — These 12 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 12 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 12 times.
Members sharing a duplicated core (12 members, 50+ identical tokens) 2015/Case.Directionality/Case.Directionality/Data/clsPara.vb:161— 2015/Case.Directionality/Case.Directionality/Data/clsPara.vb:161-177 | 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsPara.vb:120-136 | 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsPara.vb:147-163 | 2016/Case.Directionality/Case.Directionality/Data/clsPara.vb:161-177 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsPara.vb:120-136 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsPara.vb:147-163 | 2017/Case.Directionality/Case.Directionality/Data/clsPara.vb:161-177 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsPara.vb:120-136 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsPara.vb:147-163 | 2018/Case.Directionality/Case.Directionality/Data/clsPara.vb:161-177 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsPara.vb:120-136 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsPara.vb:147-163 — These 12 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 12 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 12 times.
Members sharing a duplicated core (12 members, 50+ identical tokens) 2015/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnFamData.cs:94— 2015/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnFamData.cs:94-109 | 2015/Case.ObjectStyles/Case.ObjectStyles/Data/mnData.cs:51-64 | 2015/Case.ObjectStyles/Case.ObjectStyles/Data/mnFamData.cs:99-112 | 2016/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnFamData.cs:94-109 | 2016/Case.ObjectStyles/Case.ObjectStyles/Data/mnData.cs:51-64 | 2016/Case.ObjectStyles/Case.ObjectStyles/Data/mnFamData.cs:99-112 | 2017/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnFamData.cs:94-109 | 2017/Case.ObjectStyles/Case.ObjectStyles/Data/mnData.cs:51-64 | 2017/Case.ObjectStyles/Case.ObjectStyles/Data/mnFamData.cs:99-112 | 2018/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnFamData.cs:94-109 | 2018/Case.ObjectStyles/Case.ObjectStyles/Data/mnData.cs:51-64 | 2018/Case.ObjectStyles/Case.ObjectStyles/Data/mnFamData.cs:99-112 — These 12 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 12 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 12 times.
Duplicated block (76 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:638— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:638-713 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:638-713 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:638-713 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:638-713 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 281 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 (76 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:64— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:64-139 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:64-139 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:64-139 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:64-139 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 467 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 (76 lines × 4) 2015/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb:303— 2015/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb:303-378 | 2016/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb:303-378 | 2017/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb:303-378 | 2018/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb:303-378 — before extracting anything, compare `2015/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb` and `2016/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 191 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 (70 lines × 4) 2015/Case.RoomSync/Case.RoomSync/UI/form_Sync.vb:170— 2015/Case.RoomSync/Case.RoomSync/UI/form_Sync.vb:170-239 | 2016/Case.RoomSync/Case.RoomSync/UI/form_Sync.vb:170-239 | 2017/Case.RoomSync/Case.RoomSync/UI/form_Sync.vb:170-239 | 2018/Case.RoomSync/Case.RoomSync/UI/form_Sync.vb:170-239 — before extracting anything, compare `2015/Case.RoomSync/Case.RoomSync/UI/form_Sync.vb` and `2016/Case.RoomSync/Case.RoomSync/UI/form_Sync.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 242 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 (70 lines × 4) 2015/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsSettings.vb:182— 2015/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsSettings.vb:182-251 | 2016/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsSettings.vb:182-251 | 2017/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsSettings.vb:182-251 | 2018/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsSettings.vb:182-251 — before extracting anything, compare `2015/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsSettings.vb` and `2016/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 149 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 (70 lines × 4) 2015/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb:253— 2015/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb:253-322 | 2016/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb:253-322 | 2017/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb:254-323 | 2018/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb:254-323 — before extracting anything, compare `2015/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb` and `2016/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 260 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 (64 lines × 4) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:36— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:36-99 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:36-99 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:36-99 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:36-99 — before extracting anything, compare `2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb` and `2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 685 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 (64 lines × 4) 2015/Case.ApplySysOrient/UI/form_MaxSize.cs:28— 2015/Case.ApplySysOrient/UI/form_MaxSize.cs:28-91 | 2016/Case.ApplySysOrient/UI/form_MaxSize.cs:28-91 | 2017/Case.ApplySysOrient/UI/form_MaxSize.cs:28-91 | 2018/Case.ApplySysOrient/UI/form_MaxSize.cs:28-91 — before extracting anything, compare `2015/Case.ApplySysOrient/UI/form_MaxSize.cs` and `2016/Case.ApplySysOrient/UI/form_MaxSize.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.
Duplicated block (64 lines × 4) 2015/Case.ImageToDraftingView/Case.ImageToDraftingView/Data/clsSettings.vb:11— 2015/Case.ImageToDraftingView/Case.ImageToDraftingView/Data/clsSettings.vb:11-74 | 2016/Case.ImageToDraftingView/Case.ImageToDraftingView/Data/clsSettings.vb:11-74 | 2017/Case.ImageToDraftingView/Case.ImageToDraftingView/Data/clsSettings.vb:11-74 | 2018/Case.ImageToDraftingView/Case.ImageToDraftingView/Data/clsSettings.vb:11-74 — before extracting anything, compare `2015/Case.ImageToDraftingView/Case.ImageToDraftingView/Data/clsSettings.vb` and `2016/Case.ImageToDraftingView/Case.ImageToDraftingView/Data/clsSettings.vb` 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.
Duplicated block (54 lines × 4) 2015/Case.ApplySysOrient/Data/clsSettings.cs:250— 2015/Case.ApplySysOrient/Data/clsSettings.cs:250-303 | 2016/Case.ApplySysOrient/Data/clsSettings.cs:250-303 | 2017/Case.ApplySysOrient/Data/clsSettings.cs:250-303 | 2018/Case.ApplySysOrient/Data/clsSettings.cs:250-303 — before extracting anything, compare `2015/Case.ApplySysOrient/Data/clsSettings.cs` and `2016/Case.ApplySysOrient/Data/clsSettings.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 288 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 (54 lines × 4) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:733— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:733-786 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:733-786 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:733-786 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:733-786 — before extracting anything, compare `2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb` and `2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 685 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 (54 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ParameterConfigurationManager.xaml.vb:116— 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ParameterConfigurationManager.xaml.vb:116-169 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ParameterConfigurationManager.xaml.vb:116-169 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ParameterConfigurationManager.xaml.vb:116-169 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ParameterConfigurationManager.xaml.vb:116-169 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ParameterConfigurationManager.xaml.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ParameterConfigurationManager.xaml.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 169 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 (47 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsVP.vb:141— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsVP.vb:141-187 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsVP.vb:141-187 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsVP.vb:141-187 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsVP.vb:141-187 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsVP.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsVP.vb` 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 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.
Duplicated block (47 lines × 4) 2015/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb:122— 2015/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb:122-168 | 2016/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb:122-168 | 2017/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb:123-169 | 2018/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb:123-169 — before extracting anything, compare `2015/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb` and `2016/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 260 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 (47 lines × 4) 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsRoomFamily.vb:14— 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsRoomFamily.vb:14-60 | 2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsRoomFamily.vb:14-60 | 2017/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsRoomFamily.vb:14-60 | 2018/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsRoomFamily.vb:14-60 — before extracting anything, compare `2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsRoomFamily.vb` and `2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsRoomFamily.vb` 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.
Duplicated block (34–39 lines × 3) 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Entry/B31EA3F20509489BB52A0381E8838AFC.vb:30— 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Entry/B31EA3F20509489BB52A0381E8838AFC.vb:30-68 | 2015/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/Entry/A330EB8E54CA46B3A28E41DA9E77F9F6.vb:25-58 | 2015/Case.Subs.SharedParameters/Case.Subs.SharedParameters/Entry/BC456E773F0B4A04A764DE16ECDA69C9.vb:25-60 — before extracting anything, compare `2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Entry/B31EA3F20509489BB52A0381E8838AFC.vb` and `2015/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/Entry/A330EB8E54CA46B3A28E41DA9E77F9F6.vb` 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.
Duplicated block (34–39 lines × 3) 2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Entry/B31EA3F20509489BB52A0381E8838AFC.vb:30— 2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Entry/B31EA3F20509489BB52A0381E8838AFC.vb:30-68 | 2016/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/Entry/A330EB8E54CA46B3A28E41DA9E77F9F6.vb:25-58 | 2016/Case.Subs.SharedParameters/Case.Subs.SharedParameters/Entry/BC456E773F0B4A04A764DE16ECDA69C9.vb:25-60 — before extracting anything, compare `2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Entry/B31EA3F20509489BB52A0381E8838AFC.vb` and `2016/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/Entry/A330EB8E54CA46B3A28E41DA9E77F9F6.vb` 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.
Duplicated block (34–39 lines × 3) 2017/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Entry/B31EA3F20509489BB52A0381E8838AFC.vb:30— 2017/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Entry/B31EA3F20509489BB52A0381E8838AFC.vb:30-68 | 2017/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/Entry/A330EB8E54CA46B3A28E41DA9E77F9F6.vb:25-58 | 2017/Case.Subs.SharedParameters/Case.Subs.SharedParameters/Entry/BC456E773F0B4A04A764DE16ECDA69C9.vb:25-60 — before extracting anything, compare `2017/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Entry/B31EA3F20509489BB52A0381E8838AFC.vb` and `2017/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/Entry/A330EB8E54CA46B3A28E41DA9E77F9F6.vb` 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.
Duplicated block (34 lines × 8) 2015/Case.MultiViewDuplicate/Case.MultiViewDuplicate/UI/form_Main.vb:113— 2015/Case.MultiViewDuplicate/Case.MultiViewDuplicate/UI/form_Main.vb:113-146 | 2015/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/UI/form_Main.vb:112-145 | 2016/Case.MultiViewDuplicate/Case.MultiViewDuplicate/UI/form_Main.vb:113-146 | 2016/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/UI/form_Main.vb:112-145 | 2017/Case.MultiViewDuplicate/Case.MultiViewDuplicate/UI/form_Main.vb:113-146 | 2017/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/UI/form_Main.vb:112-145 | 2018/Case.MultiViewDuplicate/Case.MultiViewDuplicate/UI/form_Main.vb:113-146 | 2018/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/UI/form_Main.vb:112-145 — before extracting anything, compare `2015/Case.MultiViewDuplicate/Case.MultiViewDuplicate/UI/form_Main.vb` and `2016/Case.MultiViewDuplicate/Case.MultiViewDuplicate/UI/form_Main.vb` as WHOLE FILES: this scan already matched 3 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. 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 × 8) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:169— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:169-202 | 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSettings.vb:136-169 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:169-202 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSettings.vb:136-169 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:169-202 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSettings.vb:136-169 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:169-202 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSettings.vb:136-169 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 422 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 × 8) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:362— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:362-395 | 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:811-844 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:362-395 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:811-844 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:362-395 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:811-844 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:362-395 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:811-844 — before extracting anything, compare `2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb` and `2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 92 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the 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 (32 lines × 4) 2015/Case.Subs.SuperTag/Case.Subs.SuperTag/Entry/A01A0A226EBE4CD89D655C55B997650F.vb:38— 2015/Case.Subs.SuperTag/Case.Subs.SuperTag/Entry/A01A0A226EBE4CD89D655C55B997650F.vb:38-69 | 2016/Case.Subs.SuperTag/Case.Subs.SuperTag/Entry/A01A0A226EBE4CD89D655C55B997650F.vb:38-69 | 2017/Case.Subs.SuperTag/Case.Subs.SuperTag/Entry/A01A0A226EBE4CD89D655C55B997650F.vb:38-69 | 2018/Case.Subs.SuperTag/Case.Subs.SuperTag/Entry/A01A0A226EBE4CD89D655C55B997650F.vb:38-69 — before extracting anything, compare `2015/Case.Subs.SuperTag/Case.Subs.SuperTag/Entry/A01A0A226EBE4CD89D655C55B997650F.vb` and `2016/Case.Subs.SuperTag/Case.Subs.SuperTag/Entry/A01A0A226EBE4CD89D655C55B997650F.vb` as WHOLE FILES: 94% 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. Read the line range as the matched WINDOW rather than a finished unit: at `2015/Case.Subs.SuperTag/Case.Subs.SuperTag/Entry/A01A0A226EBE4CD89D655C55B997650F.vb:38` 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 (32 lines × 4) 2015/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Data/clsParameter.vb:198— 2015/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Data/clsParameter.vb:198-229 | 2016/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Data/clsParameter.vb:198-229 | 2017/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Data/clsParameter.vb:198-229 | 2018/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Data/clsParameter.vb:198-229 — before extracting anything, compare `2015/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Data/clsParameter.vb` and `2016/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/Data/clsParameter.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 52 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 (32 lines × 4) 2015/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsSettings.vb:292— 2015/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsSettings.vb:292-323 | 2016/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsSettings.vb:292-323 | 2017/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsSettings.vb:292-323 | 2018/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsSettings.vb:292-323 — before extracting anything, compare `2015/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsSettings.vb` and `2016/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 114 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 (30 lines × 3) 2015/Case.ViewTemplates/Case.ViewTemplates/Entry/CmdMain.vb:37— 2015/Case.ViewTemplates/Case.ViewTemplates/Entry/CmdMain.vb:37-66 | 2016/Case.ViewTemplates/Case.ViewTemplates/Entry/CmdMain.vb:37-66 | 2017/Case.ViewTemplates/Case.ViewTemplates/Entry/CmdMain.vb:37-66 — before extracting anything, compare `2015/Case.ViewTemplates/Case.ViewTemplates/Entry/CmdMain.vb` and `2016/Case.ViewTemplates/Case.ViewTemplates/Entry/CmdMain.vb` as WHOLE FILES: 96% 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. Read the line range as the matched WINDOW rather than a finished unit: at `2015/Case.ViewTemplates/Case.ViewTemplates/Entry/CmdMain.vb:37` 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 (30 lines × 3) 2015/Case.RoomSync/Case.RoomSync/Entry/CmdMain.vb:34— 2015/Case.RoomSync/Case.RoomSync/Entry/CmdMain.vb:34-63 | 2016/Case.RoomSync/Case.RoomSync/Entry/CmdMain.vb:34-63 | 2017/Case.RoomSync/Case.RoomSync/Entry/CmdMain.vb:34-63 — before extracting anything, compare `2015/Case.RoomSync/Case.RoomSync/Entry/CmdMain.vb` and `2016/Case.RoomSync/Case.RoomSync/Entry/CmdMain.vb` as WHOLE FILES: 96% 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. Read the line range as the matched WINDOW rather than a finished unit: at `2015/Case.RoomSync/Case.RoomSync/Entry/CmdMain.vb:34` 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 (30 lines × 3) Case.AppsRibbon.2017/Entry/AppMain.vb:39— Case.AppsRibbon.2017/Entry/AppMain.vb:39-68 | Case.AppsRibbon.2018/Entry/AppMain.vb:39-68 | Case.AppsRibbon/Entry/AppMain.vb:39-68 — before extracting anything, compare `Case.AppsRibbon.2017/Entry/AppMain.vb` and `Case.AppsRibbon.2018/Entry/AppMain.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 148 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 (27 lines × 4) 2015/Case.Subs.KeyMatcher/Entry/CmdMain.cs:24— 2015/Case.Subs.KeyMatcher/Entry/CmdMain.cs:24-50 | 2016/Case.Subs.KeyMatcher/Entry/CmdMain.cs:24-50 | 2017/Case.Subs.KeyMatcher/Entry/CmdMain.cs:24-50 | 2018/Case.Subs.KeyMatcher/Entry/CmdMain.cs:24-50 — before extracting anything, compare `2015/Case.Subs.KeyMatcher/Entry/CmdMain.cs` and `2016/Case.Subs.KeyMatcher/Entry/CmdMain.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. 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 (27 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb:41— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb:41-67 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb:41-67 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb:41-67 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb:41-67 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 109 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 (27 lines × 4) 2015/Case.Subs.Worksets/Case.Subs.Worksets/Charts/clsModCharts.vb:16— 2015/Case.Subs.Worksets/Case.Subs.Worksets/Charts/clsModCharts.vb:16-42 | 2016/Case.Subs.Worksets/Case.Subs.Worksets/Charts/clsModCharts.vb:16-42 | 2017/Case.Subs.Worksets/Case.Subs.Worksets/Charts/clsModCharts.vb:16-42 | 2018/Case.Subs.Worksets/Case.Subs.Worksets/Charts/clsModCharts.vb:16-42 — before extracting anything, compare `2015/Case.Subs.Worksets/Case.Subs.Worksets/Charts/clsModCharts.vb` and `2016/Case.Subs.Worksets/Case.Subs.Worksets/Charts/clsModCharts.vb` 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 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.
Duplicated block (25–26 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F1.vb:32— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F1.vb:32-57 | 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F2.vb:34-58 | 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F3.vb:32-56 | 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F4.vb:32-56 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F1.vb` and `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F2.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 67 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the 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–26 lines × 4) 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F1.vb:32— 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F1.vb:32-57 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F2.vb:34-58 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F3.vb:32-56 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F4.vb:32-56 — before extracting anything, compare `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F1.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F2.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 67 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the 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–26 lines × 4) 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F1.vb:32— 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F1.vb:32-57 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F2.vb:34-58 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F3.vb:32-56 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F4.vb:32-56 — before extracting anything, compare `2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F1.vb` and `2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F2.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 67 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the 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 (21–22 lines × 7) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F1.vb:29— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F1.vb:29-50 | 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F2.vb:31-51 | 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F3.vb:29-49 | 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F4.vb:29-49 | 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2512.vb:32-53 | 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2513.vb:29-50 | 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2514.vb:29-50 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F1.vb` and `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F2.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 67 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the 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 (21–22 lines × 7) 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F1.vb:29— 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F1.vb:29-50 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F2.vb:31-51 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F3.vb:29-49 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F4.vb:29-49 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2512.vb:32-53 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2513.vb:29-50 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2514.vb:29-50 — before extracting anything, compare `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F1.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F2.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 67 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the 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 (21–22 lines × 7) 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F1.vb:29— 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F1.vb:29-50 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F2.vb:31-51 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F3.vb:29-49 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F4.vb:29-49 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2512.vb:32-53 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2513.vb:29-50 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2514.vb:29-50 — before extracting anything, compare `2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F1.vb` and `2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F2.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 67 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the 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 (16–18 lines × 5) 2015/Case.DimensionOverrides/Case.DimensionOverrides/Entry/CmdMain.cs:26— 2015/Case.DimensionOverrides/Case.DimensionOverrides/Entry/CmdMain.cs:26-41 | 2015/Case.ObjectStyles/Case.ObjectStyles/Entry/CmdMain.cs:23-40 | 2015/Case.ParallelWalls/Case.ParallelWalls/Entry/CmdMain.cs:23-38 | 2015/Case.ReportGroupsByView/Case.ReportGroupsByView/Entry/CmdMain.cs:23-40 | 2015/Case.UngroupAll/Case.UngroupAll/Entry/CmdMain.cs:23-40 — before extracting anything, compare `2015/Case.DimensionOverrides/Case.DimensionOverrides/Entry/CmdMain.cs` and `2015/Case.ObjectStyles/Case.ObjectStyles/Entry/CmdMain.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 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. Read the line range as the matched WINDOW rather than a finished unit: at `2015/Case.DimensionOverrides/Case.DimensionOverrides/Entry/CmdMain.cs:26` 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 (16–18 lines × 5) 2016/Case.DimensionOverrides/Case.DimensionOverrides/Entry/CmdMain.cs:26— 2016/Case.DimensionOverrides/Case.DimensionOverrides/Entry/CmdMain.cs:26-41 | 2016/Case.ObjectStyles/Case.ObjectStyles/Entry/CmdMain.cs:23-40 | 2016/Case.ParallelWalls/Case.ParallelWalls/Entry/CmdMain.cs:23-38 | 2016/Case.ReportGroupsByView/Case.ReportGroupsByView/Entry/CmdMain.cs:23-40 | 2016/Case.UngroupAll/Case.UngroupAll/Entry/CmdMain.cs:23-40 — before extracting anything, compare `2016/Case.DimensionOverrides/Case.DimensionOverrides/Entry/CmdMain.cs` and `2016/Case.ObjectStyles/Case.ObjectStyles/Entry/CmdMain.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 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. Read the line range as the matched WINDOW rather than a finished unit: at `2016/Case.DimensionOverrides/Case.DimensionOverrides/Entry/CmdMain.cs:26` 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 (16–18 lines × 5) 2017/Case.DimensionOverrides/Case.DimensionOverrides/Entry/CmdMain.cs:26— 2017/Case.DimensionOverrides/Case.DimensionOverrides/Entry/CmdMain.cs:26-41 | 2017/Case.ObjectStyles/Case.ObjectStyles/Entry/CmdMain.cs:23-40 | 2017/Case.ParallelWalls/Case.ParallelWalls/Entry/CmdMain.cs:23-38 | 2017/Case.ReportGroupsByView/Case.ReportGroupsByView/Entry/CmdMain.cs:23-40 | 2017/Case.UngroupAll/Case.UngroupAll/Entry/CmdMain.cs:23-40 — before extracting anything, compare `2017/Case.DimensionOverrides/Case.DimensionOverrides/Entry/CmdMain.cs` and `2017/Case.ObjectStyles/Case.ObjectStyles/Entry/CmdMain.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 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. Read the line range as the matched WINDOW rather than a finished unit: at `2017/Case.DimensionOverrides/Case.DimensionOverrides/Entry/CmdMain.cs:26` 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 × 8) 2015/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:47— 2015/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:47-58 | 2015/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:210-221 | 2016/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:47-58 | 2016/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:210-221 | 2017/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:47-58 | 2017/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:210-221 | 2018/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:47-58 | 2018/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:210-221 — before extracting anything, compare `2015/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb` and `2015/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb` 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.
Duplicated block (12 lines × 8) 2015/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsElement.vb:53— 2015/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsElement.vb:53-64 | 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsFamily.vb:38-49 | 2016/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsElement.vb:53-64 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsFamily.vb:38-49 | 2017/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsElement.vb:53-64 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsFamily.vb:38-49 | 2018/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsElement.vb:53-64 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsFamily.vb:38-49 — before extracting anything, compare `2015/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsElement.vb` and `2016/Case.Subs.SuperTag/Case.Subs.SuperTag/Data/clsElement.vb` 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 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.
Duplicated block (12 lines × 8) 2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:544— 2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:544-555 | 2015/Case.ViewTemplates/Case.ViewTemplates/UI/form_Main.vb:152-163 | 2016/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:544-555 | 2016/Case.ViewTemplates/Case.ViewTemplates/UI/form_Main.vb:152-163 | 2017/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:544-555 | 2017/Case.ViewTemplates/Case.ViewTemplates/UI/form_Main.vb:152-163 | 2018/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:544-555 | 2018/Case.ViewTemplates/Case.ViewTemplates/UI/form_Main.vb:152-163 — before extracting anything, compare `2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb` and `2015/Case.ViewTemplates/Case.ViewTemplates/UI/form_Main.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 62 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 (6 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb:350— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb:350-355 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb:350-355 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb:350-355 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb:350-355 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtScheduleData.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 109 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 (6 lines × 4) 2015/Case.Subs.Linestyles/Case.Subs.Linestyles/Data/clsSettings.vb:78— 2015/Case.Subs.Linestyles/Case.Subs.Linestyles/Data/clsSettings.vb:78-83 | 2016/Case.Subs.Linestyles/Case.Subs.Linestyles/Data/clsSettings.vb:78-83 | 2017/Case.Subs.Linestyles/Case.Subs.Linestyles/Data/clsSettings.vb:78-83 | 2018/Case.Subs.Linestyles/Case.Subs.Linestyles/Data/clsSettings.vb:78-83 — before extracting anything, compare `2015/Case.Subs.Linestyles/Case.Subs.Linestyles/Data/clsSettings.vb` and `2016/Case.Subs.Linestyles/Case.Subs.Linestyles/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 4 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. 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 (6 lines × 4) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:36— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:36-41 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:36-41 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:36-41 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:36-41 — before extracting anything, compare `2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb` and `2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 257 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· Near-duplicate member family (4 members, 52 shared lines) · ×2
Near-duplicate member family (4 members, 52 shared lines) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F4.vb:29— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F4.vb:29-96 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F4.vb:29-96 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F4.vb:29-96 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F4.vb:29-96 — These 4 members are variants of one another: a block of 52 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.
Near-duplicate member family (4 members, 52 shared lines) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:40— 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:40-194 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:40-194 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:40-194 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:40-194 — These 4 members are variants of one another: a block of 52 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 (4 members, 31 shared lines) · ×2
Near-duplicate member family (4 members, 31 shared lines) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/OpenNURBS/clsONSort.vb:59— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/OpenNURBS/clsONSort.vb:59-337 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/OpenNURBS/clsONSort.vb:59-337 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/OpenNURBS/clsONSort.vb:59-337 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/OpenNURBS/clsONSort.vb:59-337 — These 4 members are variants of one another: a block of 31 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.
Near-duplicate member family (4 members, 31 shared lines) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSharedParameters.vb:196— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSharedParameters.vb:196-282 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSharedParameters.vb:196-282 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSharedParameters.vb:196-282 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSharedParameters.vb:196-282 — These 4 members are variants of one another: a block of 31 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 copy of a member (24 corresponding lines) · ×2
Edited copy of a member (24 corresponding lines) 2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/SplitContainerEx.vb:32— 2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/SplitContainerEx.vb:32-55 | 2016/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/SplitContainerEx.vb:32-55 — 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) 2017/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/SplitContainerEx.vb:32— 2017/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/SplitContainerEx.vb:32-55 | 2018/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/SplitContainerEx.vb:32-55 — 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 copy of a member (38 corresponding lines) · ×2
Edited copy of a member (38 corresponding lines) 2017/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:401— 2017/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:401-438 | 2018/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:401-438 — 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.
Edited copy of a member (38 corresponding lines) 2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:401— 2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:401-438 | 2016/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:401-438 — 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· Members sharing a duplicated core (25 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (25 members, 50+ identical tokens) REDACTED:21— REDACTED:21-47 | REDACTED:21-47 | REDACTED:21-47 | REDACTED:21-47 | REDACTED:25-48 | REDACTED:21-47 | REDACTED:21-47 | REDACTED:21-47 | REDACTED:21-47 | REDACTED:21-47 | REDACTED:21-47 | REDACTED:21-47 | REDACTED:25-48 | REDACTED:21-47 | REDACTED:21-47 | REDACTED:21-47 | REDACTED:21-47 | REDACTED:21-47 | REDACTED:21-47 | REDACTED:21-47 | REDACTED:25-48 | REDACTED:21-47 | REDACTED:21-47 | REDACTED:21-47 | REDACTED:21-47 — These 25 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 25 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 25 times.
Members sharing a duplicated core (25 members, 50+ identical tokens) REDACTED:75— REDACTED:75-98 | REDACTED:75-98 | REDACTED:75-98 | REDACTED:75-98 | REDACTED:76-98 | REDACTED:75-98 | REDACTED:75-98 | REDACTED:75-98 | REDACTED:75-98 | REDACTED:75-98 | REDACTED:75-98 | REDACTED:75-98 | REDACTED:76-98 | REDACTED:75-98 | REDACTED:75-98 | REDACTED:75-98 | REDACTED:75-98 | REDACTED:75-98 | REDACTED:75-98 | REDACTED:75-98 | REDACTED:76-98 | REDACTED:75-98 | REDACTED:75-98 | REDACTED:75-98 | REDACTED:75-98 — These 25 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 25 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 25 times.
Duplicated block (139 lines × 4) 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:274— 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:274-412 | 2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:274-412 | 2017/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:274-412 | 2018/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:274-412 — before extracting anything, compare `2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb` and `2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 500 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 (139 lines × 4) 2015/Case.Subs.SharedParameters/Case.Subs.SharedParameters/Data/clsSettings.vb:21— 2015/Case.Subs.SharedParameters/Case.Subs.SharedParameters/Data/clsSettings.vb:21-159 | 2016/Case.Subs.SharedParameters/Case.Subs.SharedParameters/Data/clsSettings.vb:21-159 | 2017/Case.Subs.SharedParameters/Case.Subs.SharedParameters/Data/clsSettings.vb:21-159 | 2018/Case.Subs.SharedParameters/Case.Subs.SharedParameters/Data/clsSettings.vb:21-159 — before extracting anything, compare `2015/Case.Subs.SharedParameters/Case.Subs.SharedParameters/Data/clsSettings.vb` and `2016/Case.Subs.SharedParameters/Case.Subs.SharedParameters/Data/clsSettings.vb` 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.
Duplicated block (126 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:124— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:124-249 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:124-249 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:124-249 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:124-249 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 610 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 (126 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSettings.vb:313— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSettings.vb:313-438 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSettings.vb:313-438 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSettings.vb:313-438 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSettings.vb:313-438 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSettings.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 5 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. 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 (104 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:591— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:591-694 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:591-694 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:591-694 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:591-694 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 402 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 (104 lines × 4) 2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:230— 2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:230-333 | 2016/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:230-333 | 2017/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:230-333 | 2018/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:230-333 — before extracting anything, compare `2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb` and `2016/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 373 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 (95 lines × 4) 2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:35— 2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:35-129 | 2016/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:35-129 | 2017/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:35-129 | 2018/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:35-129 — before extracting anything, compare `2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb` and `2016/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 373 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 (95 lines × 4) 2015/Case.ChangeReplaceFamTypeNames/Case.ChangeReplaceFamTypeNames/UI/form_Main.vb:52— 2015/Case.ChangeReplaceFamTypeNames/Case.ChangeReplaceFamTypeNames/UI/form_Main.vb:52-146 | 2016/Case.ChangeReplaceFamTypeNames/Case.ChangeReplaceFamTypeNames/UI/form_Main.vb:52-146 | 2017/Case.ChangeReplaceFamTypeNames/Case.ChangeReplaceFamTypeNames/UI/form_Main.vb:52-146 | 2018/Case.ChangeReplaceFamTypeNames/Case.ChangeReplaceFamTypeNames/UI/form_Main.vb:52-146 — before extracting anything, compare `2015/Case.ChangeReplaceFamTypeNames/Case.ChangeReplaceFamTypeNames/UI/form_Main.vb` and `2016/Case.ChangeReplaceFamTypeNames/Case.ChangeReplaceFamTypeNames/UI/form_Main.vb` 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 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.
Duplicated block (92 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:738— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:738-829 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:738-829 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:738-829 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:738-829 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 402 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 (92 lines × 4) 2015/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/UI/form_Main.vb:116— 2015/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/UI/form_Main.vb:116-207 | 2016/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/UI/form_Main.vb:116-207 | 2017/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/UI/form_Main.vb:116-207 | 2018/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/UI/form_Main.vb:111-202 — before extracting anything, compare `2015/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/UI/form_Main.vb` and `2016/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/UI/form_Main.vb` as WHOLE FILES: this scan already matched 3 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. 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 (89 lines × 4) 2015/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb:343— 2015/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb:343-431 | 2016/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb:343-431 | 2017/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb:343-431 | 2018/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb:344-432 — before extracting anything, compare `2015/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb` and `2016/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 364 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 (89 lines × 4) 2015/Case.SharedParameters/Case.SharedParameters/Data/clsSettings.vb:22— 2015/Case.SharedParameters/Case.SharedParameters/Data/clsSettings.vb:22-110 | 2016/Case.SharedParameters/Case.SharedParameters/Data/clsSettings.vb:22-110 | 2017/Case.SharedParameters/Case.SharedParameters/Data/clsSettings.vb:22-110 | 2018/Case.SharedParameters/Case.SharedParameters/Data/clsSettings.vb:22-110 — before extracting anything, compare `2015/Case.SharedParameters/Case.SharedParameters/Data/clsSettings.vb` and `2016/Case.SharedParameters/Case.SharedParameters/Data/clsSettings.vb` 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.
Duplicated block (84 lines × 4) 2015/Case.ModeledRoomTags/Case.ModeledRoomTags/UI/form_Main.vb:100— 2015/Case.ModeledRoomTags/Case.ModeledRoomTags/UI/form_Main.vb:100-183 | 2016/Case.ModeledRoomTags/Case.ModeledRoomTags/UI/form_Main.vb:100-183 | 2017/Case.ModeledRoomTags/Case.ModeledRoomTags/UI/form_Main.vb:100-183 | 2018/Case.ModeledRoomTags/Case.ModeledRoomTags/UI/form_Main.vb:100-183 — before extracting anything, compare `2015/Case.ModeledRoomTags/Case.ModeledRoomTags/UI/form_Main.vb` and `2016/Case.ModeledRoomTags/Case.ModeledRoomTags/UI/form_Main.vb` as WHOLE FILES: this scan already matched 3 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. 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 (84 lines × 4) 2015/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Form/form_Main.vb:278— 2015/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Form/form_Main.vb:278-361 | 2016/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Form/form_Main.vb:278-361 | 2017/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Form/form_Main.vb:278-361 | 2018/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Form/form_Main.vb:278-361 — before extracting anything, compare `2015/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Form/form_Main.vb` and `2016/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Form/form_Main.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 215 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 (75 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsIoConfig.vb:62— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsIoConfig.vb:62-136 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsIoConfig.vb:62-136 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsIoConfig.vb:62-136 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsIoConfig.vb:62-136 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsIoConfig.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsIoConfig.vb` 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 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.
Duplicated block (75 lines × 4) 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsViews.vb:15— 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsViews.vb:15-89 | 2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsViews.vb:15-89 | 2017/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsViews.vb:15-89 | 2018/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsViews.vb:15-89 — before extracting anything, compare `2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsViews.vb` and `2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsViews.vb` 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.
Duplicated block (74 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:390— 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:390-463 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:390-463 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:390-463 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:389-462 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 317 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 (74 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsDesignOption.vb:19— 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsDesignOption.vb:19-92 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsDesignOption.vb:19-92 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsDesignOption.vb:19-92 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsDesignOption.vb:19-92 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsDesignOption.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsDesignOption.vb` 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.
Duplicated block (71 lines × 4) 2015/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsExcel.vb:72— 2015/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsExcel.vb:72-142 | 2016/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsExcel.vb:72-142 | 2017/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsExcel.vb:72-142 | 2018/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsExcel.vb:72-142 — before extracting anything, compare `2015/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsExcel.vb` and `2016/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsExcel.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 187 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 (71 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_SmartSync.vb:15— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_SmartSync.vb:15-85 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_SmartSync.vb:15-85 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_SmartSync.vb:15-85 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_SmartSync.vb:15-85 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_SmartSync.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_SmartSync.vb` 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.
Duplicated block (69 lines × 4) REDACTED:224— REDACTED:224-292 | REDACTED:224-292 | REDACTED:224-292 | REDACTED:224-292 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 421 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 (69 lines × 4) 2015/Case.ImageToDraftingView/Case.ImageToDraftingView/Forms/form_Main.vb:67— 2015/Case.ImageToDraftingView/Case.ImageToDraftingView/Forms/form_Main.vb:67-135 | 2016/Case.ImageToDraftingView/Case.ImageToDraftingView/Forms/form_Main.vb:67-135 | 2017/Case.ImageToDraftingView/Case.ImageToDraftingView/Forms/form_Main.vb:67-135 | 2018/Case.ImageToDraftingView/Case.ImageToDraftingView/Forms/form_Main.vb:67-135 — before extracting anything, compare `2015/Case.ImageToDraftingView/Case.ImageToDraftingView/Forms/form_Main.vb` and `2016/Case.ImageToDraftingView/Case.ImageToDraftingView/Forms/form_Main.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 155 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 (68 lines × 2) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:335— 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:335-402 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:335-402 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 267 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 (68 lines × 2) 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:335— 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:335-402 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:335-402 — before extracting anything, compare `2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb` and `2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 267 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 (67 lines × 4) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:257— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:257-323 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:257-323 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:257-323 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:257-323 — before extracting anything, compare `2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb` and `2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 685 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 (67 lines × 4) 2015/Case.RoomInsertionPoint/Case.RoomInsertionPoint/Entry/CmdMain.vb:51— 2015/Case.RoomInsertionPoint/Case.RoomInsertionPoint/Entry/CmdMain.vb:51-117 | 2016/Case.RoomInsertionPoint/Case.RoomInsertionPoint/Entry/CmdMain.vb:51-117 | 2017/Case.RoomInsertionPoint/Case.RoomInsertionPoint/Entry/CmdMain.vb:51-117 | 2018/Case.RoomInsertionPoint/Case.RoomInsertionPoint/Entry/CmdMain.vb:46-112 — before extracting anything, compare `2015/Case.RoomInsertionPoint/Case.RoomInsertionPoint/Entry/CmdMain.vb` and `2016/Case.RoomInsertionPoint/Case.RoomInsertionPoint/Entry/CmdMain.vb` as WHOLE FILES: 97% 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 (65 lines × 4) 2015/Case.LineChanger/Case.LineChanger/Data/clsSettings.vb:199— 2015/Case.LineChanger/Case.LineChanger/Data/clsSettings.vb:199-263 | 2016/Case.LineChanger/Case.LineChanger/Data/clsSettings.vb:199-263 | 2017/Case.LineChanger/Case.LineChanger/Data/clsSettings.vb:199-263 | 2018/Case.LineChanger/Case.LineChanger/Data/clsSettings.vb:199-263 — before extracting anything, compare `2015/Case.LineChanger/Case.LineChanger/Data/clsSettings.vb` and `2016/Case.LineChanger/Case.LineChanger/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 126 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 (65 lines × 4) 2015/Case.ReportGroupsByView/Case.ReportGroupsByView/Data/clsData.cs:14— 2015/Case.ReportGroupsByView/Case.ReportGroupsByView/Data/clsData.cs:14-78 | 2016/Case.ReportGroupsByView/Case.ReportGroupsByView/Data/clsData.cs:14-78 | 2017/Case.ReportGroupsByView/Case.ReportGroupsByView/Data/clsData.cs:14-78 | 2018/Case.ReportGroupsByView/Case.ReportGroupsByView/Data/clsData.cs:14-78 — before extracting anything, compare `2015/Case.ReportGroupsByView/Case.ReportGroupsByView/Data/clsData.cs` and `2016/Case.ReportGroupsByView/Case.ReportGroupsByView/Data/clsData.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.
Duplicated block (63 lines × 4) 2015/Case.ReportGroupsByView/Case.ReportGroupsByView/Data/clsSettings.cs:133— 2015/Case.ReportGroupsByView/Case.ReportGroupsByView/Data/clsSettings.cs:133-195 | 2016/Case.ReportGroupsByView/Case.ReportGroupsByView/Data/clsSettings.cs:133-195 | 2017/Case.ReportGroupsByView/Case.ReportGroupsByView/Data/clsSettings.cs:133-195 | 2018/Case.ReportGroupsByView/Case.ReportGroupsByView/Data/clsSettings.cs:133-195 — before extracting anything, compare `2015/Case.ReportGroupsByView/Case.ReportGroupsByView/Data/clsSettings.cs` and `2016/Case.ReportGroupsByView/Case.ReportGroupsByView/Data/clsSettings.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 123 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 (63 lines × 4) 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsPara.vb:24— 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsPara.vb:24-86 | 2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsPara.vb:24-86 | 2017/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsPara.vb:24-86 | 2018/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsPara.vb:24-86 — before extracting anything, compare `2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsPara.vb` and `2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsPara.vb` 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.
Duplicated block (62 lines × 4) 2015/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:360— 2015/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:360-421 | 2016/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:360-421 | 2017/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:360-421 | 2018/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:360-421 — before extracting anything, compare `2015/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb` and `2016/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 245 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 (62 lines × 4) 2015/Case.Subs.Worksets/Case.Subs.Worksets/Charts/clsModCharts.vb:58— 2015/Case.Subs.Worksets/Case.Subs.Worksets/Charts/clsModCharts.vb:58-119 | 2016/Case.Subs.Worksets/Case.Subs.Worksets/Charts/clsModCharts.vb:58-119 | 2017/Case.Subs.Worksets/Case.Subs.Worksets/Charts/clsModCharts.vb:58-119 | 2018/Case.Subs.Worksets/Case.Subs.Worksets/Charts/clsModCharts.vb:58-119 — before extracting anything, compare `2015/Case.Subs.Worksets/Case.Subs.Worksets/Charts/clsModCharts.vb` and `2016/Case.Subs.Worksets/Case.Subs.Worksets/Charts/clsModCharts.vb` 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 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.
Duplicated block (61 lines × 4) 2015/Case.Subs.Linestyles/Case.Subs.Linestyles/Data/clsSettings.vb:220— 2015/Case.Subs.Linestyles/Case.Subs.Linestyles/Data/clsSettings.vb:220-280 | 2016/Case.Subs.Linestyles/Case.Subs.Linestyles/Data/clsSettings.vb:220-280 | 2017/Case.Subs.Linestyles/Case.Subs.Linestyles/Data/clsSettings.vb:220-280 | 2018/Case.Subs.Linestyles/Case.Subs.Linestyles/Data/clsSettings.vb:220-280 — before extracting anything, compare `2015/Case.Subs.Linestyles/Case.Subs.Linestyles/Data/clsSettings.vb` and `2016/Case.Subs.Linestyles/Case.Subs.Linestyles/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 4 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. 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 (61 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:176— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:176-236 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:176-236 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:176-236 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:176-236 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 467 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 (56 lines × 4) 2015/Case.ApplySysOrient/Data/clsSettings.cs:187— 2015/Case.ApplySysOrient/Data/clsSettings.cs:187-242 | 2016/Case.ApplySysOrient/Data/clsSettings.cs:187-242 | 2017/Case.ApplySysOrient/Data/clsSettings.cs:187-242 | 2018/Case.ApplySysOrient/Data/clsSettings.cs:187-242 — before extracting anything, compare `2015/Case.ApplySysOrient/Data/clsSettings.cs` and `2016/Case.ApplySysOrient/Data/clsSettings.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 288 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 (56 lines × 4) 2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/clsSettings.vb:38— 2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/clsSettings.vb:38-93 | 2016/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/clsSettings.vb:38-93 | 2017/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/clsSettings.vb:38-93 | 2018/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/clsSettings.vb:38-93 — before extracting anything, compare `2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/clsSettings.vb` and `2016/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/clsSettings.vb` 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.
Duplicated block (53 lines × 4) 2015/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb:456— 2015/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb:456-508 | 2016/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb:456-508 | 2017/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb:456-508 | 2018/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb:456-508 — before extracting anything, compare `2015/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb` and `2016/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 215 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) 2015/Case.ExportSharedParameters/Case.ExportSharedParameters/Classes/Entry/cmd.cs:114— 2015/Case.ExportSharedParameters/Case.ExportSharedParameters/Classes/Entry/cmd.cs:114-166 | 2016/Case.ExportSharedParameters/Case.ExportSharedParameters/Classes/Entry/cmd.cs:114-166 | 2017/Case.ExportSharedParameters/Case.ExportSharedParameters/Classes/Entry/cmd.cs:114-166 | 2018/Case.ExportSharedParameters/Case.ExportSharedParameters/Classes/Entry/cmd.cs:114-166 — before extracting anything, compare `2015/Case.ExportSharedParameters/Case.ExportSharedParameters/Classes/Entry/cmd.cs` and `2016/Case.ExportSharedParameters/Case.ExportSharedParameters/Classes/Entry/cmd.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. Read the line range as the matched WINDOW rather than a finished unit: at `2015/Case.ExportSharedParameters/Case.ExportSharedParameters/Classes/Entry/cmd.cs:114` 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 (25 lines × 3) REDACTED:102— REDACTED:102-126 | REDACTED:102-126 | REDACTED:102-126 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 264 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:102` 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 (25 lines × 3) 2015/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb:120— 2015/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb:120-144 | 2016/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb:120-144 | 2017/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb:120-144 — before extracting anything, compare `2015/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb` and `2016/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 364 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 (46 lines × 4) 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Entry/AF73BA45B4B94C7585CB3E425D423F5E.vb:49— 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Entry/AF73BA45B4B94C7585CB3E425D423F5E.vb:49-94 | 2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Entry/AF73BA45B4B94C7585CB3E425D423F5E.vb:49-94 | 2017/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Entry/AF73BA45B4B94C7585CB3E425D423F5E.vb:49-94 | 2018/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Entry/AF73BA45B4B94C7585CB3E425D423F5E.vb:49-94 — before extracting anything, compare `2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Entry/AF73BA45B4B94C7585CB3E425D423F5E.vb` and `2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Entry/AF73BA45B4B94C7585CB3E425D423F5E.vb` as WHOLE FILES: 97% 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. Read the line range as the matched WINDOW rather than a finished unit: at `2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Entry/AF73BA45B4B94C7585CB3E425D423F5E.vb:49` 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 (46 lines × 4) 2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:174— 2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:174-219 | 2016/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:174-219 | 2017/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:174-219 | 2018/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:174-219 — before extracting anything, compare `2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb` and `2016/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 373 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 (40 lines × 4) REDACTED:52— REDACTED:52-91 | REDACTED:52-91 | REDACTED:52-91 | REDACTED:52-91 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 147 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 (40 lines × 4) 2015/Case.RevClouds/Case.RevClouds/Data/clsSettings.vb:80— 2015/Case.RevClouds/Case.RevClouds/Data/clsSettings.vb:80-119 | 2016/Case.RevClouds/Case.RevClouds/Data/clsSettings.vb:80-119 | 2017/Case.RevClouds/Case.RevClouds/Data/clsSettings.vb:80-119 | 2018/Case.RevClouds/Case.RevClouds/Data/clsSettings.vb:80-119 — before extracting anything, compare `2015/Case.RevClouds/Case.RevClouds/Data/clsSettings.vb` and `2016/Case.RevClouds/Case.RevClouds/Data/clsSettings.vb` 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 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.
Duplicated block (29 lines × 2) 2015/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb:83— 2015/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb:83-111 | 2016/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb:83-111 — before extracting anything, compare `2015/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb` and `2016/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 260 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 (29 lines × 2) 2017/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb:84— 2017/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb:84-112 | 2018/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb:84-112 — before extracting anything, compare `2017/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb` and `2018/Case.BasicReporting/Case.BasicReporting/Forms/form_Main.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 260 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 (27 lines × 8) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:404— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:404-430 | 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:853-879 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:404-430 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:853-879 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:404-430 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:853-879 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:404-430 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:853-879 — before extracting anything, compare `2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb` and `2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 92 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the 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 (27 lines × 8) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:1018— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:1018-1044 | 2015/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsExcel.vb:391-417 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:1018-1044 | 2016/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsExcel.vb:391-417 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:1018-1044 | 2017/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsExcel.vb:391-417 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:1018-1044 | 2018/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsExcel.vb:391-417 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 610 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 (26 lines × 3) 2015/Case.ViewCreator/Case.ViewCreator/Classes/Entry/cmd.cs:29— 2015/Case.ViewCreator/Case.ViewCreator/Classes/Entry/cmd.cs:29-54 | 2016/Case.ViewCreator/Case.ViewCreator/Classes/Entry/cmd.cs:29-54 | 2017/Case.ViewCreator/Case.ViewCreator/Classes/Entry/cmd.cs:29-54 — before extracting anything, compare `2015/Case.ViewCreator/Case.ViewCreator/Classes/Entry/cmd.cs` and `2016/Case.ViewCreator/Case.ViewCreator/Classes/Entry/cmd.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. 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 (26 lines × 3) 2015/Case.ImageToDraftingView/Case.ImageToDraftingView/Forms/form_Main.vb:232— 2015/Case.ImageToDraftingView/Case.ImageToDraftingView/Forms/form_Main.vb:232-257 | 2016/Case.ImageToDraftingView/Case.ImageToDraftingView/Forms/form_Main.vb:232-257 | 2017/Case.ImageToDraftingView/Case.ImageToDraftingView/Forms/form_Main.vb:232-257 — before extracting anything, compare `2015/Case.ImageToDraftingView/Case.ImageToDraftingView/Forms/form_Main.vb` and `2016/Case.ImageToDraftingView/Case.ImageToDraftingView/Forms/form_Main.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 155 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 (23 lines × 3) 2015/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb:163— 2015/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb:163-185 | 2016/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb:163-185 | 2017/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb:163-185 — before extracting anything, compare `2015/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb` and `2016/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 364 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 (23 lines × 3) Case.AppsRibbon.2017/Entry/AppMain.vb:277— Case.AppsRibbon.2017/Entry/AppMain.vb:277-299 | Case.AppsRibbon.2018/Entry/AppMain.vb:277-299 | Case.AppsRibbon/Entry/AppMain.vb:277-299 — before extracting anything, compare `Case.AppsRibbon.2017/Entry/AppMain.vb` and `Case.AppsRibbon.2018/Entry/AppMain.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 148 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 (18 lines × 2) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb:21— 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb:21-38 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb:21-38 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 149 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 (18 lines × 2) 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb:21— 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb:21-38 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb:21-38 — before extracting anything, compare `2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb` and `2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 149 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 (14 lines × 2) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:127— 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:127-140 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:127-140 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 317 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 (14 lines × 2) 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:127— 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:127-140 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:127-140 — before extracting anything, compare `2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb` and `2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 317 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 (13 lines × 2) 2015/Case.Export.Families/Case.Export.Families/Forms/form_Familes.vb:323— 2015/Case.Export.Families/Case.Export.Families/Forms/form_Familes.vb:323-335 | 2016/Case.Export.Families/Case.Export.Families/Forms/form_Familes.vb:323-335 — before extracting anything, compare `2015/Case.Export.Families/Case.Export.Families/Forms/form_Familes.vb` and `2016/Case.Export.Families/Case.Export.Families/Forms/form_Familes.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 93 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 (13 lines × 2) 2017/Case.Export.Families/Case.Export.Families/Forms/form_Familes.vb:323— 2017/Case.Export.Families/Case.Export.Families/Forms/form_Familes.vb:323-335 | 2018/Case.Export.Families/Case.Export.Families/Forms/form_Familes.vb:317-329 — before extracting anything, compare `2017/Case.Export.Families/Case.Export.Families/Forms/form_Familes.vb` and `2018/Case.Export.Families/Case.Export.Families/Forms/form_Familes.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 93 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 (68 lines × 4) 2015/Case.Directionality/Case.Directionality/Data/clsSettings.vb:20— 2015/Case.Directionality/Case.Directionality/Data/clsSettings.vb:20-87 | 2016/Case.Directionality/Case.Directionality/Data/clsSettings.vb:20-87 | 2017/Case.Directionality/Case.Directionality/Data/clsSettings.vb:20-87 | 2018/Case.Directionality/Case.Directionality/Data/clsSettings.vb:20-87 — before extracting anything, compare `2015/Case.Directionality/Case.Directionality/Data/clsSettings.vb` and `2016/Case.Directionality/Case.Directionality/Data/clsSettings.vb` 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.
Duplicated block (68 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsView.vb:25— 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsView.vb:25-92 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsView.vb:25-92 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsView.vb:25-92 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsView.vb:25-92 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsView.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsView.vb` 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.
Duplicated block (114 lines × 4) 2015/Case.FreeBenchmarking/Case.FreeBenchmarking/Forms/form_Main.vb:11— 2015/Case.FreeBenchmarking/Case.FreeBenchmarking/Forms/form_Main.vb:11-124 | 2016/Case.FreeBenchmarking/Case.FreeBenchmarking/Forms/form_Main.vb:11-124 | 2017/Case.FreeBenchmarking/Case.FreeBenchmarking/Forms/form_Main.vb:11-124 | 2018/Case.FreeBenchmarking/Case.FreeBenchmarking/Forms/form_Main.vb:11-124 — before extracting anything, compare `2015/Case.FreeBenchmarking/Case.FreeBenchmarking/Forms/form_Main.vb` and `2016/Case.FreeBenchmarking/Case.FreeBenchmarking/Forms/form_Main.vb` 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.
Duplicated block (114 lines × 4) 2015/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:114— 2015/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:114-227 | 2016/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:114-227 | 2017/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:114-227 | 2018/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb:114-227 — before extracting anything, compare `2015/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb` and `2016/Case.Subs.SuperTag/Case.Subs.SuperTag/UI/Form_Main.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 264 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 (98 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/My Project/MyExtensions/MyWpfExtension.vb:20— 2015/Case.Subs.Xyz/Case.Subs.Xyz/My Project/MyExtensions/MyWpfExtension.vb:20-117 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/My Project/MyExtensions/MyWpfExtension.vb:20-117 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/My Project/MyExtensions/MyWpfExtension.vb:20-117 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/My Project/MyExtensions/MyWpfExtension.vb:20-117 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/My Project/MyExtensions/MyWpfExtension.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/My Project/MyExtensions/MyWpfExtension.vb` 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.
Duplicated block (98 lines × 4) 2015/Case.ViewportReporting/Case.ViewportReporting/My Project/MyExtensions/MyWpfExtension.vb:20— 2015/Case.ViewportReporting/Case.ViewportReporting/My Project/MyExtensions/MyWpfExtension.vb:20-117 | 2016/Case.ViewportReporting/Case.ViewportReporting/My Project/MyExtensions/MyWpfExtension.vb:20-117 | 2017/Case.ViewportReporting/Case.ViewportReporting/My Project/MyExtensions/MyWpfExtension.vb:20-117 | 2018/Case.ViewportReporting/Case.ViewportReporting/My Project/MyExtensions/MyWpfExtension.vb:20-117 — before extracting anything, compare `2015/Case.ViewportReporting/Case.ViewportReporting/My Project/MyExtensions/MyWpfExtension.vb` and `2016/Case.ViewportReporting/Case.ViewportReporting/My Project/MyExtensions/MyWpfExtension.vb` 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.
Duplicated block (5 lines × 2) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:440— 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:440-444 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:440-444 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 267 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 (5 lines × 2) 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:440— 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:440-444 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:440-444 — before extracting anything, compare `2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb` and `2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 267 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.
form_Main.buttonOk_Click (cyclomatic 20) REDACTED:66— form_Main.buttonOk_Click has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Build failed — The target solution did not build cleanly (errors: 4587), which caps Solution Shape at 3/10 — the most basic shape signal is that it compiles. First errors: BC30002: Type 'Document' is not defined.; BC30002: Type 'Category' is not defined.; BC30002: Type 'Element' is not defined.; BC30002: Type 'ElementId' is not defined.; BC30002: Type 'RevitLinkType' is not defined..
form_Main.buttonOk_Click (cognitive 69) REDACTED:66— form_Main.buttonOk_Click has cognitive complexity 69 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
form_Main.ButtonOk_Click (cognitive 29) 2018/Case.HiddenParameterToParameter/Case.HiddenParameterToParameter/UI/form_Main.vb:107— form_Main.ButtonOk_Click has cognitive complexity 29 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
CmdMain.Execute (cognitive 16) 2018/Case.RoomInsertionPoint/Case.RoomInsertionPoint/Entry/CmdMain.vb:23— CmdMain.Execute has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D4 · Code Duplication· Near-duplicate member family (25 members, 34 shared lines) · ×1
Near-duplicate member family (25 members, 34 shared lines) REDACTED:110— REDACTED:110-150 | REDACTED:110-150 | REDACTED:110-151 | REDACTED:110-151 | REDACTED:110-148 | REDACTED:110-150 | REDACTED:110-150 | REDACTED:110-150 | REDACTED:110-150 | REDACTED:110-150 | REDACTED:110-151 | REDACTED:110-151 | REDACTED:110-148 | REDACTED:110-150 | REDACTED:110-150 | REDACTED:110-150 | REDACTED:110-150 | REDACTED:110-150 | REDACTED:110-151 | REDACTED:110-151 | REDACTED:110-148 | REDACTED:110-150 | REDACTED:110-150 | REDACTED:110-150 | REDACTED:110-150 — These 25 members are variants of one another: a block of 34 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 25 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 25 times.
D4 · Code Duplication· Near-duplicate member family (12 members, 22 shared lines) · ×1
Near-duplicate member family (12 members, 22 shared lines) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:38— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:38-88 | 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:36-99 | 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:431-513 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:38-88 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:36-99 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:431-513 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:38-88 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:36-99 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:431-513 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:38-88 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:36-99 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:431-513 — These 12 members are variants of one another: a block of 22 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 12 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 12 times.
D4 · Code Duplication· Near-duplicate member family (8 members, 66 shared lines) · ×1
Near-duplicate member family (8 members, 66 shared lines) 2015/Case.RoomInsertionPoint/Case.RoomInsertionPoint/Data/clsRoom.vb:266— 2015/Case.RoomInsertionPoint/Case.RoomInsertionPoint/Data/clsRoom.vb:266-338 | 2015/Case.RoomInsertionPoint/Case.RoomInsertionPoint/Data/clsRoom.vb:348-424 | 2016/Case.RoomInsertionPoint/Case.RoomInsertionPoint/Data/clsRoom.vb:266-338 | 2016/Case.RoomInsertionPoint/Case.RoomInsertionPoint/Data/clsRoom.vb:348-424 | 2017/Case.RoomInsertionPoint/Case.RoomInsertionPoint/Data/clsRoom.vb:266-338 | 2017/Case.RoomInsertionPoint/Case.RoomInsertionPoint/Data/clsRoom.vb:348-424 | 2018/Case.RoomInsertionPoint/Case.RoomInsertionPoint/Data/clsRoom.vb:266-338 | 2018/Case.RoomInsertionPoint/Case.RoomInsertionPoint/Data/clsRoom.vb:348-424 — These 8 members are variants of one another: a block of 66 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 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· Near-duplicate member family (8 members, 61 shared lines) · ×1
Near-duplicate member family (8 members, 61 shared lines) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:348— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:348-430 | 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:798-879 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:348-430 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:798-879 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:348-430 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:798-879 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:348-430 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:798-879 — These 8 members are variants of one another: a block of 61 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 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· Near-duplicate member family (8 members, 55 shared lines) · ×1
Near-duplicate member family (8 members, 55 shared lines) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2512.vb:32— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2512.vb:32-281 | 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2513.vb:29-232 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2512.vb:32-281 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2513.vb:29-232 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2512.vb:32-281 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2513.vb:29-232 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2512.vb:32-281 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2513.vb:29-232 — These 8 members are variants of one another: a block of 55 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 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· Near-duplicate member family (8 members, 39 shared lines) · ×1
Near-duplicate member family (8 members, 39 shared lines) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:36— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:36-99 | 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:431-513 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:36-99 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:431-513 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:36-99 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:431-513 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:36-99 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:431-513 — These 8 members are variants of one another: a block of 39 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 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· Near-duplicate member family (8 members, 35 shared lines) · ×1
Near-duplicate member family (8 members, 35 shared lines) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:190— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:190-245 | 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:257-329 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:190-245 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:257-329 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:190-245 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:257-329 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:190-245 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:257-329 — These 8 members are variants of one another: a block of 35 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 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· Near-duplicate member family (8 members, 23 shared lines) · ×1
Near-duplicate member family (8 members, 23 shared lines) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:257— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:257-329 | 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:341-419 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:257-329 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:341-419 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:257-329 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:341-419 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:257-329 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:341-419 — These 8 members are variants of one another: a block of 23 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 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· Near-duplicate member family (4 members, 354 shared lines) · ×1
Near-duplicate member family (4 members, 354 shared lines) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:390— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:390-829 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:390-829 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:390-829 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:390-829 — These 4 members are variants of one another: a block of 354 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 (4 members, 330 shared lines) · ×1
Near-duplicate member family (4 members, 330 shared lines) 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:44— 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:44-412 | 2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:44-412 | 2017/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:44-412 | 2018/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:44-412 — These 4 members are variants of one another: a block of 330 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 (4 members, 223 shared lines) · ×1
Near-duplicate member family (4 members, 223 shared lines) 2015/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb:195— 2015/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb:195-431 | 2016/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb:195-431 | 2017/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb:195-431 | 2018/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb:196-432 — These 4 members are variants of one another: a block of 223 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 (4 members, 192 shared lines) · ×1
Near-duplicate member family (4 members, 192 shared lines) 2015/Case.RoomSync/Case.RoomSync/UI/form_Sync.vb:45— 2015/Case.RoomSync/Case.RoomSync/UI/form_Sync.vb:45-239 | 2016/Case.RoomSync/Case.RoomSync/UI/form_Sync.vb:45-239 | 2017/Case.RoomSync/Case.RoomSync/UI/form_Sync.vb:45-239 | 2018/Case.RoomSync/Case.RoomSync/UI/form_Sync.vb:45-239 — These 4 members are variants of one another: a block of 192 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 (4 members, 157 shared lines) · ×1
Near-duplicate member family (4 members, 157 shared lines) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:54— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:54-237 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:54-237 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:54-237 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:54-237 — These 4 members are variants of one another: a block of 157 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 (4 members, 145 shared lines) · ×1
Near-duplicate member family (4 members, 145 shared lines) REDACTED:238— REDACTED:238-414 | REDACTED:238-414 | REDACTED:238-414 | REDACTED:234-410 — These 4 members are variants of one another: a block of 145 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 (4 members, 111 shared lines) · ×1
Near-duplicate member family (4 members, 111 shared lines) REDACTED:67— REDACTED:67-192 | REDACTED:67-190 | REDACTED:67-190 | REDACTED:62-185 — These 4 members are variants of one another: a block of 111 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 (4 members, 97 shared lines) · ×1
Near-duplicate member family (4 members, 97 shared lines) 2015/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb:248— 2015/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb:248-378 | 2016/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb:248-378 | 2017/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb:248-378 | 2018/Case.LightingLayout/Case.LightingLayout/UI/form_Main.vb:248-378 — These 4 members are variants of one another: a block of 97 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 (4 members, 81 shared lines) · ×1
Near-duplicate member family (4 members, 81 shared lines) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:304— 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:304-407 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:304-407 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:304-407 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:304-407 — These 4 members are variants of one another: a block of 81 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 (4 members, 76 shared lines) · ×1
Near-duplicate member family (4 members, 76 shared lines) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:584— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:584-713 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:584-713 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:584-713 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/UI/form_Sync.vb:584-713 — These 4 members are variants of one another: a block of 76 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 (4 members, 75 shared lines) · ×1
Near-duplicate member family (4 members, 75 shared lines) REDACTED:409— REDACTED:409-490 | REDACTED:409-490 | REDACTED:409-490 | REDACTED:409-490 — These 4 members are variants of one another: a block of 75 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 (4 members, 59 shared lines) · ×1
Near-duplicate member family (4 members, 59 shared lines) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F2.vb:31— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F2.vb:31-105 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F2.vb:31-105 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F2.vb:31-105 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F2.vb:31-105 — These 4 members are variants of one another: a block of 59 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 (4 members, 58 shared lines) · ×1
Near-duplicate member family (4 members, 58 shared lines) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb:51— 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb:51-261 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb:51-261 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb:51-261 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb:51-261 — These 4 members are variants of one another: a block of 58 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 (4 members, 55 shared lines) · ×1
Near-duplicate member family (4 members, 55 shared lines) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsFile.vb:61— 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsFile.vb:61-117 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsFile.vb:61-117 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsFile.vb:61-117 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsFile.vb:61-117 — These 4 members are variants of one another: a block of 55 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 (4 members, 54 shared lines) · ×1
Near-duplicate member family (4 members, 54 shared lines) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:680— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:680-786 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:680-786 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:680-786 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:680-786 — These 4 members are variants of one another: a block of 54 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 (4 members, 46 shared lines) · ×1
Near-duplicate member family (4 members, 46 shared lines) 2015/Case.Export.Families/Case.Export.Families/Forms/form_Familes.vb:53— 2015/Case.Export.Families/Case.Export.Families/Forms/form_Familes.vb:53-188 | 2016/Case.Export.Families/Case.Export.Families/Forms/form_Familes.vb:53-188 | 2017/Case.Export.Families/Case.Export.Families/Forms/form_Familes.vb:53-188 | 2018/Case.Export.Families/Case.Export.Families/Forms/form_Familes.vb:53-188 — These 4 members are variants of one another: a block of 46 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 (4 members, 42 shared lines) · ×1
Near-duplicate member family (4 members, 42 shared lines) 2015/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb:267— 2015/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb:267-354 | 2016/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb:267-354 | 2017/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb:267-354 | 2018/Case.Subs.Renamer/Case.Subs.Renamer/UI/form_Rename.vb:267-354 — 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· Near-duplicate member family (4 members, 30 shared lines) · ×1
Near-duplicate member family (4 members, 30 shared lines) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:149— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:149-199 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:149-199 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:149-199 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:149-199 — These 4 members are variants of one another: a block of 30 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 (4 members, 29 shared lines) · ×1
Near-duplicate member family (4 members, 29 shared lines) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:255— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:255-336 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:255-336 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:255-336 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:255-336 — These 4 members are variants of one another: a block of 29 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 (4 members, 25 shared lines) · ×1
Near-duplicate member family (4 members, 25 shared lines) 2015/Case.Subs.SharedParameters/Case.Subs.SharedParameters/Data/clsSharedParameters.vb:161— 2015/Case.Subs.SharedParameters/Case.Subs.SharedParameters/Data/clsSharedParameters.vb:161-269 | 2016/Case.Subs.SharedParameters/Case.Subs.SharedParameters/Data/clsSharedParameters.vb:161-269 | 2017/Case.Subs.SharedParameters/Case.Subs.SharedParameters/Data/clsSharedParameters.vb:161-269 | 2018/Case.Subs.SharedParameters/Case.Subs.SharedParameters/Data/clsSharedParameters.vb:161-269 — These 4 members are variants of one another: a block of 25 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· Members sharing a duplicated core (44 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (44 members, 50+ identical tokens) 2015/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsSortableBindingList.vb:57— 2015/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsSortableBindingList.vb:57-73 | 2015/Case.LightingLayout/Case.LightingLayout/Data/clsSortableBindingList.vb:58-73 | 2015/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Data/clsSortableBindingList.vb:58-73 | 2015/Case.RevClouds/Case.RevClouds/Data/clsSortableBindingList.vb:58-73 | 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSortableBindingList.vb:56-71 | 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSortableBindingList.vb:56-71 | 2015/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/Data/clsSortableBindingList.vb:56-71 | 2015/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsSortableBindingList.vb:56-71 | 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSortableBindingList.vb:56-71 | 2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/clsSortableBindingList.vb:56-71 | 2015/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsSortableBindingList.vb:56-71 | 2016/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsSortableBindingList.vb:57-73 | 2016/Case.LightingLayout/Case.LightingLayout/Data/clsSortableBindingList.vb:58-73 | 2016/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Data/clsSortableBindingList.vb:58-73 | 2016/Case.RevClouds/Case.RevClouds/Data/clsSortableBindingList.vb:58-73 | 2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSortableBindingList.vb:56-71 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSortableBindingList.vb:56-71 | 2016/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/Data/clsSortableBindingList.vb:56-71 | 2016/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsSortableBindingList.vb:56-71 | 2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSortableBindingList.vb:56-71 | 2016/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/clsSortableBindingList.vb:56-71 | 2016/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsSortableBindingList.vb:56-71 | 2017/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsSortableBindingList.vb:57-73 | 2017/Case.LightingLayout/Case.LightingLayout/Data/clsSortableBindingList.vb:58-73 | 2017/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Data/clsSortableBindingList.vb:58-73 | 2017/Case.RevClouds/Case.RevClouds/Data/clsSortableBindingList.vb:58-73 | 2017/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSortableBindingList.vb:56-71 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSortableBindingList.vb:56-71 | 2017/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/Data/clsSortableBindingList.vb:56-71 | 2017/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsSortableBindingList.vb:56-71 | 2017/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSortableBindingList.vb:56-71 | 2017/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/clsSortableBindingList.vb:56-71 | 2017/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsSortableBindingList.vb:56-71 | 2018/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsSortableBindingList.vb:57-73 | 2018/Case.LightingLayout/Case.LightingLayout/Data/clsSortableBindingList.vb:58-73 | 2018/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Data/clsSortableBindingList.vb:58-73 | 2018/Case.RevClouds/Case.RevClouds/Data/clsSortableBindingList.vb:58-73 | 2018/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSortableBindingList.vb:56-71 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSortableBindingList.vb:56-71 | 2018/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/Data/clsSortableBindingList.vb:56-71 | 2018/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsSortableBindingList.vb:56-71 | 2018/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSortableBindingList.vb:56-71 | 2018/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/clsSortableBindingList.vb:56-71 | 2018/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsSortableBindingList.vb:56-71 — These 44 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 44 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 44 times.
D4 · Code Duplication· Members sharing a duplicated core (20 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (20 members, 50+ identical tokens) 2015/Case.LightingLayout/Case.LightingLayout/Data/clsRoom.vb:241— 2015/Case.LightingLayout/Case.LightingLayout/Data/clsRoom.vb:241-267 | 2015/Case.LightingLayout/Case.LightingLayout/Data/clsSpace.vb:241-267 | 2015/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsRoomTagInfo.vb:186-218 | 2015/Case.RoomInsertionPoint/Case.RoomInsertionPoint/Data/clsRoom.vb:64-90 | 2015/Case.RoomSync/Case.RoomSync/Data/clsRoom.vb:144-170 | 2016/Case.LightingLayout/Case.LightingLayout/Data/clsRoom.vb:241-267 | 2016/Case.LightingLayout/Case.LightingLayout/Data/clsSpace.vb:241-267 | 2016/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsRoomTagInfo.vb:186-218 | 2016/Case.RoomInsertionPoint/Case.RoomInsertionPoint/Data/clsRoom.vb:64-90 | 2016/Case.RoomSync/Case.RoomSync/Data/clsRoom.vb:144-170 | 2017/Case.LightingLayout/Case.LightingLayout/Data/clsRoom.vb:241-267 | 2017/Case.LightingLayout/Case.LightingLayout/Data/clsSpace.vb:241-267 | 2017/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsRoomTagInfo.vb:186-218 | 2017/Case.RoomInsertionPoint/Case.RoomInsertionPoint/Data/clsRoom.vb:64-90 | 2017/Case.RoomSync/Case.RoomSync/Data/clsRoom.vb:144-170 | 2018/Case.LightingLayout/Case.LightingLayout/Data/clsRoom.vb:241-267 | 2018/Case.LightingLayout/Case.LightingLayout/Data/clsSpace.vb:241-267 | 2018/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsRoomTagInfo.vb:186-218 | 2018/Case.RoomInsertionPoint/Case.RoomInsertionPoint/Data/clsRoom.vb:64-90 | 2018/Case.RoomSync/Case.RoomSync/Data/clsRoom.vb:144-170 — These 20 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 20 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 20 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) 2015/Case.ApplySysOrient/Data/clsSettings.cs:121— 2015/Case.ApplySysOrient/Data/clsSettings.cs:121-179 | 2015/Case.ApplySysOrient/Data/clsSettings.cs:185-242 | 2015/Case.ApplySysOrient/Data/clsSettings.cs:248-303 | 2015/Case.ApplySysOrient/Data/clsSettings.cs:309-370 | 2016/Case.ApplySysOrient/Data/clsSettings.cs:121-179 | 2016/Case.ApplySysOrient/Data/clsSettings.cs:185-242 | 2016/Case.ApplySysOrient/Data/clsSettings.cs:248-303 | 2016/Case.ApplySysOrient/Data/clsSettings.cs:309-370 | 2017/Case.ApplySysOrient/Data/clsSettings.cs:121-179 | 2017/Case.ApplySysOrient/Data/clsSettings.cs:185-242 | 2017/Case.ApplySysOrient/Data/clsSettings.cs:248-303 | 2017/Case.ApplySysOrient/Data/clsSettings.cs:309-370 | 2018/Case.ApplySysOrient/Data/clsSettings.cs:121-179 | 2018/Case.ApplySysOrient/Data/clsSettings.cs:185-242 | 2018/Case.ApplySysOrient/Data/clsSettings.cs:248-303 | 2018/Case.ApplySysOrient/Data/clsSettings.cs:309-370 — 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.
Duplicated block (241 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:711— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:711-951 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:711-951 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:711-951 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb:711-951 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsExcel.vb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 610 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 (219 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2512.vb:63— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2512.vb:63-281 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2512.vb:63-281 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2512.vb:63-281 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2512.vb:63-281 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2512.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2512.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 283 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 (196 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:312— 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:312-507 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:312-507 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:312-507 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:312-507 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 604 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 (191 lines × 4) 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:44— 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:44-234 | 2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:44-234 | 2017/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:44-234 | 2018/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb:44-234 — before extracting anything, compare `2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb` and `2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/UI/form_RoomMasses.vb` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 500 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 (176 lines × 4) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/UI/form_ImportMain.xaml.vb:56— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/UI/form_ImportMain.xaml.vb:56-231 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/UI/form_ImportMain.xaml.vb:56-231 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/UI/form_ImportMain.xaml.vb:56-231 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/UI/form_ImportMain.xaml.vb:56-231 — before extracting anything, compare `2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/UI/form_ImportMain.xaml.vb` and `2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/UI/form_ImportMain.xaml.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 299 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 (172 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2513.vb:61— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2513.vb:61-232 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2513.vb:61-232 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2513.vb:61-232 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2513.vb:61-232 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2513.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2513.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 229 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 (158 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:390— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:390-547 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:390-547 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:390-547 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb:390-547 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsRvtCategoryData.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 402 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 (155 lines × 4) REDACTED:40— REDACTED:40-194 | REDACTED:40-194 | REDACTED:40-194 | REDACTED:40-194 — before extracting anything, compare `REDACTED` and `REDACTED` 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 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 (144 lines × 4) 2015/Case.Directionality/Case.Directionality/Data/clsExternalWalls.vb:177— 2015/Case.Directionality/Case.Directionality/Data/clsExternalWalls.vb:177-320 | 2016/Case.Directionality/Case.Directionality/Data/clsExternalWalls.vb:177-320 | 2017/Case.Directionality/Case.Directionality/Data/clsExternalWalls.vb:177-320 | 2018/Case.Directionality/Case.Directionality/Data/clsExternalWalls.vb:177-320 — before extracting anything, compare `2015/Case.Directionality/Case.Directionality/Data/clsExternalWalls.vb` and `2016/Case.Directionality/Case.Directionality/Data/clsExternalWalls.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 252 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 (141 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:160— 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:160-300 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:160-300 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:160-300 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:160-300 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 604 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 (139–140 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:154— 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:154-293 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:154-293 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:154-293 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:154-292 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 317 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 (134 lines × 4) 2015/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb:195— 2015/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb:195-328 | 2016/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb:195-328 | 2017/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb:195-328 | 2018/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb:196-329 — before extracting anything, compare `2015/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb` and `2016/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 364 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 (128 lines × 4) 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:57— 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:57-184 | 2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:57-184 | 2017/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:57-184 | 2018/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb:57-184 — before extracting anything, compare `2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb` and `2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/UI/form_Main.vb` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 323 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 (124 lines × 4) 2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:169— 2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:169-292 | 2016/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:169-292 | 2017/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:169-292 | 2018/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:169-292 — before extracting anything, compare `2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb` and `2016/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 323 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 (122 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb:286— 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb:286-407 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb:286-407 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb:286-407 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb:286-407 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 221 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 (112 lines × 4) 2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:300— 2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:300-411 | 2016/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:300-411 | 2017/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:300-411 | 2018/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb:300-411 — before extracting anything, compare `2015/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb` and `2016/Case.Subs.Worksets/Case.Subs.Worksets/UI/MultiSelectTreeview.vb` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 323 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 (109 lines × 4) 2015/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/UI/form_Main.vb:69— 2015/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/UI/form_Main.vb:69-177 | 2016/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/UI/form_Main.vb:69-177 | 2017/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/UI/form_Main.vb:69-177 | 2018/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/UI/form_Main.vb:69-177 — before extracting anything, compare `2015/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/UI/form_Main.vb` and `2016/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/UI/form_Main.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 214 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 (108 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2514.vb:39— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2514.vb:39-146 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2514.vb:39-146 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2514.vb:39-146 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2514.vb:39-146 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2514.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2514.vb` as WHOLE FILES: 98% 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. Read the line range as the matched WINDOW rather than a finished unit: at `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2514.vb:39` 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 (103 lines × 4) 2015/Case.RoomSync/Case.RoomSync/UI/form_Sync.vb:66— 2015/Case.RoomSync/Case.RoomSync/UI/form_Sync.vb:66-168 | 2016/Case.RoomSync/Case.RoomSync/UI/form_Sync.vb:66-168 | 2017/Case.RoomSync/Case.RoomSync/UI/form_Sync.vb:66-168 | 2018/Case.RoomSync/Case.RoomSync/UI/form_Sync.vb:66-168 — before extracting anything, compare `2015/Case.RoomSync/Case.RoomSync/UI/form_Sync.vb` and `2016/Case.RoomSync/Case.RoomSync/UI/form_Sync.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 242 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 (101 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:517— 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:517-617 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:517-617 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:517-617 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:517-617 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 604 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 (100 lines × 4) 2015/Case.MultiViewDuplicate/Case.MultiViewDuplicate/UI/form_Main.vb:69— 2015/Case.MultiViewDuplicate/Case.MultiViewDuplicate/UI/form_Main.vb:69-168 | 2016/Case.MultiViewDuplicate/Case.MultiViewDuplicate/UI/form_Main.vb:69-168 | 2017/Case.MultiViewDuplicate/Case.MultiViewDuplicate/UI/form_Main.vb:69-168 | 2018/Case.MultiViewDuplicate/Case.MultiViewDuplicate/UI/form_Main.vb:69-168 — before extracting anything, compare `2015/Case.MultiViewDuplicate/Case.MultiViewDuplicate/UI/form_Main.vb` and `2016/Case.MultiViewDuplicate/Case.MultiViewDuplicate/UI/form_Main.vb` as WHOLE FILES: this scan already matched 3 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. 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 (90 lines × 4) 2015/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb:185— 2015/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb:185-274 | 2016/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb:185-274 | 2017/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb:185-274 | 2018/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb:185-274 — before extracting anything, compare `2015/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb` and `2016/Case.LightingLayout/Case.LightingLayout/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 260 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 (88 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:59— 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:59-146 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:59-146 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:59-146 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb:59-146 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsReportingData.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 604 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 (87 lines × 4) 2015/Case.Directionality/Case.Directionality/UI/form_Main.vb:131— 2015/Case.Directionality/Case.Directionality/UI/form_Main.vb:131-217 | 2016/Case.Directionality/Case.Directionality/UI/form_Main.vb:131-217 | 2017/Case.Directionality/Case.Directionality/UI/form_Main.vb:131-217 | 2018/Case.Directionality/Case.Directionality/UI/form_Main.vb:131-217 — before extracting anything, compare `2015/Case.Directionality/Case.Directionality/UI/form_Main.vb` and `2016/Case.Directionality/Case.Directionality/UI/form_Main.vb` 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 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.
Duplicated block (86 lines × 4) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb:213— 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb:213-298 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb:213-298 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb:213-298 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb:213-298 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 274 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 (82 lines × 4) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:798— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:798-879 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:798-879 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:798-879 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:798-879 — before extracting anything, compare `2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb` and `2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 685 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 (81 lines × 4) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:315— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:315-395 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:315-395 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:315-395 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:315-395 — before extracting anything, compare `2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb` and `2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 257 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 (79 lines × 4) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:341— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:341-419 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:341-419 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:341-419 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:341-419 — before extracting anything, compare `2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb` and `2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 685 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 (73 lines × 4) 2015/Case.Subs.Linestyles/Case.Subs.Linestyles/Data/clsSettings.vb:130— 2015/Case.Subs.Linestyles/Case.Subs.Linestyles/Data/clsSettings.vb:130-202 | 2016/Case.Subs.Linestyles/Case.Subs.Linestyles/Data/clsSettings.vb:130-202 | 2017/Case.Subs.Linestyles/Case.Subs.Linestyles/Data/clsSettings.vb:130-202 | 2018/Case.Subs.Linestyles/Case.Subs.Linestyles/Data/clsSettings.vb:130-202 — before extracting anything, compare `2015/Case.Subs.Linestyles/Case.Subs.Linestyles/Data/clsSettings.vb` and `2016/Case.Subs.Linestyles/Case.Subs.Linestyles/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 4 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. 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 (43 lines × 8) 2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:591— 2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:591-633 | 2015/Case.ViewTemplates/Case.ViewTemplates/UI/form_Main.vb:199-241 | 2016/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:591-633 | 2016/Case.ViewTemplates/Case.ViewTemplates/UI/form_Main.vb:199-241 | 2017/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:591-633 | 2017/Case.ViewTemplates/Case.ViewTemplates/UI/form_Main.vb:199-241 | 2018/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:591-633 | 2018/Case.ViewTemplates/Case.ViewTemplates/UI/form_Main.vb:199-241 — before extracting anything, compare `2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb` and `2015/Case.ViewTemplates/Case.ViewTemplates/UI/form_Main.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 62 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 (38 lines × 8) 2015/Case.RoomInsertionPoint/Case.RoomInsertionPoint/Data/clsRoom.vb:301— 2015/Case.RoomInsertionPoint/Case.RoomInsertionPoint/Data/clsRoom.vb:301-338 | 2015/Case.RoomInsertionPoint/Case.RoomInsertionPoint/Data/clsRoom.vb:387-424 | 2016/Case.RoomInsertionPoint/Case.RoomInsertionPoint/Data/clsRoom.vb:301-338 | 2016/Case.RoomInsertionPoint/Case.RoomInsertionPoint/Data/clsRoom.vb:387-424 | 2017/Case.RoomInsertionPoint/Case.RoomInsertionPoint/Data/clsRoom.vb:301-338 | 2017/Case.RoomInsertionPoint/Case.RoomInsertionPoint/Data/clsRoom.vb:387-424 | 2018/Case.RoomInsertionPoint/Case.RoomInsertionPoint/Data/clsRoom.vb:301-338 | 2018/Case.RoomInsertionPoint/Case.RoomInsertionPoint/Data/clsRoom.vb:387-424 — before extracting anything, compare `2015/Case.RoomInsertionPoint/Case.RoomInsertionPoint/Data/clsRoom.vb` and `2016/Case.RoomInsertionPoint/Case.RoomInsertionPoint/Data/clsRoom.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 95 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 (40 lines × 3) 2015/Case.LightingLayout/Case.LightingLayout/Entry/CmdMain.vb:55— 2015/Case.LightingLayout/Case.LightingLayout/Entry/CmdMain.vb:55-94 | 2016/Case.LightingLayout/Case.LightingLayout/Entry/CmdMain.vb:55-94 | 2017/Case.LightingLayout/Case.LightingLayout/Entry/CmdMain.vb:55-94 — before extracting anything, compare `2015/Case.LightingLayout/Case.LightingLayout/Entry/CmdMain.vb` and `2016/Case.LightingLayout/Case.LightingLayout/Entry/CmdMain.vb` as WHOLE FILES: 97% 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. Read the line range as the matched WINDOW rather than a finished unit: at `2015/Case.LightingLayout/Case.LightingLayout/Entry/CmdMain.vb:55` 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 (37–38 lines × 8) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb:160— 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb:160-196 | 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb:255-292 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb:160-196 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb:255-292 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb:160-196 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb:255-292 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb:160-196 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb:255-292 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePoint.xaml.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 274 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 (36–37 lines × 8) 2015/Case.LineChanger/Case.LineChanger/Data/clsSettings.vb:151— 2015/Case.LineChanger/Case.LineChanger/Data/clsSettings.vb:151-186 | 2015/Case.Subs.Linestyles/Case.Subs.Linestyles/Data/clsSettings.vb:240-276 | 2016/Case.LineChanger/Case.LineChanger/Data/clsSettings.vb:151-186 | 2016/Case.Subs.Linestyles/Case.Subs.Linestyles/Data/clsSettings.vb:240-276 | 2017/Case.LineChanger/Case.LineChanger/Data/clsSettings.vb:151-186 | 2017/Case.Subs.Linestyles/Case.Subs.Linestyles/Data/clsSettings.vb:240-276 | 2018/Case.LineChanger/Case.LineChanger/Data/clsSettings.vb:151-186 | 2018/Case.Subs.Linestyles/Case.Subs.Linestyles/Data/clsSettings.vb:240-276 — before extracting anything, compare `2015/Case.LineChanger/Case.LineChanger/Data/clsSettings.vb` and `2016/Case.LineChanger/Case.LineChanger/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 126 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–36 lines × 2) 2018/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/Entry/A330EB8E54CA46B3A28E41DA9E77F9F6.vb:25— 2018/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/Entry/A330EB8E54CA46B3A28E41DA9E77F9F6.vb:25-58 | 2018/Case.Subs.SharedParameters/Case.Subs.SharedParameters/Entry/BC456E773F0B4A04A764DE16ECDA69C9.vb:25-60 — before extracting anything, compare `2018/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/Entry/A330EB8E54CA46B3A28E41DA9E77F9F6.vb` and `2018/Case.Subs.SharedParameters/Case.Subs.SharedParameters/Entry/BC456E773F0B4A04A764DE16ECDA69C9.vb` 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.
Duplicated block (33–34 lines × 22) REDACTED:116— REDACTED:116-148 | REDACTED:116-148 | REDACTED:116-149 | REDACTED:116-149 | REDACTED:116-148 | REDACTED:116-148 | REDACTED:116-148 | REDACTED:116-148 | REDACTED:116-148 | REDACTED:116-149 | REDACTED:116-149 | REDACTED:116-148 | REDACTED:116-148 | REDACTED:116-148 | REDACTED:116-148 | REDACTED:116-148 | REDACTED:116-149 | REDACTED:116-149 | REDACTED:116-148 | REDACTED:116-148 | REDACTED:116-148 | REDACTED:116-148 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 5 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. 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) 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Entry/D4E12C09AFB84891A24F3AF186B13DD3.vb:24— 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Entry/D4E12C09AFB84891A24F3AF186B13DD3.vb:24-57 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Entry/D4E12C09AFB84891A24F3AF186B13DD3.vb:24-57 — before extracting anything, compare `2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Entry/D4E12C09AFB84891A24F3AF186B13DD3.vb` and `2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Entry/D4E12C09AFB84891A24F3AF186B13DD3.vb` 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.
Duplicated block (32–33 lines × 8) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2512.vb:42— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2512.vb:42-73 | 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2513.vb:39-71 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2512.vb:42-73 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2513.vb:39-71 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2512.vb:42-73 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2513.vb:39-71 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2512.vb:42-73 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2513.vb:39-71 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2512.vb` and `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2513.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 79 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the 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 `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2512.vb:42` 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 (33 lines × 3) REDACTED:115— REDACTED:115-147 | REDACTED:115-147 | REDACTED:115-147 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 121 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 (31 lines × 3) 2015/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Forms/form_Main.vb:229— 2015/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Forms/form_Main.vb:229-259 | 2016/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Forms/form_Main.vb:229-259 | 2017/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Forms/form_Main.vb:229-259 — before extracting anything, compare `2015/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Forms/form_Main.vb` and `2016/Case.DeleteViewsAndPurge/Case.DeleteViewsAndPurge/Forms/form_Main.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 137 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 (30 lines × 8) 2015/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:396— 2015/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:396-425 | 2015/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:453-482 | 2016/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:396-425 | 2016/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:453-482 | 2017/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:396-425 | 2017/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:453-482 | 2018/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb:391-420 | 2018/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb:453-482 — before extracting anything, compare `2015/Case.SharedParameters/Case.SharedParameters/UI/form_Main.vb` and `2015/Case.Subs.SharedParameters/Case.Subs.SharedParameters/UI/form_Main.vb` 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.
Duplicated block (28–30 lines × 8) 2015/Case.RoomInsertionPoint/Case.RoomInsertionPoint/Data/clsRoom.vb:266— 2015/Case.RoomInsertionPoint/Case.RoomInsertionPoint/Data/clsRoom.vb:266-293 | 2015/Case.RoomInsertionPoint/Case.RoomInsertionPoint/Data/clsRoom.vb:348-377 | 2016/Case.RoomInsertionPoint/Case.RoomInsertionPoint/Data/clsRoom.vb:266-293 | 2016/Case.RoomInsertionPoint/Case.RoomInsertionPoint/Data/clsRoom.vb:348-377 | 2017/Case.RoomInsertionPoint/Case.RoomInsertionPoint/Data/clsRoom.vb:266-293 | 2017/Case.RoomInsertionPoint/Case.RoomInsertionPoint/Data/clsRoom.vb:348-377 | 2018/Case.RoomInsertionPoint/Case.RoomInsertionPoint/Data/clsRoom.vb:266-293 | 2018/Case.RoomInsertionPoint/Case.RoomInsertionPoint/Data/clsRoom.vb:348-377 — before extracting anything, compare `2015/Case.RoomInsertionPoint/Case.RoomInsertionPoint/Data/clsRoom.vb` and `2016/Case.RoomInsertionPoint/Case.RoomInsertionPoint/Data/clsRoom.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 95 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 `2015/Case.RoomInsertionPoint/Case.RoomInsertionPoint/Data/clsRoom.vb: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. 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 (28 lines × 2) 2016/Case.Navis2BCF/Case.Navis2BCF/CASERibbon.cs:36— 2016/Case.Navis2BCF/Case.Navis2BCF/CASERibbon.cs:36-63 | 2017/Case.Navis2BCF/Case.Navis2BCF/CASERibbon.cs:36-63 — before extracting anything, compare `2016/Case.Navis2BCF/Case.Navis2BCF/CASERibbon.cs` and `2017/Case.Navis2BCF/Case.Navis2BCF/CASERibbon.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 79 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 (25–29 lines × 16) 2015/Case.DimensionOverrides/Case.DimensionOverrides/Entry/CmdMain.cs:37— 2015/Case.DimensionOverrides/Case.DimensionOverrides/Entry/CmdMain.cs:37-62 | 2015/Case.FamilySubcategories/Case.FamilySubcategories/Entry/CmdMain.cs:32-56 | 2015/Case.ObjectStyles/Case.ObjectStyles/Entry/CmdMain.cs:36-64 | 2015/Case.ReportGroupsByView/Case.ReportGroupsByView/Entry/CmdMain.cs:36-64 | 2016/Case.DimensionOverrides/Case.DimensionOverrides/Entry/CmdMain.cs:37-62 | 2016/Case.FamilySubcategories/Case.FamilySubcategories/Entry/CmdMain.cs:32-56 | 2016/Case.ObjectStyles/Case.ObjectStyles/Entry/CmdMain.cs:36-64 | 2016/Case.ReportGroupsByView/Case.ReportGroupsByView/Entry/CmdMain.cs:36-64 | 2017/Case.DimensionOverrides/Case.DimensionOverrides/Entry/CmdMain.cs:37-62 | 2017/Case.FamilySubcategories/Case.FamilySubcategories/Entry/CmdMain.cs:32-56 | 2017/Case.ObjectStyles/Case.ObjectStyles/Entry/CmdMain.cs:36-64 | 2017/Case.ReportGroupsByView/Case.ReportGroupsByView/Entry/CmdMain.cs:36-64 | 2018/Case.DimensionOverrides/Case.DimensionOverrides/Entry/CmdMain.cs:32-57 | 2018/Case.FamilySubcategories/Case.FamilySubcategories/Entry/CmdMain.cs:32-56 | 2018/Case.ObjectStyles/Case.ObjectStyles/Entry/CmdMain.cs:36-64 | 2018/Case.ReportGroupsByView/Case.ReportGroupsByView/Entry/CmdMain.cs:36-64 — before extracting anything, compare `2015/Case.DimensionOverrides/Case.DimensionOverrides/Entry/CmdMain.cs` and `2015/Case.ObjectStyles/Case.ObjectStyles/Entry/CmdMain.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 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. Read the line range as the matched WINDOW rather than a finished unit: at `2015/Case.DimensionOverrides/Case.DimensionOverrides/Entry/CmdMain.cs:37` 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 (28–29 lines × 4) 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F1.vb:29— 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F1.vb:29-57 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F2.vb:31-58 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F3.vb:29-56 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F4.vb:29-56 — before extracting anything, compare `2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F1.vb` and `2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F2.vb` 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 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.
Duplicated block (28 lines × 57) REDACTED:102— REDACTED:102-129 | REDACTED:102-129 | REDACTED:102-129 | REDACTED:102-129 | REDACTED:102-129 | REDACTED:102-129 | REDACTED:102-129 | REDACTED:102-129 | REDACTED:102-129 | REDACTED:102-129 | REDACTED:102-129 | REDACTED:102-129 | REDACTED:102-129 | REDACTED:102-129 | REDACTED:102-129 | REDACTED:102-129 | REDACTED:102-129 | REDACTED:108-135 | REDACTED:102-129 | REDACTED:102-129 | REDACTED:102-129 | REDACTED:102-129 | REDACTED:102-129 | REDACTED:102-129 | REDACTED:102-129 | REDACTED:102-129 | REDACTED:102-129 | REDACTED:102-129 | REDACTED:102-129 | REDACTED:102-129 | REDACTED:102-129 | REDACTED:102-129 | REDACTED:102-129 | REDACTED:102-129 | REDACTED:102-129 | REDACTED:102-129 | REDACTED:108-135 | REDACTED:102-129 | REDACTED:102-129 | REDACTED:102-129 | REDACTED:102-129 | REDACTED:102-129 | REDACTED:102-129 | REDACTED:102-129 | REDACTED:102-129 | REDACTED:102-129 | REDACTED:102-129 | REDACTED:102-129 | REDACTED:102-129 | REDACTED:102-129 | REDACTED:102-129 | REDACTED:102-129 | REDACTED:102-129 | REDACTED:102-129 | REDACTED:102-129 | REDACTED:108-135 | REDACTED:102-129 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 70 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 (28 lines × 3) Case.AppsRibbon.2017/Entry/AppMain.vb:108— Case.AppsRibbon.2017/Entry/AppMain.vb:108-135 | Case.AppsRibbon.2018/Entry/AppMain.vb:108-135 | Case.AppsRibbon/Entry/AppMain.vb:108-135 — before extracting anything, compare `Case.AppsRibbon.2017/Entry/AppMain.vb` and `Case.AppsRibbon.2018/Entry/AppMain.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 148 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 (24–27 lines × 25) REDACTED:21— REDACTED:21-47 | REDACTED:21-47 | REDACTED:21-47 | REDACTED:21-47 | REDACTED:25-48 | REDACTED:21-47 | REDACTED:21-47 | REDACTED:21-47 | REDACTED:21-47 | REDACTED:21-47 | REDACTED:21-47 | REDACTED:21-47 | REDACTED:25-48 | REDACTED:21-47 | REDACTED:21-47 | REDACTED:21-47 | REDACTED:21-47 | REDACTED:21-47 | REDACTED:21-47 | REDACTED:21-47 | REDACTED:25-48 | REDACTED:21-47 | REDACTED:21-47 | REDACTED:21-47 | REDACTED:21-47 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 5 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. 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 (21–27 lines × 20) 2015/Case.LightingLayout/Case.LightingLayout/Data/clsRoom.vb:244— 2015/Case.LightingLayout/Case.LightingLayout/Data/clsRoom.vb:244-264 | 2015/Case.LightingLayout/Case.LightingLayout/Data/clsSpace.vb:244-264 | 2015/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsRoomTagInfo.vb:189-215 | 2015/Case.RoomInsertionPoint/Case.RoomInsertionPoint/Data/clsRoom.vb:67-87 | 2015/Case.RoomSync/Case.RoomSync/Data/clsRoom.vb:144-170 | 2016/Case.LightingLayout/Case.LightingLayout/Data/clsRoom.vb:244-264 | 2016/Case.LightingLayout/Case.LightingLayout/Data/clsSpace.vb:244-264 | 2016/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsRoomTagInfo.vb:189-215 | 2016/Case.RoomInsertionPoint/Case.RoomInsertionPoint/Data/clsRoom.vb:67-87 | 2016/Case.RoomSync/Case.RoomSync/Data/clsRoom.vb:144-170 | 2017/Case.LightingLayout/Case.LightingLayout/Data/clsRoom.vb:244-264 | 2017/Case.LightingLayout/Case.LightingLayout/Data/clsSpace.vb:244-264 | 2017/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsRoomTagInfo.vb:189-215 | 2017/Case.RoomInsertionPoint/Case.RoomInsertionPoint/Data/clsRoom.vb:67-87 | 2017/Case.RoomSync/Case.RoomSync/Data/clsRoom.vb:144-170 | 2018/Case.LightingLayout/Case.LightingLayout/Data/clsRoom.vb:244-264 | 2018/Case.LightingLayout/Case.LightingLayout/Data/clsSpace.vb:244-264 | 2018/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsRoomTagInfo.vb:189-215 | 2018/Case.RoomInsertionPoint/Case.RoomInsertionPoint/Data/clsRoom.vb:67-87 | 2018/Case.RoomSync/Case.RoomSync/Data/clsRoom.vb:144-170 — before extracting anything, compare `2015/Case.LightingLayout/Case.LightingLayout/Data/clsRoom.vb` and `2016/Case.LightingLayout/Case.LightingLayout/Data/clsRoom.vb` 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.
Duplicated block (27 lines × 3) Case.AppsRibbon.2017/Entry/AppMain.vb:356— Case.AppsRibbon.2017/Entry/AppMain.vb:356-382 | Case.AppsRibbon.2018/Entry/AppMain.vb:356-382 | Case.AppsRibbon/Entry/AppMain.vb:356-382 — before extracting anything, compare `Case.AppsRibbon.2017/Entry/AppMain.vb` and `Case.AppsRibbon.2018/Entry/AppMain.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 148 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 (27 lines × 2) 2015/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb:509— 2015/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb:509-535 | 2016/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb:509-535 — before extracting anything, compare `2015/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb` and `2016/Case.ExtrudeRoomsToMass/Case.ExtrudeRoomsToMass/UI/form_RoomMasses.vb` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 364 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 (23–24 lines × 25) REDACTED:75— REDACTED:75-98 | REDACTED:75-98 | REDACTED:75-98 | REDACTED:75-98 | REDACTED:76-98 | REDACTED:75-98 | REDACTED:75-98 | REDACTED:75-98 | REDACTED:75-98 | REDACTED:75-98 | REDACTED:75-98 | REDACTED:75-98 | REDACTED:76-98 | REDACTED:75-98 | REDACTED:75-98 | REDACTED:75-98 | REDACTED:75-98 | REDACTED:75-98 | REDACTED:75-98 | REDACTED:75-98 | REDACTED:76-98 | REDACTED:75-98 | REDACTED:75-98 | REDACTED:75-98 | REDACTED:75-98 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 5 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. 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 (23 lines × 12) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2512.vb:245— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2512.vb:245-267 | 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2513.vb:199-221 | 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2514.vb:110-133 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2512.vb:245-267 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2513.vb:199-221 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2514.vb:110-133 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2512.vb:245-267 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2513.vb:199-221 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2514.vb:110-133 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2512.vb:245-267 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2513.vb:199-221 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2514.vb:110-133 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2512.vb` and `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Entry/D9B42C3FEA6F4F9E8E1B62E993AA2513.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 79 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the 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 (22–23 lines × 12) 2015/Case.ApplySysOrient/Data/clsSettings.cs:146— 2015/Case.ApplySysOrient/Data/clsSettings.cs:146-167 | 2015/Case.ApplySysOrient/Data/clsSettings.cs:272-293 | 2015/Case.ApplySysOrient/Data/clsSettings.cs:336-358 | 2016/Case.ApplySysOrient/Data/clsSettings.cs:146-167 | 2016/Case.ApplySysOrient/Data/clsSettings.cs:272-293 | 2016/Case.ApplySysOrient/Data/clsSettings.cs:336-358 | 2017/Case.ApplySysOrient/Data/clsSettings.cs:146-167 | 2017/Case.ApplySysOrient/Data/clsSettings.cs:272-293 | 2017/Case.ApplySysOrient/Data/clsSettings.cs:336-358 | 2018/Case.ApplySysOrient/Data/clsSettings.cs:146-167 | 2018/Case.ApplySysOrient/Data/clsSettings.cs:272-293 | 2018/Case.ApplySysOrient/Data/clsSettings.cs:336-358 — before extracting anything, compare `2015/Case.ApplySysOrient/Data/clsSettings.cs` and `2016/Case.ApplySysOrient/Data/clsSettings.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 288 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 `2015/Case.ApplySysOrient/Data/clsSettings.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 (21–23 lines × 8) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:443— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:443-463 | 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:512-534 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:443-463 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:512-534 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:443-463 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:512-534 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:443-463 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:512-534 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 467 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:534` calls `clsConfig`, `UpdateConfigFile` and `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Config.vb:463` 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 (22 lines × 8) 2015/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnFamData.cs:130— 2015/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnFamData.cs:130-151 | 2015/Case.ObjectStyles/Case.ObjectStyles/Data/mnFamData.cs:136-157 | 2016/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnFamData.cs:130-151 | 2016/Case.ObjectStyles/Case.ObjectStyles/Data/mnFamData.cs:136-157 | 2017/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnFamData.cs:130-151 | 2017/Case.ObjectStyles/Case.ObjectStyles/Data/mnFamData.cs:136-157 | 2018/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnFamData.cs:130-151 | 2018/Case.ObjectStyles/Case.ObjectStyles/Data/mnFamData.cs:136-157 — before extracting anything, compare `2015/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnFamData.cs` and `2016/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnFamData.cs` as WHOLE FILES: this scan already matched 4 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. 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 `2015/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnFamData.cs:130` 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 (22 lines × 57) REDACTED:62— REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 | REDACTED:62-83 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 70 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 (22 lines × 12) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:44— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:44-65 | 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:40-61 | 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:453-474 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:44-65 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:40-61 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:453-474 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:44-65 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:40-61 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:453-474 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:44-65 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:40-61 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:453-474 — before extracting anything, compare `2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb` and `2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 92 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the 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 (21–22 lines × 8) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F1.vb:39— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F1.vb:39-60 | 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F3.vb:39-59 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F1.vb:39-60 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F3.vb:39-59 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F1.vb:39-60 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F3.vb:39-59 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F1.vb:39-60 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F3.vb:39-59 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F1.vb` and `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F3.vb` as WHOLE FILES: this scan already matched 4 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. Read the line range as the matched WINDOW rather than a finished unit: at `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F1.vb:39` 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 (21 lines × 8) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F2.vb:41— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F2.vb:41-61 | 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F4.vb:39-59 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F2.vb:41-61 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F4.vb:39-59 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F2.vb:41-61 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F4.vb:39-59 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F2.vb:41-61 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F4.vb:39-59 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F2.vb` and `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F4.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 123 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the 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 `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F2.vb:41` 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 (22 lines × 3) Case.AppsRibbon.2017/Entry/AppMain.vb:245— Case.AppsRibbon.2017/Entry/AppMain.vb:245-266 | Case.AppsRibbon.2018/Entry/AppMain.vb:245-266 | Case.AppsRibbon/Entry/AppMain.vb:245-266 — before extracting anything, compare `Case.AppsRibbon.2017/Entry/AppMain.vb` and `Case.AppsRibbon.2018/Entry/AppMain.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 148 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 (19–21 lines × 8) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:60— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:60-80 | 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:114-132 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:60-80 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:114-132 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:60-80 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:114-132 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:60-80 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:114-132 — before extracting anything, compare `2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb` and `2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 383 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.
Duplicated block (20–21 lines × 8) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:205— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:205-224 | 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:286-306 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:205-224 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:286-306 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:205-224 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:286-306 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:205-224 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:286-306 — before extracting anything, compare `2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb` and `2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 685 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.
Duplicated block (20 lines × 57) REDACTED:15— REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 | REDACTED:15-34 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 70 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 (19–20 lines × 25) REDACTED:132— REDACTED:132-150 | REDACTED:132-150 | REDACTED:132-151 | REDACTED:132-151 | REDACTED:130-148 | REDACTED:132-150 | REDACTED:132-150 | REDACTED:132-150 | REDACTED:132-150 | REDACTED:132-150 | REDACTED:132-151 | REDACTED:132-151 | REDACTED:130-148 | REDACTED:132-150 | REDACTED:132-150 | REDACTED:132-150 | REDACTED:132-150 | REDACTED:132-150 | REDACTED:132-151 | REDACTED:132-151 | REDACTED:130-148 | REDACTED:132-150 | REDACTED:132-150 | REDACTED:132-150 | REDACTED:132-150 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 5 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. 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:132` 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 × 12) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:257— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:257-274 | 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:326-343 | 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:410-427 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:257-274 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:326-343 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:410-427 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:257-274 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:326-343 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:410-427 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:257-274 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:326-343 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:410-427 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 330 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 (20 lines × 8) REDACTED:100— REDACTED:100-119 | REDACTED:134-153 | REDACTED:100-119 | REDACTED:132-151 | REDACTED:100-119 | REDACTED:132-151 | REDACTED:95-114 | REDACTED:127-146 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 123 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `REDACTED:122` calls `ResetTextPosition` and `REDACTED:125` 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 (19–20 lines × 4) 2018/Case.RoomSync/Case.RoomSync/Entry/CmdMain.vb:24— 2018/Case.RoomSync/Case.RoomSync/Entry/CmdMain.vb:24-42 | 2018/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Entry/AF73BA45B4B94C7585CB3E425D423F5E.vb:39-58 | 2018/Case.Subs.SuperTag/Case.Subs.SuperTag/Entry/A01A0A226EBE4CD89D655C55B997650F.vb:28-46 | 2018/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Entry/CEB749CFCF844AE8B76F40E3EBAA2FF7.vb:25-43 — 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 (18–20 lines × 2) 2015/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:259— 2015/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:259-276 | 2015/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:376-395 — 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 (18–19 lines × 16) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F1.vb:39— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F1.vb:39-57 | 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F2.vb:41-58 | 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F3.vb:39-56 | 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F4.vb:39-56 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F1.vb:39-57 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F2.vb:41-58 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F3.vb:39-56 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F4.vb:39-56 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F1.vb:39-57 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F2.vb:41-58 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F3.vb:39-56 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F4.vb:39-56 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F1.vb:39-57 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F2.vb:41-58 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F3.vb:39-56 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F4.vb:39-56 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F1.vb` and `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F2.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 67 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the 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 `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Entry/DE309158ACE741799F90E9210DEEF5F1.vb:39` 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 (16 lines × 16) 2015/Case.ApplySysOrient/Data/clsSettings.cs:144— 2015/Case.ApplySysOrient/Data/clsSettings.cs:144-159 | 2015/Case.ApplySysOrient/Data/clsSettings.cs:207-222 | 2015/Case.ApplySysOrient/Data/clsSettings.cs:270-285 | 2015/Case.ApplySysOrient/Data/clsSettings.cs:334-349 | 2016/Case.ApplySysOrient/Data/clsSettings.cs:144-159 | 2016/Case.ApplySysOrient/Data/clsSettings.cs:207-222 | 2016/Case.ApplySysOrient/Data/clsSettings.cs:270-285 | 2016/Case.ApplySysOrient/Data/clsSettings.cs:334-349 | 2017/Case.ApplySysOrient/Data/clsSettings.cs:144-159 | 2017/Case.ApplySysOrient/Data/clsSettings.cs:207-222 | 2017/Case.ApplySysOrient/Data/clsSettings.cs:270-285 | 2017/Case.ApplySysOrient/Data/clsSettings.cs:334-349 | 2018/Case.ApplySysOrient/Data/clsSettings.cs:144-159 | 2018/Case.ApplySysOrient/Data/clsSettings.cs:207-222 | 2018/Case.ApplySysOrient/Data/clsSettings.cs:270-285 | 2018/Case.ApplySysOrient/Data/clsSettings.cs:334-349 — before extracting anything, compare `2015/Case.ApplySysOrient/Data/clsSettings.cs` and `2016/Case.ApplySysOrient/Data/clsSettings.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 288 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 (17–19 lines × 8) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:73— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:73-91 | 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:486-502 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:73-91 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:486-502 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:73-91 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:486-502 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:73-91 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:486-502 — before extracting anything, compare `2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb` and `2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 685 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.
Duplicated block (19 lines × 8) 2015/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:251— 2015/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:251-269 | 2015/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:368-388 | 2016/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:251-269 | 2016/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:368-388 | 2017/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:251-269 | 2017/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:368-388 | 2018/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:251-269 | 2018/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb:368-388 — before extracting anything, compare `2015/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb` and `2016/Case.RoomSync/Case.RoomSync/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 245 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.
Duplicated block (16–18 lines × 4) 2018/Case.DimensionOverrides/Case.DimensionOverrides/Entry/CmdMain.cs:21— 2018/Case.DimensionOverrides/Case.DimensionOverrides/Entry/CmdMain.cs:21-36 | 2018/Case.ObjectStyles/Case.ObjectStyles/Entry/CmdMain.cs:23-40 | 2018/Case.ParallelWalls/Case.ParallelWalls/Entry/CmdMain.cs:23-38 | 2018/Case.ReportGroupsByView/Case.ReportGroupsByView/Entry/CmdMain.cs:23-40 — before extracting anything, compare `2018/Case.DimensionOverrides/Case.DimensionOverrides/Entry/CmdMain.cs` and `2018/Case.ObjectStyles/Case.ObjectStyles/Entry/CmdMain.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 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. Read the line range as the matched WINDOW rather than a finished unit: at `2018/Case.DimensionOverrides/Case.DimensionOverrides/Entry/CmdMain.cs:21` 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 (15–17 lines × 25) REDACTED:110— REDACTED:110-126 | REDACTED:110-126 | REDACTED:110-126 | REDACTED:110-126 | REDACTED:110-124 | REDACTED:110-126 | REDACTED:110-126 | REDACTED:110-126 | REDACTED:110-126 | REDACTED:110-126 | REDACTED:110-126 | REDACTED:110-126 | REDACTED:110-124 | REDACTED:110-126 | REDACTED:110-126 | REDACTED:110-126 | REDACTED:110-126 | REDACTED:110-126 | REDACTED:110-126 | REDACTED:110-126 | REDACTED:110-124 | REDACTED:110-126 | REDACTED:110-126 | REDACTED:110-126 | REDACTED:110-126 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 5 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. 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:110` 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. 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, `REDACTED:126` calls `ToString` and `REDACTED:124` 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–17 lines × 16) 2015/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsSortableBindingList.vb:57— 2015/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsSortableBindingList.vb:57-73 | 2015/Case.LightingLayout/Case.LightingLayout/Data/clsSortableBindingList.vb:58-73 | 2015/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Data/clsSortableBindingList.vb:58-73 | 2015/Case.RevClouds/Case.RevClouds/Data/clsSortableBindingList.vb:58-73 | 2016/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsSortableBindingList.vb:57-73 | 2016/Case.LightingLayout/Case.LightingLayout/Data/clsSortableBindingList.vb:58-73 | 2016/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Data/clsSortableBindingList.vb:58-73 | 2016/Case.RevClouds/Case.RevClouds/Data/clsSortableBindingList.vb:58-73 | 2017/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsSortableBindingList.vb:57-73 | 2017/Case.LightingLayout/Case.LightingLayout/Data/clsSortableBindingList.vb:58-73 | 2017/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Data/clsSortableBindingList.vb:58-73 | 2017/Case.RevClouds/Case.RevClouds/Data/clsSortableBindingList.vb:58-73 | 2018/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsSortableBindingList.vb:57-73 | 2018/Case.LightingLayout/Case.LightingLayout/Data/clsSortableBindingList.vb:58-73 | 2018/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Data/clsSortableBindingList.vb:58-73 | 2018/Case.RevClouds/Case.RevClouds/Data/clsSortableBindingList.vb:58-73 — before extracting anything, compare `2015/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsSortableBindingList.vb` and `2015/Case.LightingLayout/Case.LightingLayout/Data/clsSortableBindingList.vb` 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. 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 (16 lines × 12) 2015/Case.Directionality/Case.Directionality/Data/clsPara.vb:162— 2015/Case.Directionality/Case.Directionality/Data/clsPara.vb:162-177 | 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsPara.vb:121-136 | 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsPara.vb:148-163 | 2016/Case.Directionality/Case.Directionality/Data/clsPara.vb:162-177 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsPara.vb:121-136 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsPara.vb:148-163 | 2017/Case.Directionality/Case.Directionality/Data/clsPara.vb:162-177 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsPara.vb:121-136 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsPara.vb:148-163 | 2018/Case.Directionality/Case.Directionality/Data/clsPara.vb:162-177 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsPara.vb:121-136 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsPara.vb:148-163 — before extracting anything, compare `2015/Case.Directionality/Case.Directionality/Data/clsPara.vb` and `2016/Case.Directionality/Case.Directionality/Data/clsPara.vb` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `2015/Case.Directionality/Case.Directionality/Data/clsPara.vb:160` calls `GetParameterValue` and `2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsPara.vb:119` 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 (17 lines × 8) 2015/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Data/clsView.vb:93— 2015/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Data/clsView.vb:93-109 | 2015/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/Data/clsView.vb:81-97 | 2016/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Data/clsView.vb:93-109 | 2016/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/Data/clsView.vb:81-97 | 2017/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Data/clsView.vb:93-109 | 2017/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/Data/clsView.vb:81-97 | 2018/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Data/clsView.vb:93-109 | 2018/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/Data/clsView.vb:81-97 — before extracting anything, compare `2015/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Data/clsView.vb` and `2015/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/Data/clsView.vb` 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 (16 lines × 28) 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSortableBindingList.vb:56— 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSortableBindingList.vb:56-71 | 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSortableBindingList.vb:56-71 | 2015/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/Data/clsSortableBindingList.vb:56-71 | 2015/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsSortableBindingList.vb:56-71 | 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSortableBindingList.vb:56-71 | 2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/clsSortableBindingList.vb:56-71 | 2015/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsSortableBindingList.vb:56-71 | 2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSortableBindingList.vb:56-71 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSortableBindingList.vb:56-71 | 2016/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/Data/clsSortableBindingList.vb:56-71 | 2016/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsSortableBindingList.vb:56-71 | 2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSortableBindingList.vb:56-71 | 2016/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/clsSortableBindingList.vb:56-71 | 2016/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsSortableBindingList.vb:56-71 | 2017/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSortableBindingList.vb:56-71 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSortableBindingList.vb:56-71 | 2017/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/Data/clsSortableBindingList.vb:56-71 | 2017/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsSortableBindingList.vb:56-71 | 2017/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSortableBindingList.vb:56-71 | 2017/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/clsSortableBindingList.vb:56-71 | 2017/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsSortableBindingList.vb:56-71 | 2018/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSortableBindingList.vb:56-71 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSortableBindingList.vb:56-71 | 2018/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/Data/clsSortableBindingList.vb:56-71 | 2018/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsSortableBindingList.vb:56-71 | 2018/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSortableBindingList.vb:56-71 | 2018/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/clsSortableBindingList.vb:56-71 | 2018/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsSortableBindingList.vb:56-71 — before extracting anything, compare `2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSortableBindingList.vb` and `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSortableBindingList.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 36 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 (14–16 lines × 12) 2015/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnFamData.cs:94— 2015/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnFamData.cs:94-109 | 2015/Case.ObjectStyles/Case.ObjectStyles/Data/mnData.cs:51-64 | 2015/Case.ObjectStyles/Case.ObjectStyles/Data/mnFamData.cs:99-112 | 2016/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnFamData.cs:94-109 | 2016/Case.ObjectStyles/Case.ObjectStyles/Data/mnData.cs:51-64 | 2016/Case.ObjectStyles/Case.ObjectStyles/Data/mnFamData.cs:99-112 | 2017/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnFamData.cs:94-109 | 2017/Case.ObjectStyles/Case.ObjectStyles/Data/mnData.cs:51-64 | 2017/Case.ObjectStyles/Case.ObjectStyles/Data/mnFamData.cs:99-112 | 2018/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnFamData.cs:94-109 | 2018/Case.ObjectStyles/Case.ObjectStyles/Data/mnData.cs:51-64 | 2018/Case.ObjectStyles/Case.ObjectStyles/Data/mnFamData.cs:99-112 — before extracting anything, compare `2015/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnFamData.cs` and `2016/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnFamData.cs` as WHOLE FILES: this scan already matched 4 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. 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 (15–16 lines × 8) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:231— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:231-245 | 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:314-329 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:231-245 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:314-329 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:231-245 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:314-329 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:231-245 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:314-329 — before extracting anything, compare `2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb` and `2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 685 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 (11 lines × 12) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:105— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:105-115 | 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:133-143 | 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:161-171 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:105-115 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:133-143 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:161-171 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:105-115 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:133-143 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:161-171 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:105-115 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:133-143 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:161-171 — before extracting anything, compare `2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb` and `2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 257 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 (13–14 lines × 12) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:231— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:231-243 | 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:314-327 | 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:495-508 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:231-243 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:314-327 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:495-508 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:231-243 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:314-327 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:495-508 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:231-243 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:314-327 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:495-508 — before extracting anything, compare `2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb` and `2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 685 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 (11 lines × 8) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:269— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:269-279 | 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:359-369 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:269-279 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:359-369 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:269-279 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:359-369 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:269-279 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:359-369 — before extracting anything, compare `2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb` and `2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 685 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 (12 lines × 12) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:234— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:234-245 | 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:318-329 | 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:408-419 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:234-245 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:318-329 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:408-419 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:234-245 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:318-329 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:408-419 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:234-245 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:318-329 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:408-419 — before extracting anything, compare `2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb` and `2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 685 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 (9–12 lines × 8) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:68— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:68-79 | 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_ModifyViewReference.vb:39-47 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:68-79 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_ModifyViewReference.vb:39-47 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:68-79 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_ModifyViewReference.vb:39-47 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb:68-79 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_ModifyViewReference.vb:39-47 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/UI/form_Find.vb` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 330 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 (12 lines × 3) Case.AppsRibbon.2017/Utility/modUtility.vb:31— Case.AppsRibbon.2017/Utility/modUtility.vb:31-42 | Case.AppsRibbon.2018/Utility/modUtility.vb:31-42 | Case.AppsRibbon/Utility/modUtility.vb:31-42 — before extracting anything, compare `Case.AppsRibbon.2017/Utility/modUtility.vb` and `Case.AppsRibbon.2018/Utility/modUtility.vb` 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 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.
Duplicated block (9–11 lines × 32) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:77— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:77-87 | 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:490-498 | 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:757-765 | 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:93-101 | 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:121-129 | 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:149-157 | 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:177-185 | 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/clsFormUtil.vb:34-44 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:77-87 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:490-498 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:757-765 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:93-101 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:121-129 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:149-157 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:177-185 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/clsFormUtil.vb:34-44 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:77-87 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:490-498 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:757-765 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:93-101 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:121-129 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:149-157 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:177-185 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/clsFormUtil.vb:34-44 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:77-87 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:490-498 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:757-765 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:93-101 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:121-129 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:149-157 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTFamilyMassUtils.vb:177-185 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/clsFormUtil.vb:34-44 — before extracting anything, compare `2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb` and `2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 685 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.
Duplicated block (10 lines × 16) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:234— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:234-243 | 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:318-327 | 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:408-417 | 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:499-508 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:234-243 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:318-327 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:408-417 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:499-508 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:234-243 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:318-327 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:408-417 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:499-508 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:234-243 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:318-327 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:408-417 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:499-508 — before extracting anything, compare `2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb` and `2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 685 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:510` calls `Add` and `2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:419` 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 (9 lines × 16) 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:367— 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:367-375 | 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:405-413 | 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:816-824 | 2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:854-862 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:367-375 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:405-413 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:816-824 | 2016/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:854-862 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:367-375 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:405-413 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:816-824 | 2017/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:854-862 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:367-375 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb:405-413 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:816-824 | 2018/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb:854-862 — before extracting anything, compare `2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTBrepEdgeUtils.vb` and `2015/Case.Subs.OpenNURBS/Case.Subs.OpenNURBS/Data/Translators/RVTCurveUtils.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 92 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the 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 × 8) 2015/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsExcel.vb:299— 2015/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsExcel.vb:299-307 | 2015/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb:382-390 | 2016/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsExcel.vb:299-307 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb:382-390 | 2017/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsExcel.vb:299-307 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb:382-390 | 2018/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsExcel.vb:299-307 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/Classes/clsExcel.vb:382-390 — before extracting anything, compare `2015/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsExcel.vb` and `2016/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsExcel.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 187 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 (5–6 lines × 44) 2015/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsSortableBindingList.vb:57— 2015/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsSortableBindingList.vb:57-62 | 2015/Case.LightingLayout/Case.LightingLayout/Data/clsSortableBindingList.vb:58-62 | 2015/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Data/clsSortableBindingList.vb:58-62 | 2015/Case.RevClouds/Case.RevClouds/Data/clsSortableBindingList.vb:58-62 | 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSortableBindingList.vb:56-60 | 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSortableBindingList.vb:56-60 | 2015/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/Data/clsSortableBindingList.vb:56-60 | 2015/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsSortableBindingList.vb:56-60 | 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSortableBindingList.vb:56-60 | 2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/clsSortableBindingList.vb:56-60 | 2015/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsSortableBindingList.vb:56-60 | 2016/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsSortableBindingList.vb:57-62 | 2016/Case.LightingLayout/Case.LightingLayout/Data/clsSortableBindingList.vb:58-62 | 2016/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Data/clsSortableBindingList.vb:58-62 | 2016/Case.RevClouds/Case.RevClouds/Data/clsSortableBindingList.vb:58-62 | 2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSortableBindingList.vb:56-60 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSortableBindingList.vb:56-60 | 2016/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/Data/clsSortableBindingList.vb:56-60 | 2016/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsSortableBindingList.vb:56-60 | 2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSortableBindingList.vb:56-60 | 2016/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/clsSortableBindingList.vb:56-60 | 2016/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsSortableBindingList.vb:56-60 | 2017/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsSortableBindingList.vb:57-62 | 2017/Case.LightingLayout/Case.LightingLayout/Data/clsSortableBindingList.vb:58-62 | 2017/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Data/clsSortableBindingList.vb:58-62 | 2017/Case.RevClouds/Case.RevClouds/Data/clsSortableBindingList.vb:58-62 | 2017/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSortableBindingList.vb:56-60 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSortableBindingList.vb:56-60 | 2017/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/Data/clsSortableBindingList.vb:56-60 | 2017/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsSortableBindingList.vb:56-60 | 2017/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSortableBindingList.vb:56-60 | 2017/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/clsSortableBindingList.vb:56-60 | 2017/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsSortableBindingList.vb:56-60 | 2018/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsSortableBindingList.vb:57-62 | 2018/Case.LightingLayout/Case.LightingLayout/Data/clsSortableBindingList.vb:58-62 | 2018/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Data/clsSortableBindingList.vb:58-62 | 2018/Case.RevClouds/Case.RevClouds/Data/clsSortableBindingList.vb:58-62 | 2018/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSortableBindingList.vb:56-60 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSortableBindingList.vb:56-60 | 2018/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/Data/clsSortableBindingList.vb:56-60 | 2018/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsSortableBindingList.vb:56-60 | 2018/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSortableBindingList.vb:56-60 | 2018/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/clsSortableBindingList.vb:56-60 | 2018/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsSortableBindingList.vb:56-60 — before extracting anything, compare `2015/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsSortableBindingList.vb` and `2015/Case.LightingLayout/Case.LightingLayout/Data/clsSortableBindingList.vb` 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. 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 (168 lines × 16) 2015/Case.LineChanger/Case.LineChanger/Data/clsPara.vb:20— 2015/Case.LineChanger/Case.LineChanger/Data/clsPara.vb:20-187 | 2015/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsPara.vb:20-187 | 2015/Case.RevClouds/Case.RevClouds/Data/clsPara.vb:20-187 | 2015/Case.Subs.Linestyles/Case.Subs.Linestyles/Data/clsPara.vb:20-187 | 2016/Case.LineChanger/Case.LineChanger/Data/clsPara.vb:20-187 | 2016/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsPara.vb:20-187 | 2016/Case.RevClouds/Case.RevClouds/Data/clsPara.vb:20-187 | 2016/Case.Subs.Linestyles/Case.Subs.Linestyles/Data/clsPara.vb:20-187 | 2017/Case.LineChanger/Case.LineChanger/Data/clsPara.vb:20-187 | 2017/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsPara.vb:20-187 | 2017/Case.RevClouds/Case.RevClouds/Data/clsPara.vb:20-187 | 2017/Case.Subs.Linestyles/Case.Subs.Linestyles/Data/clsPara.vb:20-187 | 2018/Case.LineChanger/Case.LineChanger/Data/clsPara.vb:20-187 | 2018/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsPara.vb:20-187 | 2018/Case.RevClouds/Case.RevClouds/Data/clsPara.vb:20-187 | 2018/Case.Subs.Linestyles/Case.Subs.Linestyles/Data/clsPara.vb:20-187 — before extracting anything, compare `2015/Case.LineChanger/Case.LineChanger/Data/clsPara.vb` and `2015/Case.ModeledRoomTags/Case.ModeledRoomTags/Data/clsPara.vb` as WHOLE FILES: 97% 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 (151 lines × 4) 2015/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Data/clsSettings.vb:36— 2015/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Data/clsSettings.vb:36-186 | 2016/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Data/clsSettings.vb:36-186 | 2017/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Data/clsSettings.vb:36-186 | 2018/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Data/clsSettings.vb:36-186 — before extracting anything, compare `2015/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Data/clsSettings.vb` and `2016/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Data/clsSettings.vb` 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.
Duplicated block (143 lines × 4) 2015/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/Data/clsSettings.vb:56— 2015/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/Data/clsSettings.vb:56-198 | 2016/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/Data/clsSettings.vb:56-198 | 2017/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/Data/clsSettings.vb:56-198 | 2018/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/Data/clsSettings.vb:56-198 — before extracting anything, compare `2015/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/Data/clsSettings.vb` and `2016/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/Data/clsSettings.vb` 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.
Duplicated block (197 lines × 4) 2015/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsSettings.vb:21— 2015/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsSettings.vb:21-217 | 2016/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsSettings.vb:21-217 | 2017/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsSettings.vb:21-217 | 2018/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsSettings.vb:21-217 — before extracting anything, compare `2015/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsSettings.vb` and `2016/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsSettings.vb` 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.
Duplicated block (280 lines × 4) 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsTagInstance.vb:23— 2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsTagInstance.vb:23-302 | 2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsTagInstance.vb:23-302 | 2017/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsTagInstance.vb:23-302 | 2018/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsTagInstance.vb:23-302 — before extracting anything, compare `2015/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsTagInstance.vb` and `2016/Case.Subs.ViewSync/Case.Subs.ViewSync/Data/clsTagInstance.vb` 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.
Duplicated block (121 lines × 4) 2015/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsRvtElemType.vb:19— 2015/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsRvtElemType.vb:19-139 | 2016/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsRvtElemType.vb:19-139 | 2017/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsRvtElemType.vb:19-139 | 2018/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsRvtElemType.vb:19-139 — before extracting anything, compare `2015/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsRvtElemType.vb` and `2016/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsRvtElemType.vb` 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. Read the line range as the matched WINDOW rather than a finished unit: at `2015/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsRvtElemType.vb:19` 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 (178 lines × 4) 2015/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsSettings.vb:24— 2015/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsSettings.vb:24-201 | 2016/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsSettings.vb:24-201 | 2017/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsSettings.vb:24-201 | 2018/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsSettings.vb:24-201 — before extracting anything, compare `2015/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsSettings.vb` and `2016/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsSettings.vb` 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.
Duplicated block (93 lines × 4) 2015/Case.ViewportReporting/Case.ViewportReporting/Data/clsSheetViewports.vb:19— 2015/Case.ViewportReporting/Case.ViewportReporting/Data/clsSheetViewports.vb:19-111 | 2016/Case.ViewportReporting/Case.ViewportReporting/Data/clsSheetViewports.vb:19-111 | 2017/Case.ViewportReporting/Case.ViewportReporting/Data/clsSheetViewports.vb:19-111 | 2018/Case.ViewportReporting/Case.ViewportReporting/Data/clsSheetViewports.vb:19-111 — before extracting anything, compare `2015/Case.ViewportReporting/Case.ViewportReporting/Data/clsSheetViewports.vb` and `2016/Case.ViewportReporting/Case.ViewportReporting/Data/clsSheetViewports.vb` 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.
Duplicated block (53 lines × 3) 2015/Case.ViewportReporting/Case.ViewportReporting/UI/form_Main.xaml.vb:14— 2015/Case.ViewportReporting/Case.ViewportReporting/UI/form_Main.xaml.vb:14-66 | 2016/Case.ViewportReporting/Case.ViewportReporting/UI/form_Main.xaml.vb:14-66 | 2017/Case.ViewportReporting/Case.ViewportReporting/UI/form_Main.xaml.vb:14-66 — before extracting anything, compare `2015/Case.ViewportReporting/Case.ViewportReporting/UI/form_Main.xaml.vb` and `2016/Case.ViewportReporting/Case.ViewportReporting/UI/form_Main.xaml.vb` 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.
Duplicated block (5 lines × 28) 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSortableBindingList.vb:75— 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSortableBindingList.vb:75-79 | 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSortableBindingList.vb:75-79 | 2015/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/Data/clsSortableBindingList.vb:75-79 | 2015/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsSortableBindingList.vb:75-79 | 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSortableBindingList.vb:75-79 | 2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/clsSortableBindingList.vb:75-79 | 2015/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsSortableBindingList.vb:75-79 | 2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSortableBindingList.vb:75-79 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSortableBindingList.vb:75-79 | 2016/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/Data/clsSortableBindingList.vb:75-79 | 2016/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsSortableBindingList.vb:75-79 | 2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSortableBindingList.vb:75-79 | 2016/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/clsSortableBindingList.vb:75-79 | 2016/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsSortableBindingList.vb:75-79 | 2017/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSortableBindingList.vb:75-79 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSortableBindingList.vb:75-79 | 2017/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/Data/clsSortableBindingList.vb:75-79 | 2017/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsSortableBindingList.vb:75-79 | 2017/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSortableBindingList.vb:75-79 | 2017/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/clsSortableBindingList.vb:75-79 | 2017/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsSortableBindingList.vb:75-79 | 2018/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSortableBindingList.vb:75-79 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSortableBindingList.vb:75-79 | 2018/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/Data/clsSortableBindingList.vb:75-79 | 2018/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsSortableBindingList.vb:75-79 | 2018/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSortableBindingList.vb:75-79 | 2018/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/clsSortableBindingList.vb:75-79 | 2018/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsSortableBindingList.vb:75-79 — before extracting anything, compare `2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSortableBindingList.vb` and `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSortableBindingList.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 36 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 (9 lines × 44) 2015/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsSortableBindingList.vb:85— 2015/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsSortableBindingList.vb:85-93 | 2015/Case.LightingLayout/Case.LightingLayout/Data/clsSortableBindingList.vb:85-93 | 2015/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Data/clsSortableBindingList.vb:85-93 | 2015/Case.RevClouds/Case.RevClouds/Data/clsSortableBindingList.vb:85-93 | 2015/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSortableBindingList.vb:83-91 | 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSortableBindingList.vb:83-91 | 2015/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/Data/clsSortableBindingList.vb:83-91 | 2015/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsSortableBindingList.vb:83-91 | 2015/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSortableBindingList.vb:83-91 | 2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/clsSortableBindingList.vb:83-91 | 2015/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsSortableBindingList.vb:83-91 | 2016/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsSortableBindingList.vb:85-93 | 2016/Case.LightingLayout/Case.LightingLayout/Data/clsSortableBindingList.vb:85-93 | 2016/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Data/clsSortableBindingList.vb:85-93 | 2016/Case.RevClouds/Case.RevClouds/Data/clsSortableBindingList.vb:85-93 | 2016/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSortableBindingList.vb:83-91 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSortableBindingList.vb:83-91 | 2016/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/Data/clsSortableBindingList.vb:83-91 | 2016/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsSortableBindingList.vb:83-91 | 2016/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSortableBindingList.vb:83-91 | 2016/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/clsSortableBindingList.vb:83-91 | 2016/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsSortableBindingList.vb:83-91 | 2017/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsSortableBindingList.vb:85-93 | 2017/Case.LightingLayout/Case.LightingLayout/Data/clsSortableBindingList.vb:85-93 | 2017/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Data/clsSortableBindingList.vb:85-93 | 2017/Case.RevClouds/Case.RevClouds/Data/clsSortableBindingList.vb:85-93 | 2017/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSortableBindingList.vb:83-91 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSortableBindingList.vb:83-91 | 2017/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/Data/clsSortableBindingList.vb:83-91 | 2017/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsSortableBindingList.vb:83-91 | 2017/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSortableBindingList.vb:83-91 | 2017/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/clsSortableBindingList.vb:83-91 | 2017/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsSortableBindingList.vb:83-91 | 2018/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsSortableBindingList.vb:85-93 | 2018/Case.LightingLayout/Case.LightingLayout/Data/clsSortableBindingList.vb:85-93 | 2018/Case.MultiViewDuplicate/Case.MultiViewDuplicate/Data/clsSortableBindingList.vb:85-93 | 2018/Case.RevClouds/Case.RevClouds/Data/clsSortableBindingList.vb:85-93 | 2018/Case.Subs.DeleteViewsAndPurge/Case.Subs.DeleteViewsAndPurge/Data/clsSortableBindingList.vb:83-91 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSortableBindingList.vb:83-91 | 2018/Case.Subs.MultiViewDuplicate/Case.Subs.MultiViewDuplicate/Data/clsSortableBindingList.vb:83-91 | 2018/Case.Subs.Renamer/Case.Subs.Renamer/Data/clsSortableBindingList.vb:83-91 | 2018/Case.Subs.RoomsToMass/Case.Subs.RoomsToMass/Data/clsSortableBindingList.vb:83-91 | 2018/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/Data/clsSortableBindingList.vb:83-91 | 2018/Case.Subs.Worksets/Case.Subs.Worksets/Data/clsSortableBindingList.vb:83-91 — before extracting anything, compare `2015/Case.DoorMarkRenumber/Case.DoorMarkRenumber/Data/clsSortableBindingList.vb` and `2015/Case.LightingLayout/Case.LightingLayout/Data/clsSortableBindingList.vb` 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. 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 (163 lines × 4) 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:744— 2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:744-906 | 2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:744-906 | 2017/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:744-906 | 2018/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb:744-906 — before extracting anything, compare `2015/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb` and `2016/Case.Subs.Exceler8/Case.Subs.Exceler8/Data/clsSettings.vb` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 422 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 (5 lines × 8) 2015/Case.SharedParameters/Case.SharedParameters/Data/clsSharedParameters.vb:54— 2015/Case.SharedParameters/Case.SharedParameters/Data/clsSharedParameters.vb:54-58 | 2015/Case.Subs.SharedParameters/Case.Subs.SharedParameters/Data/clsSharedParameters.vb:79-83 | 2016/Case.SharedParameters/Case.SharedParameters/Data/clsSharedParameters.vb:54-58 | 2016/Case.Subs.SharedParameters/Case.Subs.SharedParameters/Data/clsSharedParameters.vb:79-83 | 2017/Case.SharedParameters/Case.SharedParameters/Data/clsSharedParameters.vb:54-58 | 2017/Case.Subs.SharedParameters/Case.Subs.SharedParameters/Data/clsSharedParameters.vb:79-83 | 2018/Case.SharedParameters/Case.SharedParameters/Data/clsSharedParameters.vb:54-58 | 2018/Case.Subs.SharedParameters/Case.Subs.SharedParameters/Data/clsSharedParameters.vb:79-83 — before extracting anything, compare `2015/Case.SharedParameters/Case.SharedParameters/Data/clsSharedParameters.vb` and `2015/Case.Subs.SharedParameters/Case.Subs.SharedParameters/Data/clsSharedParameters.vb` 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. 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 (7 lines × 8) 2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:646— 2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:646-652 | 2015/Case.ViewTemplates/Case.ViewTemplates/UI/form_Main.vb:254-260 | 2016/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:646-652 | 2016/Case.ViewTemplates/Case.ViewTemplates/UI/form_Main.vb:254-260 | 2017/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:646-652 | 2017/Case.ViewTemplates/Case.ViewTemplates/UI/form_Main.vb:254-260 | 2018/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb:646-652 | 2018/Case.ViewTemplates/Case.ViewTemplates/UI/form_Main.vb:254-260 — before extracting anything, compare `2015/Case.Subs.ViewTemplates/Case.Subs.ViewTemplates/UI/form_Main.vb` and `2015/Case.ViewTemplates/Case.ViewTemplates/UI/form_Main.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 62 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 (9 lines × 12) 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:494— 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:494-502 | 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:578-586 | 2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb:513-521 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:494-502 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:578-586 | 2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb:513-521 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:494-502 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:578-586 | 2017/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb:513-521 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb:494-502 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_ExportPoints.xaml.vb:577-585 | 2018/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_PlacePointsFromFile.xaml.vb:513-521 — before extracting anything, compare `2015/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb` and `2016/Case.Subs.Xyz/Case.Subs.Xyz/UI/form_DataManager.xaml.vb` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 267 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 (9 lines × 3) 2015/Case.LineChanger/Case.LineChanger/Forms/form_Main.vb:93— 2015/Case.LineChanger/Case.LineChanger/Forms/form_Main.vb:93-101 | 2016/Case.LineChanger/Case.LineChanger/Forms/form_Main.vb:93-101 | 2017/Case.LineChanger/Case.LineChanger/Forms/form_Main.vb:93-101 — before extracting anything, compare `2015/Case.LineChanger/Case.LineChanger/Forms/form_Main.vb` and `2016/Case.LineChanger/Case.LineChanger/Forms/form_Main.vb` 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 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.
Duplicated block (18 lines × 3) Case.AppsRibbon.2017/Entry/AppMain.vb:326— Case.AppsRibbon.2017/Entry/AppMain.vb:326-343 | Case.AppsRibbon.2018/Entry/AppMain.vb:326-343 | Case.AppsRibbon/Entry/AppMain.vb:326-343 — before extracting anything, compare `Case.AppsRibbon.2017/Entry/AppMain.vb` and `Case.AppsRibbon.2018/Entry/AppMain.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 148 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 × 3) Case.AppsRibbon.2017/Utility/modUtility.vb:13— Case.AppsRibbon.2017/Utility/modUtility.vb:13-22 | Case.AppsRibbon.2018/Utility/modUtility.vb:13-22 | Case.AppsRibbon/Utility/modUtility.vb:13-22 — before extracting anything, compare `Case.AppsRibbon.2017/Utility/modUtility.vb` and `Case.AppsRibbon.2018/Utility/modUtility.vb` 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 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.
Coverage not measured — no coverage collector is wired up — Coverage NOT MEASURED: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect.
No CI pipeline — No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
SC1 · Supply-chain hygiene· NuGet dependencies are not locked · ×1
NuGet dependencies are not locked — No packages.lock.json and no central package management — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
Commented-out code REDACTED:123— 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 REDACTED:132— 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 2015/Case.ExportSharedParameters/Case.ExportSharedParameters/Classes/Entry/cmd.cs:42— 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 2015/Case.ExportSharedParameters/Case.ExportSharedParameters/Classes/Entry/cmd.cs:72— 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 2015/Case.ExportSharedParameters/Case.ExportSharedParameters/Classes/Entry/cmd.cs:73— 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 2015/Case.ExportSharedParameters/Case.ExportSharedParameters/Classes/Entry/cmd.cs:74— 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 2015/Case.ExportSharedParameters/Case.ExportSharedParameters/Classes/Entry/cmd.cs:84— 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 2015/Case.ExportSharedParameters/Case.ExportSharedParameters/Classes/Entry/cmd.cs:89— 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 2015/Case.ExportSharedParameters/Case.ExportSharedParameters/Classes/Entry/cmd.cs:104— 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 2015/Case.ExportSharedParameters/Case.ExportSharedParameters/Classes/Entry/cmd.cs:145— 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 REDACTED:203— 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 2015/Case.Navis2BCF/Case.Navis2BCF/IfcGuid.cs:167— 13 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers).
Commented-out code REDACTED: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 REDACTED:429— 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 REDACTED:213— 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 2015/Case.Subs.KeyMatcher/Utility/clsGlobals.cs:297— 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 REDACTED:114— 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 REDACTED:400— 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 2016/Case.ExportSharedParameters/Case.ExportSharedParameters/Classes/Entry/cmd.cs:42— 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 2016/Case.ExportSharedParameters/Case.ExportSharedParameters/Classes/Entry/cmd.cs:72— 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 2016/Case.ExportSharedParameters/Case.ExportSharedParameters/Classes/Entry/cmd.cs:73— 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 2016/Case.ExportSharedParameters/Case.ExportSharedParameters/Classes/Entry/cmd.cs:74— 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 2016/Case.ExportSharedParameters/Case.ExportSharedParameters/Classes/Entry/cmd.cs:84— 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 2016/Case.ExportSharedParameters/Case.ExportSharedParameters/Classes/Entry/cmd.cs:89— 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 2016/Case.ExportSharedParameters/Case.ExportSharedParameters/Classes/Entry/cmd.cs:104— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Duplicated predicate 2015/Case.ApplySysOrient/Entry/CmdMain.cs:52— `!dlg.DoConduit && !dlg.DoDuct && !dlg.DoPipe & !dlg.DoTray` appears character-identically in 4 files — 2015/Case.ApplySysOrient/Entry/CmdMain.cs, 2016/Case.ApplySysOrient/Entry/CmdMain.cs, 2017/Case.ApplySysOrient/Entry/CmdMain.cs, 2018/Case.ApplySysOrient/Entry/CmdMain.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 REDACTED:244— `AnnotationCatCheck.Checked || ModelCatCheck.Checked` appears character-identically in 4 files — REDACTED, REDACTED, REDACTED, REDACTED. 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 REDACTED:243— `AnnotationCatCheck.Checked || ModelCatCheck.Checked || AnalyticalCatCheck.Checked` appears character-identically in 4 files — REDACTED, REDACTED, REDACTED, REDACTED. 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 2015/Case.ParallelWalls/Case.ParallelWalls/Data/clsVectors.cs:122— `_WallLocation == null || _RefLocation == null` appears character-identically in 4 files — 2015/Case.ParallelWalls/Case.ParallelWalls/Data/clsVectors.cs, 2016/Case.ParallelWalls/Case.ParallelWalls/Data/clsVectors.cs, 2017/Case.ParallelWalls/Case.ParallelWalls/Data/clsVectors.cs, 2018/Case.ParallelWalls/Case.ParallelWalls/Data/clsVectors.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 REDACTED:295— `app.myProduct == "MEP" && subdiscipline.Trim() == ""` appears character-identically in 4 files — REDACTED, REDACTED, REDACTED, REDACTED. 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 2015/Case.ReportGroupsByView/Case.ReportGroupsByView/UI/form_Main.cs:148— `checkBoxGroupsDetail.Checked || checkBoxGroupsModel.Checked` appears character-identically in 8 files — 2015/Case.ReportGroupsByView/Case.ReportGroupsByView/UI/form_Main.cs, REDACTED, 2016/Case.ReportGroupsByView/Case.ReportGroupsByView/UI/form_Main.cs, REDACTED. 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 2015/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs:164— `f.FamilyCategory.Name == cat.Name && f.IsEditable` appears character-identically in 4 files — 2015/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs, 2016/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs, 2017/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.cs, 2018/Case.ObjectStyles/Case.ObjectStyles/Data/mnSettings.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 2015/Case.ParallelWalls/Case.ParallelWalls/Data/clsReferenceFilter.cs:40— `m_cat == BuiltInCategory.OST_Lines || m_cat == BuiltInCategory.OST_Walls` appears character-identically in 4 files — 2015/Case.ParallelWalls/Case.ParallelWalls/Data/clsReferenceFilter.cs, 2016/Case.ParallelWalls/Case.ParallelWalls/Data/clsReferenceFilter.cs, 2017/Case.ParallelWalls/Case.ParallelWalls/Data/clsReferenceFilter.cs, 2018/Case.ParallelWalls/Case.ParallelWalls/Data/clsReferenceFilter.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 2015/Case.ParallelWalls/Case.ParallelWalls/Entry/CmdMain.cs:45— `m_key != null && m_key.GetValue(m_version.ToString()) == null` appears character-identically in 4 files — 2015/Case.ParallelWalls/Case.ParallelWalls/Entry/CmdMain.cs, 2016/Case.ParallelWalls/Case.ParallelWalls/Entry/CmdMain.cs, 2017/Case.ParallelWalls/Case.ParallelWalls/Entry/CmdMain.cs, 2018/Case.ParallelWalls/Case.ParallelWalls/Entry/CmdMain.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 2015/Case.Navis2BCF/Case.Navis2BCF/CASERibbon.cs:90— `m_pr != null && m_pr is DockPanePluginRecord && m_pr.IsEnabled` appears character-identically in 4 files — 2015/Case.Navis2BCF/Case.Navis2BCF/CASERibbon.cs, 2016/Case.Navis2BCF/Case.Navis2BCF/CASERibbon.cs, 2017/Case.Navis2BCF/Case.Navis2BCF/CASERibbon.cs, 2018/Case.Navis2BCF/Case.Navis2BCF/CASERibbon.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 2015/Case.ApplySysOrient/Data/clsUtil.cs:69— `m_resA > m_length * 0.999 && m_resA < m_length * 1.001` appears character-identically in 4 files — 2015/Case.ApplySysOrient/Data/clsUtil.cs, 2016/Case.ApplySysOrient/Data/clsUtil.cs, 2017/Case.ApplySysOrient/Data/clsUtil.cs, 2018/Case.ApplySysOrient/Data/clsUtil.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 2015/Case.ApplySysOrient/Data/clsUtil.cs:74— `m_resB > m_length * 0.999 && m_resB < m_length * 1.001` appears character-identically in 4 files — 2015/Case.ApplySysOrient/Data/clsUtil.cs, 2016/Case.ApplySysOrient/Data/clsUtil.cs, 2017/Case.ApplySysOrient/Data/clsUtil.cs, 2018/Case.ApplySysOrient/Data/clsUtil.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 REDACTED:468— `null != elementList && elementList.Any() && _elemCheck != 2` appears character-identically in 4 files — REDACTED, REDACTED, REDACTED, REDACTED. 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 REDACTED:466— `o.InstanceGuid != Guid.Empty && ChechHidden(o.AncestorsAndSelf) && o.FindFirstGeometry() != null && !o.FindFirstGeometry().Item.IsHidden` appears character-identically in 4 files — REDACTED, REDACTED, REDACTED, REDACTED. 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 REDACTED:93— `result == true && saveFileDialog.FileName != ""` appears character-identically in 4 files — REDACTED, REDACTED, REDACTED, REDACTED. 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 2015/Case.ObjectStyles/Case.ObjectStyles/Data/mnFamData.cs:147— `subCatList == null || subCatList.Size <= 0` appears character-identically in 8 files — 2015/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnFamData.cs, 2015/Case.ObjectStyles/Case.ObjectStyles/Data/mnFamData.cs, 2016/Case.FamilySubcategories/Case.FamilySubcategories/Data/mnFamData.cs, 2016/Case.ObjectStyles/Case.ObjectStyles/Data/mnFamData.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 2015/Case.ReportGroupsByView/Case.ReportGroupsByView/Data/clsSettings.cs:214— `v.ViewType == ViewType.AreaPlan || v.ViewType == ViewType.CeilingPlan || v.ViewType == ViewType.Elevation || v.ViewType == ViewType.FloorPla…` appears character-identically in 4 files — 2015/Case.ReportGroupsByView/Case.ReportGroupsByView/Data/clsSettings.cs, 2016/Case.ReportGroupsByView/Case.ReportGroupsByView/Data/clsSettings.cs, 2017/Case.ReportGroupsByView/Case.ReportGroupsByView/Data/clsSettings.cs, 2018/Case.ReportGroupsByView/Case.ReportGroupsByView/Data/clsSettings.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.
D21 · Naming Consistency· Typo in method name · ×1
Typo in method name: 'ChechHidden' appears to be a misspelling of 'CheckHidden'. While 'ShowMessage' is a different concept, the presence of a clear typo ('Chech') alongside correctly spelled verbs in similar contexts (e.g., 'ShowMessage', 'GetOriginalAngles') indicates a lack of consistency in spelling correctness within the codebase. — Rename 'ChechHidden' to 'CheckHidden'. (symbols: Method: private bool CASE.Navis2BCF.Navis2JiraWin.ChechHidden(ModelItemEnumerableCollection), Method: internal bool Case.ApplySysOrient.Data.Util.ShowMessage())
D21 · Naming Consistency· Inconsistent naming for local settings fields across different form classes. While '_s' is a common abbreviation, the codebase also uses more descriptive names like '_cmd' for command data and 'defaultInstance' for settings. However, since '_s' is used consistently across multiple forms for the same type (`clsSettings`), this is actually a consistent convention within the UI layer. No inconsistency found here as the pattern is uniform. · ×1
Inconsistent naming for local settings fields across different form classes. While '_s' is a common abbreviation, the codebase also uses more descriptive names like '_cmd' for command data and 'defaultInstance' for settings. However, since '_s' is used consistently across multiple forms for the same type (`clsSettings`), this is actually a consistent convention within the UI layer. No inconsistency found here as the pattern is uniform. — No action needed. (symbols: Field: private clsSettings Case.ApplySysOrient.UI.form_MaxSize._s, Field: private clsSettings Case.FamilySubcategories.UI.form_Main._s, Field: private clsSettings Case.ReportGroupsByView.UI.form_Main._s)
D21 · Naming Consistency· Consistent naming for Culture properties across all Resources classes. No inconsistency. · ×1
Consistent naming for Culture properties across all Resources classes. No inconsistency. — No action needed. (symbols: Property: internal CultureInfo Case.ApplySysOrient.Properties.Resources.Culture, Property: internal CultureInfo Case.ParallelWalls.Properties.Resources.Culture, Property: internal CultureInfo CASE.Navis2BCF.Properties.Resources.Culture, Property: internal CultureInfo Case.DimensionOverrides.Properties.Resources.Culture, Property: internal CultureInfo Case.FamilySubcategories.Properties.Resources.Culture, Property: internal CultureInfo Case.UngroupAll.Properties.Resources.Culture)
D21 · Naming Consistency· Consistent naming for ResourceManager fields. No inconsistency. · ×1
Consistent naming for ResourceManager fields. No inconsistency. — No action needed. (symbols: Field: private ResourceManager Case.FamilySubcategories.Properties.Resources.resourceMan, Field: private ResourceManager Case.ParallelWalls.Properties.Resources.resourceMan, Field: private ResourceManager Case.UngroupAll.Properties.Resources.resourceMan, Field: private ResourceManager Case.Subs.KeyMatcher.Properties.Resources.resourceMan)
D21 · Naming Consistency· Inconsistent naming for the resource culture field/property. Some classes use a field named 'resourceCulture' (e.g., `UngroupAll`), while others use a property named 'Culture' (e.g., `ApplySysOrient`). These represent the same concept (the current culture for resource lookup) but are named differently. · ×1
Inconsistent naming for the resource culture field/property. Some classes use a field named 'resourceCulture' (e.g., `UngroupAll`), while others use a property named 'Culture' (e.g., `ApplySysOrient`). These represent the same concept (the current culture for resource lookup) but are named differently. — Standardize on 'Culture' property or 'resourceCulture' field across all Resources classes. (symbols: Field: private CultureInfo Case.UngroupAll.Properties.Resources.resourceCulture, Property: internal CultureInfo Case.ApplySysOrient.Properties.Resources.Culture)
D21 · Naming Consistency· Inconsistent naming for the resource manager field/property. Some classes use a field named 'resourceMan' (e.g., `FamilySubcategories`), while others use a property named 'ResourceManager' (e.g., `Navis2BCF`). These represent the same concept. · ×1
Inconsistent naming for the resource manager field/property. Some classes use a field named 'resourceMan' (e.g., `FamilySubcategories`), while others use a property named 'ResourceManager' (e.g., `Navis2BCF`). These represent the same concept. — Standardize on 'ResourceManager' property or 'resourceMan' field across all Resources classes. (symbols: Field: private ResourceManager Case.FamilySubcategories.Properties.Resources.resourceMan, Property: internal ResourceManager CASE.Navis2BCF.Properties.Resources.ResourceManager)
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.
No src/ separation — Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.
No SAST — No static application security testing detected. For this repository's stack, add a Roslyn security analyzer package referenced from the project (the analyzer packages do analyse VB.NET), plus gitleaks for committed secrets — CodeQL has no VB.NET extractor, so its csharp pack would extract nothing from this tree and then report it clean — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 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.
No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
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.
nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
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.
provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
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.
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.
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.
Run 01a15f27-af2e-77e3-8f21-76b0a9d9c7ad · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 4161 · Warnings: 2289 · Recommendations: 64 · Info: 28 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 21-10-2026 @ 15:49 UTC.
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.