Public report of rmcanany/SolidEdgeHousekeeper, published 14 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 14 November 2026, 12:28 UTC · Survey ID cd_1984ad2263154b6988f0a56492b4c841
rmcanany/SolidEdgeHousekeeper
Measured 14 November 2026, 12:28 UTC, at code version c371e55
Boundary Type-Coupling is not measured: Bounded contexts not declared.
CAI scoreWeak
CriticalWeakAdequateStrongExemplary
Up 1 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 medium codebase: 38,835 lines of product code in 3 projects, tests not counted · Estimated rebuild effort: about 0.2 person-years · Weakest lens: Production Readiness, 17
Findings by how serious they are
89 critical523 serious66 minor
40 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
14 November 2026, 12:28 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
36of 36 dimensions measured by tools.
670of 678 findings point to an exact file and line, so you can open each one in the code. The other 8 concern the repository as a whole, such as missing documentation.
36dimensions across 5 lenses, read from 38,835 lines of product code in 3 projects.
rmcanany/SolidEdgeHousekeeper falls short of our standard for production because the project has no automated tests and we found no working pipeline that builds or tests changes to the code. It scores 41 out of 100 and is rated Weak, and seven of its 89 critical findings are leaked passwords or keys.
Production Readiness, at 17, is the weakest lens and counts most in the score. The best first step is adding automated tests, worth about 24 points. Adding an automated build and test pipeline is another step, worth about 6 points. Raising Production Readiness to 70 would lift the score to about 63.
Seven passwords or keys are open to anyone who can read the repository. The project has no automated tests, so a change can break it without warning, and eighty errors are caught and ignored, so failures can go unnoticed. Adding automated tests, replacing each exposed password or key and handling or logging the ignored errors would close these risks. The part of the code nobody has worked on for a long time needs someone to learn and document it before anyone changes it.
The product code is 38,835 lines, about €35,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.
Churn × Complexity Hotspots · Hotspot: My Project/FormPropertyInputEditor.vb My Project/FormPropertyInputEditor.vb
Churn × Complexity Hotspots · Hotspot: My Project/FormVariableInputEditor.vb My Project/FormVariableInputEditor.vb
Explicit Debt · EmptyCatchBlock My Project/TaskCheckDrawings.vb
Explicit Debt · EmptyCatchBlock My Project/UtilsFileList.vb
Explicit Debt · TodoComment My Project/UCEditVariables.vb
We compare 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: 8 findings
These 8 critical or serious findings were in the previous survey, on 26 October 2026, and are gone from this one.
Code Duplication · Members sharing a duplicated core (22 members, 50+ identical tokens) My Project/TaskBreakLinks.vb
Churn × Complexity Hotspots · Hotspot: My Project/TaskUpdateDrawingStylesFromTemplate.vb My Project/TaskUpdateDrawingStylesFromTemplate.vb
Churn × Complexity Hotspots · Hotspot: My Project/Task.vb My Project/Task.vb
Change Coupling · Change coupling: FormPropertyFilter.vb ↔ UtilsPropertyFilters.vb My Project/FormPropertyFilter.vb
Rebuild cost: about €35,000 · Estimate
Cost to rebuild
€12,000 to €58,000, for 192 to 610 hours of work, about 0.2 person-years for one engineer
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 41. 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
Medium: 38,835 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
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 1 No automated tests finding(s) in Code Coverage.
Raises the score by about 24 points · High effort · Code Coverage
2
Resolve the 80 EmptyCatchBlock finding(s) in Explicit Debt — start with UtilsSEApp.vb (8), TaskEditInteractively.vb (7), UtilsCommon.vb (7).
Raises the score by about 4 points · Medium effort · Explicit Debt
3
Add a CI workflow that builds and runs the test suite on every push/PR.
Raises the score by about 6 points · Medium effort · CI/CD gates
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €35,000 to build again, about 0.2 person-years of work. Its weakest lens is Production Readiness, at 17 (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.
If you do one thing first · First action
Resolve the 1 No automated tests finding(s) in Code Coverage. Of all the actions in this report, it raises the score most for the work it takes: about 24 points for high effort, because it clears the 1 Code Coverage findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
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 4.3 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 9% to 21% on every change. The history of the code shows how much it changes: about 13,508 lines over the last 90 days, which is about 54,782 lines a year. At that pace, the extra work comes to an estimated 12.8 to 76.8 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
At a glance — Code Health · 58% · Adequate · gated by D2 ·
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
8
High / Critical
Roadmap
Top priorities: Resolve the 1 No automated tests finding(s) in Code Coverage; Add a CI workflow that builds and runs the test suite on every push/PR; Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the `catch` blocks that emit nothing — a discarded exception is the failure the user cannot describe and you cannot reproduce.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 No automated tests finding(s) in Code Coverage.
Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the `catch` blocks that emit nothing — a discarded exception is the failure the user cannot describe and you cannot reproduce.
Bring the 168 bodies over 15 down to 15 or less in Cognitive Complexity — start with TaskUpdateBlocks.ProcessInternal (cognitive 219), TaskCheckDrawings.CheckDetachedDimensionsOrAnnotations (cognitive 206), TaskEditProperties.DoFindReplace (cognitive 147).
Per-file score 0–10 — a quality signature. Of 83 files carrying findings, judged against the Production bar: 24% slop · 60% mixed · 16% near-clean.
File
Score
Band
Worst signal
My Project/TaskCheckDrawings.vb
1.0
Slop
Explicit Debt: EmptyCatchBlock
My Project/TaskUpdateBlocks.vb
1.0
Slop
Explicit Debt: EmptyCatchBlock
My Project/UtilsCommon.vb
1.0
Slop
Explicit Debt: EmptyCatchBlock
My Project/TaskCheckRelationships.vb
1.0
Slop
Explicit Debt: EmptyCatchBlock
My Project/TaskEditInteractively.vb
1.0
Slop
Explicit Debt: EmptyCatchBlock
My Project/UtilsTopLevelAssembly.vb
1.9
Slop
Explicit Debt: EmptyCatchBlock
My Project/Form_Main.vb
1.9
Slop
Explicit Debt: EmptyCatchBlock
My Project/UtilsPreferences.vb
1.9
Slop
Explicit Debt: EmptyCatchBlock
My Project/TaskBreakLinks.vb
1.9
Slop
Explicit Debt: EmptyCatchBlock
My Project/TaskShowHideConstructions.vb
2.1
Slop
Explicit Debt: EmptyCatchBlock
My Project/UtilsFileList.vb
2.3
Slop
Explicit Debt: EmptyCatchBlock
My Project/TaskSaveDrawingAs.vb
2.8
Slop
Explicit Debt: EmptyCatchBlock
My Project/UtilsMaterials.vb
2.9
Slop
Explicit Debt: EmptyCatchBlock
My Project/TaskUpdateDrawingStylesFromTemplate.vb
2.9
Slop
Explicit Debt: EmptyCatchBlock
My Project/UtilsSEApp.vb
3.0
Slop
Explicit Debt: EmptyCatchBlock
My Project/TaskUpdateDrawings.vb
3.2
Slop
Explicit Debt: EmptyCatchBlock
My Project/HCPropertiesData.vb
3.4
Slop
Explicit Debt: EmptyCatchBlock
My Project/TaskPrint.vb
3.5
Slop
Explicit Debt: EmptyCatchBlock
My Project/FormPropertyInputEditor.vb
3.9
Slop
Explicit Debt: EmptyCatchBlock
My Project/FormExpressionEditor.vb
3.9
Slop
Explicit Debt: EmptyCatchBlock
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 — 89
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 — 523
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 — 66
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 40
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 36 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 36 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, 670 of 678 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 or a scanner, 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.
D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
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. Single-maintainer repository — bus factor is not applicable (8 contributor(s) across 1512 commit(s) sampled, automation and bot accounts excluded). One of them holds 80% of the history; the other 7 hold 2.9% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Msbuild failed when processing the file 'Housekeeper.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.
D18 Solution Shape — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. `dotnet build` reported 1 error(s), and the diagnostics it printed were: MSB4803: 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.. None of them is a .NET compiler diagnostic, which is the only signal this check reads as "the code does not compile", so the failure is recorded as a build-environment gap rather than a code defect. The usual causes are a project that targets a platform this run cannot build (a Windows-only target framework on a Linux worker) or a build step that shells out to a tool the image does not carry. Solution Shape is scored on structure and is NOT capped. Semantic analysis is independent of this build and covers every project that loaded — but a project whose restore did not complete has no resolved references, so treat its results as absent rather than clean. ★ The reach of that test, stated so this classification can be checked rather than taken on trust: it reads the C# (CS), Visual Basic (BC) and F# (FS) compiler series, and treats SDK, NuGet-restore and MSBuild codes (NETSDK, NU, MSB) as evidence that the build did not run rather than that the code is broken — read the diagnostics named above and judge for yourself. You can widen what we reach: if this build is meant to run off its own platform, without host tooling we do not carry, the diagnostics named above are what stopped it. If it is deliberately platform-bound — a Windows-only desktop product, say — there is nothing to do here: the note records our reach, not a defect in your build.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
D23 Boundary Type-Coupling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Large codebase (38,835 production LoC in the .NET projects) with no declared bounded contexts — cross-boundary type coupling is unassessed Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D30 Dependency Vulnerabilities — measured, with a gap in what it reached — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. `dotnet list package --vulnerable` could not read this solution's dependency graph — it reported an error for at least one project and returned no package data at all (typically a packages.config / non-PackageReference project, which the command cannot read). An unreadable dependency graph is not a clean one; migrate the project(s) to PackageReference to enable this scan. 1 of 2 declared ecosystem(s) (nuget packages.config) WERE scanned and every vulnerability they reported is included in this result; nuget was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that nuget is free of known-vulnerable dependencies.
C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
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.
PF3 Async & latency hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. No function of a language this check models was read, so there was no async code to examine. That is a limit of the analyzer on this repository, not a finding about it.
S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X10 Duplicated predicate — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X14 Bypassable address classification — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X15 Unvalidated length from an untrusted reader — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X19 Unrestored process-global state — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X20 Mistyped argument guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X21 Side-effecting pattern guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X22 Contradicted release guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X23 Unguarded diagnostic materialisation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X25 Inert configuration knob — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X26 Unsynchronised callback handoff — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X28 Index access outside its own emptiness guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X29 Per-element action decided by a fixed element — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X30 Support guard that admits what it rejects — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X32 Type resolved by simple name across every loaded assembly — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X6 Hand-rolled structured-format parsing — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Python, JavaScript/TypeScript, Go, Java/Kotlin/Scala, Ruby, PHP, Rust, Swift, Erlang, Elixir and Dart source only, and no C# was loaded and none of those languages was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X7 Silent fallback defaults — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C#, Python, TypeScript/JavaScript, Rust, Go, Java, Kotlin, Scala, PHP, Ruby, Swift and Dart syntax only, and no C#, Python, TypeScript/JavaScript, Rust, Go, Java, Kotlin, Scala, PHP, Ruby, Swift or Dart was loaded for this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
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.
D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
D13 REDACTED Scanning: REDACTED 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.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
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.
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.
65 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was PropertyData.New.ctor at 81. A further 3 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being PropertySet.CorrectedOLEPropName at 41 — they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: My Project/TaskShowHideConstructions.vb (TaskShowHideConstructions.CheckBoxOptions_Check_Changed at 23), My Project/Task.vb (Task.GetFormState at 16). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 60 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with PropertyData.New.ctor (cyclomatic 81), TaskCheckDrawings.CheckDetachedDimensionsOrAnnotations (cyclomatic 68). — 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 2 together lifts Cyclomatic Complexity from 5.6 to about 6.1/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
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.
+ 163 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 168 bodies over 15 down to 15 or less in Cognitive Complexity — start with TaskUpdateBlocks.ProcessInternal (cognitive 219), TaskCheckDrawings.CheckDetachedDimensionsOrAnnotations (cognitive 206), TaskEditProperties.DoFindReplace (cognitive 147). — 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 168 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.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes5.5 / 10Adequate✓ 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 38 MethodTooLong finding(s) in God Classes — start with HCStructuredStorageDoc.vb (4), TaskCheckDrawings.vb (3), TaskEditProperties.vb (3). — One of this dimension's main actionable groups (38 warning-level).
Resolve the 29 ClassTooLong finding(s) in God Classes — start with TaskUpdateBlocks.vb, TaskEditProperties.vb, TaskCheckDrawings.vb. — One of this dimension's main actionable groups (29 warning-level).
Resolve the 26 FileTooLong finding(s) in God Classes — start with Form_Main.vb, HCStructuredStorageDoc.vb, TaskUpdateBlocks.vb. — One of this dimension's main actionable groups (26 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D4 · Code Duplication4.8 / 10Weak✓ Tool-verified
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
91 duplicated block group(s) detected. 13.1 % of the production lines (5,070 of 38,835) are in a reported copy. A further 58 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
+ 96 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 7 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with TaskSaveDrawingAs.vb, TaskSaveModelAs.vb, TaskEditInteractively.vb. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 6 Duplicated block (14 lines × 2) finding(s) in Code Duplication — start with TaskCheckDrawings.vb, TaskSaveDrawingAs.vb, TaskUpdateModelStylesFromTemplate.vb. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 4 Duplicated block (10 lines × 3) finding(s) in Code Duplication — start with TaskUpdateBlocks.vb, TaskCheckDrawings.vb, TaskCheckMissingDrawing.vb. — One of this dimension's main actionable groups (4 warning-level).
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 26 Low cohesion finding(s) in Cohesion (LCOM4) — start with UtilsCommon.vb, Task.vb, TaskPrint.vb. — One of this dimension's main actionable groups (26 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D8 · Code Coverage0.0 / 10Critical✓ Tool-verified
What it measures: How much of the code is actually exercised by tests.
Method: Coverage from the analyzer's own run of the suite, computed per-file with structured exclusions for generated, trivial, and glue code. A coverage report found in the repository is never read. When the suite can't be built/run in-image, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.
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.
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 92 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.
Top hotspots: My Project/Form_Main.vb (16×46=736); My Project/TaskEditProperties.vb (9×45=405); My Project/TaskCheckDrawings.vb (5×68=340)
Hotspot: My Project/Form_Main.vb · ×10My Project/Form_Main.vb:1147
What to do
Resolve the 10 Hotspot finding(s) in Churn × Complexity Hotspots — start with Form_Main.vb, TaskEditProperties.vb, TaskCheckDrawings.vb. — One of this dimension's main actionable groups (10 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
84 deducted debt markers + unmeasured dead symbols across 38835 LoC in the .NET projects (2.0/KLoC) → score 6.1. Dead code not measured: the solution did not load cleanly, so the reference search was skipped.
Resolve the 80 EmptyCatchBlock finding(s) in Explicit Debt — start with UtilsSEApp.vb (8), TaskEditInteractively.vb (7), UtilsCommon.vb (7). — One of this dimension's main actionable groups (80 issue-level).
Resolve the 4 TodoComment finding(s) in Explicit Debt — start with HCStructuredStorageDoc.vb, TaskUpdateBlocks.vb, UCEditVariables.vb. — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
2 projects, 90 source files, 38464 hand-written lines of code (38464 production / 0 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 10794 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 0 inter-project edges (build NOT measured — `dotnet build` did not complete in the analyzer, so the build half of this dimension is unmeasured rather than failed: the score above rests on structure alone and is not capped. The diagnostics that stopped it are named under Limitations.)
✓ On the Gold path — maintain.
Detailed fixes: d18_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Housekeeper.vbproj. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.
doc comments repeat the namesMy Project/ListViewExtended/ListViewExtended/ListViewExtended.vb:246
What to do
Resolve the 60 redundant comment finding(s) in Comment Value — start with AssemblyInfo.vb (7), Form_Main.vb (4), UCEditVariables.vb (4). — One of this dimension's main actionable groups (60 recommendation-level).
Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
80 % of calls cross a namespace and 1 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: medium — clean/modular boundaries expected.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED 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.
7 finding(s): 0 critical, 7 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
What to do
Resolve the 7 REDACTED finding(s) in Secrets (history) — start with REDACTED (4), REDACTED (3). — One of this dimension's main actionable groups (7 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
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).
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (nuget packages.config). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (nuget packages.config), and the findings above are real and complete for them. nuget was not scanned (nuget: `dotnet list package --vulnerable` could not read this solution's dependency graph — it reported an error for at least one project and returned no package data at all (typically a packages.config / non-PackageReference project, which the command cannot read). An unreadable dependency graph is not a clean one; migrate the project(s) to PackageReference to enable this scan), so this is not the whole dependency surface and the result is reported at reduced confidence.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
1 of 78 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is My Project/ListViewExtended/ListViewExtended/ListViewExtended.vb. Counted over 78 of the 91 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with ListViewExtended.vb. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d34_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. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
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. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
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.
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.
~38.8k production LoC (191 types) across 3 project(s) / 9 namespace(s) with no recognised architectural style or layering — at this size, deliberate module boundaries would help. No DDD/clean/vertical-slice/CQRS/transaction-script organisation was detected — code is likely organised ad hoc, which makes change and onboarding harder as it grows.
What to do
Introduce deliberate module boundaries — by feature (vertical slices) if your team prefers, or by layer (domain/application/infrastructure). Even splitting into a few cohesive projects with a clear dependency direction would help.
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.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
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 repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
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.
Do you agree with this assessment?
P2 · Observability0.0 / 10Critical✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the `catch` blocks that emit nothing — a discarded exception is the failure the user cannot describe and you cannot reproduce.
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.
`packages.config` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — packages.config:3
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.
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 — 1 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.
Not evidenced — 5 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
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 — 73 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — no DI registrations detected
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 — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
D10 Test Quality — No tests were found in the analyzed repository to assess for quality.
D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
D12 Dependency Hygiene — Dependency hygiene not measured
D16 Bus Factor — single-maintainer repository — bus factor is not applicable
D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
D21 Naming Consistency — Naming consistency does not read Visual Basic yet; not measured.
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.
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.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
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
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — no CI workflow found
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 — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a BenchmarkDotNet reference in an .fsproj or .vbproj, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
PF3 Async & latency hygiene — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X10 Duplicated predicate — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X12 Unreachable branch — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X13 Undrained process stream — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X14 Bypassable address classification — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X15 Unvalidated length from an untrusted reader — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X16 Unfloored truncation loop — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X17 Uncapped recursion over a caller-supplied document — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X18 Disposal-pattern correctness — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X19 Unrestored process-global state — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X20 Mistyped argument guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X21 Side-effecting pattern guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X22 Contradicted release guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X23 Unguarded diagnostic materialisation — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X24 Document value interpolated into markup unescaped — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X25 Inert configuration knob — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X26 Unsynchronised callback handoff — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X27 Collection changed while being enumerated — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X28 Index access outside its own emptiness guard — X28 reached only 0% of this repository's production lines — vbnet (38,835 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X29 Per-element action decided by a fixed element — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X30 Support guard that admits what it rejects — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X32 Type resolved by simple name across every loaded assembly — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X6 Hand-rolled structured-format parsing — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X7 Silent fallback defaults — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
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 My Project/FormEditTaskListChangeColor.vb: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 My Project/FormEditTaskListChangeColor.vb:135— 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 My Project/FormExpressionEditor.vb:698— 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 My Project/FormPropertyInputEditor.vb:187— 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 My Project/FormSolidEdgeExplorer.vb:87— 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 My Project/FormTeamCenterAdd.vb:294— 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 My Project/FormVariableInputEditor.vb:115— 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 My Project/Form_Main.vb:1568— 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 My Project/Form_Main.vb:1584— 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 My Project/Form_Main.vb:3832— 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 My Project/HCIsolatedTaskProxy.vb:43— 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 My Project/HCPresets.vb:123— 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 My Project/HCPropertiesData.vb:730— 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 My Project/HCPropertiesData.vb:1249— 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 My Project/TaskBreakLinks.vb:394— 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 My Project/TaskBreakLinks.vb:455— 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 My Project/TaskCheckDrawings.vb:518— 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 My Project/TaskCheckDrawings.vb:541— 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 My Project/TaskCheckDrawings.vb:577— 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 My Project/TaskCheckDrawings.vb:600— 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 My Project/TaskCheckDrawings.vb:622— 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 My Project/TaskCheckDrawings.vb:915— 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 My Project/TaskCheckInterference.vb:225— 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 My Project/TaskCheckLinks.vb:63— 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 My Project/TaskCheckRelationships.vb:443— 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.
Orphaned knowledge My Project/ListViewExtended/ListViewExtended/ListViewExtended.vb:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
No automated tests — No automated tests — no test code was found in this repository. Untested code is the largest single risk to changing it safely. Start with the code you change most often: add a suite in a framework a runner can collect (xUnit, NUnit or MSTest), and run it in CI so the gap cannot reopen.
MethodTooLong: PropertyData.New(…) My Project/HCPropertiesData.vb:785— MethodTooLong — New(…) runs 314 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 214 over it, 3.14× 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: UtilsDocumentation.BuildReadmeFile My Project/UtilsDocumentation.vb:92— MethodTooLong — BuildReadmeFile runs 222 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 122 over it, 2.22× 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: TaskUpdateBlocks.ProcessInternal My Project/TaskUpdateBlocks.vb:449— MethodTooLong — ProcessInternal runs 207 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 107 over it, 2.07× 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: TaskCheckDrawings.CheckDetachedDimensionsOrAnnotations My Project/TaskCheckDrawings.vb:547— MethodTooLong — CheckDetachedDimensionsOrAnnotations runs 194 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 94 over it, 1.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: TaskUpdateBlocks.GenerateTaskOptionsTLP My Project/TaskUpdateBlocks.vb:1069— MethodTooLong — GenerateTaskOptionsTLP runs 194 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 94 over it, 1.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: TaskCheckDrawings.GenerateTaskOptionsTLP My Project/TaskCheckDrawings.vb:1019— MethodTooLong — GenerateTaskOptionsTLP runs 189 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 89 over it, 1.89× 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.Startup My Project/Form_Main.vb:1147— MethodTooLong — Startup runs 178 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 78 over it, 1.78× 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: TaskEditProperties.DoFindReplace My Project/TaskEditProperties.vb:1013— MethodTooLong — DoFindReplace runs 175 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 75 over it, 1.75× 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: UtilsExecute.CheckStartConditions My Project/UtilsExecute.vb:144— MethodTooLong — CheckStartConditions runs 161 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 61 over it, 1.61× 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: TaskSaveDrawingAs.GenerateTaskOptionsTLP My Project/TaskSaveDrawingAs.vb:614— MethodTooLong — GenerateTaskOptionsTLP runs 152 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 52 over it, 1.52× 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: FormTeamCenterAdd.SearchTeamCenter My Project/FormTeamCenterAdd.vb:15— MethodTooLong — SearchTeamCenter runs 149 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 49 over it, 1.49× 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: HCStructuredStorageDoc.LinkFullNames.ExtractFilenamesFromByteArray My Project/HCStructuredStorageDoc.vb:1704— MethodTooLong — ExtractFilenamesFromByteArray runs 147 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 47 over it, 1.47× 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: TaskSaveModelAs.GenerateTaskOptionsTLP My Project/TaskSaveModelAs.vb:945— MethodTooLong — GenerateTaskOptionsTLP runs 146 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 46 over it, 1.46× 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: UtilsCommon.SubstitutePropertyFormulas My Project/UtilsCommon.vb:998— MethodTooLong — SubstitutePropertyFormulas runs 146 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 46 over it, 1.46× 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: TaskCreateDrawingOfFlatPattern.GenerateTaskOptionsTLP My Project/TaskCreateDrawingOfFlatPattern.vb:514— MethodTooLong — GenerateTaskOptionsTLP runs 144 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 44 over it, 1.44× 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: UtilsFileList.FindFiles My Project/UtilsFileList.vb:246— MethodTooLong — FindFiles runs 139 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 39 over it, 1.39× 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: TaskEditInteractively.GenerateTaskOptionsTLP My Project/TaskEditInteractively.vb:342— MethodTooLong — GenerateTaskOptionsTLP runs 138 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 38 over it, 1.38× 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: TaskEditVariables.ProcessInternal My Project/TaskEditVariables.vb:102— MethodTooLong — ProcessInternal runs 135 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 35 over it, 1.35× 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: TaskUpdatePhysicalProperties.ProcessInternal My Project/TaskUpdatePhysicalProperties.vb:96— MethodTooLong — ProcessInternal runs 130 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 30 over it, 1.30× 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: UtilsMaterials.UpdateFaces My Project/UtilsMaterials.vb:502— MethodTooLong — UpdateFaces runs 128 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 28 over it, 1.28× 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: TaskEditProperties.GetHelpText My Project/TaskEditProperties.vb:1564— MethodTooLong — GetHelpText runs 124 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× 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: UtilsFileList.SortByDependency My Project/UtilsFileList.vb:905— MethodTooLong — SortByDependency runs 123 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 23 over it, 1.23× 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: HCPropertiesData.UpdateFromTemplates My Project/HCPropertiesData.vb:182— MethodTooLong — UpdateFromTemplates runs 122 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 22 over it, 1.22× 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: TaskUpdateDrawings.ProcessInternal My Project/TaskUpdateDrawings.vb:236— MethodTooLong — ProcessInternal runs 122 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 22 over it, 1.22× 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: TaskUpdateModelStylesFromTemplate.ProcessInternal My Project/TaskUpdateModelStylesFromTemplate.vb:265— MethodTooLong — ProcessInternal runs 120 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 20 over it, 1.20× 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.
ClassTooLong: TaskUpdateBlocks My Project/TaskUpdateBlocks.vb— ClassTooLong — 1361 significant lines (blank, comment-only and punctuation-only lines excluded), 25 methods. The bar is 400 significant lines; this is 961 over it, 3.40× 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: TaskEditProperties My Project/TaskEditProperties.vb— ClassTooLong — 1251 significant lines (blank, comment-only and punctuation-only lines excluded), 23 methods. The bar is 400 significant lines; this is 851 over it, 3.13× 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: TaskCheckDrawings My Project/TaskCheckDrawings.vb— ClassTooLong — 1176 significant lines (blank, comment-only and punctuation-only lines excluded), 15 methods. The bar is 400 significant lines; this is 776 over it, 2.94× 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: TaskUpdateModelStylesFromTemplate My Project/TaskUpdateModelStylesFromTemplate.vb— ClassTooLong — 1133 significant lines (blank, comment-only and punctuation-only lines excluded), 19 methods. The bar is 400 significant lines; this is 733 over it, 2.83× 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: TaskSaveModelAs My Project/TaskSaveModelAs.vb— ClassTooLong — 1094 significant lines (blank, comment-only and punctuation-only lines excluded), 18 methods. The bar is 400 significant lines; this is 694 over it, 2.74× 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: TaskUpdateDrawingStylesFromTemplate My Project/TaskUpdateDrawingStylesFromTemplate.vb— ClassTooLong — 1065 significant lines (blank, comment-only and punctuation-only lines excluded), 28 methods. The bar is 400 significant lines; this is 665 over it, 2.66× 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: UtilsFileList My Project/UtilsFileList.vb— ClassTooLong — 920 significant lines (blank, comment-only and punctuation-only lines excluded), 20 methods. The bar is 400 significant lines; this is 520 over it, 2.30× 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: TaskSaveDrawingAs My Project/TaskSaveDrawingAs.vb— ClassTooLong — 827 significant lines (blank, comment-only and punctuation-only lines excluded), 15 methods. The bar is 400 significant lines; this is 427 over it, 2.07× 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: TaskCreateDrawingOfFlatPattern My Project/TaskCreateDrawingOfFlatPattern.vb— ClassTooLong — 740 significant lines (blank, comment-only and punctuation-only lines excluded), 11 methods. The bar is 400 significant lines; this is 340 over it, 1.85× 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: TaskShowHideConstructions My Project/TaskShowHideConstructions.vb— ClassTooLong — 722 significant lines (blank, comment-only and punctuation-only lines excluded), 16 methods. The bar is 400 significant lines; this is 322 over it, 1.81× 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: FormPropertyFilter My Project/FormPropertyFilter.vb— ClassTooLong — 627 significant lines (blank, comment-only and punctuation-only lines excluded), 30 methods. The bar is 400 significant lines; this is 227 over it, 1.57× 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: TaskEditInteractively My Project/TaskEditInteractively.vb— ClassTooLong — 592 significant lines (blank, comment-only and punctuation-only lines excluded), 11 methods. The bar is 400 significant lines; this is 192 over it, 1.48× 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: TaskUpdateDrawings My Project/TaskUpdateDrawings.vb— ClassTooLong — 580 significant lines (blank, comment-only and punctuation-only lines excluded), 13 methods. The bar is 400 significant lines; this is 180 over it, 1.45× 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: UtilsExecute My Project/UtilsExecute.vb— ClassTooLong — 577 significant lines (blank, comment-only and punctuation-only lines excluded), 10 methods. The bar is 400 significant lines; this is 177 over it, 1.44× 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: FormExpressionEditor My Project/FormExpressionEditor.vb— ClassTooLong — 553 significant lines (blank, comment-only and punctuation-only lines excluded), 23 methods. The bar is 400 significant lines; this is 153 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: UtilsMaterials My Project/UtilsMaterials.vb— ClassTooLong — 545 significant lines (blank, comment-only and punctuation-only lines excluded), 16 methods. The bar is 400 significant lines; this is 145 over it, 1.36× 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: TaskCheckFilename My Project/TaskCheckFilename.vb— ClassTooLong — 544 significant lines (blank, comment-only and punctuation-only lines excluded), 13 methods. The bar is 400 significant lines; this is 144 over it, 1.36× 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: TaskCheckLinks My Project/TaskCheckLinks.vb— ClassTooLong — 539 significant lines (blank, comment-only and punctuation-only lines excluded), 21 methods. The bar is 400 significant lines; this is 139 over it, 1.35× 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: TaskBreakLinks My Project/TaskBreakLinks.vb— ClassTooLong — 532 significant lines (blank, comment-only and punctuation-only lines excluded), 16 methods. The bar is 400 significant lines; this is 132 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: UtilsTopLevelAssembly My Project/UtilsTopLevelAssembly.vb— ClassTooLong — 524 significant lines (blank, comment-only and punctuation-only lines excluded), 15 methods. The bar is 400 significant lines; this is 124 over it, 1.31× 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: Task My Project/Task.vb— ClassTooLong — 500 significant lines (blank, comment-only and punctuation-only lines excluded), 21 methods. The bar is 400 significant lines; this is 100 over it, 1.25× 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: TaskPrint My Project/TaskPrint.vb— ClassTooLong — 498 significant lines (blank, comment-only and punctuation-only lines excluded), 15 methods. The bar is 400 significant lines; this is 98 over it, 1.25× 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: TaskUpdateMaterialFromMaterialTable My Project/TaskUpdateMaterialFromMaterialTable.vb— ClassTooLong — 489 significant lines (blank, comment-only and punctuation-only lines excluded), 11 methods. The bar is 400 significant lines; this is 89 over it, 1.22× 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: TaskUpdateModelSizeInVariableTable My Project/TaskUpdateModelSizeInVariableTable.vb— ClassTooLong — 479 significant lines (blank, comment-only and punctuation-only lines excluded), 10 methods. The bar is 400 significant lines; this is 79 over it, 1.20× 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: HCPropertiesData My Project/HCPropertiesData.vb— ClassTooLong — 469 significant lines (blank, comment-only and punctuation-only lines excluded), 14 methods. The bar is 400 significant lines; this is 69 over it, 1.17× 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.
FileTooLong: My Project/Form_Main.vb My Project/Form_Main.vb— FileTooLong — 3201 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 2701 over it, 6.40× 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: My Project/HCStructuredStorageDoc.vb My Project/HCStructuredStorageDoc.vb— FileTooLong — 1916 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1416 over it, 3.83× 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: My Project/TaskUpdateBlocks.vb My Project/TaskUpdateBlocks.vb— FileTooLong — 1362 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 862 over it, 2.72× 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: My Project/TaskEditProperties.vb My Project/TaskEditProperties.vb— FileTooLong — 1252 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 752 over it, 2.50× 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: My Project/TaskCheckDrawings.vb My Project/TaskCheckDrawings.vb— FileTooLong — 1177 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 677 over it, 2.35× 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: My Project/TaskUpdateModelStylesFromTemplate.vb My Project/TaskUpdateModelStylesFromTemplate.vb— FileTooLong — 1134 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 634 over it, 2.27× 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: My Project/TaskSaveModelAs.vb My Project/TaskSaveModelAs.vb— FileTooLong — 1095 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 595 over it, 2.19× 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: My Project/TaskUpdateDrawingStylesFromTemplate.vb My Project/TaskUpdateDrawingStylesFromTemplate.vb— FileTooLong — 1066 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 566 over it, 2.13× 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: My Project/UtilsCommon.vb My Project/UtilsCommon.vb— FileTooLong — 923 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 423 over it, 1.85× 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: My Project/UtilsFileList.vb My Project/UtilsFileList.vb— FileTooLong — 921 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 421 over it, 1.84× 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: My Project/HCPropertiesData.vb My Project/HCPropertiesData.vb— FileTooLong — 867 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 367 over it, 1.73× 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: My Project/UtilsPreferences.vb My Project/UtilsPreferences.vb— FileTooLong — 847 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 347 over it, 1.69× 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: My Project/TaskSaveDrawingAs.vb My Project/TaskSaveDrawingAs.vb— FileTooLong — 828 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 328 over it, 1.66× 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: My Project/TaskCreateDrawingOfFlatPattern.vb My Project/TaskCreateDrawingOfFlatPattern.vb— FileTooLong — 741 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 241 over it, 1.48× 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: My Project/TaskShowHideConstructions.vb My Project/TaskShowHideConstructions.vb— FileTooLong — 723 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 223 over it, 1.45× 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: My Project/FormPropertyFilter.vb My Project/FormPropertyFilter.vb— FileTooLong — 628 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 128 over it, 1.26× 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: My Project/TaskEditInteractively.vb My Project/TaskEditInteractively.vb— FileTooLong — 593 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 93 over it, 1.19× 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: My Project/FormExpressionEditor.vb My Project/FormExpressionEditor.vb— FileTooLong — 590 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 90 over it, 1.18× 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: My Project/TaskUpdateDrawings.vb My Project/TaskUpdateDrawings.vb— FileTooLong — 581 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 81 over it, 1.16× 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: My Project/UtilsExecute.vb My Project/UtilsExecute.vb— FileTooLong — 578 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 78 over it, 1.16× 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: My Project/UtilsTopLevelAssembly.vb My Project/UtilsTopLevelAssembly.vb— FileTooLong — 562 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 62 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: My Project/UtilsMaterials.vb My Project/UtilsMaterials.vb— FileTooLong — 546 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 46 over it, 1.09× 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: My Project/TaskCheckFilename.vb My Project/TaskCheckFilename.vb— FileTooLong — 545 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 45 over it, 1.09× 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: My Project/TaskCheckLinks.vb My Project/TaskCheckLinks.vb— FileTooLong — 540 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 40 over it, 1.08× 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: My Project/TaskBreakLinks.vb My Project/TaskBreakLinks.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.
Low cohesion: UtilsCommon (LCOM4 16) My Project/UtilsCommon.vb:9— UtilsCommon's methods fall into 16 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 16 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: Task (LCOM4 14) My Project/Task.vb:6— Task's methods fall into 14 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 14 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: TaskPrint (LCOM4 7) My Project/TaskPrint.vb:3— TaskPrint's methods fall into 7 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 7 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: UtilsPreferences (LCOM4 6) My Project/UtilsPreferences.vb:5— UtilsPreferences's methods fall into 6 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 6 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: TaskCheckMissingDrawing (LCOM4 6) My Project/TaskCheckMissingDrawing.vb:3— TaskCheckMissingDrawing's methods fall into 6 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 6 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: TaskCheckInterference (LCOM4 5) My Project/TaskCheckInterference.vb:3— TaskCheckInterference'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: TaskShowHideConstructions (LCOM4 5) My Project/TaskShowHideConstructions.vb:3— TaskShowHideConstructions'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: TaskRunExternalProgram (LCOM4 5) My Project/TaskRunExternalProgram.vb:10— TaskRunExternalProgram'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: TaskUpdatePartCopies (LCOM4 5) My Project/TaskUpdatePartCopies.vb:3— TaskUpdatePartCopies'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: TaskCheckFilename (LCOM4 4) My Project/TaskCheckFilename.vb:3— TaskCheckFilename'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: TaskSetDocumentStatus (LCOM4 4) My Project/TaskSetDocumentStatus.vb:3— TaskSetDocumentStatus'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: TaskUpdateBlocks (LCOM4 4) My Project/TaskUpdateBlocks.vb:3— TaskUpdateBlocks'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: TaskBreakLinks (LCOM4 4) My Project/TaskBreakLinks.vb:3— TaskBreakLinks'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: TaskCheckDrawings (LCOM4 4) My Project/TaskCheckDrawings.vb:3— TaskCheckDrawings'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: TaskCheckMaterialNotInMaterialTable (LCOM4 4) My Project/TaskCheckMaterialNotInMaterialTable.vb:3— TaskCheckMaterialNotInMaterialTable'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: TaskCheckRelationships (LCOM4 4) My Project/TaskCheckRelationships.vb:3— TaskCheckRelationships'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: TaskEditInteractively (LCOM4 4) My Project/TaskEditInteractively.vb:3— TaskEditInteractively'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: TaskEditProperties (LCOM4 4) My Project/TaskEditProperties.vb:6— TaskEditProperties'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: TaskEditVariables (LCOM4 4) My Project/TaskEditVariables.vb:5— TaskEditVariables'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: TaskFitView (LCOM4 4) My Project/TaskFitView.vb:3— TaskFitView'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: TaskCreateDrawingOfFlatPattern (LCOM4 4) My Project/TaskCreateDrawingOfFlatPattern.vb:5— TaskCreateDrawingOfFlatPattern'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: TaskUpdateDrawings (LCOM4 4) My Project/TaskUpdateDrawings.vb:3— TaskUpdateDrawings'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: TaskUpdateMaterialFromMaterialTable (LCOM4 4) My Project/TaskUpdateMaterialFromMaterialTable.vb:3— TaskUpdateMaterialFromMaterialTable'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: TaskUpdateModelSizeInVariableTable (LCOM4 4) My Project/TaskUpdateModelSizeInVariableTable.vb:3— TaskUpdateModelSizeInVariableTable'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: TaskUpdateModelStylesFromTemplate (LCOM4 4) My Project/TaskUpdateModelStylesFromTemplate.vb:3— TaskUpdateModelStylesFromTemplate'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.
Hotspot: My Project/Form_Main.vb My Project/Form_Main.vb:1147— My Project/Form_Main.vb changed 16 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 46 in Form_Main.Startup at line 1147. 3 of those changes were fix/bug commits, and the other 13 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-10..2026-11-08, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-10 09:18:45 -06:00' --until='2026-11-08 09:18:45 -06:00' --full-history --no-merges -- My Project/Form_Main.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: My Project/TaskEditProperties.vb My Project/TaskEditProperties.vb:1013— My Project/TaskEditProperties.vb changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 45 in TaskEditProperties.DoFindReplace at line 1013. 1 of those changes was a fix/bug commit, and the other 8 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-10..2026-11-08, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-10 09:18:45 -06:00' --until='2026-11-08 09:18:45 -06:00' --full-history --no-merges -- My Project/TaskEditProperties.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: My Project/TaskCheckDrawings.vb My Project/TaskCheckDrawings.vb:547— My Project/TaskCheckDrawings.vb changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 68 in TaskCheckDrawings.CheckDetachedDimensionsOrAnnotations at line 547. 1 of those changes was a fix/bug commit, and the other 4 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-10..2026-11-08, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-10 09:18:45 -06:00' --until='2026-11-08 09:18:45 -06:00' --full-history --no-merges -- My Project/TaskCheckDrawings.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: My Project/TaskUpdateDrawings.vb My Project/TaskUpdateDrawings.vb:236— My Project/TaskUpdateDrawings.vb changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 38 in TaskUpdateDrawings.ProcessInternal at line 236. 1 of those changes was a fix/bug commit, and the other 5 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-10..2026-11-08, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-10 09:18:45 -06:00' --until='2026-11-08 09:18:45 -06:00' --full-history --no-merges -- My Project/TaskUpdateDrawings.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: My Project/TaskCheckFilename.vb My Project/TaskCheckFilename.vb:350— My Project/TaskCheckFilename.vb changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in TaskCheckFilename.ProcessDraftModels2 at line 350. 1 of those changes was a fix/bug commit, and the other 4 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-10..2026-11-08, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-10 09:18:45 -06:00' --until='2026-11-08 09:18:45 -06:00' --full-history --no-merges -- My Project/TaskCheckFilename.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: My Project/UtilsMaterials.vb My Project/UtilsMaterials.vb:502— My Project/UtilsMaterials.vb changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in UtilsMaterials.UpdateFaces at line 502. 1 of those changes was a fix/bug commit, and the other 3 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-10..2026-11-08, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-10 09:18:45 -06:00' --until='2026-11-08 09:18:45 -06:00' --full-history --no-merges -- My Project/UtilsMaterials.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: My Project/FormPropertyFilter.vb My Project/FormPropertyFilter.vb:474— My Project/FormPropertyFilter.vb changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in FormPropertyFilter.MoveRow at line 474. 1 of those changes was a fix/bug commit, and the other 6 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-10..2026-11-08, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-10 09:18:45 -06:00' --until='2026-11-08 09:18:45 -06:00' --full-history --no-merges -- My Project/FormPropertyFilter.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: My Project/UtilsExecute.vb My Project/UtilsExecute.vb:507— My Project/UtilsExecute.vb changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in UtilsExecute.ProcessFile at line 507. 2 of those changes were fix/bug commits, and the other 2 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-10..2026-11-08, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-10 09:18:45 -06:00' --until='2026-11-08 09:18:45 -06:00' --full-history --no-merges -- My Project/UtilsExecute.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: My Project/FormPropertyInputEditor.vb My Project/FormPropertyInputEditor.vb:232— My Project/FormPropertyInputEditor.vb changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in FormPropertyInputEditor.MoveRow at line 232. 1 of those changes was a fix/bug commit, and the other 4 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-10..2026-11-08, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-10 09:18:45 -06:00' --until='2026-11-08 09:18:45 -06:00' --full-history --no-merges -- My Project/FormPropertyInputEditor.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: My Project/FormVariableInputEditor.vb My Project/FormVariableInputEditor.vb:160— My Project/FormVariableInputEditor.vb changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in FormVariableInputEditor.MoveRow at line 160. 1 of those changes was a fix/bug commit, and the other 2 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-10..2026-11-08, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-10 09:18:45 -06:00' --until='2026-11-08 09:18:45 -06:00' --full-history --no-merges -- My Project/FormVariableInputEditor.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Duplicated block (10 lines × 2) My Project/TaskSaveDrawingAs.vb:662— My Project/TaskSaveDrawingAs.vb:662-671 | My Project/TaskSaveDrawingAs.vb:705-714 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) My Project/TaskSaveModelAs.vb:984— My Project/TaskSaveModelAs.vb:984-993 | My Project/TaskSaveModelAs.vb:1027-1036 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) My Project/TaskEditInteractively.vb:179— My Project/TaskEditInteractively.vb:179-188 | My Project/TaskRunExternalProgram.vb:110-119 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) My Project/TaskCreateDrawingOfFlatPattern.vb:680— My Project/TaskCreateDrawingOfFlatPattern.vb:680-689 | My Project/TaskEditProperties.vb:1379-1388 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) My Project/TaskUpdateBlocks.vb:1201— My Project/TaskUpdateBlocks.vb:1201-1212 | My Project/TaskUpdateMaterialFromMaterialTable.vb:418-427 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) My Project/TaskCheckLinks.vb:488— My Project/TaskCheckLinks.vb:488-497 | My Project/TaskCheckLinks.vb:514-523 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `My Project/TaskCheckLinks.vb:499` calls `GetParent`, `TrimEnd` and `My Project/TaskCheckLinks.vb:524` 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 (10 lines × 2) My Project/UtilsTopLevelAssembly.vb:207— My Project/UtilsTopLevelAssembly.vb:207-217 | My Project/UtilsTopLevelAssembly.vb:222-231 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) My Project/TaskCheckDrawings.vb:592— My Project/TaskCheckDrawings.vb:592-605 | My Project/TaskCheckDrawings.vb:614-627 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) My Project/TaskSaveDrawingAs.vb:629— My Project/TaskSaveDrawingAs.vb:629-642 | My Project/TaskSaveModelAs.vb:960-973 — before extracting anything, compare `My Project/TaskSaveDrawingAs.vb` and `My Project/TaskSaveModelAs.vb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 164 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) My Project/TaskUpdateModelStylesFromTemplate.vb:963— My Project/TaskUpdateModelStylesFromTemplate.vb:963-976 | My Project/TaskUpdateModelStylesFromTemplate.vb:984-997 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) My Project/FormPropertyListCustomize.vb:344— My Project/FormPropertyListCustomize.vb:344-357 | My Project/FormPropertyListCustomize.vb:381-394 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `My Project/FormPropertyListCustomize.vb:342` calls `List` and `My Project/FormPropertyListCustomize.vb:380` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (14 lines × 2) My Project/FormPropertyFilter.vb:750— My Project/FormPropertyFilter.vb:750-763 | My Project/FormVariableInputEditor.vb:507-520 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (14 lines × 2) My Project/Task.vb:279— My Project/Task.vb:279-292 | My Project/Task.vb:304-317 — 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.
TodoComment My Project/HCStructuredStorageDoc.vb:1230— ' ###### TODO: Maybe don't assume string, but check the actual property type and proceed accordingly. ###### — 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 My Project/TaskUpdateBlocks.vb:1045— ' ###### TODO: Check for a duplicate block ###### — 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 My Project/UCEditVariables.vb:76— ' TODO: This should not be needed if properties had setters — 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 My Project/UtilsMaterials.vb:211— ' TODO: Probably need to check if RetainFaceStyleOverrides is enabled. I think this doesn't do that. — 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.
TooManyMethods: Form_Main My Project/Form_Main.vb— TooManyMethods — 3133 significant lines (blank, comment-only and punctuation-only lines excluded), 187 methods. The bar is 30 methods; this is 157 over it, 6.23× 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.
TooManyMethods: UtilsPreferences My Project/UtilsPreferences.vb— TooManyMethods — 846 significant lines (blank, comment-only and punctuation-only lines excluded), 43 methods. The bar is 30 methods; this is 13 over it, 1.43× 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.
TooManyMethods: HCStructuredStorageDoc My Project/HCStructuredStorageDoc.vb— TooManyMethods — 1915 significant lines (blank, comment-only and punctuation-only lines excluded), 36 methods. The bar is 30 methods; this is 6 over it, 1.20× 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.
TooManyMethods: UtilsCommon My Project/UtilsCommon.vb— TooManyMethods — 922 significant lines (blank, comment-only and punctuation-only lines excluded), 31 methods. The bar is 30 methods; this is 1 over it, 1.03× 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 × 3) My Project/TaskUpdateBlocks.vb:402— My Project/TaskUpdateBlocks.vb:402-411 | My Project/TaskUpdateDrawingStylesFromTemplate.vb:173-182 | My Project/TaskUpdateDrawings.vb:183-192 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (10 lines × 3) My Project/TaskCheckDrawings.vb:395— My Project/TaskCheckDrawings.vb:395-404 | My Project/TaskPrint.vb:162-171 | My Project/TaskSaveDrawingAs.vb:219-228 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (10 lines × 3) My Project/TaskCheckMissingDrawing.vb:41— My Project/TaskCheckMissingDrawing.vb:41-50 | My Project/TaskCheckRelationships.vb:67-76 | My Project/TaskSaveModelAs.vb:255-264 — before extracting anything, compare `My Project/TaskCheckMissingDrawing.vb` and `My Project/TaskCheckRelationships.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 3) My Project/TaskCheckPartCopies.vb:8— My Project/TaskCheckPartCopies.vb:8-17 | My Project/TaskUpdateDesignForCost.vb:8-17 | My Project/TaskUpdateFlatPattern.vb:8-17 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (11 lines × 2) My Project/TaskCheckDrawings.vb:1233— My Project/TaskCheckDrawings.vb:1233-1243 | My Project/TaskCheckDrawings.vb:1244-1256 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `My Project/TaskCheckDrawings.vb:1244` calls `Padding` and `My Project/TaskCheckDrawings.vb:1257` 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 (11 lines × 2) My Project/TaskCheckLinks.vb:696— My Project/TaskCheckLinks.vb:696-706 | My Project/TaskUpdateBlocks.vb:1523-1533 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (11 lines × 2) My Project/UCEditVariables.vb:149— My Project/UCEditVariables.vb:149-159 | My Project/UCPropertyFilter.vb:273-283 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (11 lines × 2) My Project/UCEditProperties.vb:39— My Project/UCEditProperties.vb:39-49 | My Project/UCPropertyFilter.vb:52-62 — before extracting anything, compare `My Project/UCEditProperties.vb` and `My Project/UCPropertyFilter.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 63 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) My Project/TaskCreateDrawingOfFlatPattern.vb:581— My Project/TaskCreateDrawingOfFlatPattern.vb:581-588 | My Project/TaskCreateDrawingOfFlatPattern.vb:597-604 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) My Project/TaskSaveDrawingAs.vb:760— My Project/TaskSaveDrawingAs.vb:760-767 | My Project/TaskSaveDrawingAs.vb:778-785 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) My Project/UCTaskControl.vb:191— My Project/UCTaskControl.vb:191-198 | My Project/UCTaskControl.vb:218-225 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) My Project/FormPropertyInputEditor.vb:640— My Project/FormPropertyInputEditor.vb:640-647 | My Project/FormVariableInputEditor.vb:537-544 — before extracting anything, compare `My Project/FormPropertyInputEditor.vb` and `My Project/FormVariableInputEditor.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 106 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) My Project/TaskCreateDrawingOfFlatPattern.vb:646— My Project/TaskCreateDrawingOfFlatPattern.vb:646-652 | My Project/TaskEditProperties.vb:1379-1385 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) My Project/TaskPrint.vb:418— My Project/TaskPrint.vb:418-424 | My Project/TaskSaveDrawingAs.vb:688-694 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) My Project/TaskUpdateMaterialFromMaterialTable.vb:428— My Project/TaskUpdateMaterialFromMaterialTable.vb:428-434 | My Project/TaskUpdateMaterialFromMaterialTable.vb:450-456 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) My Project/TaskFitView.vb:249— My Project/TaskFitView.vb:249-255 | My Project/TaskSaveModelAs.vb:1217-1223 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication· Edited copy of a member (29 corresponding lines) · ×3
Edited copy of a member (29 corresponding lines) My Project/FormPropertyInputEditor.vb:496— My Project/FormPropertyInputEditor.vb:496-525 | My Project/FormVariableInputEditor.vb:434-462 — These two members are one piece of code written twice and then edited apart: 29 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 (29 corresponding lines) My Project/HCPropertiesData.vb:13— My Project/HCPropertiesData.vb:13-44 | My Project/HCPresets.vb:12-40 — These two members are one piece of code written twice and then edited apart: 29 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 (29 corresponding lines) My Project/TaskSetDocumentStatus.vb:95— My Project/TaskSetDocumentStatus.vb:95-123 | My Project/UtilsExecute.vb:734-771 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×3
Edited copy of a member (11 corresponding lines) My Project/UtilsPreferences.vb:741— My Project/UtilsPreferences.vb:741-751 | My Project/UtilsPreferences.vb:823-833 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) My Project/FormEditTaskList.vb:270— My Project/FormEditTaskList.vb:270-280 | My Project/FormPropertyListCustomize.vb:255-266 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) My Project/FormPropertyFilter.vb:582— My Project/FormPropertyFilter.vb:582-592 | My Project/FormPropertyInputEditor.vb:338-348 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (4 corresponding lines) · ×3
Edited copy of a member (4 corresponding lines) My Project/TaskSaveDrawingAs.vb:42— My Project/TaskSaveDrawingAs.vb:42-45 | My Project/TaskSaveModelAs.vb:53-56 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) My Project/TaskSaveDrawingAs.vb:94— My Project/TaskSaveDrawingAs.vb:94-97 | My Project/TaskSaveModelAs.vb:105-108 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) My Project/FormEditTaskList.vb:25— My Project/FormEditTaskList.vb:25-28 | My Project/FormPropertyListCustomize.vb:21-24 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (13 lines × 2) My Project/TaskSaveDrawingAs.vb:651— My Project/TaskSaveDrawingAs.vb:651-663 | My Project/TaskSaveModelAs.vb:973-985 — before extracting anything, compare `My Project/TaskSaveDrawingAs.vb` and `My Project/TaskSaveModelAs.vb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 164 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) My Project/TaskUpdateBlocks.vb:1124— My Project/TaskUpdateBlocks.vb:1124-1136 | My Project/TaskUpdateBlocks.vb:1284-1296 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `My Project/TaskUpdateBlocks.vb:1139` calls `Padding` and `My Project/TaskUpdateBlocks.vb:1299` 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 (13 lines × 2) My Project/TaskCreateDrawingOfFlatPattern.vb:748— My Project/TaskCreateDrawingOfFlatPattern.vb:748-760 | My Project/TaskUpdateDrawingStylesFromTemplate.vb:1279-1291 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (12 lines × 2) My Project/TaskCheckDrawings.vb:1504— My Project/TaskCheckDrawings.vb:1504-1515 | My Project/TaskUpdateDrawings.vb:719-730 — before extracting anything, compare `My Project/TaskCheckDrawings.vb` and `My Project/TaskUpdateDrawings.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) My Project/FormPropertyInputEditor.vb:179— My Project/FormPropertyInputEditor.vb:179-190 | My Project/FormVariableInputEditor.vb:107-118 — before extracting anything, compare `My Project/FormPropertyInputEditor.vb` and `My Project/FormVariableInputEditor.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 106 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) My Project/TaskCheckFlatPattern.vb:60— My Project/TaskCheckFlatPattern.vb:60-71 | My Project/TaskUpdateFlatPattern.vb:59-70 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) My Project/TaskCreateDrawingOfFlatPattern.vb:525— My Project/TaskCreateDrawingOfFlatPattern.vb:525-533 | My Project/TaskUpdateModelStylesFromTemplate.vb:1118-1126 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) My Project/TaskUpdateMaterialFromMaterialTable.vb:597— My Project/TaskUpdateMaterialFromMaterialTable.vb:597-605 | My Project/TaskUpdateMaterialFromMaterialTable.vb:612-620 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) My Project/UCEditProperties.vb:260— My Project/UCEditProperties.vb:260-268 | My Project/UCPropertyFilter.vb:250-258 — before extracting anything, compare `My Project/UCEditProperties.vb` and `My Project/UCPropertyFilter.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 63 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (4 members, 50+ identical tokens) My Project/TaskCheckFilename.vb:601— My Project/TaskCheckFilename.vb:601-644 | My Project/TaskCheckLinks.vb:711-736 | My Project/TaskCheckMaterialNotInMaterialTable.vb:288-319 | My Project/TaskCheckMissingDrawing.vb:163-180 — 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) My Project/TaskUpdateModelStylesFromTemplate.vb:634— My Project/TaskUpdateModelStylesFromTemplate.vb:634-691 | My Project/TaskUpdateModelStylesFromTemplate.vb:700-758 | My Project/TaskUpdateModelStylesFromTemplate.vb:767-824 | My Project/TaskUpdateModelStylesFromTemplate.vb:833-890 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication· Edited copy of a member (33 corresponding lines) · ×2
Edited copy of a member (33 corresponding lines) My Project/ListViewExtended/ListViewExtended/ListViewExtended.vb:68— My Project/ListViewExtended/ListViewExtended/ListViewExtended.vb:68-106 | My Project/ListViewExtended/ListViewExtended/ListViewExtended.vb:110-142 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (33 corresponding lines) My Project/TaskCheckLinks.vb:209— My Project/TaskCheckLinks.vb:209-245 | My Project/TaskUpdateDrawingStylesFromTemplate.vb:843-875 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (30 corresponding lines) · ×2
Edited copy of a member (30 corresponding lines) My Project/UtilsCommon.vb:267— My Project/UtilsCommon.vb:267-296 | My Project/UtilsCommon.vb:304-337 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (30 corresponding lines) My Project/UtilsPropertyFilters.vb:44— My Project/UtilsPropertyFilters.vb:44-73 | My Project/UtilsTopLevelAssembly.vb:250-279 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 18+ corresponding lines) · ×2
Edited copies of one member (4 members, 18+ corresponding lines) My Project/TaskCheckInterference.vb:41— My Project/TaskCheckInterference.vb:41-60 | My Project/TaskCheckMissingDrawing.vb:41-58 | My Project/TaskCheckRelationships.vb:67-88 | My Project/TaskRunExternalProgram.vb:110-130 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 18+ corresponding lines) My Project/TaskCheckLinks.vb:53— My Project/TaskCheckLinks.vb:53-70 | My Project/TaskUpdateBlocks.vb:105-123 | My Project/TaskUpdateBlocks.vb:134-151 | My Project/TaskUpdateBlocks.vb:161-178 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×2
Edited copy of a member (20 corresponding lines) My Project/TaskCheckFlatPattern.vb:52— My Project/TaskCheckFlatPattern.vb:52-71 | My Project/TaskCheckPartCopies.vb:52-73 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) My Project/UtilsCommon.vb:600— My Project/UtilsCommon.vb:600-623 | My Project/UtilsCommon.vb:627-646 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 19+ corresponding lines) · ×2
Edited copies of one member (3 members, 19+ corresponding lines) My Project/TaskCreateDrawingOfFlatPattern.vb:894— My Project/TaskCreateDrawingOfFlatPattern.vb:894-919 | My Project/TaskSaveModelAs.vb:1352-1370 | My Project/TaskUpdateModelSizeInVariableTable.vb:546-566 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 19+ corresponding lines) My Project/FormPropertyFilter.vb:719— My Project/FormPropertyFilter.vb:719-737 | My Project/FormPropertyInputEditor.vb:571-589 | My Project/FormVariableInputEditor.vb:472-490 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×2
Edited copy of a member (12 corresponding lines) My Project/HCStructuredStorageDoc.vb:2576— My Project/HCStructuredStorageDoc.vb:2576-2587 | My Project/HCStructuredStorageDoc.vb:2595-2606 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) My Project/TaskCheckMissingDrawing.vb:89— My Project/TaskCheckMissingDrawing.vb:89-102 | My Project/TaskCheckMissingDrawing.vb:108-119 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×2
Edited copy of a member (10 corresponding lines) My Project/HCPropertiesData.vb:50— My Project/HCPropertiesData.vb:50-62 | My Project/HCPresets.vb:46-55 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) My Project/HCSavedExpressions.vb:182— My Project/HCSavedExpressions.vb:182-191 | My Project/HCPropertyFilter.vb:69-78 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (22 lines × 2) My Project/UCEditProperties.vb:232— My Project/UCEditProperties.vb:232-253 | My Project/UCPropertyFilter.vb:223-244 — before extracting anything, compare `My Project/UCEditProperties.vb` and `My Project/UCPropertyFilter.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 63 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the 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 lines × 2) My Project/UCEditProperties.vb:349— My Project/UCEditProperties.vb:349-371 | My Project/UCTaskControl.vb:250-271 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (17 lines × 2) My Project/UtilsCommon.vb:269— My Project/UtilsCommon.vb:269-285 | My Project/UtilsCommon.vb:306-322 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) My Project/TaskSaveDrawingAs.vb:690— My Project/TaskSaveDrawingAs.vb:690-706 | My Project/TaskSaveModelAs.vb:1012-1028 — before extracting anything, compare `My Project/TaskSaveDrawingAs.vb` and `My Project/TaskSaveModelAs.vb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 164 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the 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 (20 lines × 2) My Project/FormPropertyInputEditor.vb:617— My Project/FormPropertyInputEditor.vb:617-636 | My Project/FormVariableInputEditor.vb:513-532 — before extracting anything, compare `My Project/FormPropertyInputEditor.vb` and `My Project/FormVariableInputEditor.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 106 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the 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 (20 lines × 2) My Project/UtilsTopLevelAssembly.vb:253— My Project/UtilsTopLevelAssembly.vb:253-272 | My Project/UtilsTopLevelAssembly.vb:320-339 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 3) My Project/TaskSaveModelAs.vb:1066— My Project/TaskSaveModelAs.vb:1066-1073 | My Project/TaskSaveModelAs.vb:1076-1083 | My Project/TaskSaveModelAs.vb:1086-1093 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `My Project/TaskSaveModelAs.vb:1076` calls `Padding` and `My Project/TaskSaveModelAs.vb:1096` 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 (8 lines × 3) My Project/TaskCheckMaterialNotInMaterialTable.vb:204— My Project/TaskCheckMaterialNotInMaterialTable.vb:204-212 | My Project/TaskEditProperties.vb:1369-1376 | My Project/TaskUpdateMaterialFromMaterialTable.vb:384-392 — before extracting anything, compare `My Project/TaskCheckMaterialNotInMaterialTable.vb` and `My Project/TaskEditProperties.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6 lines × 2) My Project/TaskCheckMaterialNotInMaterialTable.vb:218— My Project/TaskCheckMaterialNotInMaterialTable.vb:218-223 | My Project/TaskSetDocumentStatus.vb:153-158 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) My Project/FormPropertyInputEditor.vb:652— My Project/FormPropertyInputEditor.vb:652-657 | My Project/FormVariableInputEditor.vb:549-554 — before extracting anything, compare `My Project/FormPropertyInputEditor.vb` and `My Project/FormVariableInputEditor.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 106 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Appears unstructured (no recognised architecture) — ~38.8k production LoC (191 types) across 3 project(s) / 9 namespace(s) with no recognised architectural style or layering — at this size, deliberate module boundaries would help. No DDD/clean/vertical-slice/CQRS/transaction-script organisation was detected — code is likely organised ad hoc, which makes change and onboarding harder as it grows.
PropertyData.New.ctor (cyclomatic 81) My Project/HCPropertiesData.vb:785— PropertyData.New.ctor has cyclomatic complexity 81 (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.
TaskCheckDrawings.CheckDetachedDimensionsOrAnnotations (cyclomatic 68) My Project/TaskCheckDrawings.vb:547— TaskCheckDrawings.CheckDetachedDimensionsOrAnnotations has cyclomatic complexity 68 (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.
TaskUpdateBlocks.ProcessInternal (cyclomatic 54) My Project/TaskUpdateBlocks.vb:449— TaskUpdateBlocks.ProcessInternal has cyclomatic complexity 54 (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.
UtilsExecute.CheckStartConditions (cyclomatic 47) My Project/UtilsExecute.vb:144— UtilsExecute.CheckStartConditions 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_Main.Startup (cyclomatic 46) My Project/Form_Main.vb:1147— Form_Main.Startup 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.
TaskEditProperties.DoFindReplace (cyclomatic 45) My Project/TaskEditProperties.vb:1013— TaskEditProperties.DoFindReplace 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.
MaterialTable.TraverseNodes (cyclomatic 44) My Project/HCStructuredStorageDoc.vb:2229— MaterialTable.TraverseNodes 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.
FormTeamCenterAdd.SearchTeamCenter (cyclomatic 39) My Project/FormTeamCenterAdd.vb:15— FormTeamCenterAdd.SearchTeamCenter has cyclomatic complexity 39 (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.
UtilsFileList.FindFiles (cyclomatic 38) My Project/UtilsFileList.vb:246— UtilsFileList.FindFiles has cyclomatic complexity 38 (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.
TaskUpdateDrawings.ProcessInternal (cyclomatic 38) My Project/TaskUpdateDrawings.vb:236— TaskUpdateDrawings.ProcessInternal has cyclomatic complexity 38 (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.
UtilsFileList.SortByDependency (cyclomatic 37) My Project/UtilsFileList.vb:905— UtilsFileList.SortByDependency 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.
UtilsPreferences.BuildTaskListFromScratch (cyclomatic 37) My Project/UtilsPreferences.vb:984— UtilsPreferences.BuildTaskListFromScratch 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.
UtilsMaterials.UpdateFaces (cyclomatic 33) My Project/UtilsMaterials.vb:502— UtilsMaterials.UpdateFaces 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.
LinkFullNames.ExtractFilenamesFromByteArray (cyclomatic 32) My Project/HCStructuredStorageDoc.vb:1704— LinkFullNames.ExtractFilenamesFromByteArray 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. This is NOT this file's highest cyclomatic complexity: PropertySet.CorrectedOLEPropName (cyclomatic 41) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
TaskCheckDrawings.CheckBoxOptions_Check_Changed (cyclomatic 32) My Project/TaskCheckDrawings.vb:1344— TaskCheckDrawings.CheckBoxOptions_Check_Changed 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.
TaskEditVariables.ProcessInternal (cyclomatic 29) My Project/TaskEditVariables.vb:102— TaskEditVariables.ProcessInternal 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.
UtilsCommon.SubstitutePropertyFormulas (cyclomatic 29) My Project/UtilsCommon.vb:998— UtilsCommon.SubstitutePropertyFormulas 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.
TaskEditProperties.ProcessInternal (cyclomatic 28) My Project/TaskEditProperties.vb:266— TaskEditProperties.ProcessInternal has cyclomatic complexity 28 (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.
TaskCheckFilename.ProcessDraftModels2 (cyclomatic 27) My Project/TaskCheckFilename.vb:350— TaskCheckFilename.ProcessDraftModels2 has cyclomatic complexity 27 (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.
TaskUpdateModelStylesFromTemplate.UpdateBaseFaceStyles (cyclomatic 27) My Project/TaskUpdateModelStylesFromTemplate.vb:1006— TaskUpdateModelStylesFromTemplate.UpdateBaseFaceStyles has cyclomatic complexity 27 (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.
TaskUpdatePhysicalProperties.ProcessInternal (cyclomatic 27) My Project/TaskUpdatePhysicalProperties.vb:96— TaskUpdatePhysicalProperties.ProcessInternal has cyclomatic complexity 27 (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.
TaskUpdateBlocks.DataGridViewOptions_Leave (cyclomatic 26) My Project/TaskUpdateBlocks.vb:1385— TaskUpdateBlocks.DataGridViewOptions_Leave 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.
HCPropertiesData.UpdateFromTemplates (cyclomatic 25) My Project/HCPropertiesData.vb:182— HCPropertiesData.UpdateFromTemplates 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.
UtilsPreferences.SetSEDefaultFolders (cyclomatic 25) My Project/UtilsPreferences.vb:227— UtilsPreferences.SetSEDefaultFolders 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.
TaskCheckDrawings.CheckDrawingTablesOutOfDate (cyclomatic 25) My Project/TaskCheckDrawings.vb:790— TaskCheckDrawings.CheckDrawingTablesOutOfDate 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.
UtilsExecute.ProcessFile (cyclomatic 24) My Project/UtilsExecute.vb:507— UtilsExecute.ProcessFile 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.CopyTemplatesToTasks (cyclomatic 24) My Project/Form_Main.vb:1477— Form_Main.CopyTemplatesToTasks 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.
TaskSaveModelAs.ProcessInternal (cyclomatic 24) My Project/TaskSaveModelAs.vb:315— TaskSaveModelAs.ProcessInternal 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.
BlockLibrary.GetNamesBytes (cyclomatic 23) My Project/HCStructuredStorageDoc.vb:2417— BlockLibrary.GetNamesBytes 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. This is NOT this file's highest cyclomatic complexity: PropertySet.CorrectedOLEPropName (cyclomatic 41) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
HCStructuredStorageDoc.SubstitutePropertyFormulas (cyclomatic 22) My Project/HCStructuredStorageDoc.vb:422— HCStructuredStorageDoc.SubstitutePropertyFormulas 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. This is NOT this file's highest cyclomatic complexity: PropertySet.CorrectedOLEPropName (cyclomatic 41) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
LinkFullNames.GetFullNameFromOLEStream (cyclomatic 22) My Project/HCStructuredStorageDoc.vb:1586— LinkFullNames.GetFullNameFromOLEStream 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. This is NOT this file's highest cyclomatic complexity: PropertySet.CorrectedOLEPropName (cyclomatic 41) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
UtilsExecute.ProcessAll (cyclomatic 22) My Project/UtilsExecute.vb:26— UtilsExecute.ProcessAll 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.
UtilsFileList.New_UpdateFileList (cyclomatic 22) My Project/UtilsFileList.vb:109— UtilsFileList.New_UpdateFileList 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.
UtilsFileList.UpdateLVItem (cyclomatic 21) My Project/UtilsFileList.vb:1199— UtilsFileList.UpdateLVItem 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.
TaskCreateDrawingOfFlatPattern.ProcessInternal (cyclomatic 21) My Project/TaskCreateDrawingOfFlatPattern.vb:285— TaskCreateDrawingOfFlatPattern.ProcessInternal 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.
TaskRunExternalProgram.ProcessInternal (cyclomatic 21) My Project/TaskRunExternalProgram.vb:153— TaskRunExternalProgram.ProcessInternal 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.
FormSolidEdgeExplorer.PopulateTreeView (cyclomatic 20) My Project/FormSolidEdgeExplorer.vb:64— FormSolidEdgeExplorer.PopulateTreeView 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.
TaskUpdateBlocks.CheckStartConditions (cyclomatic 20) My Project/TaskUpdateBlocks.vb:1322— TaskUpdateBlocks.CheckStartConditions 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.
TaskUpdateBlocks.CheckBoxOptions_Check_Changed (cyclomatic 20) My Project/TaskUpdateBlocks.vb:1538— TaskUpdateBlocks.CheckBoxOptions_Check_Changed 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.
UtilsFileList.CheckStartConditions (cyclomatic 20) My Project/UtilsFileList.vb:20— UtilsFileList.CheckStartConditions 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.
UtilsPreferences.SaveFormMainSettings (cyclomatic 20) My Project/UtilsPreferences.vb:32— UtilsPreferences.SaveFormMainSettings 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.
TaskUpdateDrawingStylesFromTemplate.DoReplaceBorders (cyclomatic 20) My Project/TaskUpdateDrawingStylesFromTemplate.vb:321— TaskUpdateDrawingStylesFromTemplate.DoReplaceBorders 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.
FormPropertyInputEditor.CheckInputs (cyclomatic 19) My Project/FormPropertyInputEditor.vb:49— FormPropertyInputEditor.CheckInputs 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.
TaskCheckLinks.GetLinkFilenames (cyclomatic 19) My Project/TaskCheckLinks.vb:248— TaskCheckLinks.GetLinkFilenames 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.
TaskCheckRelationships.CheckFeatures (cyclomatic 19) My Project/TaskCheckRelationships.vb:307— TaskCheckRelationships.CheckFeatures 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.
TaskEditProperties.DoReplacement (cyclomatic 19) My Project/TaskEditProperties.vb:887— TaskEditProperties.DoReplacement 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.
TaskUpdateModelStylesFromTemplate.DoUpdateViewStyles (cyclomatic 19) My Project/TaskUpdateModelStylesFromTemplate.vb:528— TaskUpdateModelStylesFromTemplate.DoUpdateViewStyles 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.ListViewFiles_DragDrop (cyclomatic 18) My Project/Form_Main.vb:2106— Form_Main.ListViewFiles_DragDrop 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.
TaskUpdateModelStylesFromTemplate.ProcessInternal (cyclomatic 18) My Project/TaskUpdateModelStylesFromTemplate.vb:265— TaskUpdateModelStylesFromTemplate.ProcessInternal 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.
UtilsTopLevelAssembly.GetContains (cyclomatic 18) My Project/UtilsTopLevelAssembly.vb:104— UtilsTopLevelAssembly.GetContains 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.
UtilsSEApp.SEStart (cyclomatic 18) My Project/UtilsSEApp.vb:27— UtilsSEApp.SEStart 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.
UtilsExecute.ProcessFiles (cyclomatic 17) My Project/UtilsExecute.vb:420— UtilsExecute.ProcessFiles 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.
TaskCheckDrawings.CheckDrawInView (cyclomatic 17) My Project/TaskCheckDrawings.vb:880— TaskCheckDrawings.CheckDrawInView 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.
TaskSaveDrawingAs.GenerateNewFilename (cyclomatic 17) My Project/TaskSaveDrawingAs.vb:333— TaskSaveDrawingAs.GenerateNewFilename 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.
TaskSaveModelAs.GenerateNewFilename (cyclomatic 17) My Project/TaskSaveModelAs.vb:478— TaskSaveModelAs.GenerateNewFilename 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.
TaskSaveModelAs.CheckBoxOptions_Check_Changed (cyclomatic 17) My Project/TaskSaveModelAs.vb:1216— TaskSaveModelAs.CheckBoxOptions_Check_Changed 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.
HCPropertiesData.ScanFilesForProps (cyclomatic 16) My Project/HCPropertiesData.vb:651— HCPropertiesData.ScanFilesForProps 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.
UtilsDocumentation.BuildReadmeFile (cyclomatic 16) My Project/UtilsDocumentation.vb:92— UtilsDocumentation.BuildReadmeFile 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.
FormPropertyFilter.MoveRow (cyclomatic 16) My Project/FormPropertyFilter.vb:474— FormPropertyFilter.MoveRow 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.
FormPropertyInputEditor.MoveRow (cyclomatic 16) My Project/FormPropertyInputEditor.vb:232— FormPropertyInputEditor.MoveRow 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.
FormVariableInputEditor.MoveRow (cyclomatic 16) My Project/FormVariableInputEditor.vb:160— FormVariableInputEditor.MoveRow 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.
TaskSaveModelAs.SaveAsImage (cyclomatic 16) My Project/TaskSaveModelAs.vb:738— TaskSaveModelAs.SaveAsImage 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.
TaskUpdatePartCopies.ProcessInternal (cyclomatic 16) My Project/TaskUpdatePartCopies.vb:82— TaskUpdatePartCopies.ProcessInternal 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.
UtilsCommon.GetProp (cyclomatic 16) My Project/UtilsCommon.vb:817— UtilsCommon.GetProp 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.
UtilsTopLevelAssembly.FollowLinksBottomUp (cyclomatic 16) My Project/UtilsTopLevelAssembly.vb:453— UtilsTopLevelAssembly.FollowLinksBottomUp 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.
TaskUpdateBlocks.ProcessInternal (cognitive 219) My Project/TaskUpdateBlocks.vb:449— TaskUpdateBlocks.ProcessInternal has cognitive complexity 219 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TaskCheckDrawings.CheckDetachedDimensionsOrAnnotations (cognitive 206) My Project/TaskCheckDrawings.vb:547— TaskCheckDrawings.CheckDetachedDimensionsOrAnnotations has cognitive complexity 206 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TaskEditProperties.DoFindReplace (cognitive 147) My Project/TaskEditProperties.vb:1013— TaskEditProperties.DoFindReplace has cognitive complexity 147 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
MaterialTable.TraverseNodes (cognitive 127) My Project/HCStructuredStorageDoc.vb:2229— MaterialTable.TraverseNodes has cognitive complexity 127 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TaskUpdateDrawings.ProcessInternal (cognitive 124) My Project/TaskUpdateDrawings.vb:236— TaskUpdateDrawings.ProcessInternal has cognitive complexity 124 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
UtilsExecute.CheckStartConditions (cognitive 116) My Project/UtilsExecute.vb:144— UtilsExecute.CheckStartConditions has cognitive complexity 116 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
UtilsFileList.SortByDependency (cognitive 111) My Project/UtilsFileList.vb:905— UtilsFileList.SortByDependency has cognitive complexity 111 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TaskEditVariables.ProcessInternal (cognitive 104) My Project/TaskEditVariables.vb:102— TaskEditVariables.ProcessInternal has cognitive complexity 104 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TaskUpdateModelStylesFromTemplate.UpdateBaseFaceStyles (cognitive 100) My Project/TaskUpdateModelStylesFromTemplate.vb:1006— TaskUpdateModelStylesFromTemplate.UpdateBaseFaceStyles has cognitive complexity 100 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
LinkFullNames.ExtractFilenamesFromByteArray (cognitive 97) My Project/HCStructuredStorageDoc.vb:1704— LinkFullNames.ExtractFilenamesFromByteArray has cognitive complexity 97 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
UtilsFileList.UpdateLVItem (cognitive 96) My Project/UtilsFileList.vb:1199— UtilsFileList.UpdateLVItem has cognitive complexity 96 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TaskCheckFilename.ProcessDraftModels2 (cognitive 92) My Project/TaskCheckFilename.vb:350— TaskCheckFilename.ProcessDraftModels2 has cognitive complexity 92 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TaskCheckRelationships.CheckFeatures (cognitive 90) My Project/TaskCheckRelationships.vb:307— TaskCheckRelationships.CheckFeatures 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.
TaskEditProperties.ProcessInternal (cognitive 90) My Project/TaskEditProperties.vb:266— TaskEditProperties.ProcessInternal 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.
TaskSaveModelAs.ProcessInternal (cognitive 88) My Project/TaskSaveModelAs.vb:315— TaskSaveModelAs.ProcessInternal has cognitive complexity 88 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
FormTeamCenterAdd.SearchTeamCenter (cognitive 86) My Project/FormTeamCenterAdd.vb:15— FormTeamCenterAdd.SearchTeamCenter has cognitive complexity 86 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
UtilsFileList.FindFiles (cognitive 82) My Project/UtilsFileList.vb:246— UtilsFileList.FindFiles has cognitive complexity 82 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
UtilsCommon.SubstitutePropertyFormulas (cognitive 77) My Project/UtilsCommon.vb:998— UtilsCommon.SubstitutePropertyFormulas 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.
UtilsMaterials.UpdateFaces (cognitive 75) My Project/UtilsMaterials.vb:502— UtilsMaterials.UpdateFaces 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.
HCPropertiesData.UpdateFromTemplates (cognitive 74) My Project/HCPropertiesData.vb:182— HCPropertiesData.UpdateFromTemplates 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.
LinkFullNames.GetFullNameFromOLEStream (cognitive 70) My Project/HCStructuredStorageDoc.vb:1586— LinkFullNames.GetFullNameFromOLEStream 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.
TaskCheckDrawings.CheckDrawingTablesOutOfDate (cognitive 68) My Project/TaskCheckDrawings.vb:790— TaskCheckDrawings.CheckDrawingTablesOutOfDate 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_Main.CopyTemplatesToTasks (cognitive 67) My Project/Form_Main.vb:1477— Form_Main.CopyTemplatesToTasks has cognitive complexity 67 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TaskEditProperties.DoReplacement (cognitive 66) My Project/TaskEditProperties.vb:887— TaskEditProperties.DoReplacement has cognitive complexity 66 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TaskUpdateBlocks.DataGridViewOptions_Leave (cognitive 64) My Project/TaskUpdateBlocks.vb:1385— TaskUpdateBlocks.DataGridViewOptions_Leave has cognitive complexity 64 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TaskUpdatePhysicalProperties.ProcessInternal (cognitive 64) My Project/TaskUpdatePhysicalProperties.vb:96— TaskUpdatePhysicalProperties.ProcessInternal has cognitive complexity 64 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
UtilsExecute.ProcessFile (cognitive 63) My Project/UtilsExecute.vb:507— UtilsExecute.ProcessFile 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.
TaskCreateDrawingOfFlatPattern.ProcessInternal (cognitive 61) My Project/TaskCreateDrawingOfFlatPattern.vb:285— TaskCreateDrawingOfFlatPattern.ProcessInternal has cognitive complexity 61 (threshold 15). To reduce it, flatten the nesting: invert conditions into early 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.Startup (cognitive 60) My Project/Form_Main.vb:1147— Form_Main.Startup 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.
UtilsTopLevelAssembly.FollowLinksBottomUp (cognitive 60) My Project/UtilsTopLevelAssembly.vb:453— UtilsTopLevelAssembly.FollowLinksBottomUp 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.
TaskCheckDrawings.CheckDrawInView (cognitive 58) My Project/TaskCheckDrawings.vb:880— TaskCheckDrawings.CheckDrawInView 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.
TaskUpdatePartCopies.ProcessInternal (cognitive 58) My Project/TaskUpdatePartCopies.vb:82— TaskUpdatePartCopies.ProcessInternal 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.
TaskUpdateModelStylesFromTemplate.DoUpdateViewStyles (cognitive 57) My Project/TaskUpdateModelStylesFromTemplate.vb:528— TaskUpdateModelStylesFromTemplate.DoUpdateViewStyles 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.
HCPropertiesData.ScanFilesForProps (cognitive 56) My Project/HCPropertiesData.vb:651— HCPropertiesData.ScanFilesForProps has cognitive complexity 56 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
UtilsFileList.CheckStartConditions (cognitive 56) My Project/UtilsFileList.vb:20— UtilsFileList.CheckStartConditions has cognitive complexity 56 (threshold 15). To reduce it, flatten the nesting: invert conditions into early 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.ListViewFiles_DragDrop (cognitive 56) My Project/Form_Main.vb:2106— Form_Main.ListViewFiles_DragDrop has cognitive complexity 56 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
FormPropertyInputEditor.CheckInputs (cognitive 55) My Project/FormPropertyInputEditor.vb:49— FormPropertyInputEditor.CheckInputs 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.
TaskCheckDrawings.CheckDimensionsOverridden (cognitive 55) My Project/TaskCheckDrawings.vb:922— TaskCheckDrawings.CheckDimensionsOverridden 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.
TaskUpdateBlocks.CheckStartConditions (cognitive 54) My Project/TaskUpdateBlocks.vb:1322— TaskUpdateBlocks.CheckStartConditions has cognitive complexity 54 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
UtilsTopLevelAssembly.GetContains (cognitive 54) My Project/UtilsTopLevelAssembly.vb:104— UtilsTopLevelAssembly.GetContains has cognitive complexity 54 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
HCStructuredStorageDoc.SubstitutePropertyFormulas (cognitive 53) My Project/HCStructuredStorageDoc.vb:422— HCStructuredStorageDoc.SubstitutePropertyFormulas has cognitive complexity 53 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
UtilsFileList.GetLinks (cognitive 52) My Project/UtilsFileList.vb:850— UtilsFileList.GetLinks 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.
TaskCheckLinks.GetLinkFilenames (cognitive 52) My Project/TaskCheckLinks.vb:248— TaskCheckLinks.GetLinkFilenames 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.
UtilsDocumentation.BuildReadmeFile (cognitive 50) My Project/UtilsDocumentation.vb:92— UtilsDocumentation.BuildReadmeFile 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.
TaskUpdateModelSizeInVariableTable.ProcessInternal (cognitive 48) My Project/TaskUpdateModelSizeInVariableTable.vb:192— TaskUpdateModelSizeInVariableTable.ProcessInternal 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.
TaskUpdateDrawingStylesFromTemplate.DoReplaceBorders (cognitive 46) My Project/TaskUpdateDrawingStylesFromTemplate.vb:321— TaskUpdateDrawingStylesFromTemplate.DoReplaceBorders has cognitive complexity 46 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
FormSolidEdgeExplorer.PopulateTreeView (cognitive 45) My Project/FormSolidEdgeExplorer.vb:64— FormSolidEdgeExplorer.PopulateTreeView 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.
UtilsSEApp.SEStart (cognitive 45) My Project/UtilsSEApp.vb:27— UtilsSEApp.SEStart 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.
TaskUpdateDrawingStylesFromTemplate.CheckStartConditions (cognitive 44) My Project/TaskUpdateDrawingStylesFromTemplate.vb:1059— TaskUpdateDrawingStylesFromTemplate.CheckStartConditions 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.
UtilsCommon.GetDocRange (cognitive 44) My Project/UtilsCommon.vb:73— UtilsCommon.GetDocRange 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.
UtilsCommon.CopyProperties (cognitive 44) My Project/UtilsCommon.vb:1236— UtilsCommon.CopyProperties 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.
TaskEditProperties.ProcessInternal (cognitive 43) My Project/TaskEditProperties.vb:166— TaskEditProperties.ProcessInternal 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.
UtilsTopLevelAssembly.VisitLinks (cognitive 43) My Project/UtilsTopLevelAssembly.vb:193— UtilsTopLevelAssembly.VisitLinks 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.
TaskCheckFilename.ProcessFile2 (cognitive 42) My Project/TaskCheckFilename.vb:273— TaskCheckFilename.ProcessFile2 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.
TaskSaveDrawingAs.GenerateNewFilename (cognitive 41) My Project/TaskSaveDrawingAs.vb:333— TaskSaveDrawingAs.GenerateNewFilename 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.
TaskSaveModelAs.GenerateNewFilename (cognitive 41) My Project/TaskSaveModelAs.vb:478— TaskSaveModelAs.GenerateNewFilename 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.
HCStructuredStorageDoc.ProcessFormula (cognitive 40) My Project/HCStructuredStorageDoc.vb:602— HCStructuredStorageDoc.ProcessFormula has cognitive complexity 40 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TaskRunExternalProgram.ProcessInternal (cognitive 40) My Project/TaskRunExternalProgram.vb:153— TaskRunExternalProgram.ProcessInternal has cognitive complexity 40 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
UtilsExecute.ProcessAll (cognitive 39) My Project/UtilsExecute.vb:26— UtilsExecute.ProcessAll 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.
UtilsPreferences.SetSEDefaultFolders (cognitive 39) My Project/UtilsPreferences.vb:227— UtilsPreferences.SetSEDefaultFolders 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.
TaskCheckPartCopies.ProcessInternal (cognitive 39) My Project/TaskCheckPartCopies.vb:47— TaskCheckPartCopies.ProcessInternal 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.
LinkFullNames.ProcessRootStorage (cognitive 38) My Project/HCStructuredStorageDoc.vb:1525— LinkFullNames.ProcessRootStorage 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.
HCSavedExpressions.PopulateFromTextFile (cognitive 37) My Project/HCSavedExpressions.vb:35— HCSavedExpressions.PopulateFromTextFile 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.
BlockLibrary.GetNamesBytes (cognitive 37) My Project/HCStructuredStorageDoc.vb:2417— BlockLibrary.GetNamesBytes 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.
UtilsPreferences.BuildTaskListFromScratch (cognitive 36) My Project/UtilsPreferences.vb:984— UtilsPreferences.BuildTaskListFromScratch 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.
UtilsCommon.GetProp (cognitive 36) My Project/UtilsCommon.vb:817— UtilsCommon.GetProp 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.
UtilsTopLevelAssembly.GetWhereUsedBottomUp (cognitive 36) My Project/UtilsTopLevelAssembly.vb:568— UtilsTopLevelAssembly.GetWhereUsedBottomUp 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.
TaskUpdateBlocks.DoBSAddByName (cognitive 35) My Project/TaskUpdateBlocks.vb:838— TaskUpdateBlocks.DoBSAddByName 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.
UtilsPowerShell.RunScript (cognitive 35) My Project/UtilsPowerShell.vb:20— UtilsPowerShell.RunScript 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.
TaskBreakLinks.DoBreakDraftSymbols (cognitive 35) My Project/TaskBreakLinks.vb:465— TaskBreakLinks.DoBreakDraftSymbols 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.
TaskSaveModelAs.SaveAsFlatDXF (cognitive 34) My Project/TaskSaveModelAs.vb:641— TaskSaveModelAs.SaveAsFlatDXF 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.
TaskEditProperties.DoReplacement2 (cognitive 33) My Project/TaskEditProperties.vb:632— TaskEditProperties.DoReplacement2 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.
TaskEditProperties.GetPropValue2 (cognitive 33) My Project/TaskEditProperties.vb:707— TaskEditProperties.GetPropValue2 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.
UtilsTopLevelAssembly.GetLinksBottomUp (cognitive 33) My Project/UtilsTopLevelAssembly.vb:352— UtilsTopLevelAssembly.GetLinksBottomUp 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.
UtilsFileList.New_UpdateFileList (cognitive 32) My Project/UtilsFileList.vb:109— UtilsFileList.New_UpdateFileList 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.
TaskCheckDrawings.CheckDrawingViewsOutOfDate (cognitive 32) My Project/TaskCheckDrawings.vb:496— TaskCheckDrawings.CheckDrawingViewsOutOfDate 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.
FormPropertyFilter.UCSelectionChanged (cognitive 31) My Project/FormPropertyFilter.vb:596— FormPropertyFilter.UCSelectionChanged 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.
FormPropertyInputEditor.UCSelectionChanged (cognitive 31) My Project/FormPropertyInputEditor.vb:352— FormPropertyInputEditor.UCSelectionChanged 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.
FormVariableInputEditor.UCSelectionChanged (cognitive 31) My Project/FormVariableInputEditor.vb:334— FormVariableInputEditor.UCSelectionChanged 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.
UtilsPropertyFilters.ProcessFile (cognitive 31) My Project/UtilsPropertyFilters.vb:105— UtilsPropertyFilters.ProcessFile 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.
TaskSaveDrawingAs.CheckStartConditions (cognitive 31) My Project/TaskSaveDrawingAs.vb:805— TaskSaveDrawingAs.CheckStartConditions 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.
TaskUpdateBlocks.BlockLibraryBlockNames.Set (cognitive 30) My Project/TaskUpdateBlocks.vb:187— TaskUpdateBlocks.BlockLibraryBlockNames.Set 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.BT_ExportList_Click (cognitive 30) My Project/Form_Main.vb:2369— Form_Main.BT_ExportList_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.
FormPropertyFilter.MoveRow (cognitive 30) My Project/FormPropertyFilter.vb:474— FormPropertyFilter.MoveRow 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.
FormPropertyInputEditor.MoveRow (cognitive 30) My Project/FormPropertyInputEditor.vb:232— FormPropertyInputEditor.MoveRow 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.
FormVariableInputEditor.MoveRow (cognitive 30) My Project/FormVariableInputEditor.vb:160— FormVariableInputEditor.MoveRow 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.
TaskBreakLinks.DoBreakDesignCopies (cognitive 30) My Project/TaskBreakLinks.vb:220— TaskBreakLinks.DoBreakDesignCopies 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.
TaskUpdateModelStylesFromTemplate.DoUpdateTextStyles (cognitive 30) My Project/TaskUpdateModelStylesFromTemplate.vb:629— TaskUpdateModelStylesFromTemplate.DoUpdateTextStyles 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. This shape REPEATS in the file: 3 other methods here (TaskUpdateModelStylesFromTemplate.DoUpdateTextCharStyles, TaskUpdateModelStylesFromTemplate.DoUpdateLinearStyles, TaskUpdateModelStylesFromTemplate.DoUpdateDimensionStyles) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 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.
TaskUpdateModelStylesFromTemplate.DoUpdateTextCharStyles (cognitive 30) My Project/TaskUpdateModelStylesFromTemplate.vb:695— TaskUpdateModelStylesFromTemplate.DoUpdateTextCharStyles 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. This shape REPEATS in the file: 3 other methods here (TaskUpdateModelStylesFromTemplate.DoUpdateTextStyles, TaskUpdateModelStylesFromTemplate.DoUpdateLinearStyles, TaskUpdateModelStylesFromTemplate.DoUpdateDimensionStyles) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 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.
TaskUpdateModelStylesFromTemplate.DoUpdateLinearStyles (cognitive 30) My Project/TaskUpdateModelStylesFromTemplate.vb:762— TaskUpdateModelStylesFromTemplate.DoUpdateLinearStyles 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. This shape REPEATS in the file: 3 other methods here (TaskUpdateModelStylesFromTemplate.DoUpdateTextStyles, TaskUpdateModelStylesFromTemplate.DoUpdateTextCharStyles, TaskUpdateModelStylesFromTemplate.DoUpdateDimensionStyles) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 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.
TaskUpdateModelStylesFromTemplate.DoUpdateDimensionStyles (cognitive 30) My Project/TaskUpdateModelStylesFromTemplate.vb:828— TaskUpdateModelStylesFromTemplate.DoUpdateDimensionStyles 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. This shape REPEATS in the file: 3 other methods here (TaskUpdateModelStylesFromTemplate.DoUpdateTextStyles, TaskUpdateModelStylesFromTemplate.DoUpdateTextCharStyles, TaskUpdateModelStylesFromTemplate.DoUpdateLinearStyles) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 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.
FormEditTaskList.MoveRow (cognitive 29) My Project/FormEditTaskList.vb:87— FormEditTaskList.MoveRow 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.
FormPropertyListCustomize.MoveRow (cognitive 29) My Project/FormPropertyListCustomize.vb:86— FormPropertyListCustomize.MoveRow 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.
UtilsFileList.PopulateListView (cognitive 28) My Project/UtilsFileList.vb:480— UtilsFileList.PopulateListView 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_Main.New.ctor (cognitive 28) My Project/Form_Main.vb:1090— Form_Main.New.ctor 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.
TaskEditProperties.InitiateEdit2 (cognitive 28) My Project/TaskEditProperties.vb:434— TaskEditProperties.InitiateEdit2 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.
TaskUpdateDrawingStylesFromTemplate.DoTableStyles (cognitive 28) My Project/TaskUpdateDrawingStylesFromTemplate.vb:656— TaskUpdateDrawingStylesFromTemplate.DoTableStyles 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.
UtilsExecute.SetEndingStatus (cognitive 27) My Project/UtilsExecute.vb:775— UtilsExecute.SetEndingStatus 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.
TaskSaveModelAs.CheckStartConditions (cognitive 27) My Project/TaskSaveModelAs.vb:1132— TaskSaveModelAs.CheckStartConditions 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.
TaskUpdateBlocks.ManuallyAddedBlockNames.Set (cognitive 26) My Project/TaskUpdateBlocks.vb:233— TaskUpdateBlocks.ManuallyAddedBlockNames.Set 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.
TaskCheckRelationships.CheckOccurrences (cognitive 26) My Project/TaskCheckRelationships.vb:253— TaskCheckRelationships.CheckOccurrences 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.
TaskUpdateBlocks.ButtonOptions_Click (cognitive 25) My Project/TaskUpdateBlocks.vb:1639— TaskUpdateBlocks.ButtonOptions_Click 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.
UtilsFileList.GetFileNames (cognitive 25) My Project/UtilsFileList.vb:715— UtilsFileList.GetFileNames 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.
TaskSaveModelAs.SaveAsImage (cognitive 25) My Project/TaskSaveModelAs.vb:738— TaskSaveModelAs.SaveAsImage 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.
TaskCheckLinks.CheckLinks (cognitive 24) My Project/TaskCheckLinks.vb:319— TaskCheckLinks.CheckLinks 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.
TaskEditProperties.DoFormulaSubstitution2 (cognitive 24) My Project/TaskEditProperties.vb:565— TaskEditProperties.DoFormulaSubstitution2 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.
TaskUpdateDrawingStylesFromTemplate.DoDimensionStyles (cognitive 24) My Project/TaskUpdateDrawingStylesFromTemplate.vb:481— TaskUpdateDrawingStylesFromTemplate.DoDimensionStyles 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.
UtilsCommon.GetSheets (cognitive 24) My Project/UtilsCommon.vb:391— UtilsCommon.GetSheets 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.
HCStructuredStorageDoc.GetProp (cognitive 23) My Project/HCStructuredStorageDoc.vb:700— HCStructuredStorageDoc.GetProp 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.
TaskUpdateBlocks.AddBlockOccurrences (cognitive 23) My Project/TaskUpdateBlocks.vb:1011— TaskUpdateBlocks.AddBlockOccurrences 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.
UtilsExecute.ProcessFiles (cognitive 23) My Project/UtilsExecute.vb:420— UtilsExecute.ProcessFiles 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.
FormExpressionEditor.BT_SaveAs_Click (cognitive 23) My Project/FormExpressionEditor.vb:781— FormExpressionEditor.BT_SaveAs_Click 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.
TaskCheckRelationships.CheckAssemblySketches (cognitive 23) My Project/TaskCheckRelationships.vb:178— TaskCheckRelationships.CheckAssemblySketches 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.
TaskUpdateModelSizeInVariableTable.CheckStartConditions (cognitive 23) My Project/TaskUpdateModelSizeInVariableTable.vb:466— TaskUpdateModelSizeInVariableTable.CheckStartConditions 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.
TaskUpdateModelStylesFromTemplate.ProcessInternal (cognitive 23) My Project/TaskUpdateModelStylesFromTemplate.vb:265— TaskUpdateModelStylesFromTemplate.ProcessInternal 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.
TaskUpdateModelStylesFromTemplate.GetBaseStyles (cognitive 23) My Project/TaskUpdateModelStylesFromTemplate.vb:914— TaskUpdateModelStylesFromTemplate.GetBaseStyles 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.
FormPropertyFilter.CheckFormula (cognitive 22) My Project/FormPropertyFilter.vb:282— FormPropertyFilter.CheckFormula 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.
TaskBreakLinks.ProcessPropertyText (cognitive 22) My Project/TaskBreakLinks.vb:402— TaskBreakLinks.ProcessPropertyText 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.
TaskCheckFilename.CheckStartConditions (cognitive 21) My Project/TaskCheckFilename.vb:561— TaskCheckFilename.CheckStartConditions 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_Main.BT_MoveToRecycleBin_Click (cognitive 21) My Project/Form_Main.vb:2496— Form_Main.BT_MoveToRecycleBin_Click 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.
TaskUpdateDrawingStylesFromTemplate.DoLinearStyles (cognitive 21) My Project/TaskUpdateDrawingStylesFromTemplate.vb:602— TaskUpdateDrawingStylesFromTemplate.DoLinearStyles 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. This shape REPEATS in the file: 2 other methods here (TaskUpdateDrawingStylesFromTemplate.DoTextCharStyles, TaskUpdateDrawingStylesFromTemplate.DoTextStyles) 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.
TaskUpdateDrawingStylesFromTemplate.DoTextCharStyles (cognitive 21) My Project/TaskUpdateDrawingStylesFromTemplate.vb:732— TaskUpdateDrawingStylesFromTemplate.DoTextCharStyles 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. This shape REPEATS in the file: 2 other methods here (TaskUpdateDrawingStylesFromTemplate.DoLinearStyles, TaskUpdateDrawingStylesFromTemplate.DoTextStyles) 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.
TaskUpdateDrawingStylesFromTemplate.DoTextStyles (cognitive 21) My Project/TaskUpdateDrawingStylesFromTemplate.vb:785— TaskUpdateDrawingStylesFromTemplate.DoTextStyles 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. This shape REPEATS in the file: 2 other methods here (TaskUpdateDrawingStylesFromTemplate.DoLinearStyles, TaskUpdateDrawingStylesFromTemplate.DoTextCharStyles) 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.
TaskUpdateDrawingStylesFromTemplate.MoveRow (cognitive 21) My Project/TaskUpdateDrawingStylesFromTemplate.vb:1154— TaskUpdateDrawingStylesFromTemplate.MoveRow 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.
UtilsFileList.UpdatePropertiesColumns (cognitive 20) My Project/UtilsFileList.vb:1116— UtilsFileList.UpdatePropertiesColumns 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.
FormExpressionEditor.ButtonOK_Click (cognitive 20) My Project/FormExpressionEditor.vb:373— FormExpressionEditor.ButtonOK_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.
FormPropertyFilter.UpdateVariablesAndFormula (cognitive 20) My Project/FormPropertyFilter.vb:344— FormPropertyFilter.UpdateVariablesAndFormula 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.
TaskCheckFlatPattern.ProcessInternal (cognitive 20) My Project/TaskCheckFlatPattern.vb:47— TaskCheckFlatPattern.ProcessInternal 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.
TaskSaveDrawingAs.SaveAsDrawing (cognitive 20) My Project/TaskSaveDrawingAs.vb:519— TaskSaveDrawingAs.SaveAsDrawing 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.
TaskUpdateDrawingStylesFromTemplate.DoDrawingViewStyles (cognitive 20) My Project/TaskUpdateDrawingStylesFromTemplate.vb:554— TaskUpdateDrawingStylesFromTemplate.DoDrawingViewStyles 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.
Prop.SetValue (cognitive 19) My Project/HCStructuredStorageDoc.vb:1418— Prop.SetValue 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.
UtilsExecute.SetStartingStatus (cognitive 19) My Project/UtilsExecute.vb:729— UtilsExecute.SetStartingStatus 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.
UtilsMaterials.GetModelOverrides (cognitive 19) My Project/UtilsMaterials.vb:785— UtilsMaterials.GetModelOverrides 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.
UtilsPreferences.SaveFormMainSettings (cognitive 19) My Project/UtilsPreferences.vb:32— UtilsPreferences.SaveFormMainSettings 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.
FormBlockLibraryBlockNames.ButtonOK_Click (cognitive 18) My Project/FormBlockLibraryBlockNames.vb:189— FormBlockLibraryBlockNames.ButtonOK_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.
HCPropertiesData.Populate (cognitive 18) My Project/HCPropertiesData.vb:421— HCPropertiesData.Populate 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.
TaskUpdateBlocks.PlaceBlockOccurrence (cognitive 18) My Project/TaskUpdateBlocks.vb:913— TaskUpdateBlocks.PlaceBlockOccurrence 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.ListViewFiles_KeyUp (cognitive 18) My Project/Form_Main.vb:2277— Form_Main.ListViewFiles_KeyUp 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.
FormEditInteractively.FormEditInteractively_Load (cognitive 18) My Project/FormEditInteractively.vb:37— FormEditInteractively.FormEditInteractively_Load 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.
FormExpressionEditor.ProcessExpression (cognitive 18) My Project/FormExpressionEditor.vb:464— FormExpressionEditor.ProcessExpression 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.
FormPropertyFilter.CheckInputs (cognitive 18) My Project/FormPropertyFilter.vb:85— FormPropertyFilter.CheckInputs 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.
UCPropertyFilter.FilterPropertyNames (cognitive 18) My Project/UCPropertyFilter.vb:168— UCPropertyFilter.FilterPropertyNames 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.
TaskCheckRelationships.CheckSketches (cognitive 18) My Project/TaskCheckRelationships.vb:389— TaskCheckRelationships.CheckSketches 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.
TaskEditProperties.CheckStartConditions (cognitive 18) My Project/TaskEditProperties.vb:1397— TaskEditProperties.CheckStartConditions 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.
TaskPrint.ProcessInternal (cognitive 18) My Project/TaskPrint.vb:217— TaskPrint.ProcessInternal 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.
UtilsTopLevelAssembly.ReportUnrelatedFilesOLD (cognitive 18) My Project/UtilsTopLevelAssembly.vb:284— UtilsTopLevelAssembly.ReportUnrelatedFilesOLD 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.
UCEditProperties.FilterPropertyNames (cognitive 18) My Project/UCEditProperties.vb:145— UCEditProperties.FilterPropertyNames 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.
UCTaskControl.UpdateAppliesToCBs (cognitive 18) My Project/UCTaskControl.vb:52— UCTaskControl.UpdateAppliesToCBs 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.
HCSavedExpressions.GetSavedExpressionFromShorthandText (cognitive 17) My Project/HCSavedExpressions.vb:194— HCSavedExpressions.GetSavedExpressionFromShorthandText 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.
FormExpressionEditor.ProcessExpressionParameters (cognitive 17) My Project/FormExpressionEditor.vb:542— FormExpressionEditor.ProcessExpressionParameters 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.
TaskBreakLinks.DoBreakConstructionCopies (cognitive 17) My Project/TaskBreakLinks.vb:273— TaskBreakLinks.DoBreakConstructionCopies 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.
TaskCheckLinks.UpdateSearchDirectoriesDGV (cognitive 17) My Project/TaskCheckLinks.vb:595— TaskCheckLinks.UpdateSearchDirectoriesDGV 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.
TaskFitView.ProcessInternal (cognitive 17) My Project/TaskFitView.vb:113— TaskFitView.ProcessInternal 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.
TaskUpdateModelSizeInVariableTable.CheckDuplicates (cognitive 17) My Project/TaskUpdateModelSizeInVariableTable.vb:301— TaskUpdateModelSizeInVariableTable.CheckDuplicates 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.
UtilsCommon.GlobToRegex (cognitive 17) My Project/UtilsCommon.vb:455— UtilsCommon.GlobToRegex 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.
LinkFullNames.FormatByteString (cognitive 16) My Project/HCStructuredStorageDoc.vb:2025— LinkFullNames.FormatByteString 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.
TaskUpdateBlocks.DoWSAddByName (cognitive 16) My Project/TaskUpdateBlocks.vb:737— TaskUpdateBlocks.DoWSAddByName 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.
UtilsFileList.CreateColumns (cognitive 16) My Project/UtilsFileList.vb:1174— UtilsFileList.CreateColumns 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.TaskHeaderToggleAssemblyButton_Click (cognitive 16) My Project/Form_Main.vb:2830— Form_Main.TaskHeaderToggleAssemblyButton_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: 3 other methods here (Form_Main.TaskHeaderTogglePartButton_Click, Form_Main.TaskHeaderToggleSheetmetalButton_Click, Form_Main.TaskHeaderToggleDraftButton_Click) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 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.TaskHeaderTogglePartButton_Click (cognitive 16) My Project/Form_Main.vb:2857— Form_Main.TaskHeaderTogglePartButton_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: 3 other methods here (Form_Main.TaskHeaderToggleAssemblyButton_Click, Form_Main.TaskHeaderToggleSheetmetalButton_Click, Form_Main.TaskHeaderToggleDraftButton_Click) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 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.TaskHeaderToggleSheetmetalButton_Click (cognitive 16) My Project/Form_Main.vb:2883— Form_Main.TaskHeaderToggleSheetmetalButton_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: 3 other methods here (Form_Main.TaskHeaderToggleAssemblyButton_Click, Form_Main.TaskHeaderTogglePartButton_Click, Form_Main.TaskHeaderToggleDraftButton_Click) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 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.TaskHeaderToggleDraftButton_Click (cognitive 16) My Project/Form_Main.vb:2909— Form_Main.TaskHeaderToggleDraftButton_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: 3 other methods here (Form_Main.TaskHeaderToggleAssemblyButton_Click, Form_Main.TaskHeaderTogglePartButton_Click, Form_Main.TaskHeaderToggleSheetmetalButton_Click) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 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.ButtonPresetSave_Click (cognitive 16) My Project/Form_Main.vb:3940— Form_Main.ButtonPresetSave_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.
Task.SetFormState (cognitive 16) My Project/Task.vb:435— Task.SetFormState 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.
TaskCheckMaterialNotInMaterialTable.ProcessInternal (cognitive 16) My Project/TaskCheckMaterialNotInMaterialTable.vb:136— TaskCheckMaterialNotInMaterialTable.ProcessInternal 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.
TaskEditProperties.DoFormulaSubstitution (cognitive 16) My Project/TaskEditProperties.vb:980— TaskEditProperties.DoFormulaSubstitution 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.
TaskCreateDrawingOfFlatPattern.ButtonOptions_Click (cognitive 16) My Project/TaskCreateDrawingOfFlatPattern.vb:821— TaskCreateDrawingOfFlatPattern.ButtonOptions_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.
TaskUpdateModelStylesFromTemplate.ButtonOptions_Click (cognitive 16) My Project/TaskUpdateModelStylesFromTemplate.vb:1275— TaskUpdateModelStylesFromTemplate.ButtonOptions_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.
Near-duplicate member pair (67 shared lines) My Project/TaskSaveDrawingAs.vb:615— My Project/TaskSaveDrawingAs.vb:615-802 | My Project/TaskSaveModelAs.vb:946-1129 — These two members are variants of one another: 67 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Members sharing a duplicated core (22 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (22 members, 50+ identical tokens) My Project/TaskBreakLinks.vb:511— My Project/TaskBreakLinks.vb:511-582 | My Project/TaskCheckDrawings.vb:1020-1294 | My Project/TaskCheckFilename.vb:464-558 | My Project/TaskCheckInterference.vb:142-174 | My Project/TaskCheckLinks.vb:362-434 | My Project/TaskCheckMaterialNotInMaterialTable.vb:187-234 | My Project/TaskCheckMissingDrawing.vb:125-148 | My Project/TaskCheckRelationships.vb:508-547 | My Project/TaskCreateDrawingOfFlatPattern.vb:515-694 | My Project/TaskEditInteractively.vb:343-515 | My Project/TaskEditProperties.vb:1313-1394 | My Project/TaskFitView.vb:187-224 | My Project/TaskSaveDrawingAs.vb:615-802 | My Project/TaskSetDocumentStatus.vb:129-171 | My Project/TaskUpdateBlocks.vb:1070-1319 | My Project/TaskUpdateDrawingStylesFromTemplate.vb:919-1056 | My Project/TaskUpdateDrawings.vb:528-639 | My Project/TaskUpdateMaterialFromMaterialTable.vb:366-509 | My Project/TaskUpdateModelSizeInVariableTable.vb:336-463 | My Project/TaskUpdateModelStylesFromTemplate.vb:1109-1248 | My Project/TaskUpdatePartCopies.vb:184-207 | My Project/TaskUpdatePhysicalProperties.vb:285-314 — These 22 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 22 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 22 times.
D4 · Code Duplication· Members sharing a duplicated core (8 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (8 members, 50+ identical tokens) My Project/TaskCheckLinks.vb:362— My Project/TaskCheckLinks.vb:362-434 | My Project/TaskCreateDrawingOfFlatPattern.vb:515-694 | My Project/TaskEditInteractively.vb:343-515 | My Project/TaskEditProperties.vb:1313-1394 | My Project/TaskRunExternalProgram.vb:361-425 | My Project/TaskSaveModelAs.vb:946-1129 | My Project/TaskUpdateBlocks.vb:1070-1319 | My Project/TaskUpdateDrawingStylesFromTemplate.vb:919-1056 — These 8 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 8 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 8 times.
D4 · Code Duplication· Members sharing a duplicated core (7 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (7 members, 50+ identical tokens) My Project/TaskCheckMaterialNotInMaterialTable.vb:70— My Project/TaskCheckMaterialNotInMaterialTable.vb:70-92 | My Project/TaskEditVariables.vb:56-79 | My Project/TaskShowHideConstructions.vb:388-404 | My Project/TaskUpdateModelSizeInVariableTable.vb:143-169 | My Project/TaskUpdateModelStylesFromTemplate.vb:210-242 | My Project/TaskUpdatePartCopies.vb:40-59 | My Project/TaskUpdatePhysicalProperties.vb:53-73 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
D4 · Code Duplication· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (6 members, 50+ identical tokens) My Project/TaskBreakLinks.vb:123— My Project/TaskBreakLinks.vb:123-146 | My Project/TaskCheckFilename.vb:143-172 | My Project/TaskCheckLinks.vb:103-127 | My Project/TaskEditProperties.vb:114-142 | My Project/TaskFitView.vb:68-90 | My Project/TaskSetDocumentStatus.vb:54-76 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (5 members, 50+ identical tokens) My Project/TaskShowHideConstructions.vb:525— My Project/TaskShowHideConstructions.vb:525-551 | My Project/TaskShowHideConstructions.vb:558-584 | My Project/TaskShowHideConstructions.vb:591-617 | My Project/TaskShowHideConstructions.vb:625-653 | My Project/TaskShowHideConstructions.vb:710-736 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication· Edited copy of a member (50 corresponding lines) · ×1
Edited copy of a member (50 corresponding lines) My Project/FormEditTaskListChangeColor.vb:13— My Project/FormEditTaskListChangeColor.vb:13-64 | My Project/Task.vb:211-260 — These two members are one piece of code written twice and then edited apart: 50 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 58+ corresponding lines) · ×1
Edited copies of one member (3 members, 58+ corresponding lines) My Project/FormPropertyFilter.vb:476— My Project/FormPropertyFilter.vb:476-534 | My Project/FormPropertyInputEditor.vb:234-291 | My Project/FormVariableInputEditor.vb:215-272 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 58 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (158 corresponding lines) · ×1
Edited copy of a member (158 corresponding lines) My Project/HCStructuredStorageDoc.vb:441— My Project/HCStructuredStorageDoc.vb:441-598 | My Project/UtilsCommon.vb:1015-1206 — These two members are one piece of code written twice and then edited apart: 158 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 (68 corresponding lines) · ×1
Edited copy of a member (68 corresponding lines) My Project/TaskCreateDrawingOfFlatPattern.vb:822— My Project/TaskCreateDrawingOfFlatPattern.vb:822-889 | My Project/TaskUpdateModelStylesFromTemplate.vb:1276-1343 — These two members are one piece of code written twice and then edited apart: 68 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 52+ corresponding lines) · ×1
Edited copies of one member (3 members, 52+ corresponding lines) My Project/FormPropertyFilter.vb:597— My Project/FormPropertyFilter.vb:597-648 | My Project/FormPropertyInputEditor.vb:353-404 | My Project/FormVariableInputEditor.vb:335-386 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 52 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (116 corresponding lines) · ×1
Edited copy of a member (116 corresponding lines) My Project/TaskSaveDrawingAs.vb:348— My Project/TaskSaveDrawingAs.vb:348-463 | My Project/TaskSaveModelAs.vb:492-607 — These two members are one piece of code written twice and then edited apart: 116 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 (36 corresponding lines) · ×1
Edited copy of a member (36 corresponding lines) My Project/TaskBreakLinks.vb:225— My Project/TaskBreakLinks.vb:225-269 | My Project/TaskBreakLinks.vb:278-313 — These two members are one piece of code written twice and then edited apart: 36 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 (32 corresponding lines) · ×1
Edited copy of a member (32 corresponding lines) My Project/FormEditTaskList.vb:172— My Project/FormEditTaskList.vb:172-203 | My Project/FormPropertyListCustomize.vb:159-191 — These two members are one piece of code written twice and then edited apart: 32 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 (28 corresponding lines) · ×1
Edited copy of a member (28 corresponding lines) My Project/FormPropertyFilter.vb:86— My Project/FormPropertyFilter.vb:86-124 | My Project/FormVariableInputEditor.vb:26-53 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 32+ corresponding lines) · ×1
Edited copies of one member (3 members, 32+ corresponding lines) My Project/TaskCreateDrawingOfFlatPattern.vb:231— My Project/TaskCreateDrawingOfFlatPattern.vb:231-262 | My Project/TaskSaveDrawingAs.vb:219-255 | My Project/TaskSaveModelAs.vb:255-292 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 32 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 29+ corresponding lines) · ×1
Edited copies of one member (3 members, 29+ corresponding lines) My Project/TaskCheckMaterialNotInMaterialTable.vb:254— My Project/TaskCheckMaterialNotInMaterialTable.vb:254-283 | My Project/TaskUpdateDrawingStylesFromTemplate.vb:1227-1255 | My Project/TaskUpdateMaterialFromMaterialTable.vb:649-680 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 29 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 25+ corresponding lines) · ×1
Edited copies of one member (4 members, 25+ corresponding lines) My Project/TaskUpdateBlocks.vb:402— My Project/TaskUpdateBlocks.vb:402-426 | My Project/TaskUpdateDrawingStylesFromTemplate.vb:173-199 | My Project/TaskUpdateDrawings.vb:183-213 | My Project/TaskUpdateMaterialFromMaterialTable.vb:194-224 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 25 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 28+ corresponding lines) · ×1
Edited copies of one member (3 members, 28+ corresponding lines) My Project/FormPropertyListCustomize.vb:306— My Project/FormPropertyListCustomize.vb:306-334 | My Project/FormPropertyListCustomize.vb:339-373 | My Project/FormPropertyListCustomize.vb:379-406 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 28 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (19 corresponding lines) · ×1
Edited copy of a member (19 corresponding lines) My Project/Task.vb:273— My Project/Task.vb:273-292 | My Project/Task.vb:299-317 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 47+ corresponding lines) · ×1
Edited copies of one member (4 members, 47+ corresponding lines) My Project/TaskUpdateDrawingStylesFromTemplate.vb:606— My Project/TaskUpdateDrawingStylesFromTemplate.vb:606-652 | My Project/TaskUpdateDrawingStylesFromTemplate.vb:660-729 | My Project/TaskUpdateDrawingStylesFromTemplate.vb:736-782 | My Project/TaskUpdateDrawingStylesFromTemplate.vb:789-835 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 47 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (8 members, 15+ corresponding lines) · ×1
Edited copies of one member (8 members, 15+ corresponding lines) My Project/TaskActivateAndUpdateAll.vb:7— My Project/TaskActivateAndUpdateAll.vb:7-21 | My Project/TaskCheckDrawingPartsList.vb:9-24 | My Project/TaskCheckFlatPattern.vb:8-22 | My Project/TaskCheckPartCopies.vb:8-22 | My Project/TaskOpenSave.vb:7-21 | My Project/TaskRemoveFaceStyleOverrides.vb:8-22 | My Project/TaskUpdateDesignForCost.vb:8-22 | My Project/TaskUpdateFlatPattern.vb:8-22 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 20+ corresponding lines) · ×1
Edited copies of one member (4 members, 20+ corresponding lines) My Project/Form_Main.vb:2834— My Project/Form_Main.vb:2834-2853 | My Project/Form_Main.vb:2860-2879 | My Project/Form_Main.vb:2886-2905 | My Project/Form_Main.vb:2912-2931 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (21 corresponding lines) · ×1
Edited copy of a member (21 corresponding lines) My Project/TaskCheckFilename.vb:213— My Project/TaskCheckFilename.vb:213-233 | My Project/TaskCheckLinks.vb:170-199 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (24 corresponding lines) · ×1
Edited copy of a member (24 corresponding lines) My Project/UtilsCommon.vb:689— My Project/UtilsCommon.vb:689-781 | My Project/UtilsCommon.vb:790-813 — 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 (13 corresponding lines) · ×1
Edited copy of a member (13 corresponding lines) My Project/TaskEditProperties.vb:1547— My Project/TaskEditProperties.vb:1547-1559 | My Project/TaskUpdateModelStylesFromTemplate.vb:1451-1467 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (8 members, 12+ corresponding lines) · ×1
Edited copies of one member (8 members, 12+ corresponding lines) My Project/HCIsolatedTaskProxy.vb:91— My Project/HCIsolatedTaskProxy.vb:91-102 | My Project/HCIsolatedTaskProxy.vb:111-122 | My Project/HCIsolatedTaskProxy.vb:131-142 | My Project/HCIsolatedTaskProxy.vb:151-169 | My Project/HCIsolatedTaskProxy.vb:174-192 | My Project/HCIsolatedTaskProxy.vb:197-215 | My Project/HCIsolatedTaskProxy.vb:220-238 | My Project/HCIsolatedTaskProxy.vb:243-261 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×1
Edited copy of a member (18 corresponding lines) My Project/HCStructuredStorageDoc.vb:265— My Project/HCStructuredStorageDoc.vb:265-282 | My Project/HCStructuredStorageDoc.vb:286-305 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×1
Edited copy of a member (7 corresponding lines) My Project/TaskUpdateDrawingStylesFromTemplate.vb:1111— My Project/TaskUpdateDrawingStylesFromTemplate.vb:1111-1119 | My Project/FormEditTaskList.vb:412-418 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×1
Edited copy of a member (9 corresponding lines) My Project/TaskSetDocumentStatus.vb:195— My Project/TaskSetDocumentStatus.vb:195-203 | My Project/TaskPrint.vb:565-574 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 11+ corresponding lines) · ×1
Edited copies of one member (3 members, 11+ corresponding lines) My Project/FormPropertyFilter.vb:553— My Project/FormPropertyFilter.vb:553-563 | My Project/FormPropertyInputEditor.vb:311-321 | My Project/FormVariableInputEditor.vb:291-301 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 9+ corresponding lines) · ×1
Edited copies of one member (3 members, 9+ corresponding lines) My Project/FormPropertyFilter.vb:567— My Project/FormPropertyFilter.vb:567-575 | My Project/FormPropertyInputEditor.vb:325-333 | My Project/FormVariableInputEditor.vb:305-313 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (2 corresponding lines) · ×1
Edited copy of a member (2 corresponding lines) My Project/FormEditTaskList.vb:250— My Project/FormEditTaskList.vb:250-251 | My Project/FormPropertyListCustomize.vb:235-236 — These two members are one piece of code written twice and then edited apart: 2 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.
Duplicated block (27–35 lines × 2) My Project/TaskCheckMaterialNotInMaterialTable.vb:194— My Project/TaskCheckMaterialNotInMaterialTable.vb:194-220 | My Project/TaskUpdateMaterialFromMaterialTable.vb:374-408 — before extracting anything, compare `My Project/TaskCheckMaterialNotInMaterialTable.vb` and `My Project/TaskUpdateMaterialFromMaterialTable.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 85 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10–32 lines × 2) My Project/HCStructuredStorageDoc.vb:524— My Project/HCStructuredStorageDoc.vb:524-555 | My Project/UtilsCommon.vb:1077-1086 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `My Project/HCStructuredStorageDoc.vb:555` calls `Replace`, `Formulas`, `DocValues` and `My Project/UtilsCommon.vb:1086` 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 (28 lines × 2) My Project/TaskSaveDrawingAs.vb:348— My Project/TaskSaveDrawingAs.vb:348-375 | My Project/TaskSaveModelAs.vb:492-519 — before extracting anything, compare `My Project/TaskSaveDrawingAs.vb` and `My Project/TaskSaveModelAs.vb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 164 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the 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–27 lines × 2) My Project/FormPropertyInputEditor.vb:501— My Project/FormPropertyInputEditor.vb:501-525 | My Project/FormVariableInputEditor.vb:436-462 — before extracting anything, compare `My Project/FormPropertyInputEditor.vb` and `My Project/FormVariableInputEditor.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 106 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (25 lines × 2) My Project/TaskCreateDrawingOfFlatPattern.vb:822— My Project/TaskCreateDrawingOfFlatPattern.vb:822-846 | My Project/TaskUpdateDrawingStylesFromTemplate.vb:1227-1251 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (26 lines × 2) My Project/TaskUpdateModelStylesFromTemplate.vb:372— My Project/TaskUpdateModelStylesFromTemplate.vb:372-397 | My Project/TaskUpdateModelStylesFromTemplate.vb:412-437 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (23–25 lines × 5) My Project/TaskShowHideConstructions.vb:529— My Project/TaskShowHideConstructions.vb:529-551 | My Project/TaskShowHideConstructions.vb:562-584 | My Project/TaskShowHideConstructions.vb:595-617 | My Project/TaskShowHideConstructions.vb:629-653 | My Project/TaskShowHideConstructions.vb:714-736 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (23 lines × 2) My Project/TaskEditProperties.vb:1313— My Project/TaskEditProperties.vb:1313-1335 | My Project/TaskEditVariables.vb:307-329 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (24 lines × 2) My Project/TaskSaveDrawingAs.vb:665— My Project/TaskSaveDrawingAs.vb:665-688 | My Project/TaskSaveModelAs.vb:987-1010 — before extracting anything, compare `My Project/TaskSaveDrawingAs.vb` and `My Project/TaskSaveModelAs.vb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 164 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the 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 (24–25 lines × 2) My Project/TaskSaveDrawingAs.vb:872— My Project/TaskSaveDrawingAs.vb:872-896 | My Project/TaskSaveModelAs.vb:1187-1210 — before extracting anything, compare `My Project/TaskSaveDrawingAs.vb` and `My Project/TaskSaveModelAs.vb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 164 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the 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 (15–24 lines × 2) My Project/HCStructuredStorageDoc.vb:491— My Project/HCStructuredStorageDoc.vb:491-514 | My Project/UtilsCommon.vb:1055-1069 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `My Project/HCStructuredStorageDoc.vb:516` calls `MsgBox` and `My Project/UtilsCommon.vb:1070` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (14–23 lines × 2) My Project/TaskUpdateMaterialFromMaterialTable.vb:395— My Project/TaskUpdateMaterialFromMaterialTable.vb:395-417 | My Project/TaskUpdateModelStylesFromTemplate.vb:1181-1194 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (17–21 lines × 3) My Project/TaskCheckMaterialNotInMaterialTable.vb:265— My Project/TaskCheckMaterialNotInMaterialTable.vb:265-283 | My Project/TaskEditProperties.vb:1458-1474 | My Project/TaskUpdateMaterialFromMaterialTable.vb:660-680 — before extracting anything, compare `My Project/TaskCheckMaterialNotInMaterialTable.vb` and `My Project/TaskEditProperties.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the 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 (20–21 lines × 2) My Project/UCEditProperties.vb:193— My Project/UCEditProperties.vb:193-212 | My Project/UCPropertyFilter.vb:137-157 — before extracting anything, compare `My Project/UCEditProperties.vb` and `My Project/UCPropertyFilter.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 63 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (18–19 lines × 2) My Project/TaskSaveDrawingAs.vb:927— My Project/TaskSaveDrawingAs.vb:927-944 | My Project/TaskSaveModelAs.vb:1240-1258 — before extracting anything, compare `My Project/TaskSaveDrawingAs.vb` and `My Project/TaskSaveModelAs.vb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 164 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (16–17 lines × 2) My Project/FormPropertyInputEditor.vb:453— My Project/FormPropertyInputEditor.vb:453-469 | My Project/FormVariableInputEditor.vb:398-413 — before extracting anything, compare `My Project/FormPropertyInputEditor.vb` and `My Project/FormVariableInputEditor.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 106 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (15–16 lines × 3) My Project/FormPropertyFilter.vb:476— My Project/FormPropertyFilter.vb:476-491 | My Project/FormPropertyInputEditor.vb:234-248 | My Project/FormVariableInputEditor.vb:215-229 — before extracting anything, compare `My Project/FormPropertyInputEditor.vb` and `My Project/FormVariableInputEditor.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 106 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (16 lines × 2) My Project/TaskSaveDrawingAs.vb:448— My Project/TaskSaveDrawingAs.vb:448-463 | My Project/TaskSaveModelAs.vb:592-607 — before extracting anything, compare `My Project/TaskSaveDrawingAs.vb` and `My Project/TaskSaveModelAs.vb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 164 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 2) My Project/TaskCreateDrawingOfFlatPattern.vb:528— My Project/TaskCreateDrawingOfFlatPattern.vb:528-542 | My Project/TaskUpdateDrawingStylesFromTemplate.vb:956-970 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 3) My Project/TaskCheckFilename.vb:542— My Project/TaskCheckFilename.vb:542-550 | My Project/TaskCheckMaterialNotInMaterialTable.vb:218-226 | My Project/TaskEditProperties.vb:1343-1351 — before extracting anything, compare `My Project/TaskCheckFilename.vb` and `My Project/TaskCheckMaterialNotInMaterialTable.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `My Project/TaskCheckFilename.vb:539` calls `SetColumnSpan` and `My Project/TaskCheckMaterialNotInMaterialTable.vb:215` 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 (12–13 lines × 13) My Project/TaskBreakLinks.vb:568— My Project/TaskBreakLinks.vb:568-580 | My Project/TaskCheckDrawings.vb:1280-1292 | My Project/TaskCheckFilename.vb:544-556 | My Project/TaskCheckLinks.vb:420-432 | My Project/TaskCheckMaterialNotInMaterialTable.vb:220-232 | My Project/TaskCheckMissingDrawing.vb:134-146 | My Project/TaskCheckRelationships.vb:533-545 | My Project/TaskFitView.vb:210-222 | My Project/TaskUpdateDrawingStylesFromTemplate.vb:1042-1054 | My Project/TaskUpdateDrawings.vb:625-637 | My Project/TaskUpdateModelStylesFromTemplate.vb:1234-1246 | My Project/TaskUpdatePartCopies.vb:193-205 | My Project/TaskUpdatePhysicalProperties.vb:301-312 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 13 call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `My Project/TaskBreakLinks.vb:563` calls `SetColumnSpan` and `My Project/TaskCheckMaterialNotInMaterialTable.vb:215` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 5) My Project/TaskCreateDrawingOfFlatPattern.vb:686— My Project/TaskCreateDrawingOfFlatPattern.vb:686-694 | My Project/TaskEditInteractively.vb:507-515 | My Project/TaskRunExternalProgram.vb:417-425 | My Project/TaskSaveModelAs.vb:1121-1129 | My Project/TaskUpdateBlocks.vb:1311-1319 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 5 call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `My Project/TaskRunExternalProgram.vb:413` calls `SetColumnSpan` and `My Project/TaskCreateDrawingOfFlatPattern.vb:682` 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 (12–13 lines × 3) My Project/TaskSaveDrawingAs.vb:790— My Project/TaskSaveDrawingAs.vb:790-802 | My Project/TaskSetDocumentStatus.vb:160-171 | My Project/TaskUpdateModelSizeInVariableTable.vb:451-463 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `My Project/TaskSetDocumentStatus.vb:158` calls `SetColumnSpan` and `My Project/TaskUpdateModelSizeInVariableTable.vb:450` 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 (10–12 lines × 17) My Project/TaskBreakLinks.vb:572— My Project/TaskBreakLinks.vb:572-582 | My Project/TaskCheckDrawings.vb:1284-1294 | My Project/TaskCheckFilename.vb:548-558 | My Project/TaskCheckInterference.vb:164-174 | My Project/TaskCheckLinks.vb:424-434 | My Project/TaskCheckMaterialNotInMaterialTable.vb:224-234 | My Project/TaskCheckMissingDrawing.vb:138-148 | My Project/TaskCheckRelationships.vb:537-547 | My Project/TaskFitView.vb:214-224 | My Project/TaskSaveDrawingAs.vb:791-802 | My Project/TaskSetDocumentStatus.vb:161-171 | My Project/TaskUpdateDrawingStylesFromTemplate.vb:1046-1056 | My Project/TaskUpdateDrawings.vb:629-639 | My Project/TaskUpdateModelSizeInVariableTable.vb:452-463 | My Project/TaskUpdateModelStylesFromTemplate.vb:1238-1248 | My Project/TaskUpdatePartCopies.vb:197-207 | My Project/TaskUpdatePhysicalProperties.vb:305-314 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 17 call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `My Project/TaskSaveDrawingAs.vb:789` calls `SetColumnSpan` and `My Project/TaskCheckInterference.vb:163` 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 (8–12 lines × 6) My Project/TaskUpdateBlocks.vb:1221— My Project/TaskUpdateBlocks.vb:1221-1229 | My Project/TaskUpdateBlocks.vb:1231-1239 | My Project/TaskUpdateBlocks.vb:1241-1250 | My Project/TaskUpdateBlocks.vb:1261-1268 | My Project/TaskUpdateBlocks.vb:1272-1280 | My Project/TaskUpdateBlocks.vb:1282-1293 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. 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 (11 lines × 4) My Project/TaskCheckFilename.vb:634— My Project/TaskCheckFilename.vb:634-644 | My Project/TaskCheckLinks.vb:726-736 | My Project/TaskCheckMaterialNotInMaterialTable.vb:309-319 | My Project/TaskCheckMissingDrawing.vb:170-180 — before extracting anything, compare `My Project/TaskCheckFilename.vb` and `My Project/TaskCheckLinks.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 4) My Project/TaskCheckLinks.vb:409— My Project/TaskCheckLinks.vb:409-418 | My Project/TaskUpdateBlocks.vb:1143-1152 | My Project/TaskUpdateBlocks.vb:1170-1179 | My Project/TaskUpdateBlocks.vb:1302-1311 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (10–12 lines × 3) My Project/TaskCheckMaterialNotInMaterialTable.vb:296— My Project/TaskCheckMaterialNotInMaterialTable.vb:296-307 | My Project/TaskEditProperties.vb:1523-1534 | My Project/TaskUpdateMaterialFromMaterialTable.vb:549-558 — before extracting anything, compare `My Project/TaskCheckMaterialNotInMaterialTable.vb` and `My Project/TaskEditProperties.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the 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 (10 lines × 7) My Project/TaskCheckMaterialNotInMaterialTable.vb:70— My Project/TaskCheckMaterialNotInMaterialTable.vb:70-79 | My Project/TaskEditVariables.vb:56-65 | My Project/TaskShowHideConstructions.vb:388-397 | My Project/TaskUpdateModelSizeInVariableTable.vb:143-152 | My Project/TaskUpdateModelStylesFromTemplate.vb:210-219 | My Project/TaskUpdatePartCopies.vb:40-49 | My Project/TaskUpdatePhysicalProperties.vb:53-62 — before extracting anything, compare `My Project/TaskCheckMaterialNotInMaterialTable.vb` and `My Project/TaskUpdateModelSizeInVariableTable.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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 6) My Project/TaskBreakLinks.vb:123— My Project/TaskBreakLinks.vb:123-132 | My Project/TaskCheckFilename.vb:143-152 | My Project/TaskCheckLinks.vb:103-112 | My Project/TaskEditProperties.vb:114-123 | My Project/TaskFitView.vb:68-77 | My Project/TaskSetDocumentStatus.vb:54-63 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 6 call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `My Project/TaskSetDocumentStatus.vb:66` calls `SetColorFromCategory` and `My Project/TaskEditProperties.vb:126` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 11) My Project/TaskCheckDrawings.vb:1058— My Project/TaskCheckDrawings.vb:1058-1068 | My Project/TaskCheckDrawings.vb:1078-1088 | My Project/TaskCheckDrawings.vb:1098-1108 | My Project/TaskCheckDrawings.vb:1118-1128 | My Project/TaskCheckDrawings.vb:1138-1148 | My Project/TaskCheckDrawings.vb:1158-1168 | My Project/TaskCheckDrawings.vb:1191-1201 | My Project/TaskCheckDrawings.vb:1211-1221 | My Project/TaskUpdateDrawings.vb:571-580 | My Project/TaskUpdateDrawings.vb:589-598 | My Project/TaskUpdateDrawings.vb:607-616 — before extracting anything, compare `My Project/TaskCheckDrawings.vb` and `My Project/TaskUpdateDrawings.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 9) My Project/TaskCheckFilename.vb:517— My Project/TaskCheckFilename.vb:517-524 | My Project/TaskCheckFilename.vb:527-534 | My Project/TaskEditInteractively.vb:413-420 | My Project/TaskUpdateBlocks.vb:1191-1198 | My Project/TaskUpdateDrawingStylesFromTemplate.vb:1005-1012 | My Project/TaskUpdateDrawingStylesFromTemplate.vb:1015-1022 | My Project/TaskUpdateDrawingStylesFromTemplate.vb:1025-1032 | My Project/TaskUpdateDrawings.vb:546-553 | My Project/TaskUpdateMaterialFromMaterialTable.vb:482-489 — there are 9 copies across 6 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 9 sites; resolving a subset leaves the remainder to drift apart. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `My Project/TaskCheckFilename.vb:527` calls `Padding` and `My Project/TaskCheckFilename.vb:537` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 5) My Project/TaskEditInteractively.vb:397— My Project/TaskEditInteractively.vb:397-403 | My Project/TaskEditInteractively.vb:446-452 | My Project/TaskEditInteractively.vb:462-468 | My Project/TaskEditInteractively.vb:478-484 | My Project/TaskEditInteractively.vb:494-500 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (6 lines × 4) My Project/TaskUpdateModelStylesFromTemplate.vb:681— My Project/TaskUpdateModelStylesFromTemplate.vb:681-686 | My Project/TaskUpdateModelStylesFromTemplate.vb:748-753 | My Project/TaskUpdateModelStylesFromTemplate.vb:814-819 | My Project/TaskUpdateModelStylesFromTemplate.vb:880-885 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9–10 lines × 3) My Project/TaskCreateDrawingOfFlatPattern.vb:629— My Project/TaskCreateDrawingOfFlatPattern.vb:629-638 | My Project/TaskCreateDrawingOfFlatPattern.vb:663-671 | My Project/TaskEditProperties.vb:1362-1371 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (9 lines × 22) My Project/TaskCheckDrawings.vb:1059— My Project/TaskCheckDrawings.vb:1059-1068 | My Project/TaskCheckDrawings.vb:1069-1078 | My Project/TaskCheckDrawings.vb:1079-1088 | My Project/TaskCheckDrawings.vb:1089-1098 | My Project/TaskCheckDrawings.vb:1099-1108 | My Project/TaskCheckDrawings.vb:1109-1118 | My Project/TaskCheckDrawings.vb:1119-1128 | My Project/TaskCheckDrawings.vb:1129-1138 | My Project/TaskCheckDrawings.vb:1139-1148 | My Project/TaskCheckDrawings.vb:1149-1158 | My Project/TaskCheckDrawings.vb:1159-1168 | My Project/TaskCheckDrawings.vb:1169-1183 | My Project/TaskCheckDrawings.vb:1192-1201 | My Project/TaskCheckDrawings.vb:1202-1211 | My Project/TaskCheckDrawings.vb:1212-1221 | My Project/TaskCheckDrawings.vb:1222-1232 | My Project/TaskUpdateDrawings.vb:572-580 | My Project/TaskUpdateDrawings.vb:581-589 | My Project/TaskUpdateDrawings.vb:590-598 | My Project/TaskUpdateDrawings.vb:599-607 | My Project/TaskUpdateDrawings.vb:608-616 | My Project/TaskUpdateDrawings.vb:617-625 — before extracting anything, compare `My Project/TaskCheckDrawings.vb` and `My Project/TaskUpdateDrawings.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `My Project/TaskCheckDrawings.vb:1069` calls `Padding` and `My Project/TaskCheckDrawings.vb:1184` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 15) My Project/TaskCheckFilename.vb:516— My Project/TaskCheckFilename.vb:516-524 | My Project/TaskCheckFilename.vb:526-534 | My Project/TaskUpdateBlocks.vb:1122-1130 | My Project/TaskUpdateBlocks.vb:1190-1198 | My Project/TaskUpdateBlocks.vb:1200-1210 | My Project/TaskEditInteractively.vb:412-420 | My Project/TaskEditProperties.vb:1361-1369 | My Project/TaskCreateDrawingOfFlatPattern.vb:628-636 | My Project/TaskCreateDrawingOfFlatPattern.vb:662-670 | My Project/TaskUpdateDrawingStylesFromTemplate.vb:1004-1012 | My Project/TaskUpdateDrawingStylesFromTemplate.vb:1014-1022 | My Project/TaskUpdateDrawingStylesFromTemplate.vb:1024-1032 | My Project/TaskUpdateDrawings.vb:545-553 | My Project/TaskUpdateMaterialFromMaterialTable.vb:417-425 | My Project/TaskUpdateMaterialFromMaterialTable.vb:481-489 — before extracting anything, compare `My Project/TaskCheckFilename.vb` and `My Project/TaskEditProperties.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `My Project/TaskCheckFilename.vb:527` calls `Padding` and `My Project/TaskCheckFilename.vb:537` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 5) My Project/TaskCheckLinks.vb:409— My Project/TaskCheckLinks.vb:409-414 | My Project/TaskUpdateBlocks.vb:1143-1148 | My Project/TaskUpdateBlocks.vb:1170-1175 | My Project/TaskUpdateBlocks.vb:1302-1307 | My Project/TaskUpdateDrawingStylesFromTemplate.vb:982-987 — there are 5 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 5 sites; resolving a subset leaves the remainder to drift apart. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `My Project/TaskUpdateDrawingStylesFromTemplate.vb:990` calls `ClearSelection` and `My Project/TaskCheckLinks.vb:415` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 2) My Project/TaskCreateDrawingOfFlatPattern.vb:463— My Project/TaskCreateDrawingOfFlatPattern.vb:463-467 | My Project/TaskCreateDrawingOfFlatPattern.vb:469-473 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 3) My Project/HCPropertiesData.vb:1256— My Project/HCPropertiesData.vb:1256-1268 | My Project/HCPropertyFilter.vb:195-207 | My Project/HCPropertyFilter.vb:292-304 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (5 lines × 4) My Project/TaskCheckFilename.vb:103— My Project/TaskCheckFilename.vb:103-107 | My Project/TaskCheckLinks.vb:39-43 | My Project/TaskCheckMaterialNotInMaterialTable.vb:39-43 | My Project/TaskCheckMissingDrawing.vb:13-17 — before extracting anything, compare `My Project/TaskCheckFilename.vb` and `My Project/TaskCheckLinks.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 34) My Project/TaskActivateAndUpdateAll.vb:30— My Project/TaskActivateAndUpdateAll.vb:30-37 | My Project/TaskBreakLinks.vb:155-162 | My Project/TaskCheckDrawingPartsList.vb:35-42 | My Project/TaskCheckDrawings.vb:451-458 | My Project/TaskCheckFilename.vb:181-188 | My Project/TaskCheckFlatPattern.vb:33-40 | My Project/TaskCheckInterference.vb:69-76 | My Project/TaskCheckLinks.vb:137-144 | My Project/TaskCheckMaterialNotInMaterialTable.vb:101-108 | My Project/TaskCheckMissingDrawing.vb:69-76 | My Project/TaskCheckPartCopies.vb:33-40 | My Project/TaskCheckRelationships.vb:97-104 | My Project/TaskCreateDrawingOfFlatPattern.vb:271-278 | My Project/TaskEditInteractively.vb:221-228 | My Project/TaskEditProperties.vb:151-158 | My Project/TaskEditVariables.vb:88-95 | My Project/TaskFitView.vb:99-106 | My Project/TaskOpenSave.vb:32-39 | My Project/TaskPrint.vb:203-210 | My Project/TaskRemoveFaceStyleOverrides.vb:33-40 | My Project/TaskRunExternalProgram.vb:139-146 | My Project/TaskSaveDrawingAs.vb:263-270 | My Project/TaskSaveModelAs.vb:301-308 | My Project/TaskShowHideConstructions.vb:415-422 | My Project/TaskUpdateBlocks.vb:434-441 | My Project/TaskUpdateDesignForCost.vb:33-40 | My Project/TaskUpdateDrawingStylesFromTemplate.vb:210-217 | My Project/TaskUpdateDrawings.vb:222-229 | My Project/TaskUpdateFlatPattern.vb:33-40 | My Project/TaskUpdateMaterialFromMaterialTable.vb:232-239 | My Project/TaskUpdateModelSizeInVariableTable.vb:178-185 | My Project/TaskUpdateModelStylesFromTemplate.vb:251-258 | My Project/TaskUpdatePartCopies.vb:68-75 | My Project/TaskUpdatePhysicalProperties.vb:82-89 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 34 call sites, so a change lands once.
Duplicated block (5 lines × 10) My Project/TaskCheckDrawingPartsList.vb:80— My Project/TaskCheckDrawingPartsList.vb:80-85 | My Project/TaskCheckFlatPattern.vb:112-116 | My Project/TaskCheckMissingDrawing.vb:153-157 | My Project/TaskCheckPartCopies.vb:104-108 | My Project/TaskOpenSave.vb:69-73 | My Project/TaskRemoveFaceStyleOverrides.vb:100-104 | My Project/TaskShowHideConstructions.vb:872-876 | My Project/TaskUpdateDesignForCost.vb:74-78 | My Project/TaskUpdateFlatPattern.vb:111-115 | My Project/TaskUpdatePartCopies.vb:212-216 — before extracting anything, compare `My Project/TaskCheckMissingDrawing.vb` and `My Project/TaskUpdatePartCopies.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
No structured logging — No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
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.
redundant comment HousekeeperCLI/My Project/AssemblyInfo.vb:5— "General Information about an assembly is controlled through the following set of attributes. Change these attribute values to modify the information associated …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment HousekeeperCLI/My Project/AssemblyInfo.vb:9— "Review the values of the assembly attributes" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment HousekeeperCLI/My Project/AssemblyInfo.vb:20— "The following GUID is for the ID of the typelib if this project is exposed to COM" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment My Project/AssemblyInfo.vb:5— "General Information about an assembly is controlled through the following set of attributes. Change these attribute values to modify the information associated …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment My Project/AssemblyInfo.vb:9— "Review the values of the assembly attributes" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment My Project/AssemblyInfo.vb:20— "The following GUID is for the ID of the typelib if this project is exposed to COM" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment My Project/AssemblyInfo.vb:23— "Version information for an assembly consists of the following four values: Major Version Minor Version Build Number Revision You can specify all the values or y …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment My Project/FormBlockLibraryBlockNames.vb:72— "This call is required by the designer." is Visual Studio form constructor template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment My Project/FormBlockLibraryBlockNames.vb:75— "Add any initialization after the InitializeComponent() call." is Visual Studio form constructor template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment My Project/FormEditDraftTemplateCriterion.vb:22— "This call is required by the designer." is Visual Studio form constructor template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment My Project/FormEditDraftTemplateCriterion.vb:25— "Add any initialization after the InitializeComponent() call." is Visual Studio form constructor template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment My Project/FormEditInteractively.vb:30— "This call is required by the designer." is Visual Studio form constructor template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment My Project/FormEditInteractively.vb:33— "Add any initialization after the InitializeComponent() call." is Visual Studio form constructor template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment My Project/FormEditTaskList.vb:15— "This call is required by the designer." is Visual Studio form constructor template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment My Project/FormEditTaskList.vb:18— "Add any initialization after the InitializeComponent() call." is Visual Studio form constructor template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment My Project/FormExpressionEditor.vb:83— "This call is required by the designer." is Visual Studio form constructor template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment My Project/FormExpressionEditor.vb:86— "Add any initialization after the InitializeComponent() call." is Visual Studio form constructor template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment My Project/FormNewVersionAvailable.vb:7— "This call is required by the designer." is Visual Studio form constructor template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment My Project/FormNewVersionAvailable.vb:10— "Add any initialization after the InitializeComponent() call." is Visual Studio form constructor template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment My Project/FormPresetsOptions.vb:34— "This call is required by the designer." is Visual Studio form constructor template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment My Project/FormPresetsOptions.vb:37— "Add any initialization after the InitializeComponent() call." is Visual Studio form constructor template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment My Project/FormPropertyFilter.vb:45— "This call is required by the designer." is Visual Studio form constructor template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment My Project/FormPropertyFilter.vb:48— "Add any initialization after the InitializeComponent() call." is Visual Studio form constructor template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment My Project/FormPropertyInputEditor.vb:34— "This call is required by the designer." is Visual Studio form constructor template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment My Project/FormPropertyInputEditor.vb:37— "Add any initialization after the InitializeComponent() call." is Visual Studio form constructor template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
No ADRs found Housekeeper.vbproj:8— No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `Housekeeper.vbproj` makes this repository a deployable product (line 8).
D28 · Secrets (history)· Rotate the exposed credentials · ×1
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
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 dependency-update automation packages.config:3— `packages.config` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
doc comments repeat the names My Project/ListViewExtended/ListViewExtended/ListViewExtended.vb:246— 0 of 4 documented parameters and 1 of 35 summaries in `ListViewExtended` only repeat the member or parameter name (e.g. "ID of the group." for `IGroupId`). Delete the restating tags, or add what the name does not say.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
nuget: not applicable — nuget: `dotnet list package --vulnerable` could not read this solution's dependency graph — it reported an error for at least one project and returned no package data at all (typically a packages.config / non-PackageReference project, which the command cannot read). An unreadable dependency graph is not a clean one; migrate the project(s) to PackageReference to enable this 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 01a1da07-c524-7ffa-835b-5dd83cf0eef1 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 89 · Warnings: 523 · Recommendations: 65 · Info: 1 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 14-11-2026 @ 12:28 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.