Hi,
It seems like a data protection problem on azure. I found a temporary solution here <a class="postlink" href="https://github.com/SignalR/SignalR/issues/3670#issuecomment-204041898">https://github.com/SignalR/SignalR/issu ... -204041898</a>.
Can you try that ?
Hi,
The first problem about pretty error page is similar to this one I think #1887@cd3839d0-10fe-4daf-917b-a02979c17b2c.
About upgrading your solution to new version of AspNet Zero, we accept that it's not an easy thing to do. You can check this comment, it might give you an idea <a class="postlink" href="https://github.com/aspnetzero/aspnet-zero/issues/96#issuecomment-186843738">https://github.com/aspnetzero/aspnet-ze ... -186843738</a>.
You can always ask help for the errors you get during the upgrading of your project. We will be happy to help.
Hi,
The error page you see is shown for development time. There is the below code in Startup.cs which does this.
if (env.IsDevelopment())
{
app.UseDeveloperExceptionPage();
}
else
{
app.UseStatusCodePagesWithRedirects("~/Error?statusCode={0}");
app.UseExceptionHandler("/Error");
}
If you want to see pretty error page on development time, you can chage it. If you want to modify the pretty error page, you can modify *.cshtml files under "Views\Error" folder.
Hi,
We are currently busy with developing angular2 version. After that we will consider this. Please create an issue for this here <a class="postlink" href="https://github.com/aspnetzero/aspnet-zero-core/issues">https://github.com/aspnetzero/aspnet-zero-core/issues</a>, so you can follow the progress of it.
Hi,
@commondesk, you are also invited.
Hi,
No, we didn't test ADAM. We will be very happy if you have a chance to test and share your results.
Hi,
You are right, this is not a good way. You can use current UserManager, add custom methods to it and cast to ApplicationUser when necessary. Current UserManager's methods should also work for your ApplicationUser.
Or you can upgrade to latest ABP and ABP Zero.
Hi,
You can try to add Column attribute like this.
[Column(TypeName = "nvarchar(max)")]
or you can change the MaxLenght in OnModelCreating of your dbcontext.
modelBuilder.Entity<Entity>().Property(u => u.NameOfProperty)HasMaxLength(4000);
Hi,
We occupied the default url to front-end by design. You can change it but there is not an easy way of doing this and we don't recommend because it will cause many unexpected problems. You can move all controllers from MPA area to Controllers folder and make necessary changes according to this action. This might be very painful.
Hi,
You are invited on github. Now, you should be able to access samples.