Home Dashboard Directory Help
Search

Visual Studio 2010 Trial Version by Roger McElfresh


Status: 

Closed
 as Not Reproducible Help for as Not Reproducible


1
0
Sign in
to vote
Type: Bug
ID: 592012
Opened: 8/31/2010 9:09:02 AM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

Back in the dark ages when I using VS2005, The compiler would warn you that you need to #define WINVER 0x0502. VS2010 Trial version does not give you this warning and CString.Find(...) doesn't work unless you do define WINVER.
Details
Sign in to post a comment.
Posted by Microsoft on 9/19/2010 at 10:16 PM
Hi, given that we have not heard back from you, we will go ahead and close this Connect Issue. If you get a chance to review and provide the information requested earlier, you can go ahead and reactivate this issue.(Click “Edit this item” button on the site and change the “Status” to “Active”)
Posted by Microsoft on 9/14/2010 at 10:22 PM
any update?
Posted by Microsoft on 9/13/2010 at 1:52 AM
Thank you for reporting this issue. In order to research the issue reported, we must first reproduce in our labs. Unfortunately, we are unable to reproduce the issue with the steps you provided. We tried to repro with the following steps:

1.Create a c++ project with precompiled header <stdafx.h>
2.WINVER is defined by including targetver.h which includes sdkddkver.h.

Could you please provide us with the following information?

1.Did you including targetver.h which includes sdkddkver.h with defaut setting?
2.Could you provide you code to us?

It would be greatly appreciated if you could provide us this information as quickly as possible.

Thank you,
Visual Studio Product Team
Posted by Microsoft on 8/31/2010 at 10:56 PM
Thanks for your feedback. We are routing 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 8/31/2010 at 5:04 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)
Sign in to post a workaround.