I've a small problem regarding pack-uri's in my application, this involves inconsistencies during runtime and design time.
During design-time I am able to use relative uri - what i presume to be relative to local assembly i.e. pack://application:,,,/Resources/add_small.png but during runtime the image is never displayed. I've found a way to work around this matter by referencing
the assembly itself in the uri i.e. pack://application:,,,/BluewaterFishing.Package.Basic;component/Resources/add_small.png
Recently I've been trying out visfire products as a charting solution and I stumble on the same type of constancies between design- and run-time. During design time the charts display normally and during runtime a exception is thrown "A first chance
exception of type 'System.Windows.Markup.XamlParseException' occurred in PresentationFramework.dll. Additional information: Set property 'System.Windows.FrameworkTemplate.Template' threw an exception."
In terms of product setup, I'm closely following the traditional Microsoft conventions as seen in their products: Visual Studio, Exchange Server. I'm using the following path layout seen below. In my application I'm using the main executable as a boot-strapper
for the different modules. The problems occur in such a module.
View Complete Post