All-in-one project toolkit for .NET developers - deployment, watch, and debug management
Note: Currently supports IIS Web Deploy (MSDeploy) via
.pubxmlprofiles. Docker and other targets are planned.
- Profile Detection: Scans workspace for
.pubxmlfiles per project. - IIS Deployment: One-click deploy to Staging, Production, or Dev environments.
- Credential Management: Securely encrypted password storage.
- Profile Editor: Direct UI for managing publish profiles.
- Auto Browser Launch: Opens site after successful deployment.
- IIS Log Viewer: Download and view logs from the server.
- Web.config Modifier: Adjust settings during deployment.
- Multi-Project Watch: Run multiple
dotnet watchinstances. - Groups: Manage sets of projects (e.g., "Full Stack") to watch or debug together.
- Status Tracking: Visual indicators for running processes.
- Tracking: Log of all deployments with status and duration.
- Organization: Grouped by date (Today, Yesterday, etc.).
- Download the latest
.vsixfrom Releases. - Open VS Code, press
Ctrl+Shift+P, and run Extensions: Install from VSIX.
- Open Workspace: Open a folder with your .NET projects.
- Access Toolkit: Click the .NET Toolkit icon in the Activity Bar.
- Deploy: Expand a project, find a profile, and click the Deploy (rocket) icon.
The extension organizes profiles hierarchically:
📦 .NET Project Toolkit
├── 📂 Server
│ ├── 🌐 MyApp.Api
│ │ ├── 📄 DEV-API [DEV]
│ │ ├── 📄 STAGING-API [STAGING]
│ │ └── 📄 PROD-API [PROD]
Environment Badges:
- DEV: Development (Green)
- STAGING: Staging (Blue)
- PROD: Production (Red)
Create Profile: Right-click a project -> Create Publish Profile.
- Environments: DEV, STAGING, PROD.
- Log Path: Optional path to IIS stdout logs.
Edit Profile: Click any profile to open the Profile Info Panel.
- Modify URL, credentials, or settings.
- Enable Open in browser or Stdout logging.
Deploy to Staging/Dev: Click the Deploy icon next to the profile.
Deploy to Production: Click Deploy. A confirmation dialog is required for safety.
Process: Build -> Publish -> Deploy (MSDeploy) -> Verify -> Launch Browser.
View IIS stdout logs directly within VS Code:
- Open a publish profile to view the Profile Info Panel.
- Scroll to Deployment Options.
- Ensure Log Path is set (e.g.,
C:\inetpub\logs\LogFiles\W3SVC1). - Click the View Logs button.
- Logs are downloaded and displayed in the Output panel.
- Start: Click Play on a project or group.
- Groups: Click
+to create a group of projects to watch simultaneously.
- Debug: Click Debug icon on a project or group to attach debugger.
- Groups: Create groups to debug microservices together.
View past deployments in the History view.
- Shows status (Success/Failure) and duration.
Settings (Ctrl+, -> search "dotnet toolkit"):
| Setting | Default | Description |
|---|---|---|
dotnetToolkit.passwordStorage |
secret |
Use secret (encrypted) or envvar (environment variables). |
dotnetToolkit.openBrowserOnDeploy |
true |
Open browser after deployment. |
dotnetWorkspace.dotnetPath |
dotnet |
Path to dotnet CLI. |
- Credentials: Stored using OS-secure storage (Credential Manager/Keychain) by default.
- Production Safety: Explicit confirmation required for PROD deployments.
- Project Not Found: Ensure
.csprojbuilds successfully. Refresh the view. - Credentials: If saving fails, check if your OS Keychain is unlocked.
- Logs: If logs are empty, verify the Log Path on the server and ensure the user has read permissions.
Contributions are always welcome!
- Report Bugs: Open an issue to report bugs or request features.
- Submit PRs: Fork the repo, simplify your workflow, and submit a Pull Request.
If you find this extension helpful, consider supporting its development!
Made with ❤️ for .NET developers