Base solution for your next web application

Activities of "smackofham"

OK - found the issue - for whatever reason a developer added {useHash:true} to the root-routing.module.ts. At this point I have no idea why, but, there it is.

Thank you.

I have, and as far as I can tell, it looks fine:

{
  "remoteServiceBaseUrl": "https://not-real-uri-api.azurewebsites.net",
  "appBaseUrl": "https://not-real-uri.azurewebsites.net",
  "localeMappings": [
    {
      "from": "pt-BR",
      "to": "pt"
    },
    {
      "from": "zh-CN",
      "to": "zh"
    },
    {
      "from": "he-IL",
      "to": "he"
    }
  ]
}

OK - so what I've found is that our routing seems odd. The URL is in this format: https://www.random.com/#/account/login

The email activation url is: https://www.random.com/account/confirm-email

If i add the /#/ to the second URL, everything works. Where is this coming from, and why? We have made no modifications to the routing.

{
  "ConnectionStrings": {
    "Default": "<RemovedConnectionString>"
  },
  "App": {
    "ServerRootAddress": "http://localhost:9901/",
    "ClientRootAddress": "#{appBaseUrl}#",
    "CorsOrigins": "http://localhost:9902"
  }
}

We are replacing the #{appBaseUrl}# token during deployment. That changes to the web app url.

OK, so for anyone who follows behind me with the same issue, it turns out we needed to downgrade netstandard library to 2.0.1 for this to work. Seems to be a breaking change in the 2.0.3 version?

Yes - this is a hosted VS2017 build agent. It has Visual Studio 2017 Enterprise installed already.

No.

Showing 1 to 7 of 7 entries