[Bug] XAML: DynamicResource

Hello,

ReSharper shows blue squiggly for a {DynamicResource MyResource} when MyResource does not exist. But that is precisely why I use DynamicResource here : to defer the lookup to run-time, because the resource will only be available later. I suggest to have this warning removed. This behavior is completely correct for StaticResource however.

This leads me to a question : when will XAML context actions will be configurable, like C# and standard XML are?
I'm also looking for more intellisense automatic completion in XAML files. Ctrl+Space works like a charm in most cases, but having Intellisense while typing like in C# would really be great.

Performance improvements in this area will be a top one too. I always edit my XAML files on XAML-mode only (I found the Visual Studio designer to be so slow and useless - even with SP1 - compared to typing everything; I use Blend when I really need a designer) and even without the designer, the performance is just awful on a 2000 lines file on good hardware. This file is a resource dictionary containing styles and templates for everything in my application, and is far from complete. It's just painful to edit due to the frequent lags which make working with it frustrating. Note that unlike some people, I have absolutely no performance problems with C# alone, even with solution-wide analysis enabled. I can't split the file much due to the way resource dictionaries work - ie. include a shared dictionary in two other dictionaries and every object it contains will be loaded twice in memory.

Thanks,

--
Julien

2 comments
Comment actions Permalink

I second the removal of the blue squiggly for DynamicResource's.

"MrJul" <no_reply@jetbrains.com> wrote in message
news:71050.169811217369788161.JavaMail.jive@app4.labs.intellij.net...

Hello,

>

ReSharper shows blue squiggly for a {DynamicResource MyResource} when
MyResource does not exist. But that is precisely why I use DynamicResource
here : to defer the lookup to run-time, because the resource will only be
available later. I suggest to change this remove warning, completely true
for StaticResource however.

>

This leads me to a question : when will XAML context actions will be
configurable, like C# and standard XML are?
I'm also looking for more intellisense automatic completion in XAML files.
Ctrl+Space works like a charm in most cases, but having Intellisense while
typing like in C# would really be great.

>

Performance improvements in this area will be a top one too. I always edit
my XAML files on XAML-mode only (I found the Visual Studio designer to be
so slow and useless - even with SP1 - compared to typing everything; I use
Blend when I really need a designer) and even without the designer, the
performance is just awful on a 2000 lines file on good hardware. This file
is a resource dictionary containing styles and templates for everything in
my application, and is far from complete and it's just painful to edit due
to the frequent lags which make working with it frustrating. Note that
unlike other peoples, I have absolutely no performance problems with C#
alone, even with solution-wide analysis enabled. I can't split the file
much due to the way resource dictionaries work - ie. include a shared
dictionary in two others dictionary, every object in it will be twice in
memory.

>

Thanks,

>

--
Julien


0
Comment actions Permalink

I agree about the blue squiggly for unresolved DynamicResource references.
I also posted an inquiry about improved XAML intellisense support in the EAP
newsgroup on 21 July, but it has yet to receive a response.

Mike

"Oren Novotny" <oren.novotny@community.nospam> wrote in message
news:g6o607$sem$1@is.intellij.net...
>I second the removal of the blue squiggly for DynamicResource's.
>

"MrJul" <no_reply@jetbrains.com> wrote in message
news:71050.169811217369788161.JavaMail.jive@app4.labs.intellij.net...

>> Hello,
>>
>> ReSharper shows blue squiggly for a {DynamicResource MyResource} when
>> MyResource does not exist. But that is precisely why I use
>> DynamicResource here : to defer the lookup to run-time, because the
>> resource will only be available later. I suggest to change this remove
>> warning, completely true for StaticResource however.
>>
>> This leads me to a question : when will XAML context actions will be
>> configurable, like C# and standard XML are?
>> I'm also looking for more intellisense automatic completion in XAML
>> files. Ctrl+Space works like a charm in most cases, but having
>> Intellisense while typing like in C# would really be great.
>>
>> Performance improvements in this area will be a top one too. I always
>> edit my XAML files on XAML-mode only (I found the Visual Studio designer
>> to be so slow and useless - even with SP1 - compared to typing
>> everything; I use Blend when I really need a designer) and even without
>> the designer, the performance is just awful on a 2000 lines file on good
>> hardware. This file is a resource dictionary containing styles and
>> templates for everything in my application, and is far from complete and
>> it's just painful to edit due to the frequent lags which make working
>> with it frustrating. Note that unlike other peoples, I have absolutely no
>> performance problems with C# alone, even with solution-wide analysis
>> enabled. I can't split the file much due to the way resource dictionaries
>> work - ie. include a shared dictionary in two others dictionary, every
>> object in it will be twice in memory.
>>
>> Thanks,
>>
>> --
>> Julien


0

Please sign in to leave a comment.