Common Issues
This guide covers the most common issues users encounter and how to resolve them.Extension Not Activating
Symptoms
- Extension doesn’t activate when opening workspace
- No activation notification appears
- Commands not available in Command Palette
- No “DotNET Build Buddy” in Output panel
Solutions
Check Workspace Contains .NET Files
Check Workspace Contains .NET Files
- Source files:
*.cs,*.fs,*.vb - Project files:
*.csproj,*.fsproj,*.vbproj - Solution files:
*.sln
Verify Extension is Installed and Enabled
Verify Extension is Installed and Enabled
Check VS Code Version
Check VS Code Version
- Help → About
- Look for version number
- Help → Check for Updates
- Or download from code.visualstudio.com
Review Output Panel
Review Output Panel
Reload Window
Reload Window
- Press
Ctrl+R(Windows/Linux) orCmd+R(Mac) - Command Palette → “Developer: Reload Window”
- Close and reopen VS Code
Files Not Being Detected
Symptoms
- New files not added to project files automatically
- Project files not updating when files change
- File changes not triggering updates
Solutions
Check Auto-Update Setting
Check Auto-Update Setting
Ctrl+,):- Set to
trueto enable - Or use manual update commands
Verify Watch Patterns
Verify Watch Patterns
Check Exclude Patterns
Check Exclude Patterns
Manual Update
Manual Update
Verify Workspace Folder
Verify Workspace Folder
- File → Open Folder (not “Open File”)
- Verify correct folder is opened
- Check Explorer panel shows workspace root
Project Files Not Generated
Symptoms
- No
.csproj,.fsproj, or.vbprojfiles created - Commands complete but files don’t appear
- “Project files updated successfully” but nothing changes
Solutions
Check File Permissions
Check File Permissions
- Check folder isn’t read-only
- May need to run VS Code as administrator
Verify Source Files Exist
Verify Source Files Exist
Check Output for Errors
Check Output for Errors
Verify Directory Structure
Verify Directory Structure
bin/directoriesobj/directories- Excluded patterns
NuGet Compatibility Not Working
Symptoms
- No compatibility warnings appear
- Inline diagnostics not showing
- No squiggly lines under packages
- Problems panel empty
Solutions
Enable Compatibility Checking
Enable Compatibility Checking
true for full functionality.Verify Package References Exist
Verify Package References Exist
Check API Integration
Check API Integration
Clear Cache
Clear Cache
Ctrl+R clears in-memory cache.Check Ignore List
Check Ignore List
Inline Diagnostics Not Appearing
Symptoms
- No squiggly lines under packages
- Tooltips not showing
- Hover reveals nothing
Solutions
Open Project File in Editor
Open Project File in Editor
Check Problems Panel
Check Problems Panel
Reload Window
Reload Window
Ctrl+R or Command Palette → “Developer: Reload Window”Verify Issues Actually Exist
Verify Issues Actually Exist
-
Try a known incompatible package:
(incompatible with
net8.0) -
Set target framework:
- Save file and check for red squiggle
Performance Issues
Symptoms
- Slow response to file changes
- Lag when opening project files
- High CPU usage
- Extension delays
Solutions
Enable Caching
Enable Caching
Disable API if Not Needed
Disable API if Not Needed
Increase API Timeout
Increase API Timeout
Disable Auto-Update
Disable Auto-Update
Reduce Watch Patterns
Reduce Watch Patterns
False Compatibility Warnings
Symptoms
- Package marked as incompatible but builds fine
- Incorrect suggestions
- Wrong version recommendations
Solutions
Verify in Real Build
Verify in Real Build
Check NuGet.org
Check NuGet.org
- Go to nuget.org
- Search for package
- Check “Frameworks” section
- Compare with your target framework
Add to Ignore List
Add to Ignore List
Verify Target Framework
Verify Target Framework
<TargetFramework>:Report Issue
Report Issue
- Go to GitHub Issues
- Search for existing reports
- Create new issue with:
- Package name and version
- Target framework
- Evidence it works (build logs)
- Extension version
Solution File Issues
Symptoms
- Solution file not generated
- Projects not included
- GUID errors
- Solution won’t open in Visual Studio
Solutions
Ensure Projects Exist
Ensure Projects Exist
Verify Project Paths
Verify Project Paths
.sln:Manual Generation
Manual Generation
Check Permissions
Check Permissions
Configuration Not Applied
Symptoms
- Settings changes not taking effect
- Extension ignoring configuration
- Defaults still in use
Solutions
Verify JSON Syntax
Verify JSON Syntax
- Open
settings.json:Ctrl+,→ click{}icon (top right) - Look for syntax errors (red squiggles)
- Fix issues:
- Missing commas
- Extra commas
- Unclosed quotes
- Unclosed braces
Check Setting Scope
Check Setting Scope
- User settings: Apply globally
- Workspace settings: Override user settings
Ctrl+,→ User tabCtrl+,→ Workspace tab
Reload Window
Reload Window
- Press
Ctrl+R - Or: Command Palette → “Developer: Reload Window”
Verify Setting Names
Verify Setting Names
dotnetBuildBuddy.Correct:Debugging
Enable Detailed Logging
Output Panel Logs
Check Extension Status
Recovery Procedures
Reset Extension
If That Fails: Uninstall/Reinstall
- Extensions panel → DotNET Build Buddy → Uninstall
- Restart VS Code
- Extensions panel → Search “DotNET Build Buddy” → Install
Restore Project Files
Regenerate Files
Ctrl+Shift+P → “DotNET Build Buddy: Refresh All .NET Files”Getting Help
Before Reporting Issues
Reporting Issues
When creating a GitHub issue, include:Environment Information
- VS Code version (Help → About)
- Extension version (Extensions panel → DotNET Build Buddy)
- Operating system
- Workspace structure (tree command or screenshot)
Logs and Output
- Output panel logs (copy text)
- Developer Console errors (screenshot)
- Relevant project files (sanitize sensitive data)
Community Support
- GitHub Issues: github.com/MilesONerd/DotNET-Build-Buddy/issues
- GitHub Discussions: Check for discussions and Q&A
- Documentation: Review all documentation first
Prevention Best Practices
Keep Extension Updated
Review Configuration
Monitor Logs
Use Version Control
Test After Updates
Backup Before Changes
Quick Reference
Common Commands
| Command | Shortcut | Description |
|---|---|---|
| Command Palette | Ctrl+Shift+P | Access all commands |
| Output Panel | Ctrl+Shift+U | View extension logs |
| Problems Panel | Ctrl+Shift+M | View diagnostics |
| Developer Console | Ctrl+Shift+I | Debug extension |
| Reload Window | Ctrl+R | Restart extension |
| Settings | Ctrl+, | Configure extension |
Important Settings
Log Locations
| Type | Location |
|---|---|
| Output Panel | Ctrl+Shift+U → “DotNET Build Buddy” |
| Developer Console | Ctrl+Shift+I → Console tab |
| VS Code Logs | Help → Toggle Developer Tools → Console |
Still Having Issues?
If you’ve tried everything in this guide and still experiencing problems:- Search existing issues: GitHub Issues
- Create detailed bug report: Include all information from “Reporting Issues” section
- Be patient: Maintainers respond as quickly as possible
- Reloading window (
Ctrl+R) - Verifying settings are correct
- Checking Output panel for errors