I have installed the Microsoft Windows SDK for Windows 7 and .NET Framework 4 through this link ( http://www.microsoft.com/downloads/dlx/en-us/listdetailsview.aspx?FamilyID=6b6c21d2-2006-4afa-9702-529fa782d63b ) on a Windows 7 machine and trying to following the instructions about how to create a Handwriting Recognition WPF application using this guide ( http://msdn.microsoft.com/en-us/library/ms754080%28VS.90%29.aspx ).
However, I couldn't find the IACore.dll, IAWinFX.dll and IALoader.dll mentioned inside the guide. I have even done a search in my Windows installation drive just in case they are installed in another location. But it just seems that the files are not even installed anywhere.
Or is there any alternative for me to build a WPF Handwriting Recognition application?
I found it in:
c:\Program Files\Reference Assemblies\Microsoft\Tablet PC\v1.7\
Related
The Issue:
Our application is a .NET 5 Windows Desktop application. The licensing capability requires the application to use the System.Management component from NuGet to create a unique device ID from the system processor ID, MAC Address and BIOS serial number.
This all worked great when testing it from Visual Studio debugger. However, when adding System.Management.dll to the application installer (InstallShield installer) I naturally selected the version of System.Management.dll that was in the app's build target folder. It turns out that the version of the DLL that ends up in that folder is a no-op version that throws not supported exceptions saying "System.Management is supported on Windows Desktop Apps only".
The Solution:
I found the correct version of System.Management.dll in the build TargetFolder\runtimes\win\lib\netcoreappX.x folder. In my case, since I'm using System.Management version 6.0, it is in the "netcoreapp3.1" folder.
Conclusion
There are many cases where Microsoft doesn't do the right thing. In this case, my application was specifically a .NET 5 Windows Desktop application, so we would all think that msbuild could figure out the correct thing to do. Not so. In such a case, I would have at least hoped that .NET Foundation would have provided information on this. Well, now you all know now, as well!
Cheers
I've created a WinForms (C#) application and I have to add support for the built-in flash. The device is Tablet PC running x64 architecture Windows 10 Professional (common Windows 10). Is there any way to do that? My application captures video from a built-in camera - I'm using OpenCV Sharp to do that, but I can't find any possibility to use a built-in flashlight. I need just manually turn on and off the light. I've found a lot of examples but it is possible only through UWP which I can't add to WinForms in any way.
Does anyone know the way to use the built-in flashlight in WinForms Application?
Windows API can be used in any non-UWP-C#-project by adding UwpDesktog NuGet Package
and adding these references:
c:\Program Files (x86)\Windows Kits\10\References\Windows.Foundation.FoundationContract\1.0.0.0\Windows.Foundation.FoundationContract.winmd
c:\Program Files (x86)\Windows Kits\10\References\Windows.Foundation.UniversalApiContract\1.0.0.0\Windows.Foundation.UniversalApiContract.winmd
c:\Program Files (x86)\Windows Kits\10\UnionMetadata\Facade\Windows.WinMD
c:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETCore\v4.5\System.Runtime.WindowsRuntime.dll
Then you can turn on flashlight using MediaCaptur from UWP.
I have an Windows Embedded Compact v8.00 device installed with build 6247. FYI - This device is an Siemens HMI.
Now I'm looking for the right way to develop applications for this version of Windows. I started trying with Visual Studio 2008, so I build a very simple application with just a useless textbox. After copying the executable to the device I start tried to run the test applications but nothing happens.
After searching the web I found out it's better to install Visual Studio 2015 PRO with an application builder from Microsoft's website.
Is this the right way to do? What else does I need to know when developing applications for Windows Compact 2013?
To create applications for Windows Embedded Compact 2013 you need VS2013 or VS2015 professional with the Application Builder plugin and a valid SDK installed on your PC.
If you develop managed apps you also need to check in the .NET runtime is already part of the image or find a way to deploy and install it permanently on your device (the way to do this may change depending on the device configuration, registry type etc.)
I am using a Nokia lumia630 device, which uses latest windows 10 insider preview build available.
i created a sample windows UWP application and took a build of the same.The output of the build is an Appx.
How can i install this Appx to my device? Anyone having any idea?
Deploying apps to Win 10 Mobile is a bit difficult when using the command line tool. A great alternative is the Device Portal that is available under the “For Developer” settings.Its available with the latest build.
Now You can connect to the device using a web browser and manage apps via the Apps page with no pairing/pin required. This seems to be an easy way of deploying apps than using command line.
Microsoft developed a command line tool called WinAppDeployCmd so you can deploy an Universal Windows app from a Windows 10 machine to any Windows 10 Mobile device via USB or WiFi (since they're on the same subnet). That's a perfect solution if you doesn't have Visual Studio, the app source code or you're under a Hyper-V Virtual Machine.
Basically you will need:
Windows 10 SDK
Generate the .appx package (PC)
Enable the developer mode (Mobile)
Turn on the discovery mode (Mobile)
Get the code to pair devices (Mobile)
Get mobile IP address using WinAppDeployCmd tool (PC)
Run command (PC)
The command will look like this
WinAppDeployCmd install -file “<path>” -ip <ip> -pin <pin>
The tool can be found at C:\Arquivos de Programas (x86)\Windows Kits\10\bin\x86\WinAppDeployCmd.exe
You can find a detailed step-by-step tutorial here
Visual Studio allows you to directly deploy an app to a windows phone. You need to register your windows phone as a development phone with Microsoft. Once this is done, you could use visual studio to do this for you. Not sure if you can deploy windows 10 apps to your phone at the moment. Try this link and see:
https://msdn.microsoft.com/en-us/library/windows/apps/ff769508%28v=vs.105%29.aspx Remember to Upvote if this helps.
You can register your Windows Phone 10 in developer mode. Follow these steps and you can achieve your goal.
When you use device portal like mentioned in the answers above, some might get the following error
"Failed to start deployment. Failure text: Package failed updates, dependency or conflict validation. (0x80073cf3)"
To fix this:
Add the dependencies found under "Dependencies/ARM" folder.Add it here.
I had to add following dependencies to make it work:
Microsoft.NET.CoreRuntime.1.0.appx
Microsoft.VCLibs.ARM.Debug.14.00.appx
I want to create a windows mobile app (windows mobile 5.0 and above, using CompactFramework [in SharpDevelop]) to capture photos automatically, without user involvement (like it would be with CameraCaptureDialog). After going through google searches I found out a solution that should work (http://blogs.msdn.com/marcpe/archive/2006/03/03/542941.aspx)1 but I cannot compile the source (I guess that is because I use sharpdevelop not MS Visual Studio).
Are there any other options available?
Maybe there is a binary version of that CameraCapture Library somewhere so I can use it without compiling on my own?
Anyone willing to compile the one I linked above and post it somewhere to make binary version available [I tried searching for such in google, but with no success]
The CameraCaptureDialog is part of the Microsoft.WindowsMobile.Forms assembly, which chips in ROM on WinMo 5.0 and later devices. The device SDKs also whip with copies of these assemblies so the apps can build (for example mine is on my PC at C:\Program Files\Windows Mobile 5.0 SDK R2\Managed Libraries). I would assume you should be able to manually add a reference to that assembly in SharpDevelop.