AraHaan
AraHaan
Alright, I was planning to go into the codebase and extract worthy strings to resx anyway. To localize then you would have to change the resx files.
Can you please send that log file here, it will only contain the stack trace of what went wrong with the code.
The v4 plugin is not fully completed or even stable yet as I lack enough information on the format of v4.
Leaving this open until the .NET SDK gets fixed.
Looks like the only way to fix this is to push the sdk to the github packages feed and require one to run the exe installers for the runtime. Also...
Currently the runtime is not meant to be built manually (but could be however), the Sdk I feel should be pushed to github packages where github requires a personal access...
Alternatively, the tool could instead, download the Elskom.Sdk nuget package and store it into its own nuget package feed (a folder feed) and have it silently add the feed if...
Did you run the exe installers in the Elskom/runtime repository under the latest release?
those are not meant to be consumed through nuget, those are meant to be located in ``$DOTNET_ROOT/shared/Elskom.Sdk.App`` and ``$DOTNET_ROOT/packs/Elskom.Sdk.App.Ref``. And yes the exe installer means that tool https://www.nuget.org/packages/Elskom.Net.Check for the...
I will work on fixing the installer where it will not try installing the Sdk and instead try to resolve the Sdk itself through nuget when you go to restore...