Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Reference assemblies error with constructors hidden by signature
See original GitHub issueLooks like generating a reference assembly can error out in certain cases when constructors are hidden by the signature file (even if the constructor is marked as internal in the implementation).
See for example #13385 (FSharp.Core as reference.assembly).
Issue Analytics
- State:
- Created a year ago
- Comments:12 (12 by maintainers)
Top Results From Across the Web
Why do I (sometimes) have to reference assemblies ...
error CS0012 : The type 'System.Drawing.Point' is defined in an assembly that is not referenced. You must add a reference to assembly 'System....
Read more >MSB3644: The reference assemblies for 'version' were not ...
This error occurs when the .NET reference assemblies aren't found for the version of .NET that a project requests.
Read more >Runtime C# Code Compilation Revisited for Roslyn - Rick Strahl
Recently I needed to update my scripting tools that are integrated into Markdown Monster, in order to support .NET Core.
Read more >Error when changing Scripts - Unity Forum
Shader error in 'Hidden/Universal/CoreBlit': invalid subscript 'positionCS ... Signature sig, Boolean constructor, Boolean wrapExceptions) at ...
Read more >Using-declaration
If a using-declaration brings the base class assignment operator into derived class, whose signature happens to match the derived class's copy- ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yes, however, I’m not able to reproduce this anymore.
Locally I have,
commit e63d48c7906d661ddd1bf73e1654072b5e18c80c (HEAD -> main, upstream/main, origin/main, origin/HEAD) Author: dotnet-maestro[bot] <42748379+dotnet-maestro[bot]@users.noreply.github.com>
Did a:
git clean -xdf.\Build.cmd -noVisualStudiodotnet build .\src\FSharp.Core\FSharp.Core.fsproj /p:ProduceReferenceAssembly=true -v nIt created
fsharp\artifacts\obj\FSharp.Core\Debug\netstandard2.0\refint\FSharp.Core.dllwithout any problems.@vzarytovskii @nojaf
Strange enough, I tried it again and it now works for me too. Did something change in the mean time?
I assume #13433 still needs to be resolved before
FSharp.Corecan be actually usable as a reference assembly.Anyway, I can close this issue. Thanks!