Skip to content
This repository was archived by the owner on Apr 8, 2020. It is now read-only.
This repository was archived by the owner on Apr 8, 2020. It is now read-only.

Node process doesn't seem to be released after stopping asp.net core #270

@asadsahi

Description

@asadsahi

I have observed both on windows 7 and windows 10 that if I run asp.net core spa generator multiple times, e.g start debug, stop, start debug, stop every time I run application it starts node instance and doesn't clean itself, which lead to unexpected behavior such as files are locked after asp.net process is stopped and caching old client files by node/webpack. I am not using any other node application and here is what process explorer looks like:

image

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