Open nkosi23 opened 7 months ago
@nkosi23 Thank you for writing about it and really sorry for the late reply!
This is definitely not expected behaviour in the most of the cases. Unfortunately, we don't see such behaviour in solutions that we use our F# support on, so it's likely something specific to your solution. Could you please share more info about these projects? 1) Are all these projects F# ones? 2) Are there any type providers used in project A? If yes, it may be this issue in F# compiler service that we use for parts of the analysis 3) Does the issue exist for all symbols in project A, or only for some? 4) Are there any signature files in the project A?
If there's a chance you could show a simplified repro solution (and if that's not the issue with type providers above), that could also help a lot.
Sorry for the delay in my reply,
I will look into creating a repro !
Hello,
I have noticed that when working on a solution having multiple projects with - for example - the following dependency graph:
Two annoying things happen:
This is definitely not what the development experience that solutions are supposed to offer (and as a matter of fact C#-based solutions do not have this issue).
I am running the following version of JetBrains Rider:
JetBrains Rider 2023.3 Build #RD-233.11799.261, built on December 4, 2023 Subscription is active until January 10, 2024. Runtime version: 17.0.9+7-b1087.7 amd64 VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o. Linux 6.6.3-1-default .NET Core v7.0.10 x64 GC: G1 Young Generation, G1 Old Generation Memory: 4096M Cores: 12 Registry: editor.config.csharp.support=true ide.experimental.ui=true Current Desktop: KDE