You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Interactive tools like REPLs (for example dotnet fsi) often want to use dlls from a given Framework when working in an interactive mode. They also typically need to resolve FrameworkReferences for the 'baseline' Microsoft.NETcore.App to have a minimum level of functionality. Right now these resolutions are often ad-hoc, finding the SDK directory in use and doing relative pathing. This is fragile to resolution changes in future SDKs.
Describe the solution you'd like
It would be great if the logic in the FrameworkResolution targets was consumable in another form, so that custom FrameworkReference resolution logic that may be duplicated in other projects could be centralized and made consistent.
baronfel
changed the title
Consider creating and publishing a package for Framework resolution
Consider creating and publishing a package for FrameworkReference resolution
Oct 6, 2022
Is your feature request related to a problem? Please describe.
Interactive tools like REPLs (for example
dotnet fsi
) often want to use dlls from a given Framework when working in an interactive mode. They also typically need to resolve FrameworkReferences for the 'baseline' Microsoft.NETcore.App to have a minimum level of functionality. Right now these resolutions are often ad-hoc, finding the SDK directory in use and doing relative pathing. This is fragile to resolution changes in future SDKs.Describe the solution you'd like
It would be great if the logic in the FrameworkResolution targets was consumable in another form, so that custom FrameworkReference resolution logic that may be duplicated in other projects could be centralized and made consistent.
Additional context
An example use case can be found at dotnet/fsharp#13969 (comment)
The text was updated successfully, but these errors were encountered: