Automated builds of the Visual Studio extension
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 7.8k
- Forks
- 1.2k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 49
Description
Is your feature request related to a problem? Please describe.
Currently Visual Studio extension only supports VS2019. The changes to support VS2022 are in the repo already but weren't released yet. In order to get the latest version I need to clone the whole Stride repo and build it myself, which is not convenient.
Describe the solution you'd like
A GitHub Actions (or other automation platform) workflow to compile the extension automatically on push. The resulting vsix would be then available via run artifacts. Here's how I set it up for my project, also see nightly.link for convenient artifact downloads.
Describe alternatives you've considered
- Manually compiling the stuff: inconvenient because I need to check out quite a big repo, install dependencies etc.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the repository's existing Visual Studio extension build setup and the linked Phobos nightly GitHub Actions workflow. The work is complete when pushes automatically compile the extension and expose the resulting VSIX as downloadable run artifacts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, github-actions
- Domain
- build-system, ci-cd, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100