Errors when building SampleCpp or packaging Nuget about cpp_client_telemetry HOT 5 CLOSED

Thanks for the detailed info. I was able to build after reverting to last week's bits. We will work to generate a nuget package for our use-case.

from cpp_client_telemetry.

We'll work on doc updates and more user-friendly nuget scripts, but as a lower priority (ETA: October-November). We might be able to resurrect the nuget package build, if that activity gets staffed / resourced by SLT. If you feel like there is a need for one centralized team in Azure PIE to provide the nuget, please highlight that ask to @tvilliers

from cpp_client_telemetry.

We don't currently officially support the nuget build process. This is a good resource that explains how to create a nuget and how nuspec works :
https://blogs.msdn.microsoft.com/mvpawardprogram/2016/06/28/creating-nuget-packages/

Linking issue is a recent regression from yesterday, you should be able to rollback to Friday's commit id. The fix for that issue is on code review in the list of open Pull Requests, to be merged tomorrow.

from cpp_client_telemetry.

In order to build the full set of binaries:

mkdir dist\aria-windows-sdk
build-all.bat
tools\sdk-create.cmd

This will build SDK and copy all binaries into dist folder.

After that please run the nuget packaging scripts, that are expecting the binaries in a certain location. You do not need to package the unrelated libraries (e.g. net40 SKU), only the ones you need for your product.

If you are packaging a nuget for native Universal Windows app, then you will use Microsoft.Applications.Telemetry.Windows.native.dll and its flavors (x86,x64,arm,arm64), both (Release,Debug). We do not provide code signing as part of our build pipeline. In order to provide a nuget consumable within your organization you have to rely on your org code signing pipeline.

If you are packaging a nuget for native Win32 Desktop app, then you will use the ClientTelemetry.dll and its flavors (x86,x64,arm64).

Linking issue described in your scenario is a recent regression. You can cherry-pick the fix from here to try, or wait until it gets merged in the master #93

The rest is a documentation issue for a process that we do not currently maintain nor officially support at this point due to resourcing constraints. Not a bug. I would suggest to review where the dlls get published after the build is done. Then review some common guidelines on creating a nuget package geared towards consumption within your org.

from cpp_client_telemetry.

Docs follow up #97.
@maxgolov do we have an issue to track the nuget script request?

from cpp_client_telemetry.