Workaround for target assemblies where packages with transitive references contain type providers #388
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Enables type providers to get the correct set of target assemblies when nuget packages with transitive references to other packages contain type providers, and these are used in scripts.
This is a workaround for F# tooling bug dotnet/fsharp#13710 where the type providers are instnatiated before the complete set of references relevant to a nuget package are reported correctly by ReferencedAssemblies
The "proper" F# tooling fix for dotnet/fsharp#13710 is for F# tooling to register all transitive referenced assemblies implied by a nuget package reference simultaneously, and thus report ReferencedAssemblies correctly.
The workaround for getting referenced assemblies was removed here: #305. We will eventually be able to remove the workaround again once a proper fix for dotnet/fsharp#13710 propagates through the F# tooling ecosystem for all tooling that loads type providers.