error #3291 in atlcomcli.h - by Nian Wu

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<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 790349 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 6/17/2013 9:54:28 PM
Access Restriction Public


I met below error when compile my file:

C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\atlmfc\include\atlcomcli.h(525): error #3291: invalid narrowing conversion from "int" to "unsigned int"

          DISPPARAMS dispparams = { pvarParams, NULL, nParams, 0}; 

After modify the VS2012 file atlcomcli.h Line 525 to:

          DISPPARAMS dispparams = { pvarParams, NULL, (UINT)nParams, 0}; 

The problem is gone.

DISPPARAMS is a typedef to tagDISPPARAMS which is defined in “ c:\Program Files (x86)\Windows Kits\8.0\Include\um\OAIdl.h”. Its third member is type of UINT.
Sign in to post a comment.
Posted by Ion [MSFT] on 6/27/2013 at 4:01 PM
Sorry, upon further consideration, this currently does not meet the bar for Dev12. It is postponed for Dev13. Dev12 is Visual Studio 2013.
Posted by Nian Wu on 6/26/2013 at 11:05 PM
What's the version Dev12? Is it Visual Studio 2012 or 2014?
Posted by Nian Wu on 6/26/2013 at 8:19 PM
Yes, the error is reported by Intel compiler (Intel 2013 SP1).
Posted by Ion [MSFT] on 6/24/2013 at 11:54 PM
Hi Nian, thanks for reporting this bug. I'll fix it for Dev12. But please note that the warning/error you are seeing is not generated by one of our tools (ours is C4365), so it is probably generated by one of yours. As such, I cannot provide a workaround for you.
Posted by Nian Wu on 6/21/2013 at 2:16 AM
I worked on a very large project. It is hard to separate the problem.

Most time the problem is reported as warning #3291. But sometimes it is reported as error.

From the point view of programmer, the problem is obviously. Could you forward this problem to your developer?
Posted by Helen [MSFT] on 6/18/2013 at 1:56 AM
Thank you for submitting feedback on Visual Studio and .NET Framework. In order to efficiently investigate and reproduce this issue, we are requesting additional information outlined below.

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

We look forward to hearing from you with this information.

Microsoft Visual Studio Connect Support Team
Posted by Macy [MSFT] on 6/17/2013 at 10:50 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(