A family of Microsoft suites of integrated development tools for building applications for Windows, the web, mobile devices and many other platforms. Miscellaneous topics that do not fit into specific categories.
Hi @Rod Falanga
Confusing setup, but those two errors point at two separate, fixable things. And the second VS Code window is normal: when the template creates a new project, VS Code opens it in its own window. You can close the Welcome one.
ASPIRE009 just means the newer Aspire template expects the Aspire CLI to be installed, and it isn't on your machine yet.
- Open a PowerShell window and run:
irm https://aspire.dev/install.ps1 | iex - Close and reopen your terminal (and VS Code) so the PATH change is picked up.
- Run
aspire --version. You should see a 13.x version number.
MSB4240 is coming from a different project. The message shows an SDK version being resolved from your Pluralsight CarvedRock.AppHost folder. That project pins Aspire 13.4.6, the new starter wants 13.6.1, and the same build process has loaded both, so they clash.
- In VS Code, use File > Close Folder (or Close Workspace) so the Pluralsight folder isn't loaded.
- Use File > Open Folder and open only
Downloads\aspire-starter. - If the error still shows, run
dotnet build-server shutdownin a terminal, then reopen VS Code. - Run the AppHost again.
If you want to go back to the Pluralsight course later, open that folder on its own in a separate window rather than in the same workspace.
After installing the CLI and opening only the starter folder, does aspire run from the starter folder start the dashboard?
If this resolved your issue, please consider accepting it as the answer. If either error is still there after that, let me know and I'll be happy to keep helping.
Reference: