Sounds good! Thanks for all the help!
Thanks for the information.
Kind of wish it didn't do any license check since that requires ASP.NET ZERO to stay in business and have this service available for the lifetime of our product which will hopefully be many, many, years from now. If your service goes away, and we do not upgrade to a newer version of ASP.NET ZERO (no plans to upgrade at this point), how will that impact our development and release process? If the license check fails, do we get a warning logged to the output like we are seeing or will things not work quite right or not at all? Ideally, since we have invested in using ASP.NET ZERO, we will not encounter problems developing if your service or company goes away in the future.
It appears to be working now and we do not get the error.
Can you provide some information on how the license checking works? I didn't know there was one even being performed, I thought it was just a license key that we had to include in our settings file. We may be deploying our product into locations that do not have internet access, etc. so how does this work for debug/release builds in those situations?
Thanks, Chuck
We are not really doing anything all that strange. Basically, we are doing something similar to:
public async Task HttpPostService()
{
EntityImpl item = await repository.Get(id);
item.Text = "New text";
notificationPublisher.PublishAsync("EntityChanged",...);
}
After we started calling publish async, the LastModifierUserId is no longer set. LastModificationTime is set though. We found it strange that simply adding that one function call lead to this which is why we opened a question. If I add a call to SaveChanges before the publish all values are populated like before.
Thanks. Yea, the DbMigrator project is working but the issue is it only applies the migrations once per database. So with multiple tenants in a single DB I will need to find a way to add new entity instances for each tenant. So something like a foreach(tenant) addTenantSpecificData(); would have to be executed once for each DB after the migrations have been applied I guess.
I did notice several creator classes within Migrations.Seed.Tenants so maybe creating one of those would work? I assume those will get applied after the DB migrations so any schema changes will be applied. I could then go through each tenant in the DB being updated and add any/modify any custom data for them.
Perfect!!
Thanks for the help!
Thanks for all the information marble68. If we are able to change the name ourselves in code then I wont be as worried about the name we select. If we cannot due to licensing, etc. then we will have to be sure on the name.
Any chance I can get confirmation from support on this?
Thanks!
We are currently using a local TFS server right now so maybe GIT would be better - something for us to consider later. I will move our source strucure towards how ASP.NET Zero is more typically used since that will have the least issues it sounds like.
Thanks for the information.
When you say most users directly use the provided template, do you mean they just add code to the modules that come with the default solution instead of adding new modules? Just want to make sure I understand what you are saying.
Tested in ASP.NET Zero 8.7.0 and it seems to be working correctly now.
Thanks!