title: Do I still need the RuntimeFrameworkVersion project setting with .NET Core 2.1?
body: <p>With .NET Core 1.1 I had the following problem: Whenever I updated the NuGet packages in my app, my customers were forced to update their .NET Core runtime, which was annoying. I solved this by setting RuntimeFrameworkVersion to 1.1.1, so my app would run on every system with a runtime 1.1.x (x>=1) installed. So even when I upgraded my package references to 1.1.5, the app would still work on a system with only runtime 1.1.1 installed.</p>
  
  <p>I understand that with .NET Core 2.1 the runtime selection behavior is a bit different (see for example this answer here: <a href="https://stackoverflow.com/a/46778275/487356">https://stackoverflow.com/a/46778275/487356</a>) - but I don't really understand what this means for my particular scenario.</p>
  
  <p>So... Does it make sense to set RuntimeFrameworkVersion to 2.1.0 for a .NET Core 2.1 app? Or is it safe to omit that? (Keep in mind I want my app to be able to run with any 2.1.x runtime installed - even if my referenced packages are newer).</p>