| Key: |
RSRP-53493
|
| Type: |
Bug
|
| Status: |
Closed
|
| Resolution: |
Fixed
|
| Priority: |
Blocker
|
| Assignee: |
Sergey Coox
|
| Reporter: |
Jafin
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
ReSharper
Created: 27 Nov 07 05:10
Updated: 28 Nov 07 16:30
|
|
| Component/s: |
Language - ASP.NET
|
| Fix Version/s: |
3.1
|
|
Security Level:
|
Everybody
(All jira users)
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
|
Most stock microsoft asp.net controls support passthrough of attributes. For example, you can add an "onclick" attribute to an <asp:CheckBox ... /> control and it will be properly rendered. RS, however, complains and paints it red (message "Cannot resolve symbol 'onclick'"). I think at most this should be a yellow warning.
|
|
Description
|
Most stock microsoft asp.net controls support passthrough of attributes. For example, you can add an "onclick" attribute to an <asp:CheckBox ... /> control and it will be properly rendered. RS, however, complains and paints it red (message "Cannot resolve symbol 'onclick'"). I think at most this should be a yellow warning. |
Show » |
|
CLONE -Cannot resolve symbol 'onclick' on asp.net controls
It appears to occur when the web.config contains the following line:
<controls>
..
<add tagPrefix="asp" namespace="System.Web.UI.WebControls" assembly="System.Web.Extensions, Version=3.5.0.0., Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
..
</controls>
Removing the ajax control prefix from web.config returns the OnClick functionality (as well as other eventing information back to the IDE.