Skip to content
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.

Sign up for GitHub

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

Jump to bottom

sample HellwMvc & HelloWeb can't executing. #497

Closed
yanghongjie opened this issue Apr 29, 2015 · 5 comments
Closed

sample HellwMvc & HelloWeb can't executing. #497

yanghongjie opened this issue Apr 29, 2015 · 5 comments
Labels
question

Comments

@yanghongjie
Copy link

image

dnvm upgradednvm already executed.

image

k web can work
image
@yanghongjie
Copy link
Author

but ConsoleApp . run success.

@NTaylorMullen
Copy link
Contributor

You need to run dnu restore

@yanghongjie
Copy link
Author

hi NTaylorMullen ,I'm already executed dnu restore .
if execut k web sample can work ,but k already rename dnx?
so execut dnx . web can't work.

@NTaylorMullen
Copy link
Contributor

Ahhh. So it looks like you're utilizing beta3 packages. Problem is dnx is beta4. Therefore your k web command is running the old kre runtime.

Update your project.json referrences to utilize beta4 packages. If you don't already have a feed available for the beta4 packages (they aren't on nuget.org) you can add: https://www.myget.org/F/aspnetrelease/api/v2

@yanghongjie
Copy link
Author

Yes, so that really it. At the same time I find an article
http://chris.59north.com/post/Getting-the-ASPNET-5-samples-to-work-on-Windows-with-the-new-dnvm

jkotalik added a commit that referenced this issue Nov 1, 2018
@jkotalik
Adds RequestHandler dll and hostfxr changes from ANCM (#497)
c3bc6fe
natemcmaster added a commit that referenced this issue Nov 14, 2018
@natemcmaster
Resolve flaky tests (#497)
4c49d5c 
1. Prevent an ObjectDisposedException in dotnet-watch on slower machines
2. Fix flakiness caused by PID reuse
3. Fix flakiness in tests that await the restart of dotnet-watch. The `.TimeoutAfter` method doesn't cancel the long-running task. This left 2 readers running on dotnet-watch output which caused indeterminate test outcome.
ryanbrandenburg pushed a commit that referenced this issue Nov 22, 2018
@jbagga
Use previous version of Appveyor image to avoid dotnet bug (#497)
e014f72
natemcmaster pushed a commit that referenced this issue Nov 22, 2018
@rynowak
Merge pull request #497 from dotnet-maestro-bot/merge/release/2.2-to-…
3eb50ae 
…master

[automated] Merge branch 'release/2.2' => 'master'
@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.
Assignees
No one assigned
Labels
question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@NTaylorMullen @yanghongjie