简体   繁体   中英

Is there advantage to use Visual Studio 2017 instead of VS2013 to interface my VC++ DLL to my VB.NET windows forms app?

Should I stick with Visual Studio 2013 Pro or use latest Visual Studio 2017 Pro to interface my Visual-C++ DLL to my Visual Basic .NET windows forms app GUI?

I will try P/Invoke 'wrap' the VC++ DLL for the VB app.

Yes. Visual C++ 2013 doesn't support some new features introduced in C++11/14/17.

For example, following code works fine in VC++2017 but doesn't work in VC++2013:

class A
{
public:
    int n;
};
cout << sizeof(A::n) << endl;

The compiler error on VC++2013 is:

error C2070: 'unknown': illegal sizeof operand

The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM