Projects are not loaded when the code is in network mapped drive

[viveknuna]

I have installed the tool by running the below command yesterday.

dotnet tool install --global Microsoft.VisualStudio.SlnGen.Tool

Then I run the below command to generate the solution.

@ECHO OFF
slngen --launch:false --folders:true --collapsefolders:true --solutiondir:src --solutionfile:MySolution.sln --ignoreMainProject --verbosity:normal **.csproj **.sqlproj
REM --verbosity:diag

It works as expected when my code is in C drive, But when my code is in J drive which is a network drive. It gives the below errors when I open the solution in Vishal Studio 2019.

One or more projects in the solution were not loaded correctly. Please see the Output window for details.

Error in the output window.

J:\folder\UNC\SUKWGWGDSPASDF1\VDIUsers$\User.Name\folder\src\shared\Common\MyProject.Common.csproj : error : The project file cannot be found.

How to fix it? I have to use the J drive, It's required.

[jeffkl]

@viveknuna is there a way to share the generated solution file?

I think its because of this code:

slngen/src/Shared/ExtensionMethods.Shared.cs

Lines 38 to 46 in 4858f5a

	if (Utility.RunningOnWindows)
	{
	using FileStream stream = File.Open(path, FileMode.Open, FileAccess.Read, FileShare.ReadWrite);
	StringBuilder stringBuilder = new StringBuilder(GetFinalPathNameByHandle(stream.SafeFileHandle, null, 0, 0));
	GetFinalPathNameByHandle(stream.SafeFileHandle, stringBuilder, stringBuilder.Capacity, 0);
	return stringBuilder.ToString(4, stringBuilder.Capacity - 5);

This is trying to determine the "real" path of a file if the casing is wrong which can happen when people manually type in the path to a project in a <ProjectReference /> item. But since you're using a mapped drive, I suspect this method is returning something that Visual Studio cannot understand. I'll try to find some time today to reproduce the issue.

[viveknuna]

@jeffkl sure, thank you for responding, I'll wait for the update.

[viveknuna]

@jeffkl It's working as expected. Thank you

[jeffkl]

Thanks for reporting the issue, luckily the fix was easy!