Base solution for your next web application

Activities of "Mitch"

I've actually got things working in Azure!

In Startup.cs I commented out the following line

options.PlugInSources.AddFolder(Path.Combine(_hostingEnvironment.ContentRootPath, "Plugins"));

Now ASP.Net Zero will run and allow me to log in. Not sure if the commented out line will cause me issues later though.

I'm trying to get Telerik Reporting working with ASP.Net Zero

Part of the setup is to create an API controller.

I'm following the instructions for getting the Telerik Reporting working on ASP.Net Core ([https://docs.telerik.com/reporting/html5-report-viewer-asp-net-core-2#creating-a-sample-asp-net-core-project]))

However, I'm getting an error.

HTTP500: SERVER ERROR - The server encountered an unexpected condition that prevented it from fulfilling the request. GET - <a class="postlink" href="http://localhost:62114/api/reports/resources/js/telerikReportViewer-12.0.18.227.min.js">http://localhost:62114/api/reports/reso ... 227.min.js</a>

Are there any special considerations when setting up API controllers with ASP.Net Zero that I'm missing?

I already have Telerik Reporting running with an existing MVC app so I have had success in the past. I'm just concerned that there's something that I need to do in my ASP.Net Zero Web.Mvc when using API controllers.

Any ideas?

Thanks for getting back so quick Aaron.

Could it be to do with the Logger? I'm just a bit confused as this is the first time I've tried using an API Controller with ASP.Net Zero.

ERROR 2018-04-09 18:42:52,958 [11 ] Mvc.ExceptionHandling.AbpExceptionFilter - No component for supporting the service DpmsCloud.Web.Controllers.ReportsController was found Castle.MicroKernel.ComponentNotFoundException: No component for supporting the service DpmsCloud.Web.Controllers.ReportsController was found at Castle.MicroKernel.DefaultKernel.Castle.MicroKernel.IKernelInternal.Resolve(Type service, IDictionary arguments, IReleasePolicy policy) at Castle.MicroKernel.DefaultKernel.Resolve(Type service, IDictionary arguments) at Castle.Windsor.WindsorContainer.Resolve(Type service) at Castle.Windsor.MsDependencyInjection.ScopedWindsorServiceProvider.ResolveInstanceOrNull(Type serviceType, Boolean isOptional) at Castle.Windsor.MsDependencyInjection.ScopedWindsorServiceProvider.GetServiceInternal(Type serviceType, Boolean isOptional) at Castle.Windsor.MsDependencyInjection.ScopedWindsorServiceProvider.GetRequiredService(Type serviceType) at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService(IServiceProvider provider, Type serviceType) at Microsoft.AspNetCore.Mvc.Controllers.ServiceBasedControllerActivator.Create(ControllerContext actionContext) at Microsoft.AspNetCore.Mvc.Controllers.ControllerFactoryProvider.<>c__DisplayClass5_0.<CreateControllerFactory>g__CreateController|0(ControllerContext controllerContext) at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted) at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.<InvokeInnerFilterAsync>d__15.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.<InvokeNextExceptionFilterAsync>d__23.MoveNext()

Many thanks for the advise Aaron, it worked! However there now seems to be further issues as the api URL's don't seem to be working and apparently this is caused by the api routing not working.

To be honest this is becoming a pain and I'm considering using a different reporting system with ASP Net Zero.

Thanks again for your help last week.

In addition to the Soft Delete filter I'd like to be able to add a filter for Archived data, I imagine using something named IArchive for the interface.

Is this straightforward to do?

Has anyone done something similar?

Will it involve a lot of work to get this going, are there any examples of how to create additional data filters?

Hi

Did you get an answer to this problem from Stimulsoft?

I'm about to start using Stimulsoft reports with ASP Net Zero and I'm probably going to hit the same issue.

Many thanks

Just to confirm, I'm getting the same problem. Here's my logs.

INFO 2018-04-19 23:14:46,717 [13 ] idateAntiforgeryTokenAuthorizationFilter - Antiforgery token validation failed. The required antiforgery request token was not provided in either form field "__RequestVerificationToken" or header value "X-XSRF-TOKEN". Microsoft.AspNetCore.Antiforgery.AntiforgeryValidationException: The required antiforgery request token was not provided in either form field "__RequestVerificationToken" or header value "X-XSRF-TOKEN". at Microsoft.AspNetCore.Antiforgery.Internal.DefaultAntiforgery.<ValidateRequestAsync>d__9.MoveNext() --- End of stack trace from previous location where exception was thrown ---

When creating a new language (English (United Kingdom) en-GB) using the ASP Net Zero interface, I've noticed that it still shows the default language as English (US) despite setting the default to en-GB several times.

I can fix this by removing the US version of English from the options, but it will be problematic for people who might want both language options.

I noticed this issue a few weeks ago but I've only recently got around to reporting it.

I've restarted the app many times and for some reason it always chooses US English and not GB English.

To recreate, get a fresh version of ASP.Net Zero jQuery.

Go to Administration, Languages and Create a new Language which is en-GB, choose the British Flag and then save as Default.

Restart the App and you will notice that US English is still shown as Default.

I've attached a screenshot to show US English at the top of the screen and English (United Kingdom) shown as the Default.

I hope this helps.

It's not just making it the default that an issue, I cannot select from the top right language dropdown menu.

I've created a xxxxxxx-en-GB.xml file in Localization and made sure <localizationDictionary culture="en-GB"> but still if I select English (United Kingdom) from the top right language dropdown, it gives me US English again!

This might just be an issue with en-GB as its base language (en) is the same as the ASP Net Zero default language.

Please just take a moment to setup en-GB for yourselves and then try to select it, it seems impossible.

The only workaround seems to be to disable US English.

Showing 11 to 20 of 103 entries