Supporting 64 bit variant in Vc 6.0 , must i move to vc 7.0

  • Thread starter Thread starter John H
  • Start date Start date
J

John H

Hi,
We have a product that exposes an ole automation compatible interface
using vc 6.0 .
We have a new requirement to support a 64 bit long as an automation
data type.
VC 6.0 doesn't appear to support this in that the variant structure in
oaidl.h doesn't have
LONGLONG llVal;
entry where vc 7.0 does.

Must i upgrade to Vc 7.0 to take advantage of this.?
I just want to support the data type in certain apis not produce a 64
bit product.

All help welcome.

John
 
We have a product that exposes an ole automation compatible interface
using vc 6.0 .
We have a new requirement to support a 64 bit long as an automation
data type.
VC 6.0 doesn't appear to support this in that the variant structure in
oaidl.h doesn't have
LONGLONG llVal;
entry where vc 7.0 does.

Must i upgrade to Vc 7.0 to take advantage of this.?
Click to expand...

I wouldn't have thought so. Try installing a more up-to-date version
of the Platform SDK (headers and libraries), I think those should
contain the definitions you need.

Dave
 
Hi,
Thanks for the info.
Latest sdk as per
http://www.microsoft.com/msdownload/platformsdk/sdkupdate/
does have support for 64 bit long in its variant in oaidl.h.

Excuse my ignorance -
If i was to start compiling and linking against this platform sdk to
take advantage of this functionality how would this effect the
deployment of my application?
Would i then have to test against relevant dll's that are provided as
part of the sdk and also ship these. Just need to ascertain impact in
terms of testing , deployment etc.

Regards
JOhn
 
Thanks for the info.
Latest sdk as per
http://www.microsoft.com/msdownload/platformsdk/sdkupdate/
does have support for 64 bit long in its variant in oaidl.h.
Good.

Excuse my ignorance -
If i was to start compiling and linking against this platform sdk to
take advantage of this functionality how would this effect the
deployment of my application?
Would i then have to test against relevant dll's that are provided as
part of the sdk and also ship these. Just need to ascertain impact in
terms of testing , deployment etc.
Click to expand...

Do you ship any DLLs that are provided by the SDK? If so, then I guess
you ought to test against them and ship them (assuming they are
redistributable).

Dave
 
Hi,
Currently no as not using the sdk.
But if we were to start using it i.e compiling/linking against it then
i assume we would then need to start using the dll's that come with the
sdk that supports these features and subsequently distribute with our
product.

Just want to kmow what i'm getting into.
Thanks for info so far.

Regards
John
 
Currently no as not using the sdk.

Ah, but you are in effect already using it - an earlier version that
shipped with VC6.

Generally the SDK provides you with the headers and libs for the OS
components, so you don't usually have to redistribute anything extra.

Dave
 
Hi,

Thanks again for reply.
But if using newer sdk which provides extra functionality e.g support
for 64 but long by CComVariant then this new functionality must be
implemented in newer versiosn of previous dll's e.g. atl.dll which you
must then compile, link and test against and also deploy.?
There is a redist folder that comes with this sdk.

Regards
John
 
There is a redist folder that comes with this sdk.

So I guess you need to redistribute any of those bits that your
application uses.
The PSDK I have on my machine only seems to have Win64
redistributables.

Dave
 
Back
Top