I thought I would comment on what I did since it related to issues you were having to get it to compile.
So I ran yarn as per the normal instructions and made sure that npm start would run my project before i tried anything else.
Then I npm installed the angular-cli
Then I went to run ng build --prod and got the error from #2461@7cc86646-d789-4b09-b453-d727a9d6a818 which says I need to be in a angular-cli project to run it.
After a google found this <a class="postlink" href="http://stackoverflow.com/questions/39133782/you-have-to-be-inside-an-angular-cli-project-in-order-to-use-the-build-command-a">http://stackoverflow.com/questions/3913 ... -command-a</a>
Which basically says to run
npm install -g @angular/cli@latest
After doing that and running ng build --prod again everything compiled as expected, I have yet to release this to a server but it all compiled into dist folder as expected so maybe that will help someone
Tenant admin can already edit languages as far as I am aware (just checked v4.5.1).
Tenant management is in the host level (null/empty tenant).
So if you logout of default tenant, then select tenant and empty the box then login you will be in the host level assuming you are running locally?
I have it set to use the non release candidate version and that seems to work ok for me. Are you saying that switching to the exact RC version would also fix the issue without all the other errors?
If * as the CORS setting works, it means you current CORS config is probably slightly wrong
Can you try a few other combinations in the CORS origin to see if you can find the offending one?
For example in your log it is failing on <a class="postlink" href="http://demo.host.xugo.com.au/">http://demo.host.xugo.com.au/</a>
So you will need a CORS entry for that, as far as i am aware, TENANCY NAME works by replacing that var for the server address in the .json. So if its set to {TENANCY_NAME}.host.xugo.com.au and you visit demo.portal.xugo.com.au then angular will be asking for demo.host.xugo.com.au
If that makes sense?
Thanks @ismcagdas thats what I expected!
I have an older version running (4.3 i think) running through DevOps pipeline to 2 Azure app services with a few bonus steps needed once deployed that I have yet to figure out when I have some time but i cant imagine the newer versions being any more difficult if you need help?
The DevOps pipeline can be treated as your home machine so if you can compile and deploy on your machine the steps are largely the same it can just seem more confusing. I would be happy to provide some guidance if needed.
Thanks for confirming!
Neither using set or $env = seemed to work, any other ideas?
Hi again,
Sorry I should have been clearer in my response yesterday.
I have tried both the following and they dont work
set ASPNETCORE_ENVIRONMENT=Development
and
$env:ASPNETCORE_ENVIRONMENT='Development'