Hi, At March 8, 2017, 3:09 PM, Jiří Činčura wrote:
>> Also, what is the timeline to support VS 2017? I tried by simply >> changing the registry keys from 14_Config to 15_Config, but that >> simply created a 15_Config registry key that only contained the >> registry keys for Firebird, and nothing else. It looks like that they >> have changed how the integration works. > Great. Something I don't want to hear. :) Hopefully it's just the > registry keys, not the whole DDEX story. Although I wouldn't mind fresh > API for that, preferably fully managed. > >> I can add the VS2017 support request to the tracker, just let me know >> under which component(s) that would be appropriate. > It' already there under DNET-739. I added a comment to DNET-739 with a link to the breaking changes in VS 2017 with regards to the integration and the registry keys. It looks like that the best approach would be to use the VSIX package installer, possibly using the External Settings Manager. -- Best regards, Daniel Rail Senior Software Developer ACCRA Solutions Inc. (www.accra.ca) ACCRA Med Software Inc. (www.filopto.com) ------------------------------------------------------------------------------ Announcing the Oxford Dictionaries API! The API offers world-renowned dictionary content that is easy and intuitive to access. Sign up for an account today to start using our lexical data to power your apps and projects. Get started today and enter our developer competition. http://sdm.link/oxford _______________________________________________ Firebird-net-provider mailing list Firebird-net-provider@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
