You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
No code generated during "self contained" publishing #67
It seems that no code gets generated during publishing a "self contained" (in contrast to a framework dependent) application.
This are the build errors I get:
1>CSC(0,0): Fehler TRF001: Framework is not recognized.
1>CSC(0,0): Fehler ADPG: System.InvalidOperationException: Platform is not supported.
1>CSC(0,0): Fehler DPG: System.InvalidOperationException: Platform is not supported.
Steps to reproduce the bug
Create a publishing profile in VS 2022
Change deployment mode to self contained (or standalone)
Closing this as stale/needs-repro. Self-contained publishing should still provide enough MSBuild/analyzer config information for framework recognition, but this report does not include a minimal project, publish profile, or binlog to identify what property is being dropped during publish.
If it still reproduces with the latest package, please reopen or file a fresh issue with a minimal repro and an MSBuild binary log from the self-contained publish.
I have encountered the same issue with the latest version 1.5.1. The build goes ok, but publishing with a self-contained framework throws errors:
System.InvalidOperationException: Platform is not supported.
Framework is not recognized.
And some missing partial methods that were not generated.
Thanks for confirming this still occurs in 1.5.1. I reproduced the vulnerable framework-detection path and opened #164 with a fallback that infers the UI framework from compilation references when publish-time MSBuild analyzer options are missing.
Activity
HavenDV commentedon Jun 27, 2026
Closing this as stale/needs-repro. Self-contained publishing should still provide enough MSBuild/analyzer config information for framework recognition, but this report does not include a minimal project, publish profile, or binlog to identify what property is being dropped during publish.
If it still reproduces with the latest package, please reopen or file a fresh issue with a minimal repro and an MSBuild binary log from the self-contained publish.
selvinfehric commentedon Jul 21, 2026
I have encountered the same issue with the latest version 1.5.1. The build goes ok, but publishing with a self-contained framework throws errors:
System.InvalidOperationException: Platform is not supported.
Framework is not recognized.
And some missing partial methods that were not generated.
HavenDV commentedon Jul 22, 2026
Thanks for confirming this still occurs in 1.5.1. I reproduced the vulnerable framework-detection path and opened #164 with a fallback that infers the UI framework from compilation references when publish-time MSBuild analyzer options are missing.