Xenko 3.1 Cannot resolve paths with spaces.

[FailMelon]

Release Type: Official Release/GitHub (please choose appropriate option)
Official Release - Beta

Version: Version number and/or git branch
3.1.0.1-beta01-0441

Platform(s): Does the problem occur on Windows, Android...?
Windows 10

Describe the bug
A clear and concise description of what the bug is.
When creating a new project xenko cannot find files it needs, i believe this is caused because there is a space in my windows user.

To Reproduce
Steps to reproduce the behavior:

1. Create a windows account with a space
2. Try to create a project under 3.1 build.

Expected behavior
A clear and concise description of what you expected to happen.
Xenko should be able to resolve paths with spaces.

Screenshots
If applicable, add screenshots to help explain your problem (use GitHub drag & drop)

[tebjan]

sounds like this was already fixed in latest master, just not yet published in new beta: #381

[FailMelon]

Ah i missed this pull request that would probably fix it.

[tebjan]

let's hope for a new beta soon then.

[Kryptos-FR]

@tebjan I don't think #381 will do anything for that issue.

And in general having spaces in username is bad and I expect other software to break as well. Looking on the Internet (in your favourite search engine) with a search query such as "Windows username space" brings a lot of results with various software, program or tools failing.

Even Microsoft recommends against doing so: https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-2000-server/bb726984(v=technet.10)

Logon names can contain all other special characters, including spaces, periods, dashes, and underscores. But it's generally not a good idea to use spaces in account names.

[FailMelon]

@Kryptos-FR I'm not even gonna begin to start at how ignorant that post is, if #381 doesn't fix it then it needs to be resolved still.

[Kryptos-FR]

@FailMelon I'm not even gonna begin to start how disrespectful your post was. #381 was fixing a different issue, regarding building the sources.

[xen2]

@FailMelon Thanks for the report.

This specific issue you had is an issue in the T4 template generator lib we use.
I have pushed a fix in Xenko for it already: 4372725 (and also a fix on the T4 library side: mono/t4#38).

Please wait for the next beta release.
Closing since it is already fixed.