Impressions of build 208

Hi,

I use build 208 on VS2005 (RC1) and these are my impressions so far:

- When a class implements an interface, and not all members of that
interface is implemented (correctly underlined) the action light bulb
does not show anymore. Also alt-enter does not work. This worked ok in 207.

- Still problems with partial classes. When a class is split in two
files (A and B). R# shows variables as unresolved when used in file A,
but defined in file B. After I open file B, and the file is parsed by
R#, suddenly the variables show OK in file A (not red any more). Same in
build 207.

- "Cannot access internal class". I see this warning sometimes on public
types that come from another project in my solution, and are not marked
internal or protected.

- The global keyword still cannot be resolved (for example
BackgroundImage = global::MyAssembly.Properties.Resources.MyFooImage;)

- Sometimes the "error highlight / analysis bar" next my text editor
scroll bar, is gone for some files, never saw that in build 207.

- The preparsing of the solution and it's assemblies when opening in VS
did not noticeably improve unfortunately. It's still needs a lot of time
for parsing / detecting changes for example on Microsoft.mshtml.

Besides these points 208 feels more stable and faster than 207, and
seems to be working reasonable ok in a large solution that made build
207 unusable because the error screen just kept popping up.

With kind regards,

Ward

2 comments
Comment actions Permalink

For who noticed: the protected keyword is only valid on member...so skip
protected in point 3 ;)

Ward Bekker wrote:

Hi,

I use build 208 on VS2005 (RC1) and these are my impressions so far:

- When a class implements an interface, and not all members of that
interface is implemented (correctly underlined) the action light bulb
does not show anymore. Also alt-enter does not work. This worked ok in 207.

- Still problems with partial classes. When a class is split in two
files (A and B). R# shows variables as unresolved when used in file A,
but defined in file B. After I open file B, and the file is parsed by
R#, suddenly the variables show OK in file A (not red any more). Same in
build 207.

- "Cannot access internal class". I see this warning sometimes on public
types that come from another project in my solution, and are not marked
internal or protected.

- The global keyword still cannot be resolved (for example
BackgroundImage = global::MyAssembly.Properties.Resources.MyFooImage;)

- Sometimes the "error highlight / analysis bar" next my text editor
scroll bar, is gone for some files, never saw that in build 207.

- The preparsing of the solution and it's assemblies when opening in VS
did not noticeably improve unfortunately. It's still needs a lot of time
for parsing / detecting changes for example on Microsoft.mshtml.

Besides these points 208 feels more stable and faster than 207, and
seems to be working reasonable ok in a large solution that made build
207 unusable because the error screen just kept popping up.

With kind regards,

Ward

0
Comment actions Permalink

- When a class implements an interface, and not all members of that
interface is implemented (correctly underlined) the action light bulb
does not show anymore. Also alt-enter does not work. This worked ok in
207.


Does it happen only when there are collapsed regions somewhere in the text?
In this case, this is a known problem and it will be fixed. But this problem
existed in the build #207 too.


- Still problems with partial classes. When a class is split in two
files (A and B). R# shows variables as unresolved when used in file A,
but defined in file B. After I open file B, and the file is parsed by
R#, suddenly the variables show OK in file A (not red any more). Same
in build 207.


I could not reproduce it on a simple example. Is it reproducable for you?
If yes, please submit request into the tracker and we will investigate it.


- "Cannot access internal class". I see this warning sometimes on
public types that come from another project in my solution, and are
not marked internal or protected.


Is this reproducable?


- The global keyword still cannot be resolved (for example
BackgroundImage = global::MyAssembly.Properties.Resources.MyFooImage;)


Will be supported in about 3-4 weeks.


- Sometimes the "error highlight / analysis bar" next my text editor
scroll bar, is gone for some files, never saw that in build 207.


Are errors in such files highlighted after the bar has gone?


- The preparsing of the solution and it's assemblies when opening in
VS did not noticeably improve unfortunately. It's still needs a lot of
time for parsing / detecting changes for example on Microsoft.mshtml.


Nothing has changed with this so far. The work of improving it (and changing
it to run in the background) is in progress and you can expect to see the
improved version in about 3 weeks.

Valentin Kipiatkov
Chief Scientist, Vice President of Product Development
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Hi,

I use build 208 on VS2005 (RC1) and these are my impressions so far:

- When a class implements an interface, and not all members of that
interface is implemented (correctly underlined) the action light bulb
does not show anymore. Also alt-enter does not work. This worked ok in
207.

- Still problems with partial classes. When a class is split in two
files (A and B). R# shows variables as unresolved when used in file A,
but defined in file B. After I open file B, and the file is parsed by
R#, suddenly the variables show OK in file A (not red any more). Same
in build 207.

- "Cannot access internal class". I see this warning sometimes on
public types that come from another project in my solution, and are
not marked internal or protected.

- The global keyword still cannot be resolved (for example
BackgroundImage = global::MyAssembly.Properties.Resources.MyFooImage;)

- Sometimes the "error highlight / analysis bar" next my text editor
scroll bar, is gone for some files, never saw that in build 207.

- The preparsing of the solution and it's assemblies when opening in
VS did not noticeably improve unfortunately. It's still needs a lot of
time for parsing / detecting changes for example on Microsoft.mshtml.

Besides these points 208 feels more stable and faster than 207, and
seems to be working reasonable ok in a large solution that made build
207 unusable because the error screen just kept popping up.

With kind regards,

Ward



0

Please sign in to leave a comment.