Skip to main content

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

The extension only activates when it detects .NET-related files.Activation Triggers:
  • Source files: *.cs, *.fs, *.vb
  • Project files: *.csproj, *.fsproj, *.vbproj
  • Solution files: *.sln
Verify:
# Check if you have any .NET files
ls -la **/*.cs
ls -la **/*.csproj
Fix: Create at least one .NET file in your workspace:
touch Program.cs
1

Open Extensions Panel

Press Ctrl+Shift+X to open Extensions.
2

Search for Extension

Search for “DotNET Build Buddy” and verify:
  • Extension is installed
  • Extension is enabled (not disabled)
  • No error icon appears
3

Enable if Disabled

If disabled, click the Enable button.
The extension requires VS Code 1.74.0 or higher.Check Version:
  1. Help → About
  2. Look for version number
Fix: Update VS Code if needed:
1

Open Output Panel

Press Ctrl+Shift+U to open Output.
2

Select Extension Output

In the dropdown, select “DotNET Build Buddy”.
3

Look for Messages

Check for:
  • “DotNET Build Buddy extension is now active!” (success)
  • Error messages (failures)
  • Stack traces (crashes)
Sometimes a simple reload fixes activation issues.Methods:
  • Press Ctrl+R (Windows/Linux) or Cmd+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

Verify auto-update is enabled:Settings (Ctrl+,):
{
  "dotnetBuildBuddy.autoUpdate": true
}
If Disabled:
  • Set to true to enable
  • Or use manual update commands
Check that your file types are included in watch patterns:Default Patterns:
{
  "dotnetBuildBuddy.watchPatterns": [
    "**/*.cs",
    "**/*.fs",
    "**/*.vb"
  ]
}
For Custom Extensions: Add your patterns:
{
  "dotnetBuildBuddy.watchPatterns": [
    "**/*.cs",
    "**/*.fs",
    "**/*.vb",
    "src/**/*.cs"  // Add custom pattern
  ]
}
Files in excluded directories won’t be detected.Default Exclusions:
{
  "dotnetBuildBuddy.excludePatterns": [
    "**/bin/**",
    "**/obj/**",
    "**/node_modules/**"
  ]
}
Check File Location:
# Is your file in an excluded directory?
pwd
# Should NOT be in bin/, obj/, or node_modules/
Force an immediate update:
1

Open Command Palette

Press Ctrl+Shift+P
2

Run Update Command

Type and select: “DotNET Build Buddy: Update Project Files”
3

Check Output

Watch Output panel for success or error messages.
Files must be in the workspace root or subdirectories.Check:
  • 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 .vbproj files created
  • Commands complete but files don’t appear
  • “Project files updated successfully” but nothing changes

Solutions

The extension needs write permissions to create files.On Windows:
  • Check folder isn’t read-only
  • May need to run VS Code as administrator
On Linux/Mac:
# Check permissions
ls -la

