Loses <Compile Include>s on converting to SDK

[Toastedcranium]

We are upgrading a large, multi-solution/multi-project .net framework 4.6.2 to .net 8. Most of the items work with minimal code changes when using the tool, there are just some hiccups along the way.

One of the items is: there are file links that some of the projects use, some assemblyInfo-global/solution and a trustedClient file that in the old csproject are , those are lost when converting to the SDK format. A few files depend on the access to these and right now, I have to manually add them back into the new .csproj.

This similar item happens to Reference includes that do not have hintPaths inside old csproj files. In the old project, the properties of the reference point to a specific location but do not have a hintpath in the .csproject. When converting over, it loses the path when you right click the reference and go to properties. Fixing this, I have to add to the location that the reference is installed on the machines.

Don't ask why these files are referenced this way, I am new to the project tasked with looking into complexity on upgrading to the newer framework, but it is a headache for this large project.