NcfPackageSources Beginner Quickstart (60 Minutes)
Scope: current
NcfPackageSourcesversion
Documentation baseline:NcfPackageSourcesHEAD = 631f16b4(2026-06-17)
1. What You Will Finish With This Guide
If this is your first time touching NCF source code, this guide gets you from zero to usable in about 60 minutes:
- Clone and build
NcfPackageSources. - Run the simulated host site
Senparc.Web. - Complete first-time installation, admin login, and module enablement.
- Validate a minimum AI / RAG flow.
- Know where to troubleshoot first when errors appear.
2. Prerequisites Checklist
| Item | Requirement | How to Verify |
|---|---|---|
| OS | Windows / macOS / Linux | - |
| .NET SDK | Recommended 8.0 (aligned with the current version) | dotnet --version |
| Git | Able to clone repositories | git --version |
| Browser | Chrome / Edge / Safari | - |
| Local port | 5001 (HTTPS) is available | Check Now listening on in startup logs |
| Database | Start with default SQLite | No extra install needed |
If your environment is not ready yet:
3. Minute 0-10: Clone and Confirm Commit
git clone https://github.com/NeuCharFramework/NcfPackageSources.git
cd NcfPackageSources
git rev-parse --short HEADExpected result:
- A short SHA is printed (for example
631f16b4).
4. Minute 10-20: Restore and Build
dotnet restore src/NcfPackageSources_Include_NcfSimulatedSite.sln
dotnet build src/NcfPackageSources_Include_NcfSimulatedSite.slnExpected result:
restorecompletes without blocking errors.buildends withBuild succeeded..
5. Minute 20-30: Run the Simulated Host Site
dotnet run --project tools/NcfSimulatedSite/Senparc.Web/Senparc.Web.csprojExpected result:
- Logs include
Now listening on. - Usually includes
https://localhost:5001.
Then open: https://localhost:5001
On first run, seeing the installer is expected.
6. Minute 30-40: Complete Installer and Admin Login
Recommended order:
- Finish the installer wizard. Reference: Installation
- Sign in as administrator. Reference: Admin Login
- Open admin backend and verify left menu loads. Reference: Admin Backend
Expected result:
- You can enter the admin homepage.
- Module management is accessible.
7. Minute 40-50: Enable Minimum AI / RAG Module Set
In Module Management, install and enable these modules first:
Senparc.Xncf.AIKernelSenparc.Xncf.PromptRangeSenparc.Xncf.AgentsManagerSenparc.Xncf.KnowledgeBase
Optional:
Senparc.Xncf.MCP(if you also want to validate MCP routing)
Reference: Module Management
Expected result:
- Module status shows installed/enabled (or equivalent labels).
- Corresponding admin menu entries are visible and openable.
8. Minute 50-60: Run a Minimum End-to-End Validation
Use the smallest possible action chain:
- Configure available models in
AIKernel(at least one chat model, preferably one embedding model too). - Create one PromptCode in
PromptRange. - Import a test document in
KnowledgeBaseand run embedding. - Run recall test in
KnowledgeBaseand confirm matched chunks are returned. - (Optional) Create an Agent template in
AgentsManagerthat references PromptCode and run a test.
Expected result:
- Embedding task completes.
- Recall test returns valid chunks.
- Agent test no longer fails with “model not configured”.
9. Troubleshooting Matrix (Check This First)
| Symptom | Common Cause | Fix |
|---|---|---|
dotnet command not found | SDK missing or PATH not refreshed | Install/repair .NET SDK, reopen terminal, run dotnet --info |
restore fails (timeout/source unavailable) | Network or NuGet feed issue | Verify network, retry dotnet restore, switch NuGet source if needed |
build fails (SDK mismatch) | Local SDK is too old | Upgrade to .NET 8 SDK, rerun dotnet build |
| Startup port conflict | 5001 already used | Change port in tools/NcfSimulatedSite/Senparc.Web/Properties/launchSettings.json |
| Installer page keeps showing | Initial install not finished or DB init failed | Redo installer flow and inspect startup logs |
| Module menu not visible after install | Module not enabled or insufficient permission | Recheck module state and admin role permissions |
| Function count is 0 | Missing [FunctionRender] or scan miss | Check AppService annotations and restart app |
| MCP route returns 404 | EnableMcpServer disabled or not registered | Check module Register config and startup registration path |
| AppService returns 401/403 | Auth policy not satisfied | Check login state, AdminOnly policy, Bearer/Cookie auth context |
| KnowledgeBase embedding fails | Embedding model not configured | Configure embedding model in AIKernel first |
10. Troubleshooting Priority (Use This Order)
- Module state: verify installed + enabled first.
- Function / MCP registration: then verify scan registration results.
- Auth and logs: only then inspect 401/403, policy, and runtime logs.
Following this order avoids getting lost in low-value log details.
11. Common Beginner Mistakes
Mistake 1: using
IXncfRegister.Functionsto understand Function registration.
Current mechanism is[FunctionRender]onAppServicemethods.Mistake 2: treating “installed” as “ready”.
You usually still need enablement, permissions, and configuration.Mistake 3: jumping into logs first.
Without checking module state and config, logs become noisy and misleading.Mistake 4: assuming AI errors are code bugs first.
In many cases the root cause is model/key/quota/network configuration.
12. Next-Step Roadmap (By Role)
Beginner: NcfPackageSources Overview -> NCF Capability Deep Dive -> NCF FAQ
Module developer: XNCF Overview -> Develop XNCF -> Core Interface IXncfRegister
AI application developer: NCF Capability Deep Dive -> MCP Module Docs (currently under zh docs) -> module pages for
AIKernel / PromptRange / AgentsManager / KnowledgeBaseOperations / release engineer: DatabasePlant Docs -> Windows Deployment / Docker Deployment
13. Open-Source Collaboration Entry Points
Framework-level issues (template/install/upgrade): use
NCFIssues first.
https://github.com/NeuCharFramework/NCF/issuesCore package source issues (base libs/module register/runtime behavior): use
NcfPackageSourcesIssues/PRs.
https://github.com/NeuCharFramework/NcfPackageSources/issues
Question-asking tips that dramatically improve response speed:
- Include commit SHA (or release tag).
- Include minimum reproducible steps (3-8 steps).
- Include key logs (after desensitization).
- State expected result vs actual result clearly.