@TravisEz13 The nuget packages use the release tag to set the version for the package. Also, it is used to set the version of the ref assembly. That needs to be fixed too. Is that change happening in a different PR?

@adityapatwardhan The NuGet package needs to start using the runtime DLL, per yesterday's conversation. If we don't go down that path, I think the right thing to do is to read the fileversion from the runtime and use that.

@TravisEz13 are you adding the change we discussed about the nuget ref assembly using the file version?

@TravisEz13 and me also discussed about using the runtime assembly for the ref, but there are some complications regarding it.

1. Which runtime assembly do we use, windows or linux?
2. Should the assemblies just be under lib folder? But, I believe lib does not support having RID under it.
3. Can we just have runtime folder? Will the appropriate assembly be picked for compilation?

Here are my opinions:

Which runtime assembly do we use, windows or linux?

To be consistent with the existing NuGet package, we should use the Unix version of the runtime DLL.
It's not the ideal solution for sure, but should be fine as a temp workaround.

Should the assemblies just be under lib folder? But, I believe lib does not support having RID under it.

I guess for now we can just replace the ref assembly with the runtime assembly and keep the folder structure unchanged.

Can we just have runtime folder? Will the appropriate assembly be picked for compilation?

I don't think the runtime folder alone would work.

I think this PR is ready to merge. Is there anything we are waiting on?

🎉v7.2.0-preview.7 has been released which incorporates this pull request.:tada:

Handy links:

• Release Notes