I've compiled my WPF project on Windows 7 64-bit, using VS 2010 and .NET 4. I have compiled it as a 32-bit application, of course, and it works fine in both 32- and 64-bit versions of Windows Vista/7.
But in Windows XP SP2 32-bit, I get an error:
wpfApp has encountered a problem and needs to close. We are sorry for the inconvenience."
How can I fix this so that my application will run on Windows XP?
.NET 4 requires Windows XP Service Pack 3.
Either upgrade to SP3, or downgrade your project to target .NET 3.5.
Related
I have installed my PC windows 8.1 (Core) with Visual Studio Professional 2013
I am beginner to develop Windows Mobile App. When I run sample app it shows message:
Windows Phone Emulator
Unable to start the windows phone emulator Windows phone emulator
require Hyper-V Your computer is missing the following
pre-requisites required to run Hyper-V
-Windows 8 Proffesional(64-bit)
0*80131500
How to run Windows Phone Emulator 8.1 using Windows 8.1 OS? Any alternative solution available?
Thanks & Regards
Jejai
You can run Visual Studio 2013 in your machine,no problem about the windows version.:)
Here is how to fix your error. :)
1.Goto Your BIOS settings.
2. Check for a setting called "Intel Virtualisation Technology".
I cant specify exactly where it is.But It must be there in the BIOS settings and it should have been disabled.
3.So you need to enable it.
If you can specify the model of your motherboard I can help you further. :)
I just installed Visual Studio 2013 Community Edition on Windows 8 and when I go to create a new project, all the apps I see are for Silverlight.
Is this how it should be or did I miss some SDK or something?
You can't target WP8.1 on Windows 8 - you need Windows 8.1.
WinRT apps (i.e. non-Silverlight) on Windows Phone are only compatible with Windows Phone 8.1.
Upgrade Windows to 8.1, and make sure you also have the latest WP8.1 SDK installed.
Basically your dev machine's Windows version must at least match the target Windows version (including Windows Phone).
I have an existing project built in Visual Studio 2012 with VC++, which works fine on Windows 7 or higher versions. But when running on Windows XP, it gives an error that the application needs .NET framework v4.0 or higher to run. I am unable to install .NET Framework v4.0 on that system either.
So, the problem is that I want to downgrade my project's Target Framework Version, and I could not find any way to do it in Visual Studio 2012 - Windows Forms Application project.
Is there an alternate or better solution?
You must compile two applications, one for Windows 7 or higher and one for lower than Windows 7.
For changing your application .NET Framework follow the below address
[On Menu Bar]
Project -> "Your Application Name" Properties -> Application
And change
"Target Framework"
I am trying to install Microsoft SQL Server 2008 on my 64-bit Windows XP operating system. Unfortunately, I need Windows Installer 4.5 to do this, and Windows Installer doesn't seem to run on 64-bit Windows XP. Is there a way around this?
It is actually supported on Windows XP 64-bit.
Windows XP 64-bit is Windows Server 2003 in disguise (but they often forget to mention Windows XP 64-bit - for instance, PowerShell 2.0 can actually be installed on Windows XP 64-bit). Thus locate "WindowsServer2003-KB942288-v4-x64.exe" (direct download URL), download and install.
I have a .NET WinForms application that I've converted into a COM dll using the Interop Forms Toolkit 2.1. Thet setup project for the application has both my tlb as well as the Microsoft.InteropFormTools.tlb file set to Register as vsdrpCOM. The prerequisites for the project are to ensure that Windows Installer 3.1, .NET Framework 3.5 SP1, and the Microsoft Interop Forms Redistributable Package 2.0a is installed.
When I run this locally on a Windows XP box with both Visual Studio 2010 and Visual Studio 6 installed, it works fine. However, on this Windows XP machine, I receive an error stating: "Class does not support Automation or does not support expected interface."
Any ideas?
I got it. For those of you that are running into the same, do the following:
Go into Visual Studio 2005, 2008, or 2010 (I used 2010) and build your Interop Form.
Then, go into Visual Basic 6. If your library is not already referrenced, reference the
library.
Build your VB6 executable.
Go back into Visual Studio (.NET version) and build only your installer. This way the installer and VB6 both have the same .tlb file
You're good to go. Thanks for the suggestion Kris!
You have RegAsm the assembly (see stackoverflow for more) on the machine you want to install the application on. The assembly should also be in the directory where the VB6 application runs, or installed in the GAC.