| Reporter |
Kayla Nimis (kaylanimis)
|
|---|---|
| Created | Nov 10, 2017 6:47:40 PM |
| Updated | Apr 18, 2018 6:46:23 AM |
| Subsystem | Solution Wide Error Analysis (SWEA) |
| Assignee | Dmitry Ivanov (daivanov) |
| Priority | Normal |
| State | Submitted |
| Type | Bug |
| Fix version | No Fix versions |
| Affected versions | No Affected versions |
| Fixed In Version ReSharper | Undefined |
| VsVersion | All Versions |
I have solutions with a large number of projects, and a few were added with a lower case guid project id. Solution-wide analysis reports references to those projects being missing.
For example:
<ProjectReference Include="....\Shared\G1.Accounts.Interface\G1.Accounts.Interface.csproj">
<Project>{3B92A5DD-09F5-49FB-B265-CBFCA64E6C5C}</Project>
<Name>G1.Accounts.Interface</Name>
</ProjectReference>
<ProjectReference Include="....\Shared\G1.Accounts.Utilities\G1.Accounts.Utilities.csproj">
<Project>{89c95315-90a8-4d27-a33a-640830a3e46b}</Project>
<Name>G1.Accounts.Utilities</Name>
</ProjectReference>
Shows an error here: using G1.Accounts.Utilities;
MSBuild & Resharper Build both build and launch the application correctly, but solution-wide analysis remains broken until I remove and add the references again (capitalizing the project id as a result). I'm not sure why the mixing of lower and upper case project ids is happening, but VS seems to handle it just fine.
For example:
<ProjectReference Include="....\Shared\G1.Accounts.Interface\G1.Accounts.Interface.csproj">
<Project>{3B92A5DD-09F5-49FB-B265-CBFCA64E6C5C}</Project>
<Name>G1.Accounts.Interface</Name>
</ProjectReference>
<ProjectReference Include="....\Shared\G1.Accounts.Utilities\G1.Accounts.Utilities.csproj">
<Project>{89c95315-90a8-4d27-a33a-640830a3e46b}</Project>
<Name>G1.Accounts.Utilities</Name>
</ProjectReference>
Shows an error here: using G1.Accounts.Utilities;
MSBuild & Resharper Build both build and launch the application correctly, but solution-wide analysis remains broken until I remove and add the references again (capitalizing the project id as a result). I'm not sure why the mixing of lower and upper case project ids is happening, but VS seems to handle it just fine.