Activities of "piapps"

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

Hi guys,

Just wondering if anyone else using the Angular Zero project v4.5.1 is getting an error when compiling it for production?

From a blank project (fresh download from aspnetzero.com) if i go straight to angular folder and run ng build --prod

I get an error in /node_modules/primeng/components/dropdown/dropdown.d.ts.Dropdown.html (6,13) Type string is not assignable to type boolean

Not sure if anyone else has experienced this but I have managed to fix it but had to do several things which may be useful for others

• Open package.json in the angular project and change the version of primeng from ^4.2.0-rc.1 to ^4.2.0
• Run yarn so it updates primeng (confirm it updated 'npm list primeng')
• Recompile for production and you will be hit with more errors this time it will be something about expecting 1 argument but getting 2 in several of zeros ts files. They all have null as second argument so you can just delete the problematic argument.
• Recompile and it should work, however upon visiting the site you will be hit with a wierd error in js console 'Error: Cannot enable prod mode after platform setup.'
• Open package.json and change the version of ngx-bootstrap from ^1.9.1 to ^1.9.2
• Run yarn and confirm its updated
• Recompile and voila

DISCLAIMER: I have no idea if updating those two angular modules has any other side effects. I have tested various parts of Zero afterwards but not thoroughly.

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?

Hi guys,

Just wondering with an enterprise license if we use one of the slots for a clients project and then at some point later in the future if they want to break relations can they take ownership of the license as long as they only assign whatever free developer slots that are left to that new license?

Or would it be better that at that point they purchase their own license then create a project with same name and basically get 'granted' the rights to the project?

Regards, Pete

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.

Hi guys,

We have an extension to one of our Zero projects that might benefit from using the MVC site however we mainly run the angular version.

If I generate a MVC/jquery project can I just grab the MVC project from inside that, import it into the larger angular/web api project and update dependancy locations and the MVC site should just function?

Alternatively is there any way to do this? We still havent decided if this is the way we want to go just yet but I am interested in knowing if its possible

Obviously there is already the public site in the angular project however it doesnt really integrate with any of the services by default hence the question

Thanks