adomd core
ADOMD.NET Client Needs .NET Core Support
Please tell us when this will be available. We've been waiting years, and all ADOMD.NET does is XML over HTTP - it's pretty silly that there's no support for clients running on .NET Core!
Joel Mueller
shared this idea
21 comments
-
Akshai
commented
This is being worked on. Hopefully a preview will be available in the first quarter of next year.
-
Zoltan Grose
commented
I'm hoping we don't have to wait for the Grand Unification of .NET 5 but it is looking that way.
-
Wenjin Wu
commented
Our system is using analysis services and depends heavily on ADOMD.NET. This one has been the last piece for our projects to fully upgraded to .NET core. Hope that there is a timeline for this one.
-
Roman Jendrusch
commented
I understand that the Windows Integrated Security is tricky, but I guess most of the users are shifting away from this feature because of single sign on with azure active directory. By looking in the decompiled code I saw that there are few interop calls like this https://github.com/bdebaere/Unofficial.Microsoft.AnalysisServices.AdomdClientNetCore/blob/47ee91c89629e0121ba763b02071526caf511ffc/AdomdClientNetCore/Microsoft.AnalysisServices.AdomdClient/NativeIStream.cs which could be easily replaced with native .net core objects (I guess).
For us as a company running a lot o powerbi and analysis services tabular models it is really hard to satisfy the non windows users/teams
-
Ian McCaul
commented
Any news on this? Now that .Net Core 3.0 is out this one piece it starting to become a real issue for migrating projects to the latest core framework. Is there any word on timeline?
-
Darren Gosbell
commented
@DC - there was an update 4 days before your comment "This is something being actively looked at, but we don't have a timeline to share at this point."
-
DC
commented
Its been close to a year and no update on this issue. has anything changed in last few months ?
-
Akshai
commented
This is something being actively looked at, but we don't have a timeline to share at this point.
-
Anonymous
commented
This is also causing us great pain. We are mostly a .net core/asp.net core shop now, except we cant implement functionality for SSAS because of this limitation.
-
Saurav
commented
We are unable to use Azure Durable functions v2 (which uses .NET Core) because of this limitation.
-
Deepak Sahu
commented
We are in process of upgrading all out projects to .net Core but some of them are blocked because of ADOMD.
Can you please see and try to bring in ADOMD library for .net core?
-
Anonymous
commented
Can you please tell us, whether there will be a .NET Core compatible version of AdomdClient? Maybe, with the windows-specific packages coming with .NET Core 3?
-
David Markle
commented
Now that PowerShell 6 is only for .NET Core, our ADOMD.NET based assemblies are literally the only thing holding us back to upgrading our environment. As in, I literally can’t upgrade PowerShell ever again — ever — until someone ports this. If you’re not interested in porting the code, open source it so the community can. MS claims to be interested in presenting SSAS/PowerBi as the new great way to connect to data, and .NET core as the new great way of programming, but the tooling continues to hold us back. And don’t try to tell me that there’s no demand for this. There’s no demand because the tooling is so bad that thousands of people are being “turned off” to the SSAS platform, just at the time you’re marketing it hard to the world. We need you to maintain the tools or we can’t build with them. This is outrageous.
-
DC
commented
Any updates on this? This item is open for a while now.
-
Toni Wenzel
commented
Any progress???
-
Anonymous
commented
Any updates on this?
-
Joel Mueller
commented
There is an unofficial port of ADOMD Client to .NET Core. I haven't tried it myself so I don't know how well it works with local SSAS rather than Azure (there's no support for Windows impersonation). Microsoft, this should illustrate that there is definitely demand for this feature.
https://github.com/bdebaere/Unofficial.Microsoft.AnalysisServices.AdomdClientNetCore
-
Alex Kichkailo
commented
This issue is getting quite important since ASP.NET Core will only run on .NET Core (https://github.com/aspnet/Announcements/issues/324).
Referencing AdomdClient dll in a .NET Core >2.0 app and installing Microsoft.Windows.Compatibility does not seem to help. I am getting the exception below when trying to open a connection. That's it, WindowsImpersonationContext is not part of .NET Standard 2.0
System.TypeLoadException: 'Could not load type 'System.Security.Principal.WindowsImpersonationContext' from assembly 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'.'
-
Anonymous
commented
SQL Server (SSAS) without support for .NET Core is useless for me :(
-
Anonymous
commented
It's not just about adomd client, we need adomd too for managing roles etc. For both SSAS mutidimensional and tabular models.