Skip to content

Fix OrchardCore.SourceGenerators NuGet pack failure (Lombiq Technologies: NEST-608) #19043

Open
sarahelsaig wants to merge 2 commits intoOrchardCMS:mainfrom
Lombiq:issue/NEST-608-source-generators
Open

Fix OrchardCore.SourceGenerators NuGet pack failure (Lombiq Technologies: NEST-608) #19043
sarahelsaig wants to merge 2 commits intoOrchardCMS:mainfrom
Lombiq:issue/NEST-608-source-generators

Conversation

@sarahelsaig
Copy link
Contributor

Fixes #19038

…tPath is missing the framework identifier so it has to be included in the path.
@hishamco hishamco requested a review from gvkries March 21, 2026 19:25
<IsRoslynComponent>true</IsRoslynComponent>
<EnforceExtendedAnalyzerRules>true</EnforceExtendedAnalyzerRules>
<IncludeBuildOutput>false</IncludeBuildOutput>
<EmitCompilerGeneratedFiles>true</EmitCompilerGeneratedFiles>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this alone is not the correct fix, because it would place the assembly in the lib folder as a normal reference. See #19040 for a different approach.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It places the assembly in both places:

image

Which is not harmful, and it means more consistent behavior and that this project won't have an irregular bin folder path. On the other hand, Copilot's "fix" looks very hackish and confusing. I really don't like this, even if it's 0B:

image

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.

no new build after [3.0.0-preview-18943]

2 participants