Question: How to configure project to always build as a "standalone app"

I’m looking at what it will take to port some of my projects onto the new SDK. My projects are already MSBuild-based, and just use a small set of properties and targets to get references, configurations, output paths, etc. consistent. For most of my projects, I’m really only interested in building things fully standalone (i.e. never as a portable/shared framework app). Is there an easy way that I can set up my projects with the new tooling to accomplish this? Ideally, whenever I built an executable project, all of my runtime dependencies from nuget would be copied next to my project output. Essentially, I’m looking for something similar to how the regular MSBuild targets handle <CopyNuGetImplementations>true</CopyNuGetImplementations>.

[natemcmaster]

Just ran into this as well. Is there anyway that users can write this kind of logic in their project?

<PropertyGroup>
    <RuntimeIdentifier>$(CurrentRid)</RuntimeIdentifer>
</PropertyGroup>

This way ‘dotnet publish’ always publishes as standalone for the current platform, without having to add ‘-r $rid’.

[mellinoe]

Yes, +1 to @natemcmaster 's question. Can we have an MSBuild property exposed for that? I know we would find something like that very useful in corefx, as well.