Repository navigation
sow/2026-Q3: SAM-BIM Q3 2026 updates - #12
Merged
Merged
Conversation
Generated by Michal Dengusiak and CodeClaude Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
1 app.config file was a net472-era leftover containing an assembly binding redirect, which has no effect under .NET 8. Every project here targets net8.0-windows / netstandard2.0 and is OutputType Library, and a library's .dll.config is never read at runtime (only the host .exe.config is). Its only remaining effect was to emit a stale SAM.*.dll.config file into build/ and the %APPDATA%\SAM deploy folder. Verified: TargetFrameworks are net8.0-windows/netstandard2.0 only; both projects are OutputType Library; no ConfigurationManager/System.Configuration/ AppSettings/OpenExeConfiguration usage in any .cs file; the app.config file contained only an assemblyBinding/bindingRedirect element; no .csproj/.props/ .yml references app.config/AppConfig/dll.config. Compile-only verification (dotnet build -t:Compile, Release) of SAM.Core.Grasshopper.Excel.csproj: 0 errors, 15 pre-existing unrelated NU1701 package-compatibility warnings. (Building its ProjectReference SAM.Core.Excel.csproj from scratch fails with MSB4803 because that project has an unconditional COMReference (VBIDE) and ResolveComReference is unsupported by dotnet-CLI MSBuild; this is a pre-existing environment/tooling limitation entirely unrelated to the app.config removal, so the affected project was verified against the existing build/SAM.Core.Excel.dll via -p:BuildProjectReferences=false.) Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…vers build: remove dead .NET Framework app.config leftovers
…RESS Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
docs: record merged .NET Framework app.config cleanup in PROJECT_PROGRESS
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
…om upstream contribution Removes AGENTS.md, PROJECT_PROGRESS.md and internal evidence/.claude artefacts that are SAM-BIM workflow records, not upstream project documentation. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Brings the SAM-BIM
sow/2026-Q3line of work intomaster(4 non-merge commits; 4 files changed, 85 insertions(+), 11 deletions(-)).Main changes
(Full list in the commit history.)
Validation
Changes were merged through reviewed PRs on the SAM-BIM fork, with CI/builds run there; no further validation was run for this upstream PR.
Compatibility notes
Includes AGENTS.md / PROJECT_PROGRESS.md project-continuity files where present. Dependent SAM repos are being submitted in parallel from the same branch name; merge order should follow the SAM core dependency chain.
🤖 Generated with Claude Code