This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| """ | |
| My journey started after reading this topic. And I started to gather all the breadcrumbs and clues I have found around the Internet. | |
| First of all. There is a difference between Mono and dotnet(aka .net core), as pointed by Darren Gosbell on a microsoft learn page [4]. | |
| As everyone stumbling upon this issue I tried using Mono and specific to Windows version of Adomd whic is located in this link [5]. It didn't work as there were API used specific to Windows. It was failing. | |
| Then I learned that there is actualy a 'native' dotnet app that could run those DLLs. | |
| I started by loading that native to Windows AdomdClient DLL version using Mono - Fail. | |
| Then using dotnet - Fail. | |
| And right after that I understood that a .net core DLL has to be used. So I found one on Nuget [3]. | |
| And boom, right after that the original problem has gone, but I had a malformed connection string, which I believe was leading to lib to try to run a interactive login(just imo) and then failing into an issue where it said that a function or a |