-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
dnx . kestrel crashes on OSX (1.0.0-beta4-11566) (now: 1.0.0-beta5-11682) #518
Comments
@chanan what version of Mono are you running? I'm guessing you're still at 3.x as this is a known issue with that setup. See aspnet/DataProtection#68 Upgrading to 4.0.1 via Homebrew won't help much as you'll run into another issue. See #498 |
@miguellira @chanan
Which resulted in this exception:
Apparently something fubar was still running
The above showed me the PID after I killed it everything was working well. Dnvm: 1.0.0-beta5-10368 Edit: |
After some upgrades I now have: and now running dnx . kestrel:
|
You're missing a slew of other versions. Try reading my blog post http://davidfowl.com/diagnosing-dependency-issues-with-asp-net-5/. Don't cross the streams! |
I hit the same exception as @chanan. I started with the empty project which ran OK then added Mvc6. (I also tried running with the beta5 dnx and got the IApplicationEnvironment error) Is there some way through or around this? I basically was just trying to get a simple Mvc6 app running with Code and was working from their AspNet5 page. Also, I read the post, @davidfowl , but I'm still not clear on how to get updated properly. If my DNX is beta5, how do I get on the beta5 package train? Is there another feed for that or is it just not ready yet? |
@jdasilva What package versions are you using? |
|
So you're using beta4 packages and you want to use beta5 packages. Change the version... |
"dependencies": {
"Microsoft.AspNet.Mvc": "6.0.0-beta5-*",
"Microsoft.Framework.ConfigurationModel.Json": "1.0.0-beta5-*",
"Microsoft.AspNet.Server.IIS": "1.0.0-beta5-*",
"Microsoft.AspNet.Server.WebListener": "1.0.0-beta5-*",
"Kestrel": "1.0.0-beta5-*"
} beta5-* will keep you on the latest beta5 bits |
@davidfowl Thank you very much! That helped because then I realized I needed to configure dnu properly (https://github.com/aspnet/Home/wiki/Configuring-the-feed-used-by-dnu-to-restore-packages). I did also need to
Thanks again! |
I had run this:
I couldn't upgrade mono
resulted in
Had to run:
to remove mono 3.12.1 and afterwards another command to remove mono 4.0.1
after that I was able to install the 4.0.1 version of mono correctly again
I changed the project.json file to match it like this:
Afterwards I ran this:
to have it running on 1.0.0-beta5-11682 at last I had to run another:
and then finally:
AAAAAAND
does not work |
@davidfowl I haven't been as successful as some of the others on this thread. I changed the project.json (by the way, tried to recreate from yo aspnet but it is still set to beta4), upgrade mono to 4.0.1 and tried both on the stable and unstable feeds but in either case dnu restore does not find the packages: Unable to locate Microsoft.AspNet.Mvc >= 6.0.0-beta5-* |
Likely because you don't have the right set of feeds configured |
These are the feeds in dnvm: Default Stable: https://www.nuget.org/api/v2 Looks correct, I think. |
|
@BrennanConroy I am not sure what you mean. The issue is when I do dnu restore it does not find the beta-5 packages as detailed above. |
You listed your dnvm feeds, those are use by |
@BrennanConroy Thanks made progress, now I am getting this error when running dnx . kestrel:
|
I want to make a semi announcement here related to using bleeding edge bits. Please don't use them if you're not willing to do some work to keep with the breaking changes that we make. We made the Announcements repository to notify people of breaking changes like this. TL;DR if you're unwilling to look at commits and follow along closely with the team, use the stable beta4 bits. If you want to play along with our changes then you need to do the work to keep up. Follow Announcements, follow the commits. @chanan Your specific issue comes from a design change made to Configuration that forces callers to pass in the full path to the Configuration constructor. aspnet/Configuration@7efb7b2 You have to pass it in now or alway use full paths to config files. |
@davidfowl Thanks for the tip. I've been watching the Announcements repo for a few days now and saw your recent commits. Using GitHub issues for this seems odd but it works and I am fine with it. However, it sucks that if you're on OS X and you want to use the latest bits you're stuck with Mono 4.0.1 which results in an always failing Visual Studio Code would feel more like a first rate "IDE" if I could get rid of those red squiggles. :( Maybe a list of well known issues and/or links to your write ups on the Home repo readme would avoid some of these repeating issue entries. |
…master [automated] Merge branch 'release/2.2' => 'master'
checked appliesd to the query string. @rynowak #518 #Issue: aspnet/Mvc#7720
changes are made as suggestions. @rynowak #518 #Issue: aspnet/Mvc#7720
dnvm version: 1.0.0-beta5-10372
dnu version: 1.0.0-beta4-11566
Project unmodified WebApplication generated from scaffold.
Error when running dnx . kestrel:
The text was updated successfully, but these errors were encountered: