Skip to content

If using nightly builds, are we about to break with the move to dotnet CLI? #1191

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
guardrex opened this issue Dec 21, 2015 · 2 comments
Closed

Comments

@guardrex
Copy link
Contributor

@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?

@Tratcher
Copy link
Member

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.

@guardrex
Copy link
Contributor Author

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.

SteveSandersonMS added a commit that referenced this issue Nov 27, 2018
* Clarify debug instructions further

* Fix error message

* Add "using Microsoft.JSInterop" in templates

* Clarify template descriptions
@ghost ghost locked as resolved and limited conversation to collaborators Dec 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants