Victor Vazquez

> Thanks for proposing this! > > I'm wary of adding a new overly-specific configuration option. Generally, if there was a way to indicate more items below or after the...

the `ENTRYPOINT` is expected for passing build command directly from VS. See: https://devblogs.microsoft.com/cppblog/using-msvc-in-a-docker-container-for-your-c-projects/#trying-it-all-out

@danieljurek don't we use the `success()` condition for this? so only if build and test pass, then we run the coverage step

Don't think this is a good idea. We might want to add some help for users about how to install CMake 3.12 instead, (some link or docs, it is really...

We would only need to run `rm -rf *` inside /build folder before the next configuration.. So, we would reduce or Pipeline to Win86, Win64, Linux64 and Mac64. Then, on...

This is due to Ninja version `1.10` Using Ninja version `1.8.2`, the issue is just a warning but there's no error. Here's the 1.8.2 Ninja install link: https://github.com/ninja-build/ninja/releases/tag/v1.8.2 Quick workaround...

I think @ahsonkhan did something about adding Lint... Can you confirm Ahson? Can we close this then?

I think this was already done by @antkmsft ?? as part of the CI legs enhancement?

@danieljurek based on Ashon comment >The IoT client already has extensive samples which is the mainline scenario (for example https://github.com/Azure/azure-sdk-for-c/tree/master/sdk/samples/iot/provisioning/src). Can we consider this issue done? It makes sense that...

@RickWinter , we should only create one playback-record test framework for C++ and see if we can reuse it here.