XAML Code Highlights don't work at all in 2008

When I open up a XAML file in VS 2008, Resharper highlights just about every single node in red. I get the popup on just about every single node wanting to add a namespace into my XAML file. It doesn't seem to be reading the default xmlns namespace of http://schemas.microsoft.com/winfx/2006/xaml/presentation. Instead it wants to add a clr-namespace lookup for everysingle namespace contained in there.

Is there a setting I am missing? It happens on two different computers for me both running 3.1.584.3. I'm running Vista Ultimate on both boxes.

16 comments
Comment actions Permalink

Hello,

We appreciate your feedback.

The corresponding JIRA request has been created, and you are welcome to monitor
its status at http://www.jetbrains.net/jira/browse/RSRP-57154.

Best regards,
- Development Team.


0
Comment actions Permalink

Mark,

In red or with red squiggles?
Anyway, It is dead strange. Could you please download the most recent
nightly build, open the XAML project and send us the log file.

--
Sergey V. Coox
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"



0
Comment actions Permalink

Check out my other posting on January 17th called, "Bug in Code Analysis". I attached before and after screen shots. I will grab a log next time this happens and send it along. Some days it happens constantly and other days it may only happen once or twice.

0
Comment actions Permalink

I know this is an old post but this is still a problem. I also have this issue with the Xaml Analysis. It completely breaks any code analysis done even outside the XAML files like in the basic .cs files that are the partial classes this will make it so variables declared in XAML will not show up. I am using the latest Nightly Build from Resharper 4.0 number 763

This problem doesn't happen right out of the box. it seems to be a random occurrence however it always happens directly after ReSharper does some Assembly analysis.


I have worked with you all on this problem by sending code and other things over and over again since January and each time the responses from Jetbrains just stop coming after about a week of not being able to figure the problem out. So I am going to try again via the forums.

Regards,
Michael Hohlios

0
Comment actions Permalink

Michael,

I've just fixed a bug in XAML Analysis. The symptoms were^ after project
reload R# stops recognizing XAML types. Check out tomorrow's nightly build,
pls.
--
Sergey V. Coox
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0
Comment actions Permalink

Thank you... I will get the nightly build and let you know.

Regards,
Michael Hohlios

0
Comment actions Permalink

I just installed 765 and it worked the same as the others. I found I had a period of 1 hour of good analysis then it stopped and did the same thing as described in this forum.

Regards,
Michael Hohlios

0
Comment actions Permalink

Anyone else having this error?

0
Comment actions Permalink

Sergey - What bug number was this? I can't find a reference to your fix in JIRA so I can be sure the nightly has your fix. I also get beautiful red xaml files when it appears that the project is rescanned.

0
Comment actions Permalink

Robert,

I cannot point to the request precisely, but the problem was that after
project reload all WIFE type failed to resolve in default namespace.
I think, it is exactly your problem.
--
Sergey V. Coox
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
"Robert Kenyon" <no_reply@jetbrains.com> wrote in message
news:31887769.15061207157072111.JavaMail.jive@app4.labs.intellij.net...

Sergey - What bug number was this? I can't find a reference to your fix
in JIRA so I can be sure the nightly has your fix. I also get beautiful
red xaml files when it appears that the project is rescanned.



0
Comment actions Permalink

I pulled the latest nightly build this morning (678) and working with a new WPF project this afternoon I had the same issue occur. Everything looked great for a good while and then (I didn't notice what triggered this) all xaml based types went red. This seems to happen on any WPF project not just my "big one".

I tried to turn off the Resharper plugin and turn it back on, but that resulted in a crash when re-enabled (bug submitted, anonymously unfortunately). I understand that the cause of the bug was probably losing the XAML parsing - but maybe this will give some info to help.

Shutting down VS and reopening the project seemed to reset the parsing and everything looks ok. (Note, solution wide analysis was OFF when this happened).

Hope this helps to track it down as it is VERY annoying.

P.S. I can state that time has no bearing on this. It can be 1 minute or 30 minutes - but it doesn't seem to take long.

Edited by: Robert Kenyon on Apr 4, 2008 2:53 AM

0
Comment actions Permalink

Any new updates or ideas?

0
Comment actions Permalink

Michael,

Do you reload WPF project or maybe update it from version control before it
goes red?

--
Sergey V. Coox
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0
Comment actions Permalink

If I reload the project the red goes away for a while until it decides to scan assemblies.

If I get from version control the red goes away until it scans assemblies.


My routine is . Sync then open and once I am opened I dont sync or close projects or reload them until I have done what I wanted to do . It is doing this time that the red will appear.

0
Comment actions Permalink

Michael,
What do you mean by "scan assemblies"? When it happens?
Am I right saying, that you sync your project and start working - everything
is ok. You edit, build and run your code and at some moment it goes red?

--
Sergey V. Coox
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0
Comment actions Permalink

Scanning Assemblies is what ReSharper does from time to time. It seems to follow a build tho. In the bottom right hand corner of VS there is the Resharper Icon it will change to Scanning Assemblies at certain times. I have no idea when this occurs but it does and at that point to breaks the XAML processing (Goes red).

"You edit, build and run your code and at some moment it goes red?"

Yes but sometimes I don't even have to build or edit the code. I can just be viewing the code. Sometimes it is 1 hour sometimes it is about 10 seconds before it goes red.


Hope this helps

Michael Hohlios

0

Please sign in to leave a comment.