Thanks to visit codestin.com
Credit goes to github.com

Skip to content

ProjectStartedEvents for already-run projects have bad IDs #12953

@rainersigwald

Description

@rainersigwald

Repro projects: PSE_invalid_ids.zip

Build with dotnet msbuild entry.proj -bl.

Compare the log events for the first (real) ProjectStartedEventArgs for for project1:

"BuildEventContext": {
  "EvaluationId": 36,
  "NodeId": 2,
  "TargetId": -1,
  "ProjectContextId": 36,
  "TaskId": -1,
  "ProjectInstanceId": 4,
  "SubmissionId": 0,
  "BuildRequestId": -2001796771
}

With the ones emitted the second time (when it's satisfied already and we don't need to do real work in the project):

"BuildEventContext": {
  "EvaluationId": -1,
  "NodeId": 1,
  "TargetId": -1,
  "ProjectContextId": 103,
  "TaskId": -1,
  "ProjectInstanceId": 4,
  "SubmissionId": 0,
  "BuildRequestId": -2064531812
}

NodeId is 1 when it should be 2.

EvaluationId is invalid when it should be specified.

(@baronfel and @jaredpar and I have been looking at related areas--this was discovered when Jared started asserting when a specific ProjectInstanceId appeared to move between nodes.)

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions