FDK8.0 with VS.NET 2003

[_Gaurav_Bajaj_]

I have a frame client that was built using FDK 7.2 and VS.NET 2003. Now I have upgraded to FDK 8.0/Frame 8.0, but VS.NET in use is still 2003. I read in the posts that to make FDK 8.0 work with VS.NET 2003, we have to make the following changes:<br /><br />#include <sys/types.h><br />#include <sys/stat.h><br /><br />int _stat32( const char *path, struct _stat *buffer ) { return <br />_stat(path, buffer); }<br />int _wstat32( const wchar_t *path, struct _stat *buffer ) { return <br />_wstat(path, buffer); }<br /><br />long _ftol( double );<br />long _ftol2_sse( double dblSource ) { return _ftol( dblSource ); }<br /><br />After making the above changes, I can build the solution and generate the DLL. However, in the main application (that references this frame client)... i get the following error:<br /><br />"IXPFrameLib error LNK2019: unresolved external symbol __ftol2_sse referenced in function _F_MetricFloat"<br /><br />Are we required to make any other changes? Is FDK8.0 backward compatible with FDK7.1?<br /><br />Thanks...

[_Gaurav_Bajaj_]

Has anybody faced the same problem? Any inputs/suggestions are appreciated.

[_Scott_Prentice_]

Hi Gaurav...

I'm not understanding what you mean by .. "the main application (that references this frame client)" .. isn't Frame the application that references the client?

...scott

[AxialInfo]

If you haven't yet posted there, you might find some information through the FDK Dev group: http://groups.yahoo.com/group/frame_dev/

[Russ Ward]

Guarav,

If nobody seems to know here, consider trying the Yahoo Frame dev forum at:

http://groups.yahoo.com/group/Frame_dev

Some of the same folks are there too, but maybe somebody else is there who might know.

Russ

[_Gaurav_Bajaj_]

Thanks guys... i would post at:
http://groups.yahoo.com/group/Frame_dev

Scott,
We build the FDK client (on VS.NET 2003) to get a DLL whose methods are then referenced in another application (C#). I can create this DLL using FDK 8.0 and VS.NET 2003... but when i reference it in the second application, I get the above errors.