Looks like the trial package creation just sets an msbuild property that is used to affect the PackageId but there must be a bug in the sdk pack handling whereby when it creates the nuspec and gather's the package names for the project references they must just read the PackageId from the csproj file without considering the current properties.

@igandrews @gmurray81 Who can push a fixed Trial package, so we can get the examples project building?

I’ll look to update the build script today. Since it doesn’t look like this was something recently broken I didn’t rush into this.

Thank you @igandrews! These packages are relatively new, but if anyone tries to use them, they simply won't work. We are also setting up GH actions CI for this repository and the task is blocked by the Trial packages.

I came across this yesterday too. Took me a solid hour to figure it out and fix it locally by myself. If anyone runs across this issue - a simple fix is to add the local proget to the nuget resources of the solution.

I believe this is fixed in the build BTW, we just need to produce a new set of packages after fixing a last build problem.

@gmurray81 Is there an ETA on the new trial packages?

Bump.

@kdinev this and NG 16 are just waiting on some of the release scripts coming back online in devops. Brian was working on this, will check how its going in our git scrum this morning.

also I think we were investigating a regression still.

BTW, these scripts are migrated apparently, but untested until we try to push. Still waiting on that regression to be investigated first, though.