trekrider

We are interested in trialing a windows application that includes a toolkit consisting of API's in the form of DLL's that was written in Microsoft Visual C++ 7 .NET

My question is this..

Is it reasonable to assume that I will be able to write some 'concept test' code calling those API's using a later version of Microsoft Visual C++ or will I be forced to use 7

2nd question is akin (and dependant on) the first question. If the answer to the first question is 'yes'... could I possibly use MS Visual C++ 2005 Express Edition

thank you very much



Re: Visual C++ General compatibility of commercial package API's written with Visual C++ 7 .NET with more recent release of Vis C++

rtpninja

1. Yes, that's a reasonable assumption - assuming the toolkit is intended for third-party use.

2. Good question for the VC++ Express forums.

Hope this helps.





Re: Visual C++ General compatibility of commercial package API's written with Visual C++ 7 .NET with more recent release of Vis C++

Holger Grund

Although 1 should be a reasonable assumption, industrial strength is very much subject to interpretation. There's no simple set of rules, but I general it's a good idea to be nervous, if it's a prebuilt library based on MFC or if it is a static C++ library.

Visual C++ express does not ship with Microsoft's own libraries (MFC, ATL). If these are required you're out of luck. Otherwise things should just work, though you might need to install the Windows SDK.

-hg