Clarify AyCode.Core usage in docs; add MGGRID.md to solution

Expanded documentation in copilot-instructions.md, CLAUDE.md, and ARCHITECTURE.md to clarify that core framework types are defined in AyCode.Core and should be referenced there. Added a "Related Solutions" section and updated the dependency graph. Included docs\MGGRID.md in the solution items list. Improved guidance for locating and using AyCode.Core types.
This commit is contained in:
Loretta 2026-03-29 10:06:11 +02:00
parent 6cce23a124
commit 52131fdf25
4 changed files with 9 additions and 3 deletions

View File

@ -19,6 +19,10 @@
8. SignalR uses **AcBinaryHubProtocol** (custom binary) — not the default JSON protocol. 8. SignalR uses **AcBinaryHubProtocol** (custom binary) — not the default JSON protocol.
9. Grid filters use **AcExpressionNode** serialization — LINQ expressions are serialized and sent to server. 9. Grid filters use **AcExpressionNode** serialization — LINQ expressions are serialized and sent to server.
## Related Solutions
14. **AyCode.Core** solution (`../AyCode.Core/AyCode.Core.sln`) contains all core framework code (SignalR, serialization, data sources, base classes, interfaces). When a type is referenced in this Blazor solution but not defined here (e.g. `AcSignalRDataSource`, `AcBinaryHubProtocol`, `IId<TId>`, `AcObservableCollection`, `AcLoggerBase`), look it up in AyCode.Core source.
15. For AyCode.Core domain rules see: `../AyCode.Core/.github/copilot-instructions.md`
## Conventions ## Conventions
10. Do not suggest removal/rollback as a solution — find a fix for the problem. 10. Do not suggest removal/rollback as a solution — find a fix for the problem.
11. All DLL references to AyCode.Core projects are via `DllReference` (not ProjectReference) — this is intentional. 11. All DLL references to AyCode.Core projects are via `DllReference` (not ProjectReference) — this is intentional.

View File

@ -1,4 +1,4 @@

Microsoft Visual Studio Solution File, Format Version 12.00 Microsoft Visual Studio Solution File, Format Version 12.00
# Visual Studio Version 17 # Visual Studio Version 17
VisualStudioVersion = 17.7.34024.191 VisualStudioVersion = 17.7.34024.191
@ -28,6 +28,7 @@ Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = "docs", "docs", "{C3A1D7E2-B
docs\ARCHITECTURE.md = docs\ARCHITECTURE.md docs\ARCHITECTURE.md = docs\ARCHITECTURE.md
docs\CONVENTIONS.md = docs\CONVENTIONS.md docs\CONVENTIONS.md = docs\CONVENTIONS.md
docs\GLOSSARY.md = docs\GLOSSARY.md docs\GLOSSARY.md = docs\GLOSSARY.md
docs\MGGRID.md = docs\MGGRID.md
EndProjectSection EndProjectSection
EndProject EndProject
Global Global

View File

@ -5,6 +5,6 @@ Before writing any code, read these files:
2. `docs/GLOSSARY.md` — Blazor/MAUI terminology and DevExpress conventions 2. `docs/GLOSSARY.md` — Blazor/MAUI terminology and DevExpress conventions
3. The relevant project's `README.md` for folder-specific context 3. The relevant project's `README.md` for folder-specific context
This solution depends on **AyCode.Core** — for core framework rules see `../AyCode.Core/CLAUDE.md`. This solution depends on **AyCode.Core** (`../AyCode.Core/AyCode.Core.sln`). When a type is referenced but not defined in this Blazor solution (e.g. `AcSignalRDataSource`, `AcBinaryHubProtocol`, `IId<TId>`, `AcObservableCollection`, `AcLoggerBase`), look it up in AyCode.Core source. For core framework rules see `../AyCode.Core/CLAUDE.md`.
When modifying code, update the corresponding README.md if it becomes out of sync with the code. When modifying code, update the corresponding README.md if it becomes out of sync with the code.

View File

@ -3,7 +3,7 @@
## Dependency Graph ## Dependency Graph
``` ```
AyCode.Core Solution (DLL references) AyCode.Core Solution ../AyCode.Core/AyCode.Core.sln (DLL references)
AyCode.Blazor.Models ← AyCode.Blazor.Models.Server AyCode.Blazor.Models ← AyCode.Blazor.Models.Server
@ -13,6 +13,7 @@ AyCode.Maui.Core (MAUI Hybrid host)
``` ```
**Rule:** UI projects reference AyCode.Core via DLL (not ProjectReference). This separates build graphs. **Rule:** UI projects reference AyCode.Core via DLL (not ProjectReference). This separates build graphs.
**Context:** When a core type is not found in this solution, browse `../AyCode.Core/` for its definition.
## How It Works ## How It Works