Is it appropriate to use KPM and dotnet cli tooling side by side?

Question

I'm in the process of experimenting with migrating to an ASP.net 4.6 site to DNX.

At the time of writing it's early days for the tooling in general.

I've read that dotnet cli aims to replace KRE, KVM, KPM. However is it appropriate to use kpm along side dotnet command line tools? I'm attempting to diagnose some troubles I'm having but kpm seems to have more diagnostics functionality.

Answer 1

kvm/kre/kpm were replaced by dnx/dnvm/dnu. However dnx et al. is going away in favor of dotnet CLI. For now, until dotnet CLI and matching ASP.NET Core is released use rc1-final and stick with dnx.