Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The solution explorer displays some files out of order for F# projects. #12155

Closed
vsfeedback opened this issue Sep 15, 2021 · 2 comments
Closed
Labels
Area-VS VS support for F# not covered elsewhere Feature Improvement
Milestone

Comments

@vsfeedback
Copy link

This issue has been moved from a ticket on Developer Community.


The solution explorer displays some files out of order for F# projects.
For example, this ordering in the *.fsproj file will not fully be respected by the solution explorer:

  <ItemGroup>
    <Compile Include="A\Library.fs" />
    <Compile Include="A.fs" />
    <Compile Include="B\C\Library.fs" />
    <Compile Include="B.fs" />
    <Compile Include="C\Library.fs" />
    <Compile Include="C.fs" />
  </ItemGroup>

The file "B.fs" will be displayed after the directory "C" in this case. See the image.

! [vs.jpg] (https://aka.ms/dc/image?name=Bdee0a2637253437b9dcf412822b9f3dc637636737557264392_vs.jpg&tid=dee0a2637253437b9dcf412822b9f3dc637636737557264392)

As in this case, this happens when you have files and directories with the same name and names repeat in other nested directories. The display order is restored to normal if you rename the nested "B\C" directory to any distinct name, for example to "B\D".


Original Comments

Feedback Bot on 8/4/2021, 10:46 PM:

We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.


Original Solutions

(no solutions)

@albertwoo
Copy link

I also have these kind of issue in VS:

other fs folder and files
workflow\domain1\foo1.fs
ui\domain1\foo2.fs

@vzarytovskii
Copy link
Member

I was unable to reproduce it in latest VS. If it's still the case, it needs to be reported via VS feedback and routed to CPS/Solution explorer team, since we don't control it.

@vzarytovskii vzarytovskii closed this as not planned Won't fix, can't repro, duplicate, stale Nov 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-VS VS support for F# not covered elsewhere Feature Improvement
Projects
Archived in project
Development

No branches or pull requests

4 participants