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

Key: RSRP-32269
Type: Bug Bug
Status: Investigating Investigating
Priority: Major Major
Assignee: Sergey Coox
Reporter: Oskar Austegard
Votes: 0
Watchers: 1
Operations

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

MasterType directive issue resurfaced in build 301

Created: 21 Nov 06 21:37   Updated: 14 Dec 07 17:24
Component/s: Language - ASP.NET
Fix Version/s: 3.1.1
Security Level: Everybody (All jira users)

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown

Build: 301


 Description  « Hide
The bug that prevents ReSharper from "seeing" properties of a strong typed MasterPage, which Sergey Coox reported as fixed on Sep 09 (http://www.jetbrains.net/jira/browse/RSRP-22460 et al) is showing up in build 301:

In the aspx page I'm getting an unexpected Token error at the @ sign of <%@ MasterType VirtualPath="~/WorkflowTask.master" %>

In the cs file I 'm getting RS errors when I refer to public members of the WorkflowTask class.

It doesn't matter if I use the VirtualPath or TypeName attribute, either way VS compiles without error, but RS 301 barfs.



 All   Comments   Work Log   Change History      Sort Order:
Sergey Coox - 22 Nov 06 10:16
could you create a small sample solution for us? The most probable reason is that we don't find WorkflowTask.master for some reason.
Maybe, the root folder of your website is configured to other place, than project root.