wrong/missing sal annotations on consumer oledb macros - by midonet

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 764800 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 9/26/2012 12:12:03 PM
Access Restriction Public


the compiler produces tons of warnings messages for the stuff defined in system header here atldbcli.h

compiled with /W4
Sign in to post a comment.
Posted by Microsoft on 4/29/2014 at 12:32 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 midonet on 4/5/2013 at 2:33 PM
VS2012 Update 2 installed
the error still exists
for each BEGIN_PARAM_MAP as in example below four warnings are generated 28218 28196 6101 6054

class X
int a;
Posted by Microsoft on 2/6/2013 at 5:07 PM
Hi, we have resolved these warnings, you should not see them anymore. These changes should be visible in the next version of Visual Studio.
Posted by Microsoft on 10/2/2012 at 6:18 PM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by Microsoft on 9/26/2012 at 7:51 PM
Thanks for your feedback.

In order to fix the issue, we must first reproduce the issue in our labs. In order to efficiently investigate and reproduce this issue, we are requesting additional information outlined below.

Could you please give us a demo project so that we can conduct further research?

Please submit this information to us within 3 business days. We look forward to hearing from you with this information.

Microsoft Visual Studio Connect Support Team
Posted by Microsoft on 9/26/2012 at 12:52 PM
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)