Include [TypeForwardedTo] in a.html
See original GitHub issueI’m trying to make Ref12 support .Net Core projects.
However, many members (eg, System.Span<>
) are defined in System.Runtime the reference assembly, but is forwarded (via [TypeForwardedTo]
) to System.Private.CoreLib in the actual source.
Ref12 only sees it as being in System.Runtime, so it opens https://source.dot.net/System.Runtime/Ad.html#d2517139cac388e8, which does nothing.
Can you please change the indexer to process [TypeForwardedTo]
attributes and generate links to either the filename or the corresponding a.html
in the target project?
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:11 (7 by maintainers)
Top Results From Across the Web
Solved: Assembly vs NameSpace and related to ...
Hello Experts: I am facing a problem with TypeForewodedToAttribute, Clarify, what is the Assembly and what is namespace ?
Read more >.NET type forwarding
CLR has an equivalent of HTTP redirect for types, it is called You can move a class from one assembly to another, it...
Read more >TypeForwardedTo, explicitly implemented interfaces and ...
Foo.csproj takes a project reference to NewFoo.csproj and I add the forwarding attribute: [assembly: TypeForwardedTo(typeof(IFooInterface))].
Read more >[API Proposal]: JavaScript interop with [JSImport ...
Currently we don't have public C# API to do so. We propose this API together with prototype of the implementation. Key features are:....
Read more > Brenton House - Digital Strategist - Moving a Type from one ...
In the old assembly, add a reference to the new assembly. Add [assembly: TypeForwardedTo(typeof(YourClassName))] to the old assembly; Recompile and redeploy ...
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
@KirillOsenkov, @SLaks can probably describe it better than I can, but the following code illustrates what I see.
Path.Combine
.NET Framework dll
Expected: Opens ReferenceSource website on ‘Combine’ method (.NET Framework version).
Actual: Works as expected and opens
https://referencesource.microsoft.com/#mscorlib/system/io/path.cs,2d7263f86a526264
.NET Core dll
Expected: Opens source.dot.net website on ‘Combine’ method (.NET Core version).
https://source.dot.net/#System.Private.CoreLib/shared/System/IO/Path.cs,2d7263f86a526264,references
Actual: Opens Metadata
.NET Standard dll
Expected: Opens ReferenceSource or source.dot.net website on ‘Combine’ method.
Actual: Opens Metadata
In this case there is no “source” but perhaps Ref12 could be enhanced to select a default implementation to show? .NET Framework or .NET Core source? I would certainly find this more useful than just the metadata.
Hope this helps.
Apologies I never followed up.
I’m not sure how to get from System.Runtime.Extensions.dll reference assembly to System.Private.CoreLib. There isn’t a TypeForwardedTo attribute that would bridge the two.
I’ll ask around and see what can be done here.