Skip to content

Fix #471 - consider QueryStartUpToDateCheck options, harden against sync context issues#479

Closed
latkin wants to merge 1 commit intodotnet:fsharp4from
latkin:fix-471
Closed

Fix #471 - consider QueryStartUpToDateCheck options, harden against sync context issues#479
latkin wants to merge 1 commit intodotnet:fsharp4from
latkin:fix-471

Conversation

@latkin
Copy link
Copy Markdown
Contributor

@latkin latkin commented Jun 1, 2015

Shiproom template:

  • Bug number StartUpToDateCheck(null, 1) throws ArgumentException #471
  • Customer scenario VS extensions (e.g. TestDriven .NET) invoking F# project system StartUpToDateCheck get unexpected ArgumentException due to sync context issues.
  • Fix description
    • Use IVsSolutionBuildManager5.FindActiveProjectCfgName instead of IVsSolutionBuildManager2.FindActiveProjectCfg in TryGetActiveConfigurationAndPlatform, as it is not sensitive to sync context
    • Give proper consideration to the VSUTDCF options flags passed to QueryStartUpToDateCheck
  • Testing done Manual verification w/ TestDriven.NET + IDE unit tests

…GetActiveConfigurationAndPlatform

 - Give proper consideration to the options flags passed to QueryStartUpToDateCheck
 - Use IVsSolutionBuildManager5.FindActiveProjectCfgName in TryGetActiveConfigurationAndPlatform, as it is not sensitive to sync context
   - Avoids exception for non-UI thread callers, e.g. DTEE automation

Fixes dotnet#471
@latkin
Copy link
Copy Markdown
Contributor Author

latkin commented Jun 2, 2015

Once again soliciting reviewers before I ask for approval at shiproom. /cc @enricosada @dungpa @KevinRansom etc

@MattGertz
Copy link
Copy Markdown

Approved 6/2 by ML Shiproom.

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.

3 participants