Added a Paths.cmd template so users can add their local VisualStudio …

[kamgam]

…version easily. The old one was locked to 2019 enterprise.
I added this because I am using the VS Community Edition and it seems the enterprise path is committed into the Build.cmd file. My solution allows each user to use their own VS path which allows for more flexibility without polluting the branch with differen VS path commits.

[unitycoder]

thanks, ill have a look

[unitycoder]

would it be possible to make this ready to use by default?

as in: it would default to community version (or detect if it exists) with ready to use/included paths.cmd file,
so then average user doesnt need to do that manual rename and edit?

[kamgam]

I think we could check for some default VS paths and use those if no "Paths.cmd" file was set. I'll submit a new PR once I have got that running (don't know yet when I'll have the time to do it though).

[kamgam]

Have updated the patch with auto detection for VS 2019 and 2022 Community and Enterprise edition.

It now also prints a proper message for users. I have also added a "PAUSE" command if no VS path could be found (so users notice).

If the Build.cmd is used in an automated build environment then this "pause" behaviour can be disabled by adding "-no-pause" as the first parameter, like: "Build.cmd -no-pause".

[unitycoder]

added and seems to work locally and with github actions, thanks!

[kamgam]

Thanks for merging and making the tool (I use it daily) 👍