winmd | driver allowing Windows to access MD RAID devices

I'm using Windows.Media.OCR engine to scan these two lines

But the software scan them like that:

While I'm expecting it to scan like:

KIBA/USDT 0.00003826 6.31M KIBA 241.68459400 USDT

KIBA/USDT 0.00003470 17.13M KIBA 594.48387000 USDT

The code I'm using is:

My solution structure looks like this:

The compiler complains that it finds duplicate types (of every public interface/class) in WCL1.winmd b/c that winmd file already exists in WCL4's bin directory.

One problem is that I know absolutely nothing about C++ and the link offered in the Answer to this question provides a C++ workaround that doesn't help (it's literally like reading a different-but-related language -- i.e. reading German when I only know English).

I also found this which provides another workaround but doesn't tell you where to put it. I added the specified ItemGroupDescription element into every .csproj file as well as the application's PropertySheet.props file to no avail.

I have also done the following:

• Moved the code from WCL2 into WCL3 and removed WCL2 from the solution.
• Had the application reference WCL1, WCL3 and WCL4.

Anyone else got any ideas? It would be greatly appreciated....

UPDATE:

Here's a link to a small solution that reproduces the compile errors. It seems that it comes from the Microsoft.Windows.CppWinRT NuGet package referenced by the C++ Application. That package auto-generates C++ header files from the .winmd files generated by the component projects referenced by the Application.

I installed Docker desktop for windows 10 home (version 10.0.19042) but I was never able to make it work because I keep getting this error:

Microsoft.NET framework is the latest version. When installing Docker I also let the box check to install all necessary WSL components. This is the error message from Docker:

I have an existing program win32 (x86) console app that needs to call managed code (C# from a .Net .dll). The .dll is not exposed to COM, but can be called from a C#/WinRT Component and referenced by C++/WinRT Console Template app, BUT I can't seem to call it from a win32 x86 console app even after installing the C++/WinRT NuGet package. I've built and ran this example but the consuming apps are always using the C++/WinRT template. When I try to reproduce the example with a base win32 app, I get the error REGDB_E_CLASSNOTREG Class not registered.

I found another example showing how to consume a C++/WinRT component from a win32 app, without registering classes. I thought this was my answer. However the process involves going into the application manifest and specify activatable WinRT classes by referencing the outputted .dll file whenever the C++/WinRT component builds.

Here's the problem: C#/WinRT components do not output a .dll file, only the .winmd.(see Edit) With the .winmd file, I can still reference the classes and build my project, But I end up with the same REGDB_E_CLASSNOTREG Class not registered error. I assume both the C++/WinRT and C#/WinRT components would compile into something that is in an Intermediate Language (see comments), but why does C++/WinRT output a .dll and a .winmd, while C#/WinRT only outputs .winmd files? I tried to use WinRT.Runtime.dll in place of the outputted .dll but that didnt work either.

I'm at a loss. I posted another question about the difference between the C++/WinRT template vs win32 with C++/WinRT NuGet package.

Main Problem: Can I use a C# .dll (not COM exposed) in a base win32 console app somehow?

I realized that I was using a C# Windows Runtime Component template that was specific to UWP. This might be why there was no outputted .dll when built.

Following Simon's reply, I was able to create a C# WinRT component that can be called from a Win32 console app. This C# WinRT component DOES output a .dll as well as .winmd. I followed a bit closer to the article Simon posted about consuming with C++ and managed to get it to work with basic C# functions.

I have a c++ .dll and .winmd from this solution. When I put them in a Plugin folder in Unity, build the Universal Windows project and deploy to the Hololens 2, the classes in the .dll and .winmd are recognized.

If I create a Visual Studio Universal Windows XAML project, copy the .dll and .winmd to the project path and include the .winmd via Reference-Add, all the classes are there during editing (no errors thrown during editing and building). When I build the solution, the .dll is also copied to the build path. If I, however, deploy and run the code, the project throws the following exception:

I have been using TFS 2013 for years. I have made no changes to the server. I recently added a project to my solution. (VS-2103 update five) As I updated the project I ran local builds with no problem. Tested the code in Dev and everything worked great. However, when I went to run a build in TFS I continue to receive a build failure. If I remove the project from the solution I can run a build in TFS with no problem. I have deleted / recreated the project, renamed it, recreated a build definition, rebooted both ends. It is getting hung up when I reference out to a DLL that is part of the solution. I pull out that reference and I can build via TFS no problem. Also note that the other 30 or so projects in the solution reference the same DLL and the same classes with no issue. Just this one project I added. But it builds locally???

This is for a very legacy app that runs in a datacenter on its own server. TFS runs on its own server. No cloud involved. I am pretty much a one man show nearly end-to-end. All of the source code is on my workstation. Changes are passed up to the TFS server where the final builds are created. I installed TFS year ago... It has ran great for years until...

Hoping someone can give me a clue...

Some information from the Build Failure and the Log... cannot find the DLL that is part of the solution.

Error Message - C:\Builds\1\MARCL Government Reporting\Development\src\DatabaseAccessMonitor\DBAccesMonitor_bll.vb (8): Type 'ESACR.GeneralMailer_bll' is not defined.

Warning - C:\Program Files (x86)\MSBuild\12.0\bin\Microsoft.Common.CurrentVersion.targets (1697): Could not resolve this reference. Could not locate the assembly "ESACR". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.

Warning - C:\Builds\1\MARCL Government Reporting\Development\src\DatabaseAccessMonitor\DBAccesMonitor_bll.vb (5): Namespace or type specified in the Imports 'ESACR.DataSetFilter' doesn't contain any public member or cannot be found. Make sure the namespace or the type is defined and contains at least one public member. Make sure the imported element name doesn't use any aliases.

Part of the log where you can see it cannot seem to find the ESACR.dll...

3>PrepareForBuild: Creating directory "obj\Release". ResolveAssemblyReferences: Primary reference "ESACR". 3>C:\Program Files (x86)\MSBuild\12.0\bin\Microsoft.Common.CurrentVersion.targets(1697,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "ESACR". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. [C:\Builds\1\MARCL Government Reporting\Development\src\DatabaseAccessMonitor\DatabaseAccessMonitor.vbproj] For SearchPath "{HintPathFromItem}". Considered "..\ESACR\bin\Release\ESACR.dll", but it didn't exist. For SearchPath "{TargetFrameworkDirectory}". Considered "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework.NETFramework\v4.7.2\ESACR.winmd", but it didn't exist. Considered "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework.NETFramework\v4.7.2\ESACR.dll", but it didn't exist. Considered "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework.NETFramework\v4.7.2\ESACR.exe", but it didn't exist.

I'm trying to use this PoshWinRT .NET/Powershell library, as described in this blog post, and this SO question. This worked for me before on Windows 7, but now I am on Windows 10 and since I've moved to a new computer I've cleared the assemblies cached during the build.

The code uses several classes such as Windows.Foundation.IAsyncAction, which are failing because of a missing "Windows" assembly:

CS0012 The type 'IAsyncAction' is defined in an assembly that is not referenced. You must add a reference to assembly 'Windows, Version=255.255.255.255, Culture=neutral, PublicKeyToken=null, ContentType=WindowsRuntime'. PoshWinRT D:\projects\PoshWinRT\PoshWinRT\AsyncActionWrapper.cs 21

As well as an error about that assembly:

Could not resolve this reference. Could not locate the assembly "Windows". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.

In the right-hand Solution Explorer, the following properties are shown for the "Windows" dependency in my References list:

The above .winmd has been deleted, but now I'm not sure how to re-add it. I've tried adding things like:

When I use bazel to generate c++ header source code and winmd file from midl file, I found MyType.winmd file is in output folder, while MyType.h locates at same directory as source code MyType.idl. What I want is that my generated header file locates at the same folder as MyType.winmd file.

MyType.idl:

midlrt : error MIDL1001: [msg]cannot open input file [context]Error opening or processing WinMD d:\Desktop\projects\plenusbusiness\windows\packages\microsoft.ui.xaml.2.3.191129002\lib\uap10.0\microsoft.ui.xaml.winm d. HRESULT 0x80070003. [D:\Desktop\projects\Example\node_modules\react-native-windows\Microsoft.ReactNative\Microsoft.ReactNative.vcxproj] D:\Desktop\projects\Example\node_modules\react-native-windows\ReactUWP\Views\cppwinrt\AccessibilityAction.idl(1): error MIDL5157: [msg]An invalid winmd file was specified for import [context]: D:\Desktop\projects\Example\windows\packages\Microsoft.UI.Xaml.2.3.191129002\lib\uap10.0\Microsoft.UI.Xaml.winmd [D:\Desktop\projects\Example\node_modules\react-native-windows\Microsoft.ReactNative\Microsof t.ReactNative.vcxproj]