Fix NETSDK1152 in auto-generated projects

[timcassell]

#2931 (comment)

[DrewScoggins]

We are trying this to see if it fixes the issue.

[DrewScoggins]

This does seem to fix the 1152 issue. We are now seeing a new issue however.

error NETSDK1005: Assets file 'C:\git\performance\artifacts\bin\MicroBenchmarks\Release\net11.0\MicroBenchmarks-Job-JGNDWD-1\obj\project.assets.json' doesn't have a target for 'net11.0'. Ensure that restore has run and that you have included 'net11.0' in the TargetFrameworks for your project. [C:\git\performance\artifacts\bin\MicroBenchmarks\Release\net11.0\MicroBenchmarks-Job-JGNDWD-1\DllGatherer.csproj::TargetFramework=net11.0]

[timcassell]

Can you share the contents of the generated directory?

C:\git\performance\artifacts\bin\MicroBenchmarks\Release\net11.0\MicroBenchmarks-Job-JGNDWD-1

[DrewScoggins]

https://pvscmdupload.web.z22.core.windows.net/docs/bin.zip

[timcassell]

I'm unable to view that.

[DrewScoggins]

Sorry, Github mangled it when I copied it in. https://pvscmdupload.z22.web.core.windows.net/docs/bin.zip

[timcassell]

There was no .bat or .sh files?

[Edit] Oh I guess because building the DllGatherer.csproj failed in the GenerateProject step before GenerateBuildScript could run.

[timcassell]

Can you try run it with the latest commit and upload the new directory contents?

[timcassell]

Btw, does PERFLAB_TARGET_FRAMEWORKS contain net11.0?

[DrewScoggins]

To answer your last question, yes, PERFLAB_TARGET_FRAMEWORKS does contain net11.0. For the first question, I believe that we ran the most recent commit, and we were not seeing the failure in our runs, but I am not completely certain. All I know is that right now our pipeline is in a good state, except for WASM. We are still seeing a different failure there, but I honestly don't remember the issue from before I went on vacation.

[timcassell]

Do you mean the most recent commit in this branch? Or on master? That's strange if the build is actually succeeding there, all I did was warn when the references build falls, then I would expect the following benchmark build to also fail, not succeed.