4 ms·

It doesn't appear that you can use this in a 'normal' .NET app. Any ideas why?

by rikkus 12y ago

ghuntley 12y ago
Can confirm that the actual package successfully installs into a Profile78 Portable Class Library. So whilst the marketing heavily mentions Windows Phone, in theory this library will also work on Xamarin (iOS/Android, etc) and also within standard .NET applications (ASP.NET/Console/etc). nb: haven't actually tested past installation at this stage. edit: nope :(
- rikkus 12y ago
  Ah excellent, will try that, thanks!
  - rikkus 12y ago
    It installs - but there's no DLL reference and you don't see the WindowsPreview namespace.
rikkus 12y ago
I made a C# Console app and added the nuget package. It adds, but there aren't any references. Within the nuget package, though, there is are three subdirectories within 'lib', one being 'win81'. packages\Microsoft.Windows.Ocr.1.0.0\lib\win81 Within this, there are 'ARM' 'x86' and 'x64' directories and dlls within them. VS refuses to add them to my project, so I'm guessing they're native and not COM libraries. Why would I think they might be .NET libraries if they have 'x86' and 'x64' labels? Because C++/CLI has to be compiled to separate dlls, I believe.
- pjmlp 12y ago
  It has nothing to do with C++/CLI, but with marshaling, JIT and NGEN. When calling native code outside the CLR the runtime needs to know which type of marshaling code to generate. It also plays a role when using unsafe code blocks in .NET.
NetMonkey 12y ago
This is really one of my big frustrations with Microsoft. On one hand, they really try to push everybody to upgrade to their newest and shiniest, by making a lot of stuff (like this) only available on Windows 8+. On the other hand, they don't even bother to put in a box with "What operating systems will this work on", so you don't have to do trial/error, research WinRT, and then be disappointed when you realize this will apparently never work on Windows 7. And maybe only in Metro apps? What is Windows Runtime and am I just supposed to know this? I really enjoy coding C# and working in .NET. Microsoft has some really great stable techs which work well for years and years - but increasingly if you want anything new and shiny from them, you have to run the newest OS. Which if you work with anything related to enterprise, good luck only targetting Windows 8. And honestly, despite working almost exclusively with MS tech, I just don't really trust any platform from them that doesn't have significant traction and track record as they all too often just give up and try something new - and sometimes without real replacements available.
- danbruc 12y ago
  The MSDN documentation for the classes [1] clearly states the supported platforms. Admittedly the restriction to store apps is missing on the page for the namespace [2]. Minimum supported client Windows 8.1 [Windows Store apps only] Minimum supported server Windows Server 2012 R2 [Windows Store apps only] Minimum supported phone Windows Phone 8 [1] http://msdn.microsoft.com/en-us/library/windows/apps/xaml/windowspreview.media.ocr.ocrengine.aspx http://msdn.microsoft.com/en-us/library/windows/apps/xaml/wi... [2] http://msdn.microsoft.com/en-us/library/windows/apps/xaml/windowspreview.media.ocr.aspx http://msdn.microsoft.com/en-us/library/windows/apps/xaml/wi...
  - NetMonkey 12y ago
    Ah, don't know how I missed that. Thanks. Crazy that it's limited to 8.1, and not even working on 8.0. I really wonder if there is a valid technical reason, or they just use it to push upgrades.
    - silon3 12y ago

It doesn't appear that you can use this in a 'normal' .NET app. Any ideas why?

by rikkus 12y ago

It doesn't appear that you can use this in a 'normal' .NET app. Any ideas why?

Can confirm that the actual package successfully installs into a Profile78 Portable Class Library. So whilst the marketing heavily mentions Windows Phone, in theory this library will also work on Xamarin (iOS/Android, etc) and also within standard .NET applications (ASP.NET/Console/etc). nb: haven't actually tested past installation at this stage. edit: nope :(

rikkus 12y ago
Ah excellent, will try that, thanks!
- rikkus 12y ago
  It installs - but there's no DLL reference and you don't see the WindowsPreview namespace.

rikkus 12y ago

I made a C# Console app and added the nuget package. It adds, but there aren't any references. Within the nuget package, though, there is are three subdirectories within 'lib', one being 'win81'. packages\Microsoft.Windows.Ocr.1.0.0\lib\win81 Within this, there are 'ARM' 'x86' and 'x64' directories and dlls within them. VS refuses to add them to my project, so I'm guessing they're native and not COM libraries. Why would I think they might be .NET libraries if they have 'x86' and 'x64' labels? Because C++/CLI has to be compiled to separate dlls, I believe.

pjmlp 12y ago
It has nothing to do with C++/CLI, but with marshaling, JIT and NGEN. When calling native code outside the CLR the runtime needs to know which type of marshaling code to generate. It also plays a role when using unsafe code blocks in .NET.

NetMonkey 12y ago

This is really one of my big frustrations with Microsoft. On one hand, they really try to push everybody to upgrade to their newest and shiniest, by making a lot of stuff (like this) only available on Windows 8+. On the other hand, they don't even bother to put in a box with "What operating systems will this work on", so you don't have to do trial/error, research WinRT, and then be disappointed when you realize this will apparently never work on Windows 7. And maybe only in Metro apps? What is Windows Runtime and am I just supposed to know this? I really enjoy coding C# and working in .NET. Microsoft has some really great stable techs which work well for years and years - but increasingly if you want anything new and shiny from them, you have to run the newest OS. Which if you work with anything related to enterprise, good luck only targetting Windows 8. And honestly, despite working almost exclusively with MS tech, I just don't really trust any platform from them that doesn't have significant traction and track record as they all too often just give up and try something new - and sometimes without real replacements available.

danbruc 12y ago
The MSDN documentation for the classes [1] clearly states the supported platforms. Admittedly the restriction to store apps is missing on the page for the namespace [2]. Minimum supported client Windows 8.1 [Windows Store apps only] Minimum supported server Windows Server 2012 R2 [Windows Store apps only] Minimum supported phone Windows Phone 8 [1] http://msdn.microsoft.com/en-us/library/windows/apps/xaml/windowspreview.media.ocr.ocrengine.aspx http://msdn.microsoft.com/en-us/library/windows/apps/xaml/wi... [2] http://msdn.microsoft.com/en-us/library/windows/apps/xaml/windowspreview.media.ocr.aspx http://msdn.microsoft.com/en-us/library/windows/apps/xaml/wi...
- NetMonkey 12y ago
  Ah, don't know how I missed that. Thanks. Crazy that it's limited to 8.1, and not even working on 8.0. I really wonder if there is a valid technical reason, or they just use it to push upgrades.
  - silon3 12y ago