# Fix if needed
chmod u+w .
The extension needs source files to generate projects.Check:
# Do you have source files?
ls -la **/*.cs
ls -la **/*.fs
ls -la **/*.vb
Fix: Create at least one source file:
mkdir MyProject
echo 'class Program { }' > MyProject/Program.cs
1

Open Output Panel

Ctrl+Shift+U → Select “DotNET Build Buddy”
2

Look for Errors

Common errors:
  • Permission denied (see permissions fix above)
  • Path not found (check workspace folder)
  • ENOENT errors (directory doesn’t exist)
3

Fix Based on Error

Follow error message guidance or create missing directories.
Project files are created in directories containing source files.Expected Structure:
MyWorkspace/
├── Program.cs           ← Extension creates MyWorkspace.csproj HERE
├── Services/
│   └── MyService.cs     ← Extension creates Services.csproj HERE
Not in:
  • bin/ directories
  • obj/ 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

Verify the feature is enabled:
settings.json
{
  // Master switch
  "dotnetBuildBuddy.nugetCheckEnabled": true,
  
  // API lookups (recommended)
  "dotnetBuildBuddy.nugetApiEnabled": true
}
Both must be true for full functionality.
Diagnostics only appear for actual packages in project files.Check:
MyProject.csproj
<ItemGroup>
  <!-- You need PackageReference entries -->
  <PackageReference Include="SomePackage" Version="1.0.0" />
</ItemGroup>
If Missing: Add package references to test:
<PackageReference Include="EntityFramework" Version="6.4.4" />
1

Verify Internet Connection

The extension queries NuGet.org API. Check your connection:
curl https://api.nuget.org/v3/index.json
2

Check API Timeout

Increase timeout if connection is slow:
{
  "dotnetBuildBuddy.nugetApiTimeout": 10000
}
3

Check Proxy Settings

If behind a proxy, configure VS Code proxy settings.
Clear cached compatibility results:Temporary Disable:
{
  "dotnetBuildBuddy.nugetCacheEnabled": false
}
Or Reload Window: Ctrl+R clears in-memory cache.
Packages in ignore list are skipped.Review:
{
  "dotnetBuildBuddy.nugetIgnoredPackages": [
    // Remove entries you want checked
  ]
}

Inline Diagnostics Not Appearing

Symptoms

  • No squiggly lines under packages
  • Tooltips not showing
  • Hover reveals nothing

Solutions

Diagnostics only appear when the project file is open.
1

Open File

Open your .csproj, .fsproj, or .vbproj in VS Code editor.
2

Wait for Analysis

Extension analyzes on file open. Wait a few seconds.
3

Check Squiggles

Look for red/yellow lines under <PackageReference Include="...">.
Even without inline squiggles, issues appear in Problems panel.
1

Open Problems Panel

Press Ctrl+Shift+M
2

Filter by Source

Look for issues with source “DotNET Build Buddy”
3

Click Issue

Click an issue to navigate to the source line
Diagnostics sometimes need a refresh.Reload: Press Ctrl+R or Command Palette → “Developer: Reload Window”
The package may actually be compatible.Test:
  1. Try a known incompatible package:
    <PackageReference Include="EntityFramework" Version="6.4.4" />
    
    (incompatible with net8.0)
  2. Set target framework:
    <TargetFramework>net8.0</TargetFramework>
    
  3. 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

Caching significantly improves performance:
settings.json
{
  "dotnetBuildBuddy.nugetCacheEnabled": true,
  "dotnetBuildBuddy.nugetCacheExpiry": 86400  // 24 hours
}
Local rules are faster than API lookups:
{
  "dotnetBuildBuddy.nugetApiEnabled": false
}
Trade-off: Less accurate, but much faster and works offline.
Reduce timeouts that cause retries:
{
  "dotnetBuildBuddy.nugetApiTimeout": 10000  // 10 seconds
}
Manual updates reduce background processing:
{
  "dotnetBuildBuddy.autoUpdate": false
}
Update manually when needed using commands.
Limit watched files in large workspaces:
{
  "dotnetBuildBuddy.watchPatterns": [
    "src/**/*.cs"  // Only watch src directory
  ],
  "dotnetBuildBuddy.excludePatterns": [
    "**/bin/**",
    "**/obj/**",
    "**/tests/**",     // Exclude tests
    "**/samples/**"    // Exclude samples
  ]
}

False Compatibility Warnings

Symptoms

  • Package marked as incompatible but builds fine
  • Incorrect suggestions
  • Wrong version recommendations

Solutions

Test actual compatibility:
dotnet restore
dotnet build
dotnet run
If it works, it’s a false positive.
Visit the package page to verify supported frameworks:
  1. Go to nuget.org
  2. Search for package
  3. Check “Frameworks” section
  4. Compare with your target framework
Suppress false positives:
settings.json
{
  "dotnetBuildBuddy.nugetIgnoredPackages": [
    "ProblematicPackage",
    "Internal.*"  // Wildcard patterns supported
  ]
}
Ensure project file has correct <TargetFramework>:
<PropertyGroup>
  <TargetFramework>net8.0</TargetFramework>
  <!-- Check this matches your intent -->
</PropertyGroup>
If rule is incorrect, report it:
  1. Go to GitHub Issues
  2. Search for existing reports
  3. 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

Solution needs project files to reference.Check:
find . -name "*.csproj"
find . -name "*.fsproj"
find . -name "*.vbproj"
Fix: Generate/update projects first:
Ctrl+Shift+P → "DotNET Build Buddy: Update Project Files"
Project files must be accessible from workspace root.Check paths in .sln:
Project("{GUID}") = "MyProject", "MyProject/MyProject.csproj", "{GUID}"
Relative paths must be correct.
Force solution regeneration:
1

Delete Existing Solution

rm Solution.sln
2

Generate New

Ctrl+Shift+P → “DotNET Build Buddy: Generate Solution File”
3

Check Output

Review Output panel for errors.
Ensure write permissions on workspace root:
# Linux/Mac
ls -la Solution.sln
chmod u+w Solution.sln

# Windows: Check file properties → uncheck Read-only

Configuration Not Applied

Symptoms

  • Settings changes not taking effect
  • Extension ignoring configuration
  • Defaults still in use

Solutions

Invalid JSON silently fails.Check:
  1. Open settings.json: Ctrl+, → click {}icon (top right)
  2. Look for syntax errors (red squiggles)
  3. Fix issues:
    • Missing commas
    • Extra commas
    • Unclosed quotes
    • Unclosed braces
User vs Workspace settings:
  • User settings: Apply globally
  • Workspace settings: Override user settings
Check both:
  1. Ctrl+, → User tab
  2. Ctrl+, → Workspace tab
Workspace settings take precedence.
Configuration changes may require reload:After changing settings:
  • Press Ctrl+R
  • Or: Command Palette → “Developer: Reload Window”
Settings must start with dotnetBuildBuddy.Correct:
{
  "dotnetBuildBuddy.autoUpdate": true
}
Incorrect:
{
  "autoUpdate": true  // Missing prefix
}

