BD.VendorContext.Core

The Vendor Block's domain contract. POCO-only — no B3.CRUD or B3.Messaging dependency — so a Blick can consume it without pulling in the store implementation. See ../_docs/ARCHITECTURE.md.

What's here

• Vendor — the aggregate (PersistableEntity: _id + computed FriendlyID), its field set, validation, and the ToDictionary/FromDictionary mapping to the B3.CRUD row shape.
• VendorType — the fixed domain value set (Inventory / Production / Both).
• Model/PurchaseOrders/ — the purchase-order aggregate: PurchaseOrder/PurchaseOrderLine/PurchaseOrderReceipt (each PersistableEntity, and each its own Create/Update input contract — no separate Draft type), PurchaseOrderDetail (the header-plus-lines read shape), PurchaseOrderReceiptDraft (the receipt-forwarding wire payload), and PurchaseOrderStatus (the status vocabulary).
• Notifications/ — the four published vendor-master notification shapes (VendorCreated/Updated/Archived/Unarchived), the VendorNotification base + factory, and IVendorNotificationPublication. The type names are the wire contract; the schema is additive-only. Purchase orders publish no notifications.
• Configuration/VendorConfiguration — the host-supplied ViewRole / EditRole role names (../_docs/DECISIONS.md §2).
• Exceptions/ — the domain exceptions the API maps to HTTP status codes, including the purchase-order-specific PurchaseOrderNotFoundException/PurchaseOrderValidationException/PurchaseOrderConflictException.
• ApplicationConstants — shared constants a host/Shell reads.

The write and query entry points (IVendorCommands/IVendorQueries and IPurchaseOrderCommands/ IPurchaseOrderQueries) live in BD.VendorContext.DataAccess, which implements them against B3.CRUD; a host wires that up via DI.

Publishing

Published to nuget.bdcsoft.com by ../azure-pipelines-Core.yml (trigger: master), which mints the date-based version from the pipeline's build number. Never hand-packed — the csproj <Version> is a local-build marker only (BD-BLOCK-SOP §8.3).