Hi! My project uses Virtual properties. Which turns out to be unacceptable.

[lawrakina]

My project uses virtual reference properties, I can't redo them.
public class WaggonReceive { public long WaggonReceiveId { get; set; } public long? StationSendId { get; set; } public virtual Station? StationSend { get; set; } public long PlcId { get; set; } public virtual Plc Plc { get; set; } = null!; public virtual ICollection<WaggonDispatch>? WaggonsDispatch { get; set; } }
I get an error when creating the migration.

Unable to create a 'DbContext' of type 'SRPVContext'. The exception 'Property 'CronTickerOccurrenceEntity.CronTicker' is not virtual. 'UseChangeTracki
ngProxies' requires all entity types to be public, unsealed, have virtual properties, and have a public or protected constructor. 'UseLazyLoadingProxies' requires only
the navigation properties be virtual.' was thrown while attempting to create an instance. For the different patterns supported at design time, see https://go.microsoft.com/fwlink/?linkid=851728

The error occurs because TickerQ entities do not meet the requirements of the Entity Framework for using lazy loading and proxy tracking of changes. You must disable these functions for TickerQ entities or exclude them from the proxy configuration. How to do it?

[phil-lenderfit]

Hello, I hit a similar issue recently. As a workaround I created a separate DbContext to point TickerQ at and managed the migrations for that context separately. They share the same connection string, but have a separate model and migration history.

[lawrakina]

Thanks for your reply. It's a logical decision, I'll try!