Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Dec 19, 2008 11:19 AM by BartDeVries
Aug 22, 2008 10:20 PM|LINK
Aug 28, 2008 11:45 AM|LINK
I have looked at the work-around but did not manage to get my app working again(I cannot find how to make my dll or WPF start in XP compatible mode). Anybody else allready got his website up and running again using WPF?
Aug 28, 2008 01:26 PM|LINK
I have moved any WPF processing out of the website and into a separate service and then call this using remoting (with IPC). This seems to work very well and also gives us scope to move the image processing to separate machine(s) at some point if needed
so it's better from an architectural point of view.
It doesn't appear to use as much memory as it did when running under IIS 7.0 (maybe there was a leak?) and also seems more reliable.
I don't think it's possible to make IIS 7.0 itself run in XP compatibility mode as it's part of that version of Windows but you have more control over your own service.
Aug 29, 2008 02:08 AM|LINK
The workaround worked for us! But we're not using WPF with IIS, only in a normal Windows service.
Ultimately, though, this functionality should be added back into the framework and properly tested at Microsoft, because it always used to work just fine (up until .NET 3.5 SP1 was released), and it makes a great off-screen rendering component.
As a side note, it would also be nice if the Color and BitmapSource classes (amongst others) were serializable, so they could be transported over WCF without having to convert them into other structures such as byte arrays.
Aug 29, 2008 03:06 AM|LINK
I can confirm that we are trying to fix this particular issue.
Aug 29, 2008 06:16 AM|LINK
That would be great Gerhard, can't wait to get it!
Creating a seperate service and transport thourgh wcf is not really an option for every client.
Aug 29, 2008 10:01 AM|LINK
Actually I spoke too soon. The workaround does indeed work for us, but only on Windows Vista and Windows Server 2003. However in Windows Server 2008 64-bit - the main environment that we need to run it in - the workaround does NOT seem to work.
Was this workaround tested under Windows Server 2008? It's very possible that I've simply done something wrong at my end. But I've tried many things, including different compatibility modes, running the service as Local System (instead of Network Service),
and restarting the machine.
Does anybody know of any workaround for WPF-based services under Windows Server 2008 64-bit?
Sep 04, 2008 01:28 PM|LINK
Any progess on this? We're in dire straits!
Sep 09, 2008 07:26 AM|LINK
Do you allready have some updates on the progress?
Sep 09, 2008 05:05 PM|LINK
Yes, I have an update. According to the IIS7 team there is no good way to run IIS 7 in XP compatiblity mode. Till we have a fix, your best option is to stay on 3.5 if you have a dependency on WPF in your web service. The good news is that the fix is in testing
and has passed the first stage and should be available fairly soon.