Generated Solution is Missing some Shared Project References

[michael-hawker]

Context:
https://developercommunity.visualstudio.com/t/Switch-shared-project-file-context-crash/10048136
https://developercommunity.visualstudio.com/t/Switching-context-in-a-C-code-editor-wi/1612820#T-N10090311

I think our generation of our solution (and the resulting solution) are missing some lines needed for Shared Projects to work correctly in the sample app.

For instance if I try and open one of the files in the CommunityToolkit.Labs.Shared project and switch to Wasm or WinAppSDK, VS throws an error and doesn't do anything.

I do indeed see the guids to link to these projects missing from the SharedMSBuildProjectFiles section.

I tried fiddling with it, but couldn't get it to work.

[Arlodotexe]

The solution generation script that I wrote in CommunityToolkit/Labs-Windows#82 pulled project references out of our existing and working solution file and placed them back in via a script.

Unfortunately the only useful info I have is, if there's a problem with the solution file, Visual Studio will either correct it automatically when opening then ask you to save the changes to the .sln upon closing it, or complain outright if it can't be fixed automatically.

[michael-hawker]

Right, I think even then there was some missing shared reference projects, if you inspect the projects shared references, you'll see they won't be checked, and the corresponding guid isn't in the shared project section. So I think we need to try re-creating the shared project link between those platforms again.

[Arlodotexe]

It may be worth investigating usage of official solution generation tooling, rather than homebrewing, now that we're approaching release.

[Arlodotexe]

@michael-hawker We good to close this off now that we moved to slngen?

[michael-hawker]

Yup, sounds good.