Activities of "brallierc"

Ok... so what about the appSettings? Do I need to use different ports? I feel like there must be some steps missing because I tried a fresh copy of 5.6.1 and I cant get it to work once I publish to azure

The documentation only shows examples of the settings for seperate web applications. It says that if you are using the merged solution then you only need to publish the host, does that mean I dont need to do the steps you would typically do to publish the angular cluent?

If anyone has the exact steps to publish a merged .net core/angular solution to a single azure web application service I would very much appreciate it.

Nevermind... I reran gulp --prod and it was able to publish

This might be a duplicate topic but it was ignored. I am glad someone else is experiencing the same problem. Today I tried it again with a fresh install and deployment of version 5.0.6 ASP.Net Core and Jquery to Microsoft Azure and I have the same problem. In Chrome it works fine, in Microsoft Edge I get the same error listed above

As it turns out... I am only experiencing this issue in Microsoft Edge... it works in Chrome. I figured this out when I read another post which suggested that the Login didn't work in IE... I also have that issue... so I tried Chrome and it worked so then I also tried going to my API page and it worked.

When I go to the Swagger UI page, I just get this error:

Can't read from server. It may not have the appropriate access-control-origin settings.

By the way, the article you gave me for SignalR worked! For anyone having the same problem... Add WEBSITE_LOAD_USER_PROFILE = 1 to your App Settings on your Web.Host App Service in Azure

The Audit Logs and Web Logs do not show anything specific to Swagger. However, I do also have an issue with SignalR not working (yes, I am using .Net 4.6.1 and not just core), that error message is:

ERROR 2017-12-26 04:47:05,263 [31 ] e.Diagnostics.ExceptionHandlerMiddleware - An unhandled exception has occurred: The data protection operation was unsuccessful. This may have been caused by not having the user profile loaded for the current thread's user context, which may be the case when the thread is impersonating. System.Security.Cryptography.CryptographicException: The data protection operation was unsuccessful. This may have been caused by not having the user profile loaded for the current thread's user context, which may be the case when the thread is impersonating. at System.Security.Cryptography.ProtectedData.Protect(Byte[] userData, Byte[] optionalEntropy, DataProtectionScope scope) at System.Security.Cryptography.DpapiDataProtector.ProviderProtect(Byte[] userData) at System.Security.Cryptography.DataProtector.Protect(Byte[] userData) at Microsoft.Owin.Security.DataProtection.DpapiDataProtector.Protect(Byte[] userData) at Microsoft.AspNet.SignalR.Infrastructure.DataProtectionProviderProtectedData.Protect(String data, String purpose) at Microsoft.AspNet.SignalR.PersistentConnection.ProcessNegotiationRequest(HostContext context) at Microsoft.AspNet.SignalR.PersistentConnection.ProcessRequest(HostContext context) at Microsoft.AspNet.SignalR.Hubs.HubDispatcher.ProcessRequest(HostContext context) at Microsoft.AspNet.SignalR.PersistentConnection.ProcessRequest(IDictionary2 environment) at Microsoft.AspNet.SignalR.Owin.Middleware.HubDispatcherMiddleware.Invoke(IOwinContext context) at Microsoft.Owin.Infrastructure.OwinMiddlewareTransition.Invoke(IDictionary2 environment) at Microsoft.Owin.Mapping.MapMiddleware.<Invoke>d__0.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.AspNetCore.Owin.WebSocketAcceptAdapter.<>c__DisplayClass6_0.<<AdaptWebSockets>b__0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.AspNetCore.Localization.RequestLocalizationMiddleware.<Invoke>d__4.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at IdentityServer4.Hosting.IdentityServerMiddleware.<Invoke>d__3.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task) at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.<Invoke>d__6.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.AspNetCore.Cors.Infrastructure.CorsMiddleware.<Invoke>d__7.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at IdentityServer4.Hosting.BaseUrlMiddleware.<Invoke>d__3.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Abp.AspNetZeroCore.Web.Authentication.JwtBearer.JwtTokenMiddleware.<>c__DisplayClass0_0.<<UseJwtTokenMiddleware>b__0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Abp.AspNetZeroCore.Web.Authentication.JwtBearer.JwtTokenMiddleware.<>c__DisplayClass0_0.<<UseJwtTokenMiddleware>b__0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task) at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.<Invoke>d__6.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware.<Invoke>d__6.MoveNext(

I 100% agree with the post above. I love the product but documentation is lacking. For example, it is September 17th and on September 11th version 4.5 was released, but there still hasn't been an update to the change logs. Often within the change logs there is a single line that says bug fixes and enhancements... what are those?

I've been a customer for a year and a half, which means that I have renewed once. At the time it was a tough decision because I wasn't sure what would be implemented within the roadmap that was going to be valuable to me. I would recommend more documentation on features that are coming in the next few releases (90 days would be sufficient)

Other than those comments, I love the product and I have much hope for what it will become and what it can do to speedup the development process.

Well it doesn't open a console application... also... UpdateDatabase from the package manager console doesn't work either.

Yes I did edit the appSettings to use the correct db connection string. Before anyone else asks me more questions, has anyone downloaded the latest template and made it work. I have tested it from 3 different computers, all have the same result, the migrator does not open the console window and update-database does not work.

Whenever I have ran migrator in the past, when the migrator project compiles it creates a <projectname>.migrator.exe, this template is not creating that file.