System.IO.EndOfStreamException when building with latest DNVM and Mono 4.0.1 #498

miguellira · 2015-04-29T03:50:21Z

Running into a System.IO.EndOfStreamException when building the latest sample ConsoleApp using the latest DNVM and the recently released Mono 4.0.1.

Miguels-MBP:~ miguellira$ dnvm list

Active Version              Runtime Arch Location             Alias
------ -------              ------- ---- --------             -----
  *    1.0.0-beta5-11649    mono         ~/.dnx/runtimes      default

Mono JIT compiler version 4.0.1 (tarball Mon Apr 27 01:00:48 PDT 2015)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
    TLS:           normal
    SIGSEGV:       altstack
    Notification:  kqueue
    Architecture:  amd64
    Disabled:      none
    Misc:          softdebug 
    LLVM:          supported, not enabled.
    GC:            sgen

Miguels-MBP:ConsoleApp miguellira$ dnu build

Building ConsoleApp for DNX,Version=v4.5.1
  Using Project dependency ConsoleApp 1.0.0
    Source: /Users/miguellira/Downloads/Home-dev/samples/latest/ConsoleApp/project.json

  Using Assembly dependency framework/mscorlib 4.0.0.0
    Source: /usr/local/Cellar/mono/4.0.1/lib/mono/4.5/mscorlib.dll

  Using Assembly dependency framework/System 4.0.0.0
    Source: /usr/local/Cellar/mono/4.0.1/lib/mono/4.5/System.dll

  Using Assembly dependency framework/System.Core 4.0.0.0
    Source: /usr/local/Cellar/mono/4.0.1/lib/mono/4.5/System.Core.dll

  Using Assembly dependency framework/Microsoft.CSharp 4.0.0.0
    Source: /usr/local/Cellar/mono/4.0.1/lib/mono/4.5/Microsoft.CSharp.dll

System.IO.EndOfStreamException: Failed to read past end of stream.
  at System.IO.BinaryReader.ReadChar () [0x00000] in <filename unknown>:0 
  at Microsoft.CodeAnalysis.CvtResFile.ReadStringOrID (System.IO.BinaryReader fhIn) [0x00000] in <filename unknown>:0 
  at Microsoft.CodeAnalysis.CvtResFile.ReadResFile (System.IO.Stream stream) [0x00000] in <filename unknown>:0 
  at Microsoft.CodeAnalysis.Compilation.MakeWin32ResourceList (System.IO.Stream win32Resources, Microsoft.CodeAnalysis.DiagnosticBag diagnostics) [0x00000] in <filename unknown>:0 
  at Microsoft.CodeAnalysis.CSharp.CSharpCompilation.SetupWin32Resources (Microsoft.CodeAnalysis.CSharp.Emit.PEModuleBuilder moduleBeingBuilt, System.IO.Stream win32Resources, Microsoft.CodeAnalysis.DiagnosticBag diagnostics) [0x00000] in <filename unknown>:0 
  at Microsoft.CodeAnalysis.CSharp.CSharpCompilation.CompileImpl (Microsoft.CodeAnalysis.Emit.CommonPEModuleBuilder moduleBuilder, System.IO.Stream win32Resources, System.IO.Stream xmlDocStream, Boolean generateDebugInfo, Microsoft.CodeAnalysis.DiagnosticBag diagnostics, System.Predicate`1 filterOpt, CancellationToken cancellationToken) [0x00000] in <filename unknown>:0 
  at Microsoft.CodeAnalysis.Compilation.Compile (Microsoft.CodeAnalysis.Emit.CommonPEModuleBuilder moduleBuilder, System.IO.Stream win32Resources, System.IO.Stream xmlDocStream, Boolean generateDebugInfo, Microsoft.CodeAnalysis.DiagnosticBag diagnostics, System.Predicate`1 filterOpt, CancellationToken cancellationToken) [0x00000] in <filename unknown>:0 
  at Microsoft.CodeAnalysis.Compilation.Emit (Microsoft.CodeAnalysis.EmitStreamProvider peStreamProvider, Microsoft.CodeAnalysis.EmitStreamProvider pdbStreamProvider, Microsoft.CodeAnalysis.EmitStreamProvider xmlDocumentationStreamProvider, Microsoft.CodeAnalysis.EmitStreamProvider win32ResourcesStreamProvider, IEnumerable`1 manifestResources, Microsoft.CodeAnalysis.Emit.EmitOptions options, Microsoft.CodeAnalysis.CodeGen.CompilationTestData testData, System.Func`1 getHostDiagnostics, CancellationToken cancellationToken) [0x00000] in <filename unknown>:0 
  at Microsoft.CodeAnalysis.Compilation.Emit (System.IO.Stream peStream, System.IO.Stream pdbStream, System.IO.Stream xmlDocumentationStream, System.IO.Stream win32Resources, IEnumerable`1 manifestResources, Microsoft.CodeAnalysis.Emit.EmitOptions options, Microsoft.CodeAnalysis.CodeGen.CompilationTestData testData, System.Func`1 getHostDiagnostics, CancellationToken cancellationToken) [0x00000] in <filename unknown>:0 
  at Microsoft.CodeAnalysis.Compilation.Emit (System.IO.Stream peStream, System.IO.Stream pdbStream, System.IO.Stream xmlDocumentationStream, System.IO.Stream win32Resources, IEnumerable`1 manifestResources, Microsoft.CodeAnalysis.Emit.EmitOptions options, CancellationToken cancellationToken) [0x00000] in <filename unknown>:0 
  at Microsoft.Framework.Runtime.Roslyn.RoslynProjectReference.EmitAssembly (System.String outputPath) [0x00000] in <filename unknown>:0 
  at Microsoft.Framework.PackageManager.ProjectBuilder.Build (System.String name, System.String outputPath) [0x00000] in <filename unknown>:0 
  at Microsoft.Framework.PackageManager.BuildContext.Build (System.Collections.Generic.List`1 diagnostics) [0x00000] in <filename unknown>:0 
  at Microsoft.Framework.PackageManager.BuildManager.Build () [0x00000] in <filename unknown>:0 
  at Microsoft.Framework.PackageManager.Program+<>c__DisplayClass3_4.<Main>b__8 () [0x00000] in <filename unknown>:0 
  at Microsoft.Framework.Runtime.Common.CommandLine.CommandLineApplication.Execute (System.String[] args) [0x00000] in <filename unknown>:0 
  at Microsoft.Framework.PackageManager.Program.Main (System.String[] args) [0x00000] in <filename unknown>:0 
  at (wrapper managed-to-native) System.Reflection.MonoMethod:InternalInvoke (System.Reflection.MonoMethod,object,object[],System.Exception&)
  at System.Reflection.MonoMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00000] in <filename unknown>:0 
--- End of stack trace from previous location where exception was thrown ---
  at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x00000] in <filename unknown>:0 
  at Microsoft.Framework.Runtime.Common.EntryPointExecutor.Execute (System.Reflection.Assembly assembly, System.String[] args, IServiceProvider serviceProvider) [0x00000] in <filename unknown>:0 
  at dnx.host.Bootstrapper.RunAsync (System.Collections.Generic.List`1 args) [0x00000] in <filename unknown>:0

The text was updated successfully, but these errors were encountered:

suhasj · 2015-04-29T18:34:54Z

This is known issue and we have notified the Mono team
https://bugzilla.xamarin.com/show_bug.cgi?id=29499

miguellira · 2015-04-29T18:42:52Z

Thanks @suhasj.

Is there a preferred DNVM/Mono combination at the moment? Since the mono Homebrew formula has been updated to 4.0.1 is there a recommended way to get a stable environment to build/run the samples?

suhasj · 2015-04-29T18:45:25Z

/cc @glennc

I am not sure of this since I have hit issues with both 4.0.1 and 4.1.0

javi830810 · 2015-04-29T20:09:30Z

Same issue here, mono 4.0.1 and dnx 4.5.1, please advice

davidfowl · 2015-04-29T20:10:52Z

beta4 + mono 4.0.1 and 4.1 have this issue and there's no known workaround.

ThorstenHans · 2015-04-30T09:03:08Z

Issue also appears in the following combination
Mono 4.0.1
dnx and dnu 1.0.0-beta5-11649
dnvm 1.0.0-beta5-10371

Jabe · 2015-04-30T12:24:32Z

😢

miguellira · 2015-04-30T14:33:08Z

FWIW...

If you, like me, decided to uninstall Mono 3.x after installing 4.x and will like to get back to a somewhat stable state. You can unlink Mono 4.x and reinstall 3.x by doing the following:

brew unlink mono
brew install https://raw.githubusercontent.com/Homebrew/homebrew/68a18ac660515e313cd175c550e3065320dfadec/Library/Formula/mono.rb

Unfortunately, all of the issues that exist with running Mono 3.x and the latest DNX will continue, but at least you'll be able to play around with Visual Studio Code on Mac :-)

jamespack · 2015-05-05T03:38:22Z

Possible workaround? (This is what I did)

clone mono repository, compile and install following the directions here http://www.mono-project.com/docs/compiling-mono/
brew tap aspnet/dnx
brew upgrade
brew install dnvm --without-mono

I had to uninstall everything mono-related that brew installed. But after doing this I was able to run dnu build, dnx . kestrel, etc

miguellira · 2015-05-05T04:03:14Z

@jpack61108 I haven't gone as far as building/running Mono from the latest repo. Curious... Did you have Mono installed prior to this, whether via brew or otherwise? Also, where/how did you discover the --without-mono switch? I haven't seen that documented anywhere. Thanks.

jamespack · 2015-05-05T04:06:20Z

Yes I did, from brew. I had to remove all of the brew stuff because of all the symlinking that it does. So far it is working as advertised.
James
Sent from Outlook

On Mon, May 4, 2015 at 9:03 PM -0700, "Miguel Lira" [email protected] wrote:

@jpack61108 I haven't gone as far as building/running Mono from the latest repo. Curious... Did you have Mono installed prior to this, whether via brew or otherwise? Also, where/how did you discover the --without-mono switch? I haven't seen that documented anywhere. Thanks.

—
Reply to this email directly or view it on GitHub.

jamespack · 2015-05-05T04:07:50Z

Sorry brew options $FORMULA_NAME will show you the available options for install. I believe it is on the brew wiki.
James

Sent from Outlook

On Mon, May 4, 2015 at 9:06 PM -0700, "Jimmy Pack" [email protected] wrote:

Yes I did, from brew. I had to remove all of the brew stuff because of all the symlinking that it does. So far it is working as advertised.
James
Sent from Outlook

On Mon, May 4, 2015 at 9:03 PM -0700, "Miguel Lira" [email protected] wrote:

@jpack61108 I haven't gone as far as building/running Mono from the latest repo. Curious... Did you have Mono installed prior to this, whether via brew or otherwise? Also, where/how did you discover the --without-mono switch? I haven't seen that documented anywhere. Thanks.

—
Reply to this email directly or view it on GitHub.

miguellira · 2015-05-05T04:52:49Z

@jpack61108 Thanks for the tip. I'm ready to give this a shot. Quick question, where did you install Mono? The docs suggest /mono but I'd assume you'd run into all sort of permission issues.

miguellira · 2015-05-05T06:08:25Z

@jpack61108 Decided to pull the trigger and installed mono from source at /Users/miguellira/mono. Grabbed the latest HelloMvc sample and both beta4 and the latest (beta5-11682 as of this post) have fully functional builds without any errors!

I would like to point out, however, that (as indicated in the Compiling Mono on Mac OS X article) in order to install Mono from source you need Mono installed. Also, in order to ensure the new mono is used I added the path to my ~/.bash_profile:

PATH=/Users/miguellira/mono/bin:$PATH

jamespack · 2015-05-05T10:52:18Z

Nice!! I put mine in the same place that brew does. Never really thought about putting it elsewhere

Sent from Outlook

@jpack61108 Decided to pull the trigger and installed mono from source at /Users/miguellira/mono. Grabbed the latest HelloMvc sample and both beta4 and the latest (beta5-11682 as of this post) have fully functional builds without any errors!

I would like to point out, however, that (as indicated in the Compiling Mono on Mac OS X article) in order to install Mono from source you need Mono installed. Also, in order to ensure the new mono is used I added the path to my ~/.bash_profile:

PATH=/Users/miguellira/mono/bin:$PATH

—
Reply to this email directly or view it on GitHub.

jamespack · 2015-05-05T10:56:01Z

To work around having to have mono installed to compile mono, before running make, I ran make get-monolite-latest, then make.
James

Sent from Outlook

Nice!! I put mine in the same place that brew does. Never really thought about putting it elsewhere

Sent from Outlook

@jpack61108 Decided to pull the trigger and installed mono from source at /Users/miguellira/mono. Grabbed the latest HelloMvc sample and both beta4 and the latest (beta5-11682 as of this post) have fully functional builds without any errors!

I would like to point out, however, that (as indicated in the Compiling Mono on Mac OS X article) in order to install Mono from source you need Mono installed. Also, in order to ensure the new mono is used I added the path to my ~/.bash_profile:

PATH=/Users/miguellira/mono/bin:$PATH

—
Reply to this email directly or view it on GitHub.

jamespack · 2015-05-05T16:25:42Z

@miguellira

I am not sure but I think the way I did it breaks the intellisense for c# in VS Code.

Are you still getting Intellisense for c#?

miguellira · 2015-05-05T16:59:18Z

@jpack61108 Yep, same here. Statement completion only works if I remove the PATH to my 4.1.0 version of Mono and use the 4.0.1 version installed via brew.

I'm guessing this has to do with how Omnisharp within VSCode looks for Mono. My Atom/Omnisharp setup works just fine against Mono 4.1.0. Going to dig around if I come up with a fix I'll post, please do the same.

jamespack · 2015-05-05T17:08:18Z

@miguellira Will do.

jamespack · 2015-05-05T23:58:58Z

@miguellira
Super-Hack but what I am doing until they patch everything is leaving the 4.0.1 on the path and when I want to run the build commands that require the 4.1.0 just enter PATH=/Path/to/mono/4.1.0/:$PATH

Then I can build when I want and still get the awesome intellisense that Omnisharp offers.
Im sure that could probably be automated in some way, I am not that clever yet.

miguellira · 2015-05-06T00:23:40Z

@jpack61108 Yes. That's what I settled into on my Mac. But I've also been playing with vNext on my surface pro will stick with that until another build of VSCode.

deevus · 2015-05-07T02:54:34Z

Here's what did in the interim until this is resolved. I have mono 4.0.1 and 4.1.0 (compiled from git master) both installed in Homebrew.

`~/.bash_profile`

source dnvm.sh
alias dnu="brew switch mono 4.1.0 && dnu"

code () {
  brew switch mono 4.0.1
  if [[ $# = 0 ]]
  then
    open -a "Visual Studio Code"
  else
    [[ $1 = /* ]] && F="$1" || F="$PWD/${1#./}"
    open -a "Visual Studio Code" --args "$F"
  fi
}

It's not perfect but it's quick and easy for my use case. You could go further and make sure it resets the brew version after each command but I haven't found I needed to.

jensg · 2015-05-09T20:21:21Z

I have 2 versions of mono compiled from git source mono 4.0.1 and mono 4.1.0; after Visual Studio Code is started I set mono to version 4.1.0 and can execute dnu build
Disadvantage: You need a new window of terminal. Whenever PATH had mono version 4.1.0 referenced, code autocompletion does not work. When you set PATH to include mono 4.1.0 after it is started everything is fine.

This is my ~/.bash_profile

source dnvm.sh
MONO401="/Users/jensg/mono/build"
MONO410="/Users/jensg/mono/git-build"
PREPATH=$PATH

function code {
  PATH="$MONO401/bin:$PREPATH"
  open -a "Visual Studio Code"
  PATH="$MONO410/bin:$PREPATH"
}

peterblazejewicz · 2015-05-11T19:59:25Z

Hey guys just wanted to add, that despite the fact that 'dnu build' doesnt work on Mono. You can move forward only with 'dnu restore' and 'dnx . run', you're loosing the verbose output of dnu build, but at least you can run and play.

This could not apply in all cases, I (and other people) are stuck after dnx . kestrel:
#515

borgdylan · 2015-05-27T09:34:28Z

The latest mono master fixes all issues experienced here.

brucerchapman · 2015-05-27T12:54:28Z

@borgdylan I've got my setup in a mess. I just tried getting the latest mono with https://homebrew.bintray.com/bottles/mono-4.0.1.yosemite.bottle using homebrew - still no joy. How do I get the mono master then?

jamespack · 2015-05-27T13:06:25Z

clone the repo.
git clone https://github.com/mono/mono.git
Then follow the instructions provided here

miguellira · 2015-05-27T13:27:26Z

@brucerchapman I haven't tried to build from master in awhile but as @jamespack mentions it's pretty straightforward. I did, however, run into issues with earlier mono masters so I grabbed a tarball from their Jenkins server that build successfully. The following details the setup I wound up with: #508 (comment)

Both Mono and vNext are moving targets though, so if you wanna to play with the new bits stick to beta4 but subscribe to the Announcements issues repo. Good luck.

brucerchapman · 2015-05-27T13:40:58Z

@miguellira thanks I did try building but made things worse I think. This time I'll try in a different path - `/usrs/local/{user}/mono' seems to be the recommended?

miguellira · 2015-05-27T14:18:38Z

@brucerchapman The recommendation is not to place it in /usr but you can put in anywhere. I've chosen to place it where the official homebrew version will live. I'll simply delete it and brew install when 4.1 is made official. This is how my setup looks like:

Miguels-MBP:mono miguellira$ pwd
/usr/local/Cellar/mono
Miguels-MBP:mono miguellira$ ls
4.0.1   4.1.0

akoeplinger · 2015-05-27T14:29:52Z

FYI, the fix to this problem was commited to the mono 4.0 branch, so it should turn up in the next service release: mono/mono@ed1d3ec. If you don't want to jump straight to master, you can just build and install the 4.0 branch instead.

miguellira · 2015-05-27T15:00:25Z

@akoeplinger Do you know if building and running the 4.0 branch of mono will play nice with Visual Studio Code? When I switch to my mono 4.1 build OmniSharp does not start in VSC.

akoeplinger · 2015-05-27T15:15:57Z

@miguellira don't know that sorry, but the 4.0 branch only contains fixes on top of the released 4.0, so if VSCode works with that then I don't see why it wouldn't work with the latest from 4.0 branch.

Yantrio · 2015-05-27T15:37:27Z

@miguellira If you could post an issue over on http://github.com/omnisharp/omnisharp-roslyn with any details about it not booting on 4.1 then that would be much appreciated :D

jamespack · 2015-05-27T17:05:43Z

@Yantrio I believe it is related to the version of Omnisharp that is used within VSCode.

miguellira · 2015-05-27T17:42:21Z

@Yantrio VSCode always booted, but the OmniSharp Server would not start.

FWIW, I just cloned and built mono from master (currently reading as 4.3.0)

Miguels-MBP:MiguelLira.Web miguellira$ mono --version
Mono JIT compiler version 4.3.0 (master/65f9215 Wed May 27 13:17:54 EDT 2015)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
    TLS:           normal
    SIGSEGV:       altstack
    Notification:  kqueue
    Architecture:  amd64
    Disabled:      none
    Misc:          softdebug 
    LLVM:          supported, not enabled.
    GC:            sgen

Visual Studio Code/OmniSharp works fine, dnu build runs without errors. Unfortunately, CTRL-C to kill kestrel hangs and throws a System.NullReferenceException but apparently that's a known issue and definitely something I can live with.

Yantrio · 2015-05-27T17:48:48Z

There are ways around that which are quite simple :) we can discuss it on the correct repo :) I'm grabbing mono from source to test it now.

miguellira · 2015-05-27T18:43:52Z

@Yantrio I already commented on the Announcements thread when this bug appeared on my end aspnet/Announcements#23 (comment)

This bug has been logged several times over, both here and in the KestrelHttpServer repo. I'm sure they're tackling bigger fish right now.

balneaves · 2015-06-05T17:05:46Z

For those who already have DNVM/mono installed via Homebrew you can use the 4.0.1-44 release manually without messing about with builds and symlinks (until the main mono brew is upgrade to a fixed version)

brew edit mono

Change line 4 & 5 to the following

    url "http://download.mono-project.com/sources/mono/mono-4.0.1.44.tar.bz2"
    sha256 "eaf5bd9d19818cb89483b3c9cae2ee3569643fd621560da036f6a49f6b3e3a6f"

brew upgrade mono

jamespack · 2015-06-05T23:02:59Z

@salerth This is actually the easiest solution. Thanks. Works like a champ!

cmattson · 2015-06-06T00:04:57Z

I submitted a pull request this morning to update Homebrew to 4.0.1.44. It's merged now, so brew update away!

Thanks for @salerth for the tip that .44 was working. I'd last tried .43, which still didn't.

paullyvenne · 2015-06-06T04:45:40Z

As far as I know, this bug still exists. I've followed jamespack's instructions many times but it just doesn't resolve the issue (System.IO.EndOfStreamException: Failed to read past end of stream.). I'm thinking there is some issue with that build of mono but I can't be sure, it might also be ASPNET. This issue has been around for along time, so I haven't been able to try out the latest ASPNET and I hear many other users are stuck with this issue (OSX and Linux) as well. Help anyone?

EDIT: I just noticed some new instructions, I will try that.

paullyvenne · 2015-06-06T04:56:53Z

Thanks salerth, it worked, I did almost the same thing

sudo nano /usr/local/Library/Formula/mono.rb
changed line 4 and 5 to

url "http://download.mono-project.com/sources/mono/mono-4.0.1.44.tar.bz2"
sha256 "eaf5bd9d19818cb89483b3c9cae2ee3569643fd621560da036f6a49f6b3e3a6f"

sudo brew upgrade mono

andrenventer · 2015-09-11T20:25:22Z

paullyvenne: I used your method above, but still got the error below:

I removed the node_modules folder
I removed the files bower installed

Then it worked

mono --version
Mono JIT compiler version 4.0.1 (tarball Fri Sep 11 21:59:54 SAST 2015)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
TLS: normal
SIGSEGV: altstack
Notification: kqueue
Architecture: amd64
Disabled: none
Misc: softdebug
LLVM: supported, not enabled.
GC: sgen

dnx kestrel
Application started. Press Ctrl+C to shut down.
error : [Microsoft.AspNet.Diagnostics.ErrorHandlerMiddleware] An unhandled exception has occurred: kqueue() FileSystemWatcher has reached the maximum nunmber of files to watch.
System.IO.IOException: kqueue() FileSystemWatcher has reached the maximum nunmber of files to watch.
at System.IO.KqueueMonitor.Add (System.String path, Boolean postEvents, System.Collections.Generic.List1& fds) [0x00000] in <filename unknown>:0 at System.IO.KqueueMonitor.Scan (System.String path, Boolean postEvents, System.Collections.Generic.List1& fds) [0x00000] in :0
at System.IO.KqueueMonitor.Setup () [0x00000] in :0
at System.IO.KqueueMonitor.DoMonitor () [0x00000] in :0
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x00000] in :0 ...

dougbu · 2015-09-11T22:09:24Z

Looks like Mono is hitting issues similar to what we've seen when running with Core CLR on Linux (fyi: aspnet/Mvc#3066). Try bumping up the limits FileSystemWatcher has likely hit:

sudo sh -c "echo 2048 > /proc/sys/fs/inotify/max_user_instances"
sudo sh -c "echo 131072 > /proc/sys/fs/inotify/max_user_watches"

Note the above numbers are extreme 16x the defaults.

IHealthCheckPublisher allows you to configure and run health checks regularly inside an application, and push the notifications elsewhere. All publishers are part of a single queue with a configurable period and timeout.

This was referenced Apr 29, 2015

OSX install guide missing important step of sourcing .sh file #499

Closed

dnvm upgrade fails #502

Closed

davidfowl mentioned this issue Apr 29, 2015

Console Application template does not build on OS X #504

Closed

miguellira mentioned this issue Apr 30, 2015

Unable to run the samples HelloMvc/HelloWeb #516

Closed

This was referenced Apr 30, 2015

dnx . kestrel crashes on OSX (1.0.0-beta4-11566) (now: 1.0.0-beta5-11682) #518

Closed

Could not load ILibraryExport while running HelloMvc sample #515

Closed

Yantrio mentioned this issue May 4, 2015

Let's upgrade to dnx! OmniSharp/omnisharp-roslyn#203

Closed

miguellira mentioned this issue May 5, 2015

ArgumentNullException during OmniSharp startup inside Visual Studio Code #562

Closed

moozzyk mentioned this issue May 20, 2015

Fail to build using dnu build aspnet/dnx#1908

Closed

uhaciogullari mentioned this issue May 25, 2015

Support for .NET core castleproject/Core#90

Closed

miguellira closed this as completed May 27, 2015

Antaris mentioned this issue Mar 15, 2018

[Advice] Tackling multi-tenancy with stock DI - open generics #2964

Closed

dougbu pushed a commit to dotnet-maestro-bot/AspNetCore that referenced this issue Sep 11, 2019

Remove unnecessary exclusions (dotnet#498)

9fc855f

ghost locked as resolved and limited conversation to collaborators Dec 4, 2019

System.IO.EndOfStreamException when building with latest DNVM and Mono 4.0.1 #498

System.IO.EndOfStreamException when building with latest DNVM and Mono 4.0.1 #498

Comments

miguellira commented Apr 29, 2015

suhasj commented Apr 29, 2015

Uh oh!

miguellira commented Apr 29, 2015

Uh oh!

suhasj commented Apr 29, 2015

Uh oh!

javi830810 commented Apr 29, 2015

Uh oh!

davidfowl commented Apr 29, 2015

Uh oh!

ThorstenHans commented Apr 30, 2015

Uh oh!

Jabe commented Apr 30, 2015

Uh oh!

miguellira commented Apr 30, 2015

Uh oh!

jamespack commented May 5, 2015

Uh oh!

miguellira commented May 5, 2015

Uh oh!

jamespack commented May 5, 2015

Uh oh!

jamespack commented May 5, 2015

Uh oh!

miguellira commented May 5, 2015

Uh oh!

miguellira commented May 5, 2015

Uh oh!

jamespack commented May 5, 2015

Uh oh!

jamespack commented May 5, 2015

Uh oh!

jamespack commented May 5, 2015

Uh oh!

miguellira commented May 5, 2015

Uh oh!

jamespack commented May 5, 2015

Uh oh!

jamespack commented May 5, 2015

Uh oh!

miguellira commented May 6, 2015

Uh oh!

deevus commented May 7, 2015

~/.bash_profile

Uh oh!

jensg commented May 9, 2015

Uh oh!

peterblazejewicz commented May 11, 2015

Uh oh!

borgdylan commented May 27, 2015

Uh oh!

brucerchapman commented May 27, 2015

Uh oh!

jamespack commented May 27, 2015

Uh oh!

miguellira commented May 27, 2015

Uh oh!

brucerchapman commented May 27, 2015

Uh oh!

miguellira commented May 27, 2015

Uh oh!

akoeplinger commented May 27, 2015

Uh oh!

miguellira commented May 27, 2015

Uh oh!

akoeplinger commented May 27, 2015

Uh oh!

Yantrio commented May 27, 2015

Uh oh!

jamespack commented May 27, 2015

Uh oh!

miguellira commented May 27, 2015

Uh oh!

Yantrio commented May 27, 2015

Uh oh!

miguellira commented May 27, 2015

`~/.bash_profile`