C# build errors: causes and fixes
All 22 RF codes: causes, complete fixes and reproducible build errors for SDK 1.0.0.
Reckfell.NET.Sdk 1.0.0 analyzer errors: find the exact code from the build output. Each article gives the cause and complete corrected files.
Fix a build
- Read the first
dotnet builderror: its code, file and line. - Find the code below. Fix your declaration using the working version as a reference.
- Build again. Do not copy both failing and corrected declarations into the project.
- CSxxxx and NUxxxx belong to other diagnostic groups: keep the full message and check syntax, the SDK and package restore.
Diagnostic codes
| Code | What to fix |
|---|---|
| RF0001 | Script class needs partial |
| RF0002 | Containing class needs partial |
| RF0003 | Two script classes use one path |
| RF0101 | Export does not support static |
| RF0102 | Exported type is unsupported |
| RF0103 | Exported value is read-only |
| RF0104 | Exported property needs a getter |
| RF0105 | An indexer cannot be exported |
| RF0106 | Explicit interface implementation cannot be exported |
| RF0107 | Entity references belong on Entity components |
| RF0108 | Inspector button needs a Tool class |
| RF0109 | Do not combine Export and ExportToolButton |
| RF0110 | Inspector button must return Callable |
| RF0111 | Button getter must create a Callable |
| RF0201 | Signal delegate name must end in EventHandler |
| RF0202 | Signal parameter is not Variant-compatible |
| RF0203 | Signal delegate must return void |
| RF0301 | Generic type argument is not Variant-compatible |
| RF0302 | Generic parameter needs MustBeVariant |
| RF0303 | Analyzer could not handle the type-argument context |
| RF0401 | GlobalClass requires ReckfellObject inheritance |
| RF0402 | GlobalClass must not be generic |
When one fix is not enough
One member may violate several rules. For example, Export combined with ExportToolButton produces RF0109, while a read-only property may also produce RF0103. Fix the cause rather than hiding diagnostics with NoWarn. An RF0303 trigger has not yet been confirmed; its page provides a concrete workaround and the information to retain for investigation.
Reckfell Engine documentationBack to top ↑