When I try to open a page in Cider, I get a parsing error from my main application XAML.

Here's the error:

Error 1 Value '/Library;component/Skin/Default/SkinStyle.xaml' cannot be assigned to property 'Source'. C:\...\App.xaml 8 29

Here's the XAML:

<

Hi,

Please make sure that the component Library.dll is added in References.

Cider doesn't load resources from the library which is not part of the project system.

-Obaid

Hi,

I am having the same problem. We have created global shared resources within our application and are using a ResourceDictionary.

<Application x:Class="Waters.Acqusition.IssConsole.App"

xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"

xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"

StartupUri="HomePage.xaml">

<Application.Resources>

<ResourceDictionary>

<ResourceDictionary.MergedDictionaries>

<ResourceDictionary Source="WatersCommonBrushes.xaml" />

<ResourceDictionary Source="WatersCommonStyles.xaml" />

<ResourceDictionary Source="WatersCommonFonts.xaml" />

</ResourceDictionary.MergedDictionaries>

</ResourceDictionary>

</Application.Resources>

</Application>

When we open a XAML page in Cider that uses these resources, we get the error:

Error 1 Value 'WatersCommonBrushes.xaml' cannot be assigned to property 'Source'. C:\programs\IssConsole\IssConsoleGroup\IssConsole\App.xaml 9 31 Waters.Acquisition.IssConsole

All XAML is within the same csproj so it is not related to loading resources in a different dll.

Steve

Hi Steve,

I tested your scenario, it works fine at my end.

Please send me the project and I will have a look at it.

Obaid

Hi Obaid,

How can I E-Mail my zipped up project to you?

Steve

Hi Steve,

You can get my email now from my profile.

-Obaid

Both of these scenarios should work in the August CTP - are you using the August CTP?

mark

Yes, I am using RC1 of .Net 3.0 with the August CTP of Cider.

Steve

For now reporting bugs here is the quickest way to get a response. We monitor this forum pretty actively.

I'm not sure what the problem is. If you could email me a project that repro's the issue I'll take a look

mark

Hi Aaron,

The issue is, as of today we donot support resources imported thru project references (we will be in future releases).

So build the Library.dll seperately and include in the project as library reference. This will fix the problem.

I tested it on my end, it works !!!!

Without looking at the project I would say you have just found the other limitation - local assembly references.

We are working on a design that overcomes all the limitations of locked assemblies whether that's because of local, project or file references. However, it's not quite ready for primetime yet.

I hope that answers your question.