Skip to content

Avoid windows remote debugging error pop up if possible #319

@andrew-woosnam

Description

@andrew-woosnam

When trying to remotely debug a barebones net6.0 sample web app that was pushed to windows, this error popped up:

image.png

Importantly:

This didn't impact the ability to remotely stop the app at breakpoints in VS, so it might just be noisy at worst

App was initially pushed with this manifest (I think):

version: 1
applications:
- name: WebApplication1
  path: C:\Users\awoosnam\source\repos\WebApplication1\WebApplication1\publish
  stack: windows
  buildpack: binary_buildpack
  command: cmd /c .\WebApplication1 --urls=http://0.0.0.0:%PORT%

Here's the result of cf create-app-manifest WebApplication1:

---
applications:
- name: WebApplication1
  buildpacks:
  - binary_buildpack
  stack: windows
  routes:
  - route: WebApplication1.apps.longbeach.cf-app.com
    protocol: http1
  processes:
  - type: web
    instances: 1
    memory: 1024M
    disk_quota: 1024M
    command: cmd /c .\WebApplication1 --urls=http://0.0.0.0:%PORT%
    health-check-type: port

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions