A simple java applet is to be loaded from another device on my desktop application web browser control on windows 10 (64 bit). This java applet is working fine with IE 11 (with compatibility settings on) on the windows 10 machine but when this is loaded in web browser control (WPF app on .net framework 4.0 and with "Any CPU" build settings) there is a cross on the upper left corner and java applet doesn't load. Also if the WPF app build setting is "x86" the WPF app crashes while trying to load applet.
The same applet is working without any problem with IE 8.0 on windows xp (32 bit) within webbrowser control of WPF application.
Also we won't be able to modify the java applet within the device as device is already in field.
Related
I have created one C# form base application in VS2012 and Windows 8. This application is working fine in Win 8 machine but facing 2 problems in Windows 7
I have used one statusStrip in that application with layout style HorizontalStackWithOverflow. This status Strip lable's text is properly seen in Windows 8 machine but with windows 7 machine it shows text in mirror image text format.
Some forms are not getting opened in Win 7 machine.
Please help me on this
To further clarify the title.
I don't mean HTML5 hybrid apps or apps that have been developed for windows 8/ windows phone 8 and run on windows 8.1/ windows phone 8.1
I would like to know if IBM MobileFirst supports native apps written for windows 8.1 and/or windows phone 8.1 .
For example a universal app.
From what I have read and the tutorials I've seen there is no way to generate dlls for windows 8.1 and windows phone 8.1. Am I missing something?
Have you taken a look at the IBM MobileFirst Platform Developer Center or the IBM MobileFirst Platform Knowledge Center? you'll find your answers there...
Windows Phone 8 - There are tutorials for Native Windows Phone 8.x development (more to come in the future).
https://developer.ibm.com/mobilefirstplatform/documentation/getting-started-native-wp8-development-6-3/
http://www-01.ibm.com/support/knowledgecenter/SSZH4A_6.2.0/com.ibm.worklight.dev.doc/dev/c_developing_native_apps_wp8.html
Windows 8 - Native Windows 8 support is also available (but not yet mentioned in the dev center)
http://www-01.ibm.com/support/knowledgecenter/SSHS8R_6.3.0/com.ibm.worklight.dev.doc/dev/c_developing_native_apps_w8.html
Search the Knowledge Center for more information...
#corus I was able to reproduce your problem consistently! What fixed was the changing the build action of the wlclient.properties file to Content.
Go to solution explorer
Right click on wlclient.properties and select "Properties"
Set the "Build action" property to "Content" (this is missing in the knowledge center)
Also set the "Copy to output directory" to "always"
This should fix the crash issue.
#corcus Part 1 - Currently upto IBM MF 6.3 - there is no formal support in the product UI but we have been qualifying Visual Studio 2013 in the meanwhile (https://www.ibm.com/developerworks/community/blogs/worklightsmobileplayground/entry/ibm_worklight_and_microsoft_visual_studio_2013?lang=en)
Part 2 - our current WindowsPhone8 environment is Silverlight based. What you can try doing is Create a native app with Windows8 environment (this will create a C# app). Open it in VS2013 and then add a Windows Phone 8.1 project to it. Then add the DLL references to the phone project and copy the assets to the Phone Project (or Shared Project) and try running on the Win 8.1 phone. This should work (I have tried Hybrid and it works, but not native - hence not saying conclusively)
I have created a .NET 2.0 Winforms apps that uses the browser control to load a website which uses HTML5 features and such; on my development machine which is a Windows 7 Ultimate x64 computer after creating the necessary registry keys the page loads and works 100%, my problem is when I run it on a Windows 8 32-bit machine, even after adding the registry key it will still bomb with javascript errors which happens on the dev machine if the registry key is not created, does this trick works on Windows 8 too?
64 bit setting (used on dev machine = OK)
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_BROWSER_EMULATION]
"VideoChat.exe"=dword:0000270f
32 bit setting (used on Windows 8 = ERROR)
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_BROWSER_EMULATION]
"VideoChat.exe"=dword:0000270f
Recently I was asked to work on a project which was developed for an aviculture company.
The client asked if I can make the application which was being developed in C#, to work on a tablet.
So i want to know if i finish the application in c# normally Will I be able to:
1.Use the mono for android and compile the whole project with that and get an android app easily for being used in android devices?
2.Use the executable project on a Windows 8 tablet without any changes?
I would be grateful if any one could answer these two questions.
It depends which tablet you're talking about.
On a Windows RT (ARM based) tablet like Surface, only Metro apps are supported. There are a few desktop apps, but only Microsoft can make them. So if your app is a desktop app, it won't run on Surface RT.
On a tablet with the "real" Windows 8 (x86 based, e.g. Surface Pro), you can run the same apps as on a PC.
I am working on a C# application which uses an embedded WebBrowser control to display some HTML content. I want to test whether installing IE9 http://windows.microsoft.com/ie9 will effect my application.
The MSDN blog http://blogs.msdn.com/b/ie/archive/2008/03/18/webbrowser-control-rendering-modes-in-ie8.aspx states that the WebBrowser control defaults to IE7 rendering. However, I want to know what binary is actually being used to do the IE7 rendering.
I think the WebBrowser control could be packaged with:
the version of IE included with Windows (e.g. IE8 with Windows 7)
the newest version of IE installed in Windows (e.g. IE9)
the .NET runtime, my application uses .NET 2.0
Visual Studio, my application is built using VS2008
Which of these is correct?
The .net winforms webbrowser is just a wrapper for MSIE's own browser control (in shdocvw.dll). If you have IE8 installed, it uses IE8. If you have IE9 installed it uses IE9. For some silly reason they decided to have it fall back to IE7 rendering mode.
You can override that with a meta tag in the page header, or with a registry key. See MSIEs WebBrowser control hosted in winforms app runs in compatibility mode