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

Force update project options when assembly references change #2023

Merged
merged 2 commits into from
Dec 16, 2016

Conversation

dungpa
Copy link
Contributor

@dungpa dungpa commented Dec 15, 2016

Fix #2020.

@KevinRansom
Copy link
Member

Oky I think I fished the assembly reference thing again ... packages.config got overwritten.
@dotnet-bot test this please

@@ -207,13 +207,15 @@ type internal FSharpLanguageService(package : FSharpPackage) as this =
let projectInfoManager = this.Package.ComponentModel.DefaultExportProvider.GetExport<ProjectInfoManager>().Value

/// Sync the information for the project
member this.SyncProject(project: AbstractProject, projectContext: IWorkspaceProjectContext, site: IProjectSite) =
member this.SyncProject(project: AbstractProject, projectContext: IWorkspaceProjectContext, site: IProjectSite, forceUpdate) =
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we make forceUpdate and enum please, true isn't really readable.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SyncProject is a class member with two usages at the same file. At the both call sites, I have used named parameters for forceUpdate. I don't think changing bool to two-case enums would improve readability here.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for taking care of this

Kevin

@KevinRansom KevinRansom merged commit 66829a4 into dotnet:master Dec 16, 2016
@dungpa dungpa deleted the refs branch December 16, 2016 17:32
@cartermp
Copy link
Contributor

Awesome. Thanks, @dungpa!

nosami pushed a commit to xamarin/visualfsharp that referenced this pull request Jan 26, 2022
…2023)

* Force update project options when assembly references change.

Fix dotnet#2020.

* Fix merge issue.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants