-
Notifications
You must be signed in to change notification settings - Fork 844
allow FSharpTargetsPath to be properly overwritten in a project file
#4934
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But nothing will install to this path anymore, since we removed the MSI?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That is fixed in this PR: #4819
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll have to rebase that PR to fix this bottom line, but this will still work. The MSI removal doesn't remove these files, they're just placed under Common7\IDE\....
|
I guess my overall point is that I'd prefer us to match C# as closely as we can for this stuff (keeping in mind that |
|
Please continue to support both. |
|
@0x53A Thanks for the pointer. Looking at how |
|
@0x53A It works as expected. I did the following:
|
Followup to #4922.
By previously setting
FSharpTargetsPath, etc. directly we didn't allow for that to be manually set in a project, props, or target file. By using this method the IDE can communicate where the compiler is located, but the user can still override this should they choose.Edit:
With this change compiler redirection will require a shipped version of the targets shim changes which will happen in VS 15.8.