[Bug 30280] Microsoft SQL Server Management Studio Express (SSMSE): needs WMI to select network protocol

http://bugs.winehq.org/show_bug.cgi?id=30280

Anastasius Focht  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |dotnet, download
             Status|UNCONFIRMED                 |NEW
                 CC|                            |[e-mail]
         Depends on|                            |20651
     Ever Confirmed|0                           |1

--- Comment #1 from Anastasius Focht  2012-03-26 16:55:08 CDT ---
Hello,

of course you need SQL server installed to have the SQL WMI providers
installed/registered.
Wine is still missing various infrastructure until custom WMI providers can be
supported.

This blog entry gives an overview about SQL WMI provider architecture:

http://sqlbeyond.blogspot.de/2010/02/sql-wmi-provider.html

Using managed debugger it gives:

--- snip ---
...
(33.4c): CLR exception - code e0434f4d (first chance)
OS Thread Id: 0x4c (0)
ESP       EIP     
0033d204 7b839357 [HelperMethodFrame: 0033d204] 
0033d2a8 0d2d86f4 System.Management.ManagementScope.Initialize()
0033d2d4 0d2d85c3 System.Management.ManagementObjectSearcher.Initialize()
0033d308 0d2d81f3 System.Management.ManagementObjectSearcher.Get()
0033d360 0d2d6e85
Microsoft.SqlServer.Management.Smo.Wmi.WmiBase.GetData(Microsoft.SqlServer.Management.Smo.EnumResult)
0033d374 0d2d66ec Microsoft.SqlServer.Management.Smo.Environment.GetData()
0033d3a4 0d2d2092
Microsoft.SqlServer.Management.Smo.Environment.GetData(Microsoft.SqlServer.Management.Smo.Request,
System.Object)
0033d3b4 0d2d1c9a
Microsoft.SqlServer.Management.Smo.Enumerator.GetData(System.Object,
Microsoft.SqlServer.Management.Smo.Request)
0033d3d4 0d2d1b39
Microsoft.SqlServer.Management.Smo.Enumerator.Process(System.Object,
Microsoft.SqlServer.Management.Smo.Request)
0033d408 0d2d0f68
Microsoft.SqlServer.Management.UI.ConnectionDlg.SqlConnectionProperties.InitNetworkProtocol()
0033d440 0d2d0d6f
Microsoft.SqlServer.Management.UI.ConnectionDlg.SqlConnectionProperties.OnSelection()
0033d448 0d2d0d2f
Microsoft.SqlServer.Management.UI.ConnectionDlg.SqlConnectionProperties.protocol_DropDown(System.Object,
System.EventArgs)
0033d458 0320b966 System.Windows.Forms.ComboBox.OnDropDown(System.EventArgs)
--- snip ---

--- quote ---
The SQL WMI Provider consists of two main components, located in %Program
Files%Microsoft SQL Server100Shared folder.

Sqlmgmprovider.dll :
    This is a COM DLL that hosts all SQL WMI classes.
    Since it's a COM DLL, it should be registered by using regsvr32.exe.
    SQL setup will do this so you don't have to do anything but there might be
rare cases you want to register again. (ex: C> regsvr32 sqlmgmprovider.dll)

sqlmgmprovider*.mof :
    The MOF file contains the SQL WMI schemas. This mof file is handy if you
want to check property name or method name of the specific WMI class.
    The schemas are saved to CIM repository by running mofcomp.exe.
    Again, SQL setup will do this for you but just in case you need to do it :
C> mofcomp sqlmgmproviderxpsp2up.mof (in admin console for Vista/Win7)
--- quote ---

The app probably uses "ClientProtocol" in "ManagedComputer" class to query for
supported protocols.
The "ManagedComputer" object in an SMO managed code:

http://msdn.microsoft.com/en-us/library/microsoft.sqlserver.management.smo.w...

Adding dependency to bug 20651 (basic infrastructure).

Regards