-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plans to migrate to Microsoft.Management.Infrastructure namespace? #13
Comments
Another idea could to be let user's choose which namespace they want to use. Have a default and then allow users to over ride the default if there is some reason to continue using System.Management. |
@mmashwani thanks for using ORMi. There are no plans no migrate to Microsoft.Management.Infrastructure on the current .NET Framework version. But I will start to work to migrate to .NET Core which will use https://www.nuget.org/packages/System.Management/ |
Have you actually tested this? I imagine Microsoft has reasons to make such a claim. |
@chucker I´ve done some applications using Luckily Microsoft have ported |
Besides performance, there are some other advantages to using the I haven't looked at it in great detail yet, but the method for creating a connection using either namespace doesn't seem all that different or complicated: Here are a couple of articles talking about advantages to the new namespace: From my understanding of it, as a consumer of WMI data, the new namespace mainly offers advantages in how it connects to remote machines to query data. Most of the advantages seem to be geared towards developers creating WMI providers. Still, WMI remoting is an important use case for me in most environments. In a few months time, when my work load clears a little bit, I may make an attempt at enabling support for the new namespace and submitting a pull request. |
@mmashwani I will reopen and leave this issue open. When I have a little more time I will analize the impact of making such change. |
Hey, just following up on this. Has ORMi been ported to .NET Core and will it work in an application built for net5.0-windows? |
Just a small note and warning: System.Management requires a specific minimum of .NET framework version unlike MMI. For self contained deployment of a .NET (Core) application this is a huge problem. MMI doesn't have this problem. |
I love this project. It really makes WMI much easier to use in C#. However, I was wondering if there are any plans to migrate the project to start using the Microsoft.Management.Infrastructure namespace instead of System.Management. Here is what Microsoft has to say about the choice between the two:
https://docs.microsoft.com/en-us/previous-versions/hh872326(v=vs.85)
The text was updated successfully, but these errors were encountered: