[VSCODE] Need to update to call new dockerized Windows service #4624
Comments
jgw96
added a commit
that referenced
this issue
Jan 23, 2024
fixes #4624 <!-- Link to relevant issue (for ex: "fixes #1234") which will automatically close the issue once the PR is merged --> ## PR Type <!-- Please uncomment one ore more that apply to this PR --> Bugfix <!-- - Feature --> <!-- - Code style update (formatting) --> <!-- - Refactoring (no functional changes, no api changes) --> <!-- - Build or CI related changes --> <!-- - Documentation content changes --> <!-- - Sample app changes --> <!-- - Other... Please describe: --> ## Describe the current behavior? <!-- Please describe the current behavior that is being modified or link to a relevant issue. --> We were calling the old Windows packaging service. ## Describe the new behavior? We are now calling the new Windows service ## PR Checklist - [ x] Test: run `npm run test` and ensure that all tests pass - [ x] Target main branch (or an appropriate release branch if appropriate for a bug fix) - [ x] Ensure that your contribution follows [standard accessibility guidelines](https://docs.microsoft.com/en-us/microsoft-edge/accessibility/design). Use tools like https://webhint.io/ to validate your changes. ## Additional Information
|
This was finished in the above PR |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
We now have our new dockerized Windows service, we should call this instead of the old service for Windows packaging.
What do you expect to happen?
The new Windows service is called
What version of VS Code are you using?
No response
Relevant log output
No response
Are you using the latest version of the VS Code extension?
The text was updated successfully, but these errors were encountered: