Feedback Needed

As a follow up, I went in and tried to load a User Control via LoadControl
in the code behind as well as through the web.config. ReSharper 3.0 didn't
recognize any of them. Am I missing something? Is there any way for ReSharper
3.0 to recognize UserControls? I cannot reiterate how severe of a limitation
this is! I don't know how you could possibly advertise that ReSharper 3.0
supports ASP.NET if you ship with such basic functionality missing. This
all works fine in version 2.5.x.

~Andy

Hello Dmitry,

Yes, I am using <% Register to reference the user controls. What
other option is there? The only other way I know to do it is via a <%
Reference and then calling LoadControl in the code behind, but that is
something one typically only does when dynamically loading the
control. I suppose you can declare it in the web.config, but that
only makes sense for common UserControls that are used throughout the
site....I'm certainly not going to add an entry in my web.config for
every User Control in my site (there are over 100 of them).

If it is true that Resharper 3 does not support declaring user
controls via <% Register then that is a SEVERE limitation. I don't
understand how anyone could possibly use ReSharper on an ASP.NET
project until that is fixed.

~Andy

>> Hello Andy,
>>
>> are you using '<% Register...' tags to reference other User Controls
>> in your
>> code? If yes,
>> the problem is that ReSharper doesn't recognize such tags and
>> unfortunately
>> the fix will appear not earlier than in 3.0.1.
>> This is a kind of architectural issue, and we cannot fix it in 3.0.
>> Dmitry Shaporenkov
>> JetBrains, Inc
>> http://www.jetbrains.com
>> "Develop with pleasure!"
>>> Hello Sergey,
>>>
>>> I'm sorry it took me so long to get back to you. I was on vacation.
>>> I have verified that the bug still exists in RC1 and I have attached
>>> a
>>> sample solution. Please try to get this fixed before RTM as it is a
>>> MAJOR bug and renders Resharper 3 completely unusable for me (and
>>> probably anyone else doing ASP.NET development). I have also added
>>> a
>>> bug into the tracker for this (RSRP-43723).
>>> ~Andy
>>>> Andrew. it's dead strange. Could you create a small sample solution
>>>> for us.
>>>> You may email it to me directly to qx at jetbrains dot com.
>>>> Thanks in advance.

Hello Andy,

in version 2.5.x there were other problems that are solved now. Basically,
in version 2.5.x ReSharper considered the whole Web Site as a single
big project containing all the code (this is why this problem didn't exist
in 2.5.x in the first place - ReSharper simply considered the web control
to be a member of the same project as the page that references it). However,
it doesn't match reality, since a Web Site gets compiled into a set of assemblies
which reference each other. In particular, the '<% Register...>' tag implicitly
defines that the assembly containing the .aspx page references the assembly
containing the user control. This is exactly the dependency we cannot recognize,
and fixing this is non-trivial (it's not merely a bug - it's a missing functionality)
and certainly not possible in 3.0 (remember, we have the release today).
Unfortunately, the problem was discovered too lately - right before the RC
1. We'll fix it in 3.0.1 and I believe it will be one of the influencing
factors to start 3.0.1 EAP ASAP.

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

ReSharper 3.0 to recognize UserControls? I cannot reiterate how severe
of a limitation this is! I don't know how you could possibly advertise
that ReSharper 3.0 supports ASP.NET if you ship with such basic
functionality missing. This all works fine in version 2.5.x.

Yes, I am using <% Register to reference the user controls. What
other option is there?

Can't you register UserControls in web.config just like Microsoft does for
Atlas? I don't know how this would work if they are in the same "project"
as your website. Does anyone know?

]]>

I have to agree with Andy. This bug is just too much to accept. Neither I nor the rest of my team will even look at ReSharper again until this is fixed. We've decided to go with the tools from DevExpress rather than upgrade our ReSharper licenses.

Dmitry, you and the rest of your team seriously underestimate the negative effect of this bug. ReSharper 3.0 looks like a flop.

This scenario should work

--
Sergey V. Coox
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
"flipdoubt" <flipdoubt@nospam.com> wrote in message
news:da27a8e45e3cc8c9812c274810a6@news.jetbrains.com...
>> Yes, I am using <% Register to reference the user controls. What
>> other option is there?
>

Can't you register UserControls in web.config just like Microsoft does for
Atlas? I don't know how this would work if they are in the same "project"
as your website. Does anyone know?

>

<configuration>
<system.web>
<pages>
<controls>
<add namespace="Microsoft.Web.UI" assembly="Microsoft.Web.Atlas"
tagPrefix="atlas"/>
<add namespace="Microsoft.Web.UI.Controls"
assembly="Microsoft.Web.Atlas" tagPrefix="atlas"/>
</controls>
</pages>
</system.web>
</configuration>

>

Hello flipdoubt,

I tried registering the UserControl in the web.config but couldn't get it
to work.

~Andy

>> Yes, I am using <% Register to reference the user controls. What
>> other option is there?
>>

Can't you register UserControls in web.config just like Microsoft does
for Atlas? I don't know how this would work if they are in the same
"project" as your website. Does anyone know?

<configuration>
<system.web>
<pages>
<controls>
<add namespace="Microsoft.Web.UI" assembly="Microsoft.Web.Atlas"
tagPrefix="atlas"/>
<add namespace="Microsoft.Web.UI.Controls"
assembly="Microsoft.Web.Atlas"
tagPrefix="atlas"/>
</controls>
</pages>
</system.web>
</configuration>

I tried registering the UserControl in the web.config but couldn't get
it to work.

What kind of project is it: a Web Site or a Web Application? Does anyone
know how to register controls within the same assembly as the Web Application?

Also, when you say "[I] couldn't get it to work", how did it fail? Did the
project build and run but Resharper simply failed to understand the references?
Or did it fail to compile?

Here is a post from Scott Guthrie explaining how to register user controls in web.config. This may help.

http://weblogs.asp.net/scottgu/archive/2006/11/26/tip-trick-how-to-register-user-controls-and-custom-controls-in-web-config.aspx

Andrew,

We've just discovered, that if control is registered via web.config using
tagprefix asp, Resharper does not recognize it (I.e. it happens for AJAX
controls). The bug will be fixed in a critical bugfix update quite soon
after 3.0 release.

--
Sergey V. Coox
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Hello James,

Thanks for the info. I am aware of how to register user controls in the
web.config. However, ReSharper 3 does not recognize them even in the web.config.
In addition, the site I am currently working on has over 100 UserControls
to it would not be very practical to register them all in the web.config.
(it would only make sense for controls that are used in several places throughout
the site).

I am hoping that JetBrains is able to resolve this issue very soon. I can
not consider upgrading to 3.0 until they do (and I suspect many other ASP.NET
developers feel the same way).

~Andy

Here is a post from Scott Guthrie explaining how to register user
controls in web.config. This may help.

http://weblogs.asp.net/scottgu/archive/2006/11/26/tip-trick-how-to-reg
ister-user-controls-and-custom-controls-in-web-config.aspx