Build Requirements
Development Environment
Development Environment
Required:
- Visual Studio 2015 Community Edition or later
- .NET Framework 3.5 or 4.0
- C# 8.0 language features support
- Visual Studio 2019 or 2022 Community Edition
- Windows SDK for target OS version
Target Framework
Target Framework
Seatbelt is built against .NET Framework 3.5 and .NET Framework 4.0 by default.Both versions are compatible with:
- Windows 7 and later
- Windows Server 2008 R2 and later
Language Features
Language Features
Seatbelt uses C# 8.0 features including:
- Nullable reference types
- Pattern matching enhancements
- Using declarations
- Static local functions
Compilation Steps
1
Clone or Download Source
Obtain the Seatbelt source code:
2
Open Solution
Open
Seatbelt.sln in Visual Studio:- Navigate to the project directory
- Double-click
Seatbelt.sln - Or open through Visual Studio: File → Open → Project/Solution
3
Select Configuration
Choose the build configuration:
- Configuration: Select Release (recommended for deployment)
- Platform: Select Any CPU or target architecture (x86/x64)
4
Build Project
Compile the project:
- Menu: Build → Build Solution
- Keyboard:
Ctrl + Shift + B - Command:
dotnet build(if using .NET CLI)
5
Locate Binary
Find the compiled executable:
Build Configurations
Release vs Debug
- Release
- Debug
Recommended for operational useOptimizations:
- Code optimization enabled
- Debug symbols removed
- Smaller binary size
- Better performance
.\Seatbelt\bin\Release\Seatbelt.exeChanging Target Framework
To change the target .NET Framework version:1
Open Project Properties
- Right-click on the Seatbelt project in Solution Explorer
- Select Properties
2
Modify Target Framework
- Navigate to the Application tab
- Under Target framework, select desired version:
- .NET Framework 3.5
- .NET Framework 4.0
- .NET Framework 4.5+
3
Rebuild Project
- Save changes
- Build → Rebuild Solution
Framework Selection Guidance:
- .NET 3.5 - Maximum compatibility with older Windows systems
- .NET 4.0 - Better performance, still broadly compatible
- .NET 4.5+ - Modern features, requires Windows 8+ / Server 2012+
Build from Command Line
Using MSBuild
Using .NET CLI
Build Optimization Options
Performance Optimizations
For operational use, consider these optimizations:Obfuscation Considerations
Customization Before Building
Adding Custom Commands
1
Use Template
Copy the command template:
2
Create Command
Implement your custom command class:
3
Add to Project
- Place in appropriate
.\Seatbelt\Commands\subdirectory - Add file to project in Solution Explorer
- Rebuild project
Modifying Command Groups
Edit command group definitions in the source:Common Build Issues
Missing .NET Framework
Missing .NET Framework
Error: “The target framework version is not supported”Solution:
- Install required .NET Framework Developer Pack
- Or change target framework to installed version
- Download from: https://dotnet.microsoft.com/download/dotnet-framework
C# Language Version Error
C# Language Version Error
Error: “Feature ‘X’ is not available in C# 7.3”Solution:
Update language version in project file:
Missing References
Missing References
Error: “The type or namespace name ‘X’ could not be found”Solution:
- Restore NuGet packages: Right-click solution → Restore NuGet Packages
- Or: Tools → NuGet Package Manager → Restore
Platform Target Warning
Platform Target Warning
Warning: “Platform target warning”Solution:
Set platform target explicitly:
- Project Properties → Build → Platform target → Any CPU
- Or set to x64/x86 as needed
Build Artifacts
After successful compilation:Binary Size:
- Release build: ~400-600 KB
- Debug build: ~800 KB - 1 MB
- Size varies based on .NET version and optimizations
Post-Build Steps
1
Test Build
Verify the executable works:
2
Sign Binary (Optional)
For organizational use, consider code signing:
3
Prepare for Deployment
- Copy executable to deployment location
- Rename if desired for OPSEC
- Document version and build date
Build Scripts
Automated Build Script
Batch Build Script
Troubleshooting
Build Performance
Build Performance
For faster builds:
- Disable parallel builds if experiencing issues
- Use SSD for source code location
- Close unnecessary Visual Studio extensions
- Increase Visual Studio memory allocation
Antivirus Interference
Antivirus Interference
Security software may interfere with compilation:
- Add project directory to AV exclusions
- Temporarily disable real-time protection
- Use Windows Defender exclusions for development folder
Next Steps
Usage Guide
Learn how to use Seatbelt
Command Reference
Explore available commands
Customization
Create custom modules
GitHub Issues
Report build problems