ProjectReferences could be duplicated, which ends up with ThrowArgumentItemNullOrDuplicateException

[Mingxue008]

Buildalyzer is only parsing the csproj files, and doesn't ensure that ProjectReferences to be distinct when accessed by users. After users get their AnalyseResult and try to add that result back into an AdhocWorkspace, which will call Roslyn ProjectInfo.Create() API and trigger ThrowArgumentItemNullOrDuplicateException by Roslyn default behavior. We would expect ProjectReferences to be distinct even users somehow edit their csproj files and accidently duplicated them.

[daveaglick]

Thanks a bunch for taking the lead on getting this fixed @Mingxue008! Resolved in #204.

[Mingxue008]

@daveaglick any update on the release of Buidalyzer?

[daveaglick]

@Mingxue008 I actually totally forget this wasn't released yet! Thanks for the reminder, pushing the release button now.

[Mingxue008]

Thanks for the release, much appreciated.