797 Various Issues

I'm noticing a variety of somewhat minor but annoying issues in Build 797 as
well as other builds:

Giving an Intellisense list like Array, ArraySegment, and
ArrayTypeMismatchException, typing "array" (without the quotes) typically
results in ReSharper autocompleting with ArrayTypeMismatchException instead
of Array even though "array" and "Array" are a case-insensitive exact match.

Entering the name of a class or enumeration sometimes causes ReSharper to
autocomplete with the fully-qualified name for some reason. When a property
and a class or enumeration share the same name (e.g. public UserOptions
UserOptions { get; set; } causes ReSharper to always freak on the class or
enumeration name. I've been getting around this by pressing Esc to disable
ReSharper's autocompletion. A secondary case came up today in which the
namespace of a class wasn't referenced so ReSharper prompted to insert a
using statement. When I pressed Enter, ReSharper inserted the fully
qualified name (e.g. Blah.Domain.Order order = new Blah.DomainOrder(...))
instead of insert a using statement.

For some reason Intellisense became completely disabled, although I have no
idea why. I had stepped through a block of code, and when I stopped
debugging Intellisense was no longer working. Several minutes later it just
started working again for some strange reason. It's only happened once so
far.

I would love the ability to save reformatting/code cleanup options in
ReSharper's global configuration instead of in the project. I currently have
to create the same code cleanup template in every project/solution I open or
create.


1 comment
Comment actions Permalink

For the record, I've experienced this on occasion with ReSharper 3.x ...

"Lothan" <lothan@newsguy.com> wrote in message
news:g0loan$5gs$1@is.intellij.net...
>

Entering the name of a class or enumeration sometimes causes ReSharper to
autocomplete with the fully-qualified name for some reason. When a
property and a class or enumeration share the same name (e.g. public
UserOptions UserOptions { get; set; } causes ReSharper to always freak on
the class or enumeration name. I've been getting around this by pressing
Esc to disable ReSharper's autocompletion. A secondary case came up today
in which the namespace of a class wasn't referenced so ReSharper prompted
to insert a using statement. When I pressed Enter, ReSharper inserted the
fully qualified name (e.g. Blah.Domain.Order order = new
Blah.DomainOrder(...)) instead of insert a using statement.

>

0

Please sign in to leave a comment.