Join the 80,000 other DTN customers who enjoy the fastest, most reliable data available. There is no better value than DTN!

(Move your cursor to this area to pause scrolling)




"Everything is working great with the API. I love it." - Comment from Calvin
"I've never had DTN go out on me since switching. ******* would go down a couple times every month when I was using them." - Comment from Bryce in AL.
"If someone needs the best quality data and backfill beyond what their broker provides at a rate that is the best in the industry, I highly recommend IQFeed." - Comment from Josh via Public Forum
"I was on the phone with a friend who uses CQG and right after the Fed announcement, CQG was as much as 30 seconds behind DTN.IQ. Some quotes were off by as much as 15-18 cents. Your feed never missed a beat." - Comment from Roger
"Excellent datafeed !!!" - Comment from Arely
"Very impressed with the quality of your feed - ******* is a real donkey in comparison." - Comment from A.C. via Email
"I noticed that ******* quotes locked up shortly after the interest rate announcement yesterday while yours stayed stable." - Comment from Ron in Utah
"I will tell others who want to go into trading that DTN ProphetX is an invaluable tool, I don't think anyone can trade without it..." - Comment from Luther
"After all the anxiety I had with my previous data provider it is a relief not to have to worry about data speed and integrity." - Comment from Eamonn
"I was with ******* for 4 years at $230 a month, this is a huge savings for me, GOD BLESS YOU PEOPLE," - Comment from T.S. via Email
Home  Search  Register  Login  Recent Posts

Information on DTN's Industries:
DTN Oil & Gas | DTN Trading | DTN Agriculture | DTN Weather
Follow DTNMarkets on Twitter
DTN.IQ/IQFeed on Twitter
DTN News and Analysis on Twitter
»Forums Index »Archive (2017 and earlier) »IQFeed Developer Support »Getting API Sample Code to work with MS Visual Studio 2015
Author Topic: Getting API Sample Code to work with MS Visual Studio 2015 (5 messages, Page 1 of 1)

sds
-Interested User-
Posts: 2
Joined: Mar 6, 2017


Posted: Mar 6, 2017 10:07 AM          Msg. 1 of 5
Hi,
I've just signed up for the API developer support and am looking to compile the sample source code. However, it appears that the target compiler is VS 2012 whereas I'm using VS 2015.

I did try to upgrade the project to 2015 but I get the following error message when I try to compile the code:

warning MSB8003:
Could not find WindowsSdkDir_71A variable from the registry. TargetFrameworkVersion or PlatformToolset may be set to an invalid version number.

Can anyone offer any tips on how to get this code working in VS 2015 or is there a version of this source code that works for this later compiler?

TIA


Adam

DTN_Tim Walter
-DTN Guru-
Posts: 1238
Joined: Apr 25, 2006


Posted: Mar 6, 2017 01:35 PM          Msg. 2 of 5
Good afternoon,

I know there were issues reported where Microsoft's decision to remove MBCS for MFC from the default Visual Studio project caused issues. I found a link below that tells how to re-enable this. I don't know that it is related to your issue, but it sounds like ot may be worth a try.

https://msdn.microsoft.com/en-us/library/dn251007.aspx


Tim

bg112
-Interested User-
Posts: 4
Joined: Mar 8, 2017


Posted: Mar 8, 2017 08:37 PM          Msg. 3 of 5
I am having similar issues . See my post

http://forums.dtn.com/index.cfm?page=topic&topicID=4334

I tried the link you posted and it did not help. Can someone please let me know if this issue was already solved.

bg112
-Interested User-
Posts: 4
Joined: Mar 8, 2017


Posted: Mar 8, 2017 08:50 PM          Msg. 4 of 5
Okay I just realized how to fix this. For first time Visual studio users

1. Open the .vcproj file .
2. It will ask you to convert agree.
3. Next Right click on the solution and retarget for the sdk version you have installed.

This fixes the above issues.

Okay I am able to run the program!! hooray.
Edited by bg112 on Mar 8, 2017 at 08:58 PM

sds
-Interested User-
Posts: 2
Joined: Mar 6, 2017


Posted: Mar 9, 2017 08:58 AM          Msg. 5 of 5
I too have sorted this out now. The issue for me was that the project targeted a Windows SDK toolset that I hadn't installed. Eventually VS prompted me to install this toolset and after that it all worked fine.

I must admit I am somewhat surprised that the official version of the source code is on a compiler that is nearly five years out of date.

Adam
 

 

Time: Fri May 17, 2024 3:39 AM CFBB v1.2.0 9 ms.
© AderSoftware 2002-2003