Generated_Code Classes Showing Up with Ctrl+N
Hello,
If I have a Silverlight 4 Project with a RIA Services Linked Project in my solution, and I press Ctrl+N, classes that are shared show up twice in my list and it's impossible to know which is which. Is there a way to filter this list?
Thank you!
Michael
Please sign in to leave a comment.
Hello Michael,
Could you please attach a small sample solution demonstrating this behavior?
Thank you!
Andrey Serebryansky
Senior Support Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
Hello,
I've attached the solution to this post along with a screenshot of the class name to test for.
Also, I will give you another good example here:
http://caliburnmicro.codeplex.com/SourceControl/changeset/changes/1296ea635677
This is a solution that I'm using. As you can see there are 3 projects: 1 for Native .NET, 1 for Silverlight, and 1 for Windows Phone. When you press Ctrl-N and search for "Message", you'll see that there are 3 of every class. It'd be nice to see from the Ctrl-N which project the file is in.
Thank you!
Michael
Attachment(s):
Simple.zip
Bug.png
Hello,
This appears to be addressed in ReSharper 6.0. That is, I can now clearly see the Assembly of the class I'm about to visit.
However, I would REALLY REALLY REALLY appreciate being able to ignore source (.shared.cs) files in the Generated_Code directory altogether. That is, when I CTRL-N or CTRL-B a symbol, that I would go to the *Source* (.shared.cs) file for the Generated_Code file.
Currently, when I CTRL-B a symbol that is Generated (.shared.cs), I am taken to the Generated_Code version. I would like to be taken to the *Source* (.shared.cs) version of that file.
Generated_Code files (that are shared.cs) should be completely ignored, as they are, um, generated, or rather copied from a source file. :) They provide extra noise that should be ignored altogether (since they have a corresponding source file).
I hope that makes sense.
ReSharper 6 looks really good. Great work. :)
Thank you,
Michael
Made a bug for this here:
http://youtrack.jetbrains.net/issue/RSRP-273305?projectKey=RSRP