microsoft / microsoft/aspire.dev

Setting up your development environment

Open
#64 2 comments 1 reaction 1 assignee View on GitHub

@IEvangelist is already working on this.

Since Jun 2, 2026.

Dominant language
MDX
Stars
193
Forks
87
Avg merge
1d 22h
Merged PRs (30d)
73

Description

I'm wondering how best to present the various ways that people can set up their development environments with Aspire. On one hand we say just download the CLI in a kind of "come as you are" model - but I wonder if we should provide a more prescriptive approach too for those that need more guidance to set up an optimal model.

As far as VSCode is concerned I think we've got two broad categories of development modes:

  1. Local development; with or without dev containers
  2. Remote development; remote over SSH, remote to Codespaces

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.