History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: RSRP-23708
Type: Bug Bug
Status: Closed Closed
Resolution: Cannot Reproduce
Priority: Blocker Blocker
Assignee: Sergey Coox
Reporter: James Hebben
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
ReSharper

RS intellisense may fails in content page when MasterType is set

Created: 06 Aug 06 15:57   Updated: 09 Sep 06 13:33
Component/s: None
Fix Version/s: 2.0.1
Security Level: Everybody (All jira users)

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
File Attachments: 1. Zip Archive ReSharper237MasterProblem.zip (2 kb)


Build: 237
Checked in Build: 248
Old URL: http://www.intellij.net/tracker/resharper/viewSCR?publicId=23708


 Description  « Hide
Seems if you use the MasterType directive in a content page to get a strongly typed Master property, R# intellisense will only work if the master page is called MasterPage.master.

Steps to reproduce

Create an ASP.NET project
Add a master page, and call it MasterPage2.master
Add a content page (accept default name)
in the Default.aspx.cs code (E.G. Page_Load method) type
Master. and you get intellisense.

Go to the Default.aspx page and add, as the second line:

<%@ MasterType VirtualPath="~/MasterPage2.master" %>

Go back to the Default.aspx.cs code, delete the Master. entry and retype Master.

After typing the . there is no intellisense.

(I also found that if you go through the same steps, but call the master page MyMasterPage, then R# intellisense picks up the strongly typed Master property as the base Master type. You get intellisense, but for the wrong type.)

Example source files attached.



 All   Comments   Work Log   Change History      Sort Order:
James Hebben - 09 Aug 06 11:57
Re: #23708- RS intellisense may fails in content page when MasterType is set
I am pretty sure that the intellisense was fine in build 236.

James Hebben - 09 Aug 06 11:57
Re: #23708- RS intellisense may fails in content page when MasterType is set
With build 248 I am also no longer able to repeat this; it seems to work fine now.