App broken moving from beta2 -> 3.0 rc1

I've had some pretty significant breaks in making the switch and yet have yet
found a good


Example

In beta 2 release, this worked (it sits in one of my resource dictionary
files and is used as the content of a button using a {StaticResource xxxxxxx}
statement./

<ControlTemplate x:Key="CloseOrderButtonIcon">
<Image Source="c:\\Program Files\\Icons\\closeorder.png"/>
</ControlTemplate>

The image file in question was never a resource in the project - just a file
on the hard disk that it picked up at runtime.

Then with .NET 3.0 rc1 (I didn't install anything between) the Image line
causes the thing to fail at runtime.

I'd be keen to know what the simplest equivalent is.



I have noticed other changes. i.e. stricter enforcement of other threads
not being able to write to UI controls directly. Anything that broke then
deserved to. But I do get messages about accessing things from the wrong
thread that really make no sense to me.

What I'm after is a really good breaking changes list but so far have not
found it.

--
Griff
(trying to make an industrial UI with XAML/WPF/c#)

Thanks to a helpful hint that it was my installation at fault, I found and
fixed the problem.

My WIC (Windows Imaging Component) files and somehow ended up as the wrong
version with all the CTP's I'd had installed.

Found Robert A. Wlodarczyk's Blog (MSFT) with the fix outlined.
http://blogs.msdn.com/rwlodarc/archi...25/607131.aspx

(It refers to beta 2 but the same fix works for 3.0 rc1).

All working again.











--
Griff
(trying to make an industrial UI with XAML/WPF/c#)


"Griff" wrote:

> I've had some pretty significant breaks in making the switch and yet have yet
> found a good
>
>
> Example
>
> In beta 2 release, this worked (it sits in one of my resource dictionary
> files and is used as the content of a button using a {StaticResource xxxxxxx}
> statement./
>
> <ControlTemplate x:Key="CloseOrderButtonIcon">
> <Image Source="c:\\Program Files\\Icons\\closeorder.png"/>
> </ControlTemplate>
>
> The image file in question was never a resource in the project - just a file
> on the hard disk that it picked up at runtime.
>
> Then with .NET 3.0 rc1 (I didn't install anything between) the Image line
> causes the thing to fail at runtime.
>
> I'd be keen to know what the simplest equivalent is.
>
>
>
> I have noticed other changes. i.e. stricter enforcement of other threads
> not being able to write to UI controls directly. Anything that broke then
> deserved to. But I do get messages about accessing things from the wrong
> thread that really make no sense to me.
>
> What I'm after is a really good breaking changes list but so far have not
> found it.
>
> --
> Griff
> (trying to make an industrial UI with XAML/WPF/c#)