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

fsac.cache always in obj/ #110

Open
PhilT opened this issue May 4, 2021 · 3 comments
Open

fsac.cache always in obj/ #110

PhilT opened this issue May 4, 2021 · 3 comments
Labels
enhancement good first issue Issue for new contributors

Comments

@PhilT
Copy link

PhilT commented May 4, 2021

Describe the bug
I've recently configured my project to build all intermediate and built artifacts into obj/ and bin/ outside of the main src/ folder through a Directory.Build.props file. However, it seems fsac.cache doesn't pick this up and still creates obj/fsac.cache in each of the src/project/ folders.

// src/Directory.Build.props
<Project>
  <PropertyGroup>
    <BaseOutputPath>../../build/$(MSBuildProjectName)/bin</BaseOutputPath>
    <BaseIntermediateOutputPath>../../build/$(MSBuildProjectName)/obj</BaseIntermediateOutputPath>
 </PropertyGroup>
</Project>

Expected behaviour

To find a build/project/obj/proj-info.cache file.

Instead, a file appears in src/project/obj/fsac.cache

Environment:

  • OS: Windows 10
  • FsAutoComplete: 0.45.4
  • Neovim: 0.5 Nightly
  • dotnet SDK version: 5
@baronfel
Copy link
Collaborator

baronfel commented May 5, 2021

This would be part of a larger effort to make the projects in general aware of intermediate output paths. Most of the offending code seems to be here, where there are hard references to the bin/obj directories of the project.

@PhilT
Copy link
Author

PhilT commented May 5, 2021

I could take a stab at this but I know nothing about project cracking. Any pointers?

@stkb
Copy link

stkb commented Jan 31, 2023

I've run into the same issue, also using a Directory.Build.props file. I could take a look at it but it will take a while to get up to speed.

@TheAngryByrd TheAngryByrd added enhancement good first issue Issue for new contributors labels Feb 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement good first issue Issue for new contributors
Development

No branches or pull requests

4 participants