Visual Studio 2022 warning count exists for a file, yet zero warnings in Error List.

martin_daniel

In Visual Studio 2022 when SQL Prompt extension is enabled I get warnings on an SQL file, yet when I click on the warning icon the Error List is blank.  Warnings are not being filtered out in the Error List, they are missing or the warning icon count is inaccurate. When I disable SQL Prompt there are no warnings.

Dan_J

Hi @martin_daniel

I have now heard back from our development team on this. 

It appears that the linking of warnings from the query window to the VS Error List has not yet been completed/implemented. Unfortunately, given the current very high workload we are unsure when this is likely to be worked on.

Given this, I advise keeping an eye on the release notes of future releases of SQL Prompt should this functionality be implemented - https://documentation.red-gate.com/sp/release-notes-and-other-versions

Dan_J

@martin_daniel,

Thanks for reaching out to us regarding this!

Are you seeing this issue with any syntax you use? Or only for specific syntax?

Also, what version of SQL Prompt are you currently using?

martin_daniel

@Dan_J ,

It seems to be any syntax.  Here is an example.

This code generates the error "Incorrect Syntax near 'GO':

SELECT * FROM 

GO

The second generates a warning "Schema name for procedure is not specified."
Se

The screenshot show the warning is recognized, but when clicked on it brings up the error list with no warnings. (see image below)

SQL Prompt 10.11.9.27382 (Latest Version)
Visual Studio 2022 Version 17.1.5 (Current Release)

Thank you,
Daniel

martin_daniel

Here is a screenshot of when SQL Prompt is disabled:

Dan_J

Hi @martin_daniel

Thanks for the additional information regarding this.

I think I have now been able to reproduce what you are seeing here and so I am going to escalate this to our development team for their input on this. I will come back to you again as soon as have an update.

martin_daniel

@Dan_J

Thanks for the update.  Once I started noticing the same with some errors I figured it may be a future feature that hadn't been implemented yet.

You have a great product with SQL Prompt!