Skip to content

fix StartUpToDateCheck with VSUTDCF_DTEEONLY option,#473

Closed
enricosada wants to merge 1 commit intodotnet:fsharp4from
enricosada:issue_471_uptodate_crash
Closed

fix StartUpToDateCheck with VSUTDCF_DTEEONLY option,#473
enricosada wants to merge 1 commit intodotnet:fsharp4from
enricosada:issue_471_uptodate_crash

Conversation

@enricosada
Copy link
Copy Markdown
Contributor

fix #471

return build not up-to-date if flag VSUTDCF_DTEEONLY is used for StartUpToDateCheck.

with VSUTDCF_DTEEONLY:

- QueryStartUpToDateCheck return option not supported
- StartUpToDateCheck return operation not implemented
@enricosada enricosada force-pushed the issue_471_uptodate_crash branch from 03e4720 to 47e2400 Compare May 28, 2015 12:41
@latkin
Copy link
Copy Markdown
Contributor

latkin commented May 28, 2015

@enricosada thanks for taking a look at this. We don't want to leave it unsupported, though, up-to-date check should still work even with the DTEEONLY flag. If we see this flag, I believe we should simply take a slightly different codepath (avoid some APIs that do not apply in this scenario).

Let me check C# project system and see what proper behavior should be.

@enricosada
Copy link
Copy Markdown
Contributor Author

A proper fix is better.
this pr is like old behavior and third party works , only invoke an unnecessary build ( but np )
If the fix is too complicated this pr can be a workaround for vs 2015

@latkin
Copy link
Copy Markdown
Contributor

latkin commented Jun 2, 2015

Closing this out in favor of #479

@latkin latkin closed this Jun 2, 2015
@latkin latkin added the declined label Jun 2, 2015
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