Base solution for your next web application

Activities of "dmerf"

WHY DID YOU CLOSE THIS? We were still completely blocked with our issue from making any progress.

Based upon all the things we have seen, we have decided to abandon use of ASP.NET Zero and request a refund under your 30 day guarantee. There are just too many problems including very bloated and monolithic solution design, instability, crude and glitchy code generation, poor documentation and inattentively slow software support. For the price it's just not production ready. Good luck))

I read the GitHub posting. Your terse response is not sufficient. When when can we expect that to happen? What exactly is being fixed? How do you know from the limited information I provided that our issue will be fixed? Is this fixing an erroneous error message or the problem where our run time freezes up and we can't use the framework whatsoever?

We are about to proceed with full-scale development of our new ASP.NET Zero project. The The split .NET Core 3.0 Host/Angular 8 solution which I downloaded about two weeks ago, verified and uploaded to our repo, has started throwing an error message "HttpRequestEntityChangeSetReasonProvider - Unable to get URL from HttpRequest, fallback to null". This happens when we code gen an entity from our SQL database into the solution and try to navigate to the entity's index view while running. We also reproduced this error on another developer machine which also was working before and also with a FRESHLY downloaded solution from ASP.NET Zero. We are completely blocked from starting development. We have just two days left in our 30 day money-back guarantee period. We are contemplating our options moving forward given this showstopper issue along with all the other bugs, flaws and difficulties we have previously reported. We see a similar problem was reported in incident # 8016 early last month which is still apparently unresolved going on 4 weeks later. We cannot afford to continue with ASP.NET Zero if this cannot be rapidly resolved.

INFO 2019-12-01 19:53:35,908 [40 ] c.Infrastructure.ControllerActionInvoker - Route matched with {area = "app", action = "GetEditionTenantStatistics", controller = "HostDashboard"}. Executing controller action with signature System.Threading.Tasks.Task`1[Company.Application.MultiTenancy.HostDashboard.Dto.GetEditionTenantStatisticsOutput] GetEditionTenantStatistics(Company.Application.MultiTenancy.HostDashboard.Dto.GetEditionTenantStatisticsInput) on controller Company.Application.MultiTenancy.HostDashboard.HostDashboardAppService (Company.Application.Application). INFO 2019-12-01 19:53:35,927 [36 ] .Mvc.Infrastructure.ObjectResultExecutor - Executing ObjectResult, writing value of type 'Abp.Web.Models.AjaxResponse'. INFO 2019-12-01 19:53:35,928 [36 ] c.Infrastructure.ControllerActionInvoker - Executed action Company.Application.MultiTenancy.HostDashboard.HostDashboardAppService.GetEditionTenantStatistics (Company.Application.Application) in 20.015ms INFO 2019-12-01 19:53:35,928 [36 ] ft.AspNetCore.Routing.EndpointMiddleware - Executed endpoint 'Company.Application.MultiTenancy.HostDashboard.HostDashboardAppService.GetEditionTenantStatistics (Company.Application.Application)' INFO 2019-12-01 19:53:35,928 [36 ] Microsoft.AspNetCore.Hosting.Diagnostics - Request finished in 78.3127ms 200 application/json; charset=utf-8 DEBUG 2019-12-01 19:53:38,494 [41 ] HttpRequestEntityChangeSetReasonProvider - Unable to get URL from HttpRequest, fallback to null DEBUG 2019-12-01 19:53:43,504 [41 ] HttpRequestEntityChangeSetReasonProvider - Unable to get URL from HttpRequest, fallback to null DEBUG 2019-12-01 19:53:48,517 [41 ] HttpRequestEntityChangeSetReasonProvider - Unable to get URL from HttpRequest, fallback to null DEBUG 2019-12-01 19:53:53,525 [36 ] HttpRequestEntityChangeSetReasonProvider - Unable to get URL from HttpRequest, fallback to null DEBUG 2019-12-01 19:53:58,528 [36 ] HttpRequestEntityChangeSetReasonProvider - Unable to get URL from HttpRequest, fallback to null DEBUG 2019-12-01 19:54:03,545 [36 ] HttpRequestEntityChangeSetReasonProvider - Unable to get URL from HttpRequest, fallback to null DEBUG 2019-12-01 19:54:08,561 [36 ] HttpRequestEntityChangeSetReasonProvider - Unable to get URL from HttpRequest, fallback to null DEBUG 2019-12-01 19:54:13,568 [36 ] HttpRequestEntityChangeSetReasonProvider - Unable to get URL from HttpRequest, fallback to null DEBUG 2019-12-01 19:54:18,581 [44 ] HttpRequestEntityChangeSetReasonProvider - Unable to get URL from HttpRequest, fallback to null

Has this problem been solved? We are about to proceed with full-scale development of our new ASP.NET Zero project. The split .NET Core 3.0 Host/Angular 8 solution which I downloaded about two weeks ago, verified and uploaded to our repo has started throwing this same error message "HttpRequestEntityChangeSetReasonProvider - Unable to get URL from HttpRequest, fallback to null". This happens when I code gen an entity from the database into the solution and try to navigate to the entity's index view while running. We also tested this on another developer machine which also was working before and also with a freshly download solution from ASP.NET Zero. We are completely blocked from starting development. We have two days left in our 30 day money-back guarantee period and we are contemplating our options moving forward given this showstopper issue along with all the other bugs, flaws and difficulties we have previously reported.

We had already discovered that recommendation but have been able to get refresh.bat to execute. Either it does not like path or it tries to use the wrong version of .NET Core. We have tried numerous combinations of pathing and command parameters to specify which version to use. Ideas?

We are a new ASP.NET Zero customer. We are just creating our solution using the ASP.NET CORE & Angular project type. I used the ASP.NET Zero-Load Entity From Database tool to create a new entity from an existing DB table. That seemed to work. I compiled and ran the Web.Host project. But when I try to Run Start the Angular service it fails to compile due to following issue:

ERROR in app/main/domainModel/sponsors/create-or-edit-sponsor-modal.component.ts:4:10 - error TS2305: Module '"..Web.Host/src/shared/service-proxies/service-proxies"' has no exported member 'XXXServiceProxy'.

What is causing the error and how do we fix it? Thank you!

Showing 1 to 6 of 6 entries