Asmodeus-boop
commented
1 week ago Having just done this, make sure if youre on Win that youre using .net sdk 6.0 release and nothing newer. For whatever reason it just does not work. Additionally, you need to ensure (at least in my case) that you enter system properties>Environment Variables and then when viewing the System Variables window, edit the "Path" variable. Once you have brought up the edit function, ensure that there is a path entry for your \python39 folder and the \python39\Scripts folder. On top of this I added the paths to my User Enviro variables. Verify that upon installation that some form of pathing was generated in these fields for the \dotnet path as well as \cmd. I for some reason automatically had an entry for \cmd in the directory hard drive that hosts my repository.
When running CMD, Run in admin of course unless using pwrshell. If using cmd, ensure that you if the repository is not located on the same drive as your default installation path you change it before running the prompt.
As an example:
cmd will start as C:\windows\sys32> enter "cd\" here without parenthesis
cmd will respond with C:> enter "your designated drive in which you have your cloned repo, E:\ for example"
cmd will respond with E:> "entire folder path for the blenderUmap2 folder in cloned repo:(cd E:\to\your\directory)" no ( )
Cmd responds with E:\to\your\directory> now enter "python make_releasse.py"
I did have to run a bit of a different script which you can locate on my published edit of just the python Make_release.py file.
You should be able to see the updated file in the unofficial fork I created. Thanks to both MInushG and Amrsatrio for all the hard work.
MinshuG
i got some errors when i running the make_release.py in vs code and no addons in release folder