I have a C# WinForms program which runs on Windows 8 but fails on Windows 8.1 (both the beta and the RTM). I initialize a WebBrowser control with my HTML, which contains an object tag referencing a remote Flash SWF file. I wish I could switch away from Flash, but this is the only format I can use.
In Windows 8, the file plays fine. On Windows 8.1, the object tag is successfully written to the page, but it is just a transparent box. What would have changed in Windows 8.1 that would block Flash in the WebBrowser control?
Here's a link to the code itself. The program allows for standalone playback of TWiT.tv programming with the BitGravity player.
http://wessleym.com/twit/
Thank you.
We had similar problem when our WebControl couldn't start or use Flash Objects. We solved it with Visual Studio 2013. We loaded project in VS2013 and builded it there. Now it works on Windows 8.1 normally.
I discovered after some trial-and-error that I needed to have type="application/x-shockwave-flash" specified in the <object> tag. Windows 8 worked fine without it, but Windows 8.1 trips up. My program works great now.
Related
I know that XAML is used for designing UI in combination with Blend. I am confused with so many terms, like, how XAML comes into play for WPF, Store App, Phone App or UWA. Morever, what is the difference between WPF, Store App, Phone App and UWA. Does all that means that old Desktop Project will no longer be used and replace by either WPF or Store App or UWA?
When .NET was released in ~2000, you could use WinForms to make desktop applications for Windows. It provides access to 'native' controls (i.e. A Button made in WinForms actually is a Windows Button control from user32.dll) by wrapping the Windows API in managed code. These can run in any version of Windows which has the appropriate .NET framework version installed, including upto Windows 10.
In 2006, WPF was released which is an alternative to WinForms. WPF uses XAML, which is a language based on XML, to declare the user interface elements. In a simple WPF app, the .xaml file describes the GUI and the code-behind file describes the logic. DirectX is used to draw whatever is described in the .xaml into the window.
Like Winforms, programs made using WPF can run in any version of Windows which has the appropriate .NET framework version installed, including upto Windows 10. Note that using XAML is completely optional. Whatever user interface elements you describe using XAML can also be made using your .NET language C# or VisualBasic.NET. But using XAML is usually simpler. See To XAML or not to XAML (MSDN Blogs).
From XAML (Wikipedia) :
As XAML is simply based on XML, developers and designers are able to share and edit content freely amongst themselves without requiring compilation.
From ~2012 along with Windows 8, a new kind of app called metro/modern/windows-8/windows-store-apps can be made. These apps are similar to WPF in that they use XAML for describing the GUI. These apps can run only in Windows 8, 8.1 and Windows 10. Windows 8.1 added some improvements and features but remained mostly the same. The same technology was used to make apps for Windows Phone.
With the release of Windows 10, Microsoft made UWP (Universal Windows Platform) through which you can use the same code base to target differnt kinds of devices (desktop/mobile/xbox/IoT/holographic). These apps made for the UWP are similar to the earlier Windows 8/8.1 apps. Like before, XAML is used to describe the GUI.
Only for the Windows Store apps, there is no backward compatibility. The timeline goes Windows 8 -> Windows 8.1 -> Windows 10/UWP. An app made in UWP can only run in Windows 10 and an app made in Windows 8.1 can not run in Windows 8.
I would highly recommend referring to this discussion thread in stopbyte, it has far more details and explanation of the concepts behind WPF, UWP And WinRT.
As for WinForms, from my experience it's history now. Have been almost replaced by WPF (though it still has mainstream support as mention by #Jazimov).
I'v noticed that Microsoft has stopped improving Windows Forms and probably has stopped maintaining it as well.
I just deployed my WPF application to Windows 8 and was shocked to see that none of my labels line up with their respective textboxes! In both Visual Studio 2010 and 2012 they snap-to and line up perfectly in the design view. They also line up perfectly when the application runs in Windows 7 and XP. I'm using the same resolution/DPI settings for both deployments. Has anyone else noticed this issue? Does anyone have any ideas as to why this is happening?
Are you manipulating the size of the TextBoxes or labels in your application?
I have expander control that it works in vs and blend correctly but when i build a setup file and executed it cant work correctly.(does it work correctly in win xp?)
It works fine on Windows XP. But you should install latest updates for .net framework.
We're using Visual C++ 6.0 to develop a web-application, which uses ActiveX controls.
One of them is this Microsoft Chart Control(6.0), to show some statistics or something.
Well, it works and shows up fine when the .ocx is run under a PC that has Internet Explorer 6.0.
But under an IE 7 machine, that chart isn't displayed; there is a blank image instead. It doesn't show up. No errors or exceptions thrown.
When I run the application from Eclipse in hosted mode though, it works fine again. Only when opened in IE 7, that chart disappears.
This MS Chart Control apparently uses MSCHART20.ocx
Thanks in advance for any advice towards a fix, or a workaround, or a needed upgrade.
I don't like upgrades though. But I need to figure out what kind of upgrade can be done to make this work.
We have an in-house .net 2.0 winforms app currently developed on Visual Studio 2005 in Windows XP. Everyone in the office until now is running Windows XP, and there are no issues.
We recently ordered a new computer with Windows 7 for one of our managers we were hoping to use, and the app installs fine. The issue is the spacing around every label, textbox, and button - making some forms not fit.
Is there some setting that we can use to make Windows 7 display each control where it is placed in our XP development environment and like the rest of our XP clients show?
Ugh, what kind of idiot management team gives a new machine to a manager instead of a programmer?
Control Panel + Display, Advanced tab, change the DPI setting to repro the problem on your XP machine. Read the docs for the Form.AutoScaleMode to find out what's going on.