Debugging

Enable Detailed Logging

1

Open Developer Console

Press Ctrl+Shift+I (Windows/Linux) or Cmd+Option+I (Mac)
2

Switch to Console Tab

Click the Console tab
3

Filter Messages

In filter box, type: DotNET Build Buddy
4

Reproduce Issue

Perform the action that causes the issue and watch console output

Output Panel Logs

1

Open Output Panel

Ctrl+Shift+U or View → Output
2

Select Extension Output

Dropdown → “DotNET Build Buddy”
3

Review Messages

Look for:
  • Activation messages
  • File detection messages
  • Error messages
  • API call results
  • Compatibility check results

Check Extension Status

1

Open Extensions Panel

Ctrl+Shift+X
2

Find Extension

Search for “DotNET Build Buddy”
3

Review Details

Check:
  • Enabled/Disabled status
  • Version number
  • Error icons
  • Extension details

Recovery Procedures

Reset Extension

1

Reload Window

Ctrl+R or Command Palette → “Developer: Reload Window”
2

If That Fails: Disable/Enable

Extensions panel → DotNET Build Buddy → Disable → Enable
3

If That Fails: Uninstall/Reinstall

  1. Extensions panel → DotNET Build Buddy → Uninstall
  2. Restart VS Code
  3. Extensions panel → Search “DotNET Build Buddy” → Install
4

Clear Cache (Advanced)

Delete extension cache directory (varies by OS):Windows: %APPDATA%\Code\User\workspaceStorage\Mac: ~/Library/Application Support/Code/User/workspaceStorage/Linux: ~/.config/Code/User/workspaceStorage/

Restore Project Files

1

Use Version Control

If using Git:
git diff *.csproj
git checkout -- *.csproj  # Revert if needed
2

Regenerate Files

Delete corrupted files and regenerate:
rm *.csproj Solution.sln
Then: Ctrl+Shift+P → “DotNET Build Buddy: Refresh All .NET Files”
3

Manual Recreation

Create project files manually, then let extension update them:
MyProject.csproj
<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <TargetFramework>net8.0</TargetFramework>
  </PropertyGroup>
</Project>

Getting Help

Before Reporting Issues

Reporting Issues

When creating a GitHub issue, include:
1

Environment Information

  • VS Code version (Help → About)
  • Extension version (Extensions panel → DotNET Build Buddy)
  • Operating system
  • Workspace structure (tree command or screenshot)
2

Steps to Reproduce

  1. Clear steps to reproduce issue
  2. Expected behavior
  3. Actual behavior
3

Logs and Output

  • Output panel logs (copy text)
  • Developer Console errors (screenshot)
  • Relevant project files (sanitize sensitive data)
4

Configuration

Your settings (remove sensitive data):
{
  "dotnetBuildBuddy.autoUpdate": true,
  // ... other settings
}

Community Support

Prevention Best Practices

Keep Extension Updated

Regularly update to latest version for bug fixes and improvements.

Review Configuration

Periodically review settings to ensure they match your needs.

Monitor Logs

Check Output panel occasionally for warnings or errors.

Use Version Control

Always use Git or other VCS to track changes to generated files.

Test After Updates

Test extension after VS Code updates to verify compatibility.

Backup Before Changes

Backup project files before major workspace reorganizations.

Quick Reference

Common Commands

CommandShortcutDescription
Command PaletteCtrl+Shift+PAccess all commands
Output PanelCtrl+Shift+UView extension logs
Problems PanelCtrl+Shift+MView diagnostics
Developer ConsoleCtrl+Shift+IDebug extension
Reload WindowCtrl+RRestart extension
SettingsCtrl+,Configure extension

Important Settings

settings.json
{
  // Core functionality
  "dotnetBuildBuddy.autoUpdate": true,
  
  // NuGet compatibility
  "dotnetBuildBuddy.nugetCheckEnabled": true,
  "dotnetBuildBuddy.nugetApiEnabled": true,
  "dotnetBuildBuddy.nugetCacheEnabled": true,
  
  // Performance
  "dotnetBuildBuddy.nugetApiTimeout": 5000,
  "dotnetBuildBuddy.nugetCacheExpiry": 3600,
  
  // Ignored packages
  "dotnetBuildBuddy.nugetIgnoredPackages": []
}

Log Locations

TypeLocation
Output PanelCtrl+Shift+U → “DotNET Build Buddy”
Developer ConsoleCtrl+Shift+I → Console tab
VS Code LogsHelp → Toggle Developer Tools → Console

Still Having Issues?

If you’ve tried everything in this guide and still experiencing problems:
  1. Search existing issues: GitHub Issues
  2. Create detailed bug report: Include all information from “Reporting Issues” section
  3. Be patient: Maintainers respond as quickly as possible
Most issues can be resolved by:
  1. Reloading window (Ctrl+R)
  2. Verifying settings are correct
  3. Checking Output panel for errors

Build docs developers (and LLMs) love