Home Dashboard Directory Help
Search

Transact-sql and code analysis "warning as error" are not managed separately by ShadoFil


Status: 

Active


2
0
Sign in
to vote
Type: Bug
ID: 793655
Opened: 7/12/2013 6:48:03 AM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

In a database projet, if I set "warning as error" as true in Build properties and set "warning as error" as false in code analysis, all code analysis warning are displayed as errors and not as warnings at the end of build.

So, it is impossible to see the real errors which fail the build and we think the build has failed, but not !
Details
Sign in to post a comment.
Posted by Microsoft on 4/29/2014 at 12:31 PM
Thank you for reporting this issue. This issue has been fixed in Visual Studio 2013. You can install a trial version of Visual Studio 2013 with the fix from: http://go.microsoft.com/?linkid=9832436
Posted by ShadoFil on 9/16/2013 at 5:31 AM
Ok, thanks.
Posted by Microsoft on 9/11/2013 at 8:18 AM
Sure enough the fix didn't make it out. I'll remove that from the list of bugs fixed for August. I expect this bug will go out in our October/November release. thanks!
Posted by Microsoft on 9/10/2013 at 11:14 AM
thanks for letting us know. I'll check this out.
Posted by ShadoFil on 9/10/2013 at 7:08 AM
This bogue is not fixed in SSDT August 2013 ! Instead of, a code analysis warning is always treated as an error !
Posted by Microsoft on 7/15/2013 at 1:23 AM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Microsoft on 7/12/2013 at 6:51 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.