C#•2y ago

dotnet publish fails due to a build error that doesn't happen when I run just dotnet build

Hi there,
I'm having a weird thing going on here.

I use Jetbrains Rider, and have a project that uses a class library a colleague made. The error that is happening says that

Required member X.Y must be set in the object initializer or attribute constructor

Required member X.Y must be set in the object initializer or attribute constructor

Required member X.Y must be set in the object initializer or attribute constructor

Required member X.Y must be set in the object initializer or attribute constructor. And this is super weird to see as an Error and not a warning, because 1) we never instantiate that class, it's resolved through DI and 2) this works in a regular build. So it's only during the publish part this goes wrong.

I don't even know where to begin troubleshooting this. Any advice?

Pobiega•6/14/24, 8:16 AM

Do you get the same behaviour when doing build/publish via Cli instead of via rider?

Angius•6/14/24, 8:16 AM

Is it maybe an AoT publish? Regular run might be setting that required prop via relfections, while AoT might be trying to not use reflection there

Pobiega•6/14/24, 8:16 AM

Yeah thats my guess too

EsaOP•6/14/24, 8:30 AM

I haven't actually tried these things manually

EsaOP•6/14/24, 8:31 AM

I'll give it a try

Pobiega•6/14/24, 8:31 AM

What publish arguments are you using?

EsaOP•6/14/24, 8:32 AM

so now I just tried a plain dotnet publishdotnet publish, and that worked

Pobiega•6/14/24, 8:32 AM

You could just do a --nobuild or whatever the flag is, if its a "normal" publish

EsaOP•6/14/24, 8:32 AM

but the publish I've set up, is like this

Pobiega•6/14/24, 8:33 AM

$singlefile

PPobiega $singlefile

MODiX•6/14/24, 8:33 AM

dotnet publish -c Release -r <runtime identifier> -p:PublishSingleFile=truedotnet publish -c Release -r <runtime identifier> -p:PublishSingleFile=true
Use of -p:PublishSingleFile=true-p:PublishSingleFile=true implies --self-contained true--self-contained true. Add --self-contained false--self-contained false to publish as runtime-dependent.
-r RID-r RID and -p:PublishSingleFile=true-p:PublishSingleFile=true can be moved to .csproj as the following properties:

<RuntimeIdentifier>RID</RuntimeIdentifier>
<PublishSingleFile>true</PublishSingleFile>

<RuntimeIdentifier>RID</RuntimeIdentifier>
<PublishSingleFile>true</PublishSingleFile>

but to target multiple RIDs, you have to use dotnet publishdotnet publish with the -r-r option for each RID.
You can also add -p:IncludeNativeLibrariesForSelfExtract=true-p:IncludeNativeLibrariesForSelfExtract=true to include native libraries (like Common Language Runtime dlls) in the output executable.
You might want to instead publish your application compiled Ahead Of Time to native code, see $nativeaot for examples.
Single file publishing | Runtime Identifier (RID) catalog | dotnet publishdotnet publish

Pobiega•6/14/24, 8:33 AM

Use the above to reproduce that publish from CLI, see if you get the same error

EsaOP•6/14/24, 8:34 AM

Hm, what's a runtime identifier in this case?

Pobiega•6/14/24, 8:34 AM

Win-x64

EsaOP•6/14/24, 8:35 AM

dotnet publish -c Release -r win-x64 -p:PublishSingleFile=truedotnet publish -c Release -r win-x64 -p:PublishSingleFile=true
This command also worked

EsaOP•6/14/24, 8:36 AM

Pobiega•6/14/24, 8:50 AM

only difference I can see then is the trimming

dotnet publish fails due to a build error that doesn't happen when I run just dotnet build

Similar Threads

Similar Threads

Similar Threads