2 comments

Hello Ilya,

Thank you for logging the issue. However, I am EXTREMELY disappointed to
see that it has been slated not to be fixed in v4.5. I first reported this
problem with the 3.0 beta (it worked fine in v2.5), and I simply cannot believe
it still has not been addressed. This should be a CRITICAL as it causes
many false negatives which breaks or makes unreliable all the major features
of ReSharper (e.g. Intellisense, Refactorings, Find Usages, etc). Simply
saying "This cannot be supported with the current Architecture" from release
to release is just not acceptable.

As I stated before, our company has several devs who have uninstalled ReSharper
because of this problem. Please reconsider fixing this in v4.5. Its not
even in beta yet, there should be the time to address the issue.

~Andy

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-90813.

You may want to check our request tracking policy here:
http://www.jetbrains.net/confluence/display/ReSharper/ReSharperIssue
Tracker

Best regards,
- Development Team.



0

Hello Andy,

I can understand your frustration, but we really can do nothing to fix it
in the available time before release of ReSharper 4.5. You see, ASP.NET code
generation is neither documented, nor logically inferrable in its dark corners.
We are mostly playing "read feedback, try it, guess how it should work" game
here and your feedback is extremely valuable to us. There are so many ways
people use and abuse the way ASP.NET engine generates code from markup files.
But, anyway, to support such kind of properties, like Header and Footer with
attributes applied we have to
make code generation multi-pass. Which is not possible right now.

As for ReSharper 2.5, I suppose there were no support for that kind of fields
at all and thus every field generated in outer class, like any other field
from aspx. That's why this particular case could work. We should check, actually,
how it was that time.

Sincerely,
Ilya Ryzhenkov

JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


AA> Hello Ilya,
AA>
AA> Thank you for logging the issue. However, I am EXTREMELY
AA> disappointed to see that it has been slated not to be fixed in v4.5.
AA> I first reported this problem with the 3.0 beta (it worked fine in
AA> v2.5), and I simply cannot believe it still has not been addressed.
AA> This should be a CRITICAL as it causes many false negatives which
AA> breaks or makes unreliable all the major features of ReSharper (e.g.
AA> Intellisense, Refactorings, Find Usages, etc). Simply saying "This
AA> cannot be supported with the current Architecture" from release to
AA> release is just not acceptable.
AA>
AA> As I stated before, our company has several devs who have
AA> uninstalled ReSharper because of this problem. Please reconsider
AA> fixing this in v4.5. Its not even in beta yet, there should be the
AA> time to address the issue.
AA>
AA> ~Andy
AA>
>> 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-90813.
>>
>> You may want to check our request tracking policy here:
>> http://www.jetbrains.net/confluence/display/ReSharper/ReSharper+Issue
>> + Tracker
>>
>> Best regards,
>> - Development Team.


0

Please sign in to leave a comment.