Comments on R# 2.0

1. File structure and unit test should be able to remember where it was last placed and show up in the right location next time vs.net starts
2. Unit test still pop up "Not intended to use" from NUnitFixture sometimes and trying to show R# code that throws an exception.
3. Unit test should be able to detect code changes in dependent projects and ask user whether they want to rebuild them before running unit tests
4. Code warning should not apply to code generated by .NET e.g. full namespace when declaring GUI controls, redundant cast for (ISupportInitialize), etc.
5. file structure and unit test window still miss nice icons :)

3 comments
Comment actions Permalink

1. File structure and unit test should be able to remember where it was
last placed and show up in the right location next time vs.net starts


Aren't they?

2. Unit test still pop up "Not intended to use" from NUnitFixture
sometimes and trying to show R# code that throws an exception.


Please clarify. What do you mean?

3. Unit test should be able to detect code changes in dependent projects
and ask user whether they want to rebuild them before running unit tests


If you run tests from gutter mark, the assembly will be rebuilt
If test is run by the green arrow in the UnitTest runner local toolbar, the
assembly will not be rebuilt.

This behavour is by design

4. Code warning should not apply to code generated by .NET e.g. full
namespace when declaring GUI controls, redundant cast for
(ISupportInitialize), etc


These warnings are not shown for the code wrapped into regions with some
predefined names (for eample "Windows Form Designer generated code").

There are no other ways for us to check if the given piece of code is
generated or manually coded

5. file structure and unit test window still miss nice icons :)


Yes, they are. This will be fixed

--
Eugene Pasynkov
Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0
Comment actions Permalink

>> 1. File structure and unit test should be able to remember where it was
>> last placed and show up in the right location next time vs.net starts

Aren't they?


Seeing this aswell.

>> 4. Code warning should not apply to code generated by .NET e.g. full
>> namespace when declaring GUI controls, redundant cast for
>> (ISupportInitialize), etc

These warnings are not shown for the code wrapped into regions with some
predefined names (for eample "Windows Form Designer generated code").

There are no other ways for us to check if the given piece of code is
generated or manually coded


The ability to add an attribute (resharper supplied) or setup special identifier region prefixes would be nice so that we can disable some of our own regions aswell.

Jesse

0
Comment actions Permalink

1. File structure and unit test should be able to remember where it was
last placed and show up in the right location next time vs.net starts


Aren't they?

--> It still shows as floating toolbar every time

2. Unit test still pop up "Not intended to use" from NUnitFixture
sometimes and trying to show R# code that throws an exception.


Please clarify. What do you mean?

3. Unit test should be able to detect code changes in dependent projects
and ask user whether they want to rebuild them before running unit tests


If you run tests from gutter mark, the assembly will be rebuilt
If test is run by the green arrow in the UnitTest runner local toolbar, the
assembly will not be rebuilt.

This behavour is by design

4. Code warning should not apply to code generated by .NET e.g. full
namespace when declaring GUI controls, redundant cast for
(ISupportInitialize), etc


These warnings are not shown for the code wrapped into regions with some
predefined names (for eample "Windows Form Designer generated code").

--> I have code covered with
#region Component Designer generated code
or
#region Form Designer generated code

It still optimizes away those namespaces inside InitializeComponent()


There are no other ways for us to check if the given piece of code is
generated or manually coded

5. file structure and unit test window still miss nice icons :)


Yes, they are. This will be fixed

0

Please sign in to leave a comment.