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
{{ message }}
Repository navigation
Syntax-coloring is not applied or removed when changing Build Action from None to Compile and vv #3503
Since out-of-project files are no longer colored (inverse to this issue #1977 may have you believe), there now appears to be a small issue with that: it doesn't work when the project has dirty state, it only works if you compile.
Repro steps
Basically:
Open any project *.fs file
Change the Build Action to None
Result: no effect
You can try to close/reopen the file, but still no effect.
The inverse is also true: change from None to Compile will not color the file.
Expected behavior
Since this change was applied (#1977, possibly it's VS2017, not just Visual F#), this expected behavior is different now: it should remove the coloring, or inverse, it should add the coloring back.
Actual behavior
Syntax coloring, or removing of coloring is not applied.
Known workarounds
Recompile the project.
Related information
F# 4.0 and F# 4.1 with VS2017 15.3.1.0. Also observed in recent nightlies.
A small issue, I know, but I thought to better have it reported in case somebody is working on something in this area.
changed the title [-]Removing or readding of syntax-coloring is not applied on dirty projects, only after save-compile.[/-][+]Syntax-coloring is not applied or removed when changing Build Action from None to Compile and vv[/+]on Aug 25, 2017
Behavior has changed again. Right now (in VS 2022 Community, Version 17.8.6), if the build action is set to None, it will still syntax-color the file. It also appears to process the opens and report syntax and type errors. This may result in performance degradation.
This is incorrect behavior: if the build action is None, errors should not be reported (note that regardless, build succeeds).
Activity
[-]Removing or readding of syntax-coloring is not applied on dirty projects, only after save-compile.[/-][+]Syntax-coloring is not applied or removed when changing Build Action from None to Compile and vv[/+]abelbraaksma commentedon Mar 28, 2018
Just checked with latest builds, but this still happens. Rebuild is still necessary. Seen in Visual Studio 15.6.
abelbraaksma commentedon May 16, 2024
Behavior has changed again. Right now (in VS 2022 Community, Version 17.8.6), if the build action is set to
None, it will still syntax-color the file. It also appears to process the opens and report syntax and type errors. This may result in performance degradation.This is incorrect behavior: if the build action is
None, errors should not be reported (note that regardless, build succeeds).