Activities of "godrunner"

I also noticed that the download page says v5.0.0 when yesterday it said v5.0.1, so that is confusing as to what version is actually available.

I was looking for v5.0.2

I would second that. Great work and it is very much appreciated. You guys are great!!

Is there any "official" word on this? This is core tenant functionality. Do I need to post this on Github? I don't see this issue there but could have missed it.

Thank you.

Wow, that seems odd. I'll give it a try. I am almost certain it is not documented like that.

This would be a bug for sure either way.

Greetings NickKellett!

Running

dotnet build

from the command line in the public project folder will fix this. I had the same issue.

So I downloaded a fresh copy of 4.6.1 and deployed it to Azure App Services and I get the exact same behavior as I did in 4.5.1 . So, is the framework just broken then at this time or am I doing something wrong? It all seems to work fine except for multi-tenancy which is a bit of an issue. :-)

Thanks!

Thanks @XugoWebTeam. From what you are saying it sounds like a known issue.

@smcagdas, if this is so, is it fixed in 4.6.1?

From .core project I have: public const bool MultiTenancyEnabled = true;

From appsettings.json in .host

"ServerRootAddress": "http://api.azurewebsites.net", "ClientRootAddress": "http://mysite.com",

"CorsOrigins": "http://mysite.com"

From appconfig.json in Angular project

"remoteServiceBaseUrl": "http://api.azurewebsites.net", "appBaseUrl": "http://{TENANCY_NAME}.mysite.com"

Thanks!

Using Angular-CLI on Azure version 4.5.1 All it is the basic app with the phonebook implemented. I want to do a proof of concept of everything before I start building the main app, so hosting successfully with a real domain name on Azure is the next step for us. I have the API backend and the angular client app on Azure. (did not bother with the public site for now.)

Everything works very well in testing locally and on Azure, EXCEPT, there is a problem with multitenancy / domain / tenancy logins.

• If I create a tenant called "test" I can impersonate that tenant from the host account and it appears that everything works as it should from test.mysite.com
• If go to test.mysite.com I cannot login with the test user, however, I CAN login right there with the host admin account. (which is strange isn’t it?) The test user is activated.
• I can go to fakesite.mysite.com which has never been created and I can login with the main host password.
• If I login from these different hostnames, I get the full host account with tenants.

I have checked and double checked. Any ideas??

Thanks!!

Ok, can't wait to see it!

Sounds interesting! I sure do wish there was a better way to upgrade to a new release somehow going forward. That is my vote at least!