Jet Brains Rider JetBrains.Metadata.Utils.AssemblyNameInfo is null

HI,

I am facing some issues with jet brains rider 2019.2.2 while adding DLL reference to the project as I am getting the error as(etBrains.Metadata.Utils.AssemblyNameInfo is null

) . Please find the attached screen shot and let me know your suggestions on this to resolve this issue as soon as possible.

 

Thanks & Regards,

Anand Krishna.

12 comments
Comment actions Permalink

Hello Anand,

Could you please share your dll which you tried to reference or clarify its name and where to find it? Here is a how-to about uploading files to JetBrains.

 

Kind regards,

Sofia.

0
Comment actions Permalink

I'm seeing the exact same error in 2019.3.4 whenever I try to add a reference to:

1. a project that's external to the solution I'm working in.

2. a .CS source file that's external to the solution I'm in.

 

It'd be really neat if I were able to access at least an external source file so I do not need to add its project and all of its dependencies.

 

Thank you,  eugen

0
Comment actions Permalink

Hi Eugen,

Could you please describe the repro steps about how you added the reference to your project? 

 

Kind regards,

Sofia.

0
Comment actions Permalink

This might be a little bit late, but I experience the same issue.

The steps to reproduce are pretty simple. Have two different .sln files (so basically two projects) and then try to add Project1 from Solution1 to any project from Solution2. This happens for me on the latest .NET Core version (3.1) with the latest Rider build 2020.1.

For reference, I added a short video to show how to reproduce: https://streamable.com/n6f3ng 

I don't know if I'm doing something wrong or if it's just a bug.

 

Sincerely,

Zargor

0
Comment actions Permalink

Has this been resolved? I'm facing exactly the same issue. JetBrains Rider 2019.3.1
Build #RD-193.5662.14, built on December 20, 2019

 

I've uploaded Test.csproj file that I'm trying to reference. 

Rider shows 

0
Comment actions Permalink

Hi, has this been resolved or acknowledged at least?  

0
Comment actions Permalink

Hi there,

Unfortunately, I have no luck in reproducing this issue. But this issue is very similar to https://youtrack.jetbrains.com/issue/RIDER-37009.

It would be great if you could share a full repro solution and attach it to a new youtrack ticket or to the https://youtrack.jetbrains.com/issue/RIDER-37009.

 

Kind regards,

Sofia.

0
Comment actions Permalink

I have not been able to add an external reference, which is odd because I know I've done that before.  I can add an external project.  The trick is, first add the project to the solution by right clicking on the folder where you want it to live.  Select "Add" => "Add Existing Project..." and select your .csproj.  Now you can reference the project in another project just like any other project.  Hope it helps!

0
Comment actions Permalink

The best solution is open Visual Studio and do the work from there, Rider is more like a toy even you have to pay for it. Community version of Visual Studio is free and it actually works. 

1
Comment actions Permalink

Adding an unnecessary project to a solution is not a desirable solution.

0
Comment actions Permalink

Hi Rider guys, when are you going to fix this? 

0
Comment actions Permalink

Hi there,

The only thing to fix there is the message. It is now not informative. Rider shows this message when one tries to add a reference which is not actually a .NET Assembly (to check it use https://docs.microsoft.com/en-gb/dotnet/standard/assembly/identify). 
The action "add reference -> add from" works only for dll, exe, winmd, and other .NET assembly files.

 

Kind regards,

Sofia.

1

Please sign in to leave a comment.