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.
Allow ionide to detect packages installed from nuget. Right now only paket seems to be supported since it installs the packages locally within packages/analyzers. Many projects might not be using paket (Feliz template for example). Requiring paket also makes the entry barrier higher if you just want to try out an analyzer with a console project.
Describe the solution you'd like
Finding the assemblies of analyzers will require some sort of local package resolution since nuget packages aren't installed in a local directory within a project (AFAIK at least).
Using a combination of the following commands, you can figure out where to find the analyzers:
dotnet nuget locals global-packages --list
info : global-packages: C:\Users\zaidn\.nuget\packages\
dotnet list package
Project 'OptionTest' has the following package references
[netcoreapp3.1]:
Top-level Package Requested Resolved
> FSharp.Analyzers.Sample 1.2.0 1.2.0
> FSharp.Core 4.7.0 4.7.0
This way you can construct the path of the analyzer:
For {ProjectFramework} I am not entirely sure how to figure out which target framework the analyzer was compiled with. One option is to find the first directory that starts with net or just loading whatever target framework that can be loaded
Describe alternatives you've considered
Require paket always
Additional context
N/A
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Allow ionide to detect packages installed from nuget. Right now only paket seems to be supported since it installs the packages locally within
packages/analyzers
. Many projects might not be using paket (Feliz template for example). Requiring paket also makes the entry barrier higher if you just want to try out an analyzer with a console project.Describe the solution you'd like
Finding the assemblies of analyzers will require some sort of local package resolution since nuget packages aren't installed in a local directory within a project (AFAIK at least).
Using a combination of the following commands, you can figure out where to find the analyzers:
This way you can construct the path of the analyzer:
For
{ProjectFramework}
I am not entirely sure how to figure out which target framework the analyzer was compiled with. One option is to find the first directory that starts withnet
or just loading whatever target framework that can be loadedDescribe alternatives you've considered
Require paket always
Additional context
N/A
The text was updated successfully, but these errors were encountered: