From my limited understanding, the SetupVSPackage needs to be built for each new Visual Studio release and since VS 2017 just released this month, it may be a little while before that happens on the supported branches. Since SQL Anywhere 12 went past development support last December, if you absolutely must need to use Visual Studion 2017 for project work you will need to go to SQL Anywhere versions 16 or 17 when that support becomes available for those releases. [Caveat this thread only applies to support for EF6 on VS2017 and should not be read as implying an announcement of or suggesting support for the newer EF-Core which remains to be undetermined at this time.] 1
I'll take a look at this. We will have to add VS integration for this new version.
(15 Mar '17, 10:35)
JBSchueler
Microsoft has radically changed the way things are set up with VS 2017. The registry structure is quite different (or gone entirely) so this will take some time.
(16 Mar '17, 17:23)
JBSchueler
Replies hidden
Well, thanks to the Golden Watcom Rule, we would not expect that from you:)
(17 Mar '17, 04:12)
Volker Barth
|
|