There is a validation that checks version attributes on controller request mappings to see if there is a web config around that configures the API versioning (or alternatively config properties). If there is no API versioning configuration found, a problem marker is added to the version validation.
However, when there is a web config in place that gets deleted (the whole file), the validation doesn't re-validate the controller classes in order to add that problem marker.
This is probably an overall missing piece in the validation <-> dependency tracking mechanism and should be investigated to avoid stale diagnostics from showing up.
There is a validation that checks version attributes on controller request mappings to see if there is a web config around that configures the API versioning (or alternatively config properties). If there is no API versioning configuration found, a problem marker is added to the version validation.
However, when there is a web config in place that gets deleted (the whole file), the validation doesn't re-validate the controller classes in order to add that problem marker.
This is probably an overall missing piece in the validation <-> dependency tracking mechanism and should be investigated to avoid stale diagnostics from showing up.