Activities of "marble68"

I did indeed have to create an entirely new repository.

Only then did my migrations seem to behave better.

Thank you.

Thank you for the response. Yes, I'm seeing that I have to do that in 11.2. The heathchecker context requires -context since it, too, is a dbcontext.

My deeper question is around those migrations. After merging 11.2 into my 11.0 project, I have existing migrations and need to add another for the changes in 11.2.

So, I then added a new one, to pick up the new tables (such as password history, etc).

The end result would not apply, and it ended up trying to add a bunch of foreign keys that already existed.

Is this the normal workflow? At this point, I am supposed to edit the new migration to make it compatible with my project?

Sorry if this is a dumb question - but I'm strugging to find the "best practice" for this. I will eventually have to figure it out because I can't just wipe out my database every time I update my project.

I'm just not clear on what's required. If editing the migration manually is required, I suppose that will be what I'll have to do.

Prerequisites

MVC Core version 11.2 Jquery

Status

I have an 11.0 project, and I've merged in 11.2. Everything looks good - but there are new migrations for things like previous passwords ect.

Also - the entity framework versions are different.

Since I'm using mysql, I need to regenerate these migrations and migrate my existing database.

What I tried was merging in my upgraded branch into my existing dev branch without the migration files.

However - I've not been successful at applying the changes.

Firstly, add-migration and update-database return there there is more than one dbcontext and I must specify. When I do, it still does not like the migrations generated.

What is the normal process for this? Am I missing something?

Thanks!

Prerequisites

v11 MVC Core

After spending some hours on creating a widget...

First, it prepends my Filter name as a folder, said it couldn't find my file. So I moved it there.

Then, it looked for it in the widgets folder, where I had it, and said it couldn't find it.

Any ideas what might might cause a widget to look in two different places?

AHA - Found it! Facepalm.

When adding your view - documentation says s.Add(AbpZeroTemplateDashboardCustomizationConsts.Widgets.Tenant.DailySales,

I ran into this a long time ago - facepalm.

C

Prerequisites

V11.0 Core MVC

This page That walks through creating a widget seems a bit out of date.

Is there a fresher walkthrough somewhere?

I'm about to do my third walkthrough to try and get a widget to show up! lol

Thanks if anyone has a better resource.

I wasn't thinking. I created my own object and just returned that, with the same interfaces as the PagedResultDto.

I think that did the trick

Prerequisites

v11 MVC Core

In one of my application services - I need to send a value along with the resulting PagedResultDto.

How can I add a property to the PagedResultDto object?

Since the app service inherits from IApplicationService, I can't just change my service's GetAll return type.

How might I approach this, since I need this data not just in the UI but in the dynamically generated API as well?

Thanks for any suggestions

By the way, this package doesn't work with 11.0.

Just adding the package to the project causes it throw an error in startup.

To recreate:

Add the aforementioned package: Castle.Core-Serilog Add to Public, MVC, Host, and Migrator, just like log4net. Run - You'll get the following error:

System.TypeInitializationException HResult=0x80131534 Message=The type initializer for 'Abp.Dependency.IocManager' threw an exception. Source=Abp StackTrace: at Abp.AbpBootstrapperOptions..ctor() at Abp.AbpBootstrapper..ctor(Type startupModule, Action1 optionsAction) at Abp.AbpBootstrapper.Create[TStartupModule](Action1 optionsAction) at Abp.AspNetCore.AbpServiceCollectionExtensions.AddAbpBootstrapper[TStartupModule](IServiceCollection services, Action1 optionsAction) at Abp.AspNetCore.AbpServiceCollectionExtensions.AddAbp[TStartupModule](IServiceCollection services, Action1 optionsAction, Boolean removeConventionalInterceptors) at inzibackend.Web.Startup.Startup.ConfigureServices(IServiceCollection services) in R:\Surpathv2\src\inzibackend.Web.Mvc\Startup\Startup.cs:line 201 at System.RuntimeMethodHandle.InvokeMethod(Object target, Span1& arguments, Signature sig, Boolean constructor, Boolean wrapExceptions) at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) at Microsoft.AspNetCore.Hosting.ConfigureServicesBuilder.InvokeCore(Object instance, IServiceCollection services) at Microsoft.AspNetCore.Hosting.ConfigureServicesBuilder.<>c__DisplayClass9_0.<Invoke>g__Startup|0(IServiceCollection serviceCollection) at Microsoft.AspNetCore.Hosting.StartupLoader.ConfigureServicesDelegateBuilder1.<>c__DisplayClass15_0.<BuildStartupServicesFilterPipeline>g__RunPipeline|0(IServiceCollection services) at Microsoft.AspNetCore.Hosting.ConfigureServicesBuilder.Invoke(Object instance, IServiceCollection services) at Microsoft.AspNetCore.Hosting.ConfigureServicesBuilder.<>c__DisplayClass8_0.<Build>b__0(IServiceCollection services) at Microsoft.AspNetCore.Hosting.StartupLoader.ConfigureServicesDelegateBuilder`1.<>c__DisplayClass14_0.

This exception was originally thrown at this call stack: [External Code]

Inner Exception 1: TypeLoadException: Could not load type 'Castle.Core.Pair`2' from assembly 'Castle.Core, Version=5.0.0.0, Culture=neutral, PublicKeyToken=407dd0808d44fbdc'.

Yes, it was something stupid..

Fixed by job doing the following:

ImportClientFromSPLService(){Logger=Logger}.DoImport(args);