search

smith-chem-wisc / FlashLFQ

Ultra-fast label-free quantification algorithm for mass-spectrometry proteomics
GNU Lesser General Public License v3.0
19 stars 14 forks source link

An assembly specified in the application dependencies manifest (CMD.deps.json) was not found #81

Closed ijmiller2 closed 5 years ago

ijmiller2 commented 5 years ago

Running this command:

/home/ijmiller2/.dotnet/dotnet CMD.dll

I'm getting this error:

Error:
  An assembly specified in the application dependencies manifest (CMD.deps.json) was not found:
    package: 'FluentCommandLineParser', version: '1.5.0.20-commands'
    path: 'lib/net35/FluentCommandLineParser.dll'

In case it's relevant, this is with the latest release and here's what: /home/ijmiller2/.dotnet/dotnet --info produces:


 Version:   2.1.802
 Commit:    177d0b2525

Runtime Environment:
 OS Name:     ubuntu
 OS Version:  18.04
 OS Platform: Linux
 RID:         ubuntu.18.04-x64
 Base Path:   /home/ijmiller2/.dotnet/sdk/2.1.802/

Host (useful for support):
  Version: 2.1.13
  Commit:  1a165a1588

.NET Core SDKs installed:
  2.1.802 [/home/ijmiller2/.dotnet/sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.All 2.1.13 [/home/ijmiller2/.dotnet/shared/Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.1.13 [/home/ijmiller2/.dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.1.13 [/home/ijmiller2/.dotnet/shared/Microsoft.NETCore.App]

To install additional .NET Core runtimes or SDKs:
  https://aka.ms/dotnet-download```
rmillikin commented 5 years ago

Thanks for the crash report! I will check this out tomorrow. I'm curious if this is a Linux-only issue or if it also occurs on Windows. I'll investigate....

ijmiller2 commented 5 years ago

Great, thank you!

rmillikin commented 5 years ago

I was able to reproduce this issue in Linux (Ubuntu). All versions of FlashLFQ (.NET Core command-line, .NET Framework command-line, and .NET Framework GUI) work in Windows, though. I will try to fix this Linux issue ASAP.

rmillikin commented 5 years ago

This issue was caused by Visual Studio not building .NET core apps properly; the dependent nuget packages were not packaged properly with the .NET core release. I've fixed that. I also switched command-line parsers to fix issues #72 and #71 . I'll make a new release within a few days after some more bugtesting.

ijmiller2 commented 5 years ago

Excellent! Thanks for the quick turnaround. I look forward to testing it out.

rmillikin commented 5 years ago

This should be fixed with version 1.0.1, which I just released. Please give that a try and open a new issue if you encounter other issues. Thanks again for the report!