-
Notifications
You must be signed in to change notification settings - Fork 224
Debug.Assert crash the host (dnx.exe has stopped working) #2778
Comments
Oh, and I don't have VS 2015 installed, all work done from CLI and the standard tools. |
After updating your repro code but I was able to repro this on: project.json
program.cs
|
Sorry my I don't have the Let me know if I can be of any help. |
If you didn't have a reference to |
This runs fine with CLR by the way. Fails on both X64 and X86 CoreCLRs. |
Beats me - I just have no idea. But since you asked, I had to double-check my
Maybe some transitive dependency thing going on? But then again, I was under the impression that I really must specify all the bits I was to use. Some way I can see how it was made available? |
Yeah, |
BTW, thanks to transitive dependencies, you don't need to specify all the assemblies that you use. :) |
What about
|
Yup, |
Ah, so it works like that by design? Yeah, now I remember, thats one of the changes in package management > DNX. So then this dependency "subissue" is demystified and resolved, right? 👍 |
Correct :) That whole chain is brought in by |
This is by design - Debug.Assert() calls Environment.FailFast(), which will cause this dialog to show up. I think the source of confusion here is that the dialog says "dnx.exe" instead of @per-samuelsson's assembly name, however that is also expected since the actual process running the code is dnx.exe. |
@CesarBS Should |
Yo,
Chasing a deadline, so I haven't done any real investigation, but on my env,
Debug.Assert(false)
produce the following:Env:
Project.json
Program.cs:
Let me know if u can not repro it on your end, and I'll try allocate some time to assist if you want that.
The text was updated successfully, but these errors were encountered: