Skip to content

sow/2026-Q3: SAM-BIM Q3 2026 updates - #6

Merged
michaldengusiak merged 6 commits into
HoareLea:masterfrom
SAM-BIM:sow/2026-Q3
Oct 6, 2026
Merged

michaldengusiak merged 6 commits into
HoareLea:masterfrom
SAM-BIM:sow/2026-Q3

Conversation

@michaldengusiak

Copy link
Copy Markdown
Contributor

Summary

Brings the SAM-BIM sow/2026-Q3 line of work into master (3 non-merge commits; 4 files changed, 85 insertions(+), 25 deletions(-)).

Main changes

  • docs: record merged .NET Framework app.config cleanup in PROJECT_PROGRESS
  • build: remove dead .NET Framework app.config leftovers
  • Add AI agent instructions and project progress tracking

(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

michaldengusiak and others added 5 commits August 18, 2026 10:07
Generated by Michal Dengusiak and CodeClaude

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2 app.config files were net472-era leftovers containing assembly binding
redirects (and, in one case, a CAS-era loadFromRemoteSources flag), neither of
which has any effect under .NET 8. Every project here targets net8.0-windows
or netstandard2.0 and is OutputType Library (2 explicit, 2 defaulted), and a
library's .dll.config is never read at runtime (only the host .exe.config is).
Their only remaining effect was to emit stale SAM.*.dll.config files into
build/ and the %APPDATA%\SAM deploy folder.

Grasshopper/SAM.Core.Grasshopper.Multitasker/app.config also carried
<loadFromRemoteSources enabled="true"/> (repeated at three nesting levels).
That is likewise a .NET-Framework/CAS-era mechanism only honoured in the host
.exe.config, so it is safe to delete here too — but its presence is evidence
that someone once hit a real "assembly loaded from a network share" problem
with this plugin. Worth keeping in mind if similar symptoms resurface under
.NET 8, though the fix would live elsewhere (e.g. host trust configuration),
not in this dead per-library config file.

Verified: TargetFrameworks are net8.0-windows/netstandard2.0 only (no netfx);
all 4 csproj files are OutputType Library, 2 explicit and 2 defaulted (no
Exe/WinExe); no source file references ConfigurationManager/
System.Configuration/AppSettings/OpenExeConfiguration; both app.config files
read and contain only assemblyIdentity/bindingRedirect/assemblyBinding/
runtime/loadFromRemoteSources elements; no csproj/props/yml references
app.config/AppConfig/dll.config. Compile-only verification
(dotnet build -t:Compile) on both affected projects: 0 errors each
(pre-existing MSB3277/MSB3245/CS8632/CS0162 warnings unrelated to this change,
unchanged by it).

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
@chatgpt-codex-connector

Copy link
Copy Markdown

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>
@michaldengusiak
michaldengusiak merged commit 997cecc into HoareLea:master Oct 6, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant