search

OmniSharp / omnisharp-atom

Omnisharp support for the atom editor
https://atom.io/packages/omnisharp-atom
MIT License
318 stars 61 forks source link

MEF error starting omnisharp #558

Open Spongman opened 8 years ago

Spongman commented 8 years ago

debian jessie x86 atom: v1.3.0-beta1 built from source omnisharp: 0.25.10 fresh .atom directory no other packages installed (except omnisharp dependencies)

Starting OmniSharp server (pid:31068)
OmniSharp Location: /home/me/.atom/packages/omnisharp-atom/node_modules/omnisharp-client/roslyn/omnisharp
Change the location that OmniSharp is loaded from by setting the OMNISHARP environment variable
OmniSharp Path: /home/me/web/ConsoleApplication
System.Composition.Hosting.CompositionFailedException: No importing constructor was found on type 'OmniSharp.OmnisharpWorkspace'.
  at System.Composition.TypedParts.Discovery.DiscoveredPart+d__d.MoveNext () [0x00000] in :0 
  at System.Linq.Enumerable+c__Iterator1`1[System.Composition.Hosting.Core.CompositionDependency].MoveNext () [0x00000] in :0 
  at System.Linq.Enumerable+c__Iterator1E`1[System.Composition.Hosting.Core.CompositionDependency].MoveNext () [0x00000] in :0 
  at System.Linq.Enumerable.ToArray[CompositionDependency] (IEnumerable`1 source) [0x00000] in :0 
  at System.Composition.TypedParts.Discovery.DiscoveredPart.GetDependencies (System.Composition.Hosting.Core.DependencyAccessor definitionAccessor) [0x00000] in :0 
  at System.Composition.TypedParts.Discovery.DiscoveredExport+<>c__DisplayClass2.b__0 () [
0x00000] in :0 
  at System.Composition.Hosting.Core.ExportDescriptorPromise+<>c__DisplayClass4.<.ctor>b__0 () [0x00000] in :0 
  at System.Lazy`1[System.Collections.ObjectModel.ReadOnlyCollection`1[System.Composition.Hosting.Core.CompositionDependency]].InitValue () [0x00000] in :0
david-driscoll commented 8 years ago

Would it be possible to test with the latest version and let me know what you see happening?

shadowmint commented 8 years ago

Although this was still an issue with the latest version of the plugin (0.26.7), really its an issue with mono.

Fixed by installing a newer version of mono for me (Stable 4.2.1.102).