Licensing issue with Older version of dotConnect and newer .Net framework

[gadz777]

Good day

We have encountered a licensing issue with one of our apps using an older version of dotConnect for Oracle (Devart.Data.Oracle v6.80.341.0, Devart.Data v5.0.440.0, Devart.Data.Linq v3.2.73.0).

The issue we have now is that we get the following licensing exception when our shared db library is instantiated. The following exception is thrown

"Assembly that contains embedded dotConnect for Oracle license cannot be used with this application: our-app-name-without-dot-exe.
Please correct license information."

Stack Trace:
at Devart.Data.Oracle.OracleConnection.Open()
at Devart.Data.Linq.Provider.k.a.g()

The issue was discovered after simultaneously upgrading the Development environment to VS2017 (which saw a ToolsVersion increase from 4.0 to 12.0) and .Net framework from 4.0 to 4.6.1.

We have been through a lot of debugging and investigation and all the licensing requirements for this devart component have been met
i.e. the licences.config, and licence.licx file. These have not changed since it was last working. I've verified that the licx file is actually being processed because an invalid fully qualified assembly name causes a build failure, so it is definitely trying to do a component registration

Rolling back is unfortunately not an option at this point due some other dependencies having changed, hence this was a forced upgrade.

We've done all the usual stuff, uninstall, reinstall, but that specific version does not support VS2017 so we are unable to use the licensing manager to validate the licx and .config files. I've also read ALL the forum articles relating to licensing and still no luck getting to the bottom of it. We have also tried rolling back the ToolsVersion to 4.0 with no luck.

We are looking for two things.
1. A quick fix to retain the current version of dotConnect for Oracle because we had worked with Devart in the past to implement various workarounds on our end, to bugs that were present at the time with dotConnect, so we are reluctant to drop a new version on there just yet as we would need to revert our workarounds and revalidate the app. We need this quick fix due to project timelines and resources.

2. We will then tackle the long term solution, which will most likely be upgrading to the latest version of dotConnect and revalidate the app.

Any help or advice to get us going will be greatly appreciated.

Thanks

[Shalex]

2. We will then tackle the long term solution, which will most likely be upgrading to the latest version of dotConnect and revalidate the app.

This is a correct approach, because VS2017 is supported by dotConnect for Oracle starting from the 9.3.230 build: https://www.devart.com/dotconnect/oracl ... story.html.

1. A quick fix to retain the current version of dotConnect for Oracle because we had worked with Devart in the past to implement various workarounds on our end, to bugs that were present at the time with dotConnect, so we are reluctant to drop a new version on there just yet as we would need to revert our workarounds and revalidate the app. We need this quick fix due to project timelines and resources.

Please rebuild your project with the Visual Studio version which is supported by your v6.80.341.

[Shalex]

For example: Visual Studio 2010.

[pszittyay]

I have the exact same issue with version 8.2.90. With VS 2017 and .NET 4.0 everithing works fine but not with .NET 4.7. The strange thing is that some projects works correctly and some other that have dependencies with other projects that reference devart dlls does not.
Is there a way to compile the license.dll and embedeed as a resource with an older version and the use the new .net 4.7

[Shalex]

v8.2.90 supports versions of Visual Studio up to VS2013: https://www.devart.com/dotconnect/oracl ... story.html.

Please upgrade.