You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@davidfowl The changes coming soon for dotnet CLI look like they will break us, perhaps in VS, perhaps on the server (i.e., HttpPlatformHandler), or both. What's the outlook for those of us using nightly builds and dotnet CLI?
I wonder if at some point I should get off of nightly builds and freeze my runtime version and packages at their current versions and ride out all the following changes until rc2-final hits. Sound good? If so, could you cats fire out an Announcement "Freeze!" to signal when we should do that?
The text was updated successfully, but these errors were encountered:
Yes there will be breaks, but they should be gradual. You saw the recent hosting changes. Now that there's just one command and it points to your app assembly it should be easy enough to transition from dnx web to dotnet MyApp, or just MyApp.exe. If you're concerned about breaks you can snapshot your dependency versions and increment them manually as needed.
I made the hosting changes ... works great here, so I should be ready.
Sounds like you're suggesting that processPath="%DNX_PATH%" will automatically take care of that final transition with runtime/package changes that are coming soon for dotnet. If so, I'm good.
@davidfowl The changes coming soon for dotnet CLI look like they will break us, perhaps in VS, perhaps on the server (i.e., HttpPlatformHandler), or both. What's the outlook for those of us using nightly builds and dotnet CLI?
I wonder if at some point I should get off of nightly builds and freeze my runtime version and packages at their current versions and ride out all the following changes until
rc2-final
hits. Sound good? If so, could you cats fire out an Announcement "Freeze!" to signal when we should do that?The text was updated successfully, but these errors were encountered: