Include new packages in nuspec file

[DavoudEshtehari]

• Alphabetically has been sorted.

[johnnypham]

The following are present in netcore csproj but still missing in the changes:

  <PackageReference Include="System.Threading.Tasks" Version="$(SystemThreadingTasksVersion)" />
  <PackageReference Include="System.Memory" Version="$(SystemMemoryVersion)" />
  <PackageReference Include="System.Globalization" Version="$(SystemGlobalizationVersion)" />
  <PackageReference Include="System.Xml.ReaderWriter" Version="$(SystemXmlReaderWriterVersion)" />

Should we include every package? @cheenamalhotra

[cheenamalhotra]

The following are present in netcore csproj but still missing in the changes:

  <PackageReference Include="System.Threading.Tasks" Version="$(SystemThreadingTasksVersion)" />
  <PackageReference Include="System.Memory" Version="$(SystemMemoryVersion)" />
  <PackageReference Include="System.Globalization" Version="$(SystemGlobalizationVersion)" />
  <PackageReference Include="System.Xml.ReaderWriter" Version="$(SystemXmlReaderWriterVersion)" />

Should we include every package? @cheenamalhotra

Good observation, I could build netcore project without these packages included.
If they're not needed, they could be removed perhaps? Can we try to remove them in this PR?

[DavoudEshtehari]

All the pipelines passed without those 4 package references on .NET Core, yesterday. Updated Versions.props too.

[ErikEJ]

You could consider building the nuget package using msbuild...

[JRahnama]

You could consider building the nuget package using msbuild...

that is how we build the driver and tests, if I have got your point correct. Building driver using msbuild -p:Configuration=$(Configuration) will also lead to create a folder named package with the created nuget inside it.

[cheenamalhotra]

You could consider building the nuget package using msbuild...

that is how we build the driver and tests, if I have got your point correct. Building driver using msbuild -p:Configuration=$(Configuration) will also lead to create a folder named package with the created nuget inside it.

That's our scripts doing all the work. I think @ErikEJ is referring to msbuild -t:pack (Link).

[ErikEJ]

Yes, I meant define the package in the .csproj, this also makes dependency management much simpler

[cheenamalhotra]

Our process is distributed since we need to Sign the DLLs before packing when we build release packages. For that reason we build and pack in different steps, but we can investigate any possibilities to ease this process.