Launching a WPF Application on Windows XP

I recently created a new application using WPF so that I can learn new technology. Now, when I try to deploy the application, it looks like it works fine on Vista, but on a Windows XP SP2 computer with .Net fx 3.5SP1 it cannot load the PresentationFramework.dll file.

I did some research on this and found that there is a slight build difference between the PresentationFramework.dll files on my xp test machines than on my Vista development machine.

I am wondering if anyone else might run into this problem and what they did to correct the situation so that they could develop in Windows Vista, but deploy the developed application for both Vista clients and XP.

Thanks.

I need to add a little to this ... on a Vista machine and on a client machine, I have .Net Fx 3.5 SP1. I did a little work and found out that the PresentationFramework.dll file is the same, except for the last set of version numbers.

Has anyone found a decent job for this problem?

+6
windows-xp windows-vista deployment wpf
source share
4 answers

Sorry I left this stagnation, but I realized what I was facing. It turned out that in the Windows XP box I used corruption, which I used as a test bed.

I worked between stackoverflow and another forum for the package I wrote the add-on to. When I found out about the answer, this is what I posted in case I encounter a problem in the future.

I thought I would post it here, so that I will have a link, and also in case someone else needs to link to it for the future ... I am working on an additional Dinerware add-on using WPF, and although it worked fine on to my development machine, each one I would go to run it on a test machine (a machine similar to the location field), I kept getting weird processing errors all the time.

I did hours of searching on the Internet, only walk up empty-handed until I ran into this article:

http://social.msdn.microsoft.com/Forums/en-US/wpf/thread/6e5de3d8-fc02-4504-b00f-7a2192d24a48/

which gives a link to download WIC (Windows Image Processing Components) located here:

http://www.microsoft.com/downloads/details.aspx?FamilyID=8e011506-6307-445b-b950-215def45ddd8&displaylang=en

For some reason, what happens / is that the components of Windows Imaging have become corrupt against what my application is looking for. To fix the problem, you should:

1) go to% Windir% \ $ NtUninstallWIC $ \ Spuninst \ and run the spuninst.exe file in there. This will delete the Windows image. 2) after you have completely removed the components, you will then reinstall them using the second link above.

So far I have not come across questions.

What a crazy thing that was?!?!?!?!?!? !!

Hopefully if someone else comes across this problem, I can help them quickly by> posting it there.

As I said on this forum ... I hope this helps someone else who faces this problem in the future.

+9
source share

I did a bit more experimentation and built a WPF test project and used the installation and deployment project instead of the WiX installer. for some reason, the application works fine when it is installed with the installer for installation and deployment, but when using WiX it has problems ...

To begin with, the problem is with WiX, not with .Net Fx version / build

+1
source share

You may have this problem sometimes with templates and Blend, although I thought it was fixed in the latest Blend. Basically, when Blend β€œdrags on” information to create a new template, it sometimes can only copy material from Vista to Aero, which means that the element you create then depends on Vista: - (

I really thought this was fixed, although although you may have been bitten by it if the project took some time to assemble.

0
source share

Verify that the .NET version on Vista and XP is the same.

0
source share

All Articles