Activities of "JapNolt"

I have downloaded the Angular/aspnetcore template (not merged) and I would like to deploy both to the same Azure App Service. How can I make that work? I'm assuming there are things I need to configure in the web.config and also maybe in the Azure App Service to make it work??

So if I have both the Angular app and the backend api in the same Azure App Service, it doesn't seem to work. I'm assuming that the web.config isn't correct or something with the routes isn't right. I'm assuming I should be doing something contained here but not sure how to do it in Azure App Service. <a class="postlink" href="https://aspnetzero.com/Documents/Development-Guide-Angular#iis-deploy">https://aspnetzero.com/Documents/Develo ... iis-deploy</a>

Thanks for the detailed reply.

If I do deploy to separate Azure App Services, I'm assuming I would need to have a different hostname for the front end (<a class="postlink" href="http://myservice.com">http://myservice.com</a>) and the api (<a class="postlink" href="http://myserviceapi.com">http://myserviceapi.com</a>) or is that not the case?

If doing subdomain per tenancy regardless of what deployment model is used (merged or separate), is it necessary to set the CorsOrigin for each subdomain or is it possible to set a catchall? It seems like a lot of extra work to tweak the CorsOrigin every time that a new tenant is added, especially if we have automatic tenant signup enabled.

BTW, what is your recommendation, to run merged or in separate app services?

@godrunner +1 Thanks.

Is it possible to change the default host tenant name to something that's hard to discover, ie. thisismysuperhardtenantname.portal.mycoolwebsite.com. The host tenant name would be required. In other words, a user could NOT go to portal.mycoolwebsite.com to login to the default host tenant.

I'm using ASPNetCore and Angular project. My host appsettings.json:

"App": {
    "ServerRootAddress": "http://{TENANCY_NAME}.api.mycoolwebsite.com",
    "ClientRootAddress": "http://{TENANCY_NAME}.portal.mycoolwebsite.com",
    "CorsOrigins": "http://portal.mycoolwebsite.com"
  }

My Angular appconfig.json

"remoteServiceBaseUrl": "http://{TENANCY_NAME}.api.mycoolwebsite.com",
  "appBaseUrl": "http://{TENANCY_NAME}.portal.mycoolwebsite.com",

using angular and aspnet core template

Does anybody have any guidance or samples on keeping the data in an angular component live? In other words when a record gets created in a backend table, I want the service to notify the angular UI that it needs to update/refresh. I know that signalr is the tool to use but I'm looking for guidance on best code structure.

@ismcagdas,

Would you recommend modifying the existing ChatHub and SignalRChatCommunicator to achieve the Real-time communication between the Angular front end, the ASPCore backend, and a desktop client? Or should I instead create another Hub for this functionality?

In addition to our web site we have a WPF client application for our users. We want them to be able to sign up from our client app, and we would like to require re-captcha.

The problem is I can't figure out how to display a re-captcha in our client app so I can send a code along with the request to register an account. I have tried to load a page in the WPF web browser control but the re-captcha doesn't display in the page (when it does in a browser).

Would you be able to help me figure out a way to get a re-captcha code that I could send along with my request to register an account?

We are using ASP.Net Core and Angular project. We've set the project to use the UTC Clock Provider. The examples I'm going to give use the built-in Audit Logs. I've patterned some of my other data grids and filters off of this and they're suffering the same problem.

All audit logs in the db is being saved as UTC time. When shown in the Angular UI, the audit logs are showing correctly in the TimeZone that the user has selected (in my case EST, which is GMT -5). This is all good. But when the user selects a date range to filter the audit logs, the dates sent are the "local time".

So if the user selects to show audit logs from 2018/01/26, the filters are sent to the backend as 2018/01/26 00:00:00 - 2018/01/26 23:59:59. When the data is returned, there could be some audit logs with a date of 2016/01/25 which is not what the user would expect. Instead, the date range that is sent to the app service should be in UTC which in my case would be 2018/01/25 19:00:00 - 2018/01/26 18:59:59.

Am I missing some config on the Angular side or is the date range picker not being initialized correctly with the time zone offset?

@ismcagdas My experience is the same as yours. Hmmmmm.....Ahhh, but the query inputs in the app service come in as "local time", which are then executed as is.

BTW, in my original post, my offset calculations were incorrect. Your UI is sending the correct query parameter values but the backend is converting them back to local. Instead they shouldn't be converted back to local but should remain in UTC.