Vista - Go Live advice for WPF presentationframework system.io.ioexception

(presentationframework system.io.ioexception)
hi,
I was just doing our 3rd release of one of our
new XAML-WinFx based systems and as im getting (i thought)
more confident i started to pick the assembly files (.exe, .dll)
that went live to try to keep it tidier.

To save you the time it took me to figure this out
please always include the "en-US" sub directory,
in our system this holds a file called GenericResourceLibrary.resources.dll
and if not included you will get a generic error signature box (Jan CTP)
with presentationframework system.io.ioexception contained within it.

The Architecture:

The .Net solution inside the Visual Studio 2005 consists of 3 Generic and
re-usable projects
and a very WinFx-Application specific project which holds the logic of the
application.

The generic WinFx and XAML Libraries are :-

GenericNS
Holds visual XAML objects and their associated .cs C# code behind file.
GenericNSCodeOnly
Holds non-visual objects all .cs C# Classes and Interfaces that are
traditional Utility type re-usable objects
It is .Net 2.0 Framework based but has no specific XAML code in it.
GenericResourceLibrary
Holds re-usable XAML visual styles and the associated code behind file with
very specific XAML related classes.

This have been split off to gain compile speed benefit from not having to
re-build everything every time.
A change to a XAML related file can mean a lot of extra compiling if all in
one project.

Each project in the solution has a reference to the other in the normal way.

It was the last GenericResourceLibrary that obviously caused my problems.

I hope this saves you time !

craig kelly-soens - Windows Vista WinFx XAML .Net Technical Evangelist
http://www.XpectWorld.com - customised "super-easy to use" Windows Vista
based .Net software & consultancy

To clarify: WPF follows the multi-lingual UI assembly model (MUI). In this
model for localized applications, language-neutral resources are embedded in
the main assembly (exe for application, dll for library) and
language-specific resources are embedded in a satellite assembly (if
UICulture is set as en-US in project file, then satellite assembly is
en-US\<application name>.resources.dll). All XAML (or BAML) is considered
language-specific. All resources are considered language-specific unless you
explicitly override that (using the <Localizable>False</Localizable>
metadata inside the <Resource> tag within the project file).

When you publish the application, you need to publish the satellite
assemblies as well. The Publish Wizard in Visual Studio will do this for
you, but if you're xcopying files over manually, this is worth noting.
Thanks, Craig for pointing this out.

--
Ashish Shetty [MSFT]
Program Manager, Windows Presentation Foundation (Avalon)
Blog: http://nerddawg.blogspot.com
---
This posting is provided "AS IS" with no warranties, and confers no rights.



"craig kelly-soens www.xpectworld.com"
<craigkellysoenswwwxpectworldcom@discussions.microsoft.com> wrote in message
news:96BB590B-DC3E-4FCA-AE14-A4C3495E49EE@microsoft.com...
> (presentationframework system.io.ioexception)
> hi,
> I was just doing our 3rd release of one of our
> new XAML-WinFx based systems and as im getting (i thought)
> more confident i started to pick the assembly files (.exe, .dll)
> that went live to try to keep it tidier.
>
> To save you the time it took me to figure this out
> please always include the "en-US" sub directory,
> in our system this holds a file called
> GenericResourceLibrary.resources.dll
> and if not included you will get a generic error signature box (Jan CTP)
> with presentationframework system.io.ioexception contained within it.
>
> The Architecture:
>
> The .Net solution inside the Visual Studio 2005 consists of 3 Generic and
> re-usable projects
> and a very WinFx-Application specific project which holds the logic of the
> application.
>
> The generic WinFx and XAML Libraries are :-
>
> GenericNS
> Holds visual XAML objects and their associated .cs C# code behind file.
> GenericNSCodeOnly
> Holds non-visual objects all .cs C# Classes and Interfaces that are
> traditional Utility type re-usable objects
> It is .Net 2.0 Framework based but has no specific XAML code in it.
> GenericResourceLibrary
> Holds re-usable XAML visual styles and the associated code behind file
> with
> very specific XAML related classes.
>
> This have been split off to gain compile speed benefit from not having to
> re-build everything every time.
> A change to a XAML related file can mean a lot of extra compiling if all
> in
> one project.
>
> Each project in the solution has a reference to the other in the normal
> way.
>
> It was the last GenericResourceLibrary that obviously caused my problems.
>
> I hope this saves you time !
>
> craig kelly-soens - Windows Vista WinFx XAML .Net Technical Evangelist
> http://www.XpectWorld.com - customised "super-easy to use" Windows Vista
> based .Net software & consultancy