WPF (Avalon) ReSharper support

The new Microsoft UI development technology WPF (formerly c.n. "Avalon") is about to release soon. It has support of XAML markup language and a code-behind files similiar to ASP.NET ones. The subject is when I am using ReSharper while editing this like code-behind file it naturally does not understand existing of XAML-generated partial class and treat usings particular ids (ui elements, etc) as errors. So it becomes practically unusable this way.
The simplest soluton would be supporting this like-generated files without any XAML/WPF intellisence tool (it is a whole new subsystem, I think).

9 comments
Comment actions Permalink

There is a workaround for this right now. You should just include the generated "obj" folder (it is placed under the project folder) that contains the generated files (*.g.cs). The best way to do this is to click "Show All Files" icon and then right click on the folder "Include in Project".

But it is best if the ReSharper supports this by default.

BTW: If I include/exclude/include this folder into the project the memory usage just grows every time.

0
Comment actions Permalink

Thanks for the reply. I will try to do so.

0
Comment actions Permalink

Jetbrains,

I'm facing the same situation with having to choose between XAML and Resharper.
I'm also looking at some of the Lambda expressions available for .NET 3.0,
but I admit that's far down the road. Any clarification on your roadmap
would be much appreciated.

Thanks,
Michael Hedgpeth

The new Microsoft UI development technology WPF (formerly c.n.
"Avalon") is about to release soon. It has support of XAML markup
language and a code-behind files similiar to ASP.NET ones. The subject
is when I am using ReSharper while editing this like code-behind file
it naturally does not understand existing of XAML-generated partial
class and treat usings particular ids (ui elements, etc) as errors. So
it becomes practically unusable this way.

The simplest soluton would be supporting this like-generated files
without any XAML/WPF intellisence tool (it is a whole new subsystem, I
think).



0
Comment actions Permalink

Just a note here.
Lambda expression will be part of C# 3.0 (.NET Fx 3.5), not .NET Fx 3.0.

0
Comment actions Permalink

I'm having the same problem too. Will this support be implemented? And if yes, when can that be expected to happen?

Thanks
- Marko Vuksanovic

0
Comment actions Permalink

Hello EugeneZ,

We are aware of the problem with XAML and looking into what can be done.
The decision will be made based on available resources to implement it, available
information and your votes in favor or against of supporting this new technology.
Without any doubt, next major release of ReSharper (v3.0) will support XAML
to some degree.

So, we are only looking into possibility to process generated files for v2.5,
we are not going to support refactorings, navigation, etc in the nearest
release. Currently, we are aproaching Feature Complete milestone for 2.5
and thus XAML support may shift timeframe, which we don't want to happen.
Any links and/or information about how VS2005 handles XAML are highly appreciated,
and can really change our mind in favor of giving XAML a try in 2.5 release.

Sincerely,
Ilya Ryzhenkov

JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


E> The new Microsoft UI development technology WPF (formerly c.n.
E> "Avalon") is about to release soon. It has support of XAML markup
E> language and a code-behind files similiar to ASP.NET ones. The
E> subject is when I am using ReSharper while editing this like
E> code-behind file it naturally does not understand existing of
E> XAML-generated partial class and treat usings particular ids (ui
E> elements, etc) as errors. So it becomes practically unusable this
E> way.
E>
E> The simplest soluton would be supporting this like-generated files
E> without any XAML/WPF intellisence tool (it is a whole new subsystem,
E> I think).
E>


0
Comment actions Permalink

That's great.
What I can tell is that the list of all generated files is placed in the obj folder (which is in the project's directory) and is called "NameOfTheProject.csproj.FileList.txt". Each file is on new line. But I'm not familiar if this feature is documented.

0
Comment actions Permalink

Hello Stefan,

Thanks for the info. We will look into it. If this file is populated on project
changes, if this "feature" is stable across various installations, if ...
well, so many if-s... :) We may give it a try, anyway.

Sincerely,
Ilya Ryzhenkov

JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


SD> That's great.
SD> What I can tell is that the list of all generated files is placed in
SD> the obj folder (which is in the project's directory) and is called
SD> "NameOfTheProject.csproj.FileList.txt". Each file is on new line.
SD> But I'm not familiar if this feature is documented.


0
Comment actions Permalink

Hello Ilya,

much as I'd like Resharper+XAML together, I'm more interested in a stable,
performant Resharper.

So my vote is to get 2.5 out the door on schedule, with at most some minor
measures to avoid e.g. keybinding conflicts and such, so that one doesn't
have to downright disable Resharper while working on WPF projects.

- Gulli


Hello EugeneZ,

We are aware of the problem with XAML and looking into what can be
done. The decision will be made based on available resources to
implement it, available information and your votes in favor or against
of supporting this new technology. Without any doubt, next major
release of ReSharper (v3.0) will support XAML to some degree.

So, we are only looking into possibility to process generated files
for v2.5, we are not going to support refactorings, navigation, etc in
the nearest release. Currently, we are aproaching Feature Complete
milestone for 2.5 and thus XAML support may shift timeframe, which we
don't want to happen. Any links and/or information about how VS2005
handles XAML are highly appreciated, and can really change our mind in
favor of giving XAML a try in 2.5 release.

Sincerely,
Ilya Ryzhenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

E>> The new Microsoft UI development technology WPF (formerly c.n.
E>> "Avalon") is about to release soon. It has support of XAML markup
E>> language and a code-behind files similiar to ASP.NET ones. The
E>> subject is when I am using ReSharper while editing this like
E>> code-behind file it naturally does not understand existing of
E>> XAML-generated partial class and treat usings particular ids (ui
E>> elements, etc) as errors. So it becomes practically unusable this
E>> way.
E>>
E>> The simplest soluton would be supporting this like-generated files
E>> without any XAML/WPF intellisence tool (it is a whole new subsystem,
E>> I think).
E>>


0

Please sign in to leave a comment.