Conversation
|
Thanks @jeffkl! Any thoughts on it still returning (Or at least maybe spit out some warning/info about it when it does occur?) |
Can you elaborate more? What values would return |
|
@jeffkl I can type anything in the Platform dialog: I was also, previously to this commit, trying to pass ARM64 in: But that gets stripped by the If there are custom tooling/msbuild sdks, etc... that may be used by a project, they may care about non-standard platforms, like the Uno Platform iOS ones: |
|
@michael-hawker this is extremely complicated from the command-line. Visual Studio has two concepts: Solution configuration and Project configuration. The hard part is mapping project configurations to solution configurations. When you use the UI, you get a nice grid and can create a solution platform and map it to the appropriate project platform. In some cases you'll want to create a solution configuration like "Custom Thing" but when you build it you want to map that to "x86" for the project. Since SlnGen is a command-line tool, I haven't found a good way for a user to convey these mappings. At the moment, there are some built-in mappings for C++ projects, when you select a solution platform of Any CPU, it will build x86 or amd64 if the project supports one of those. What works best is for the projects to convey what they support which is how SlnGen dynamically discovers configurations and platforms. If an SDK-style CSPROJ has: <PropertyGroup>
<Platforms>AnyCPU;x86;x64</Platforms>
</PropertyGroup>Then SlnGen will generate a solution with the correct solution platforms and map it to the project platforms. What's missing is any way to convey a mapping. I'm not sure if its worth it at the moment but we could look into something like: <ItemGroup>
<SlnGenSolutionPlatform Condition="'$(Platform)' == 'x64'">MyCustomPlatform</SlnGenSolutionPlatform>
</ItemGroup>But I'm not sure how many people need this functionality. In the 5 years that I've worked on SlnGen, no one has asked for custom mappings like this... |


Fixes #437