Re: Global application Masterpages and Intellisense
- From: Brock Allen <ballen@xxxxxxxxxxxxxxxxx>
- Date: Sun, 11 Jun 2006 22:06:19 +0000 (UTC)
Yes, this is a known bug in Visual Studio 2005. The official work around is to put back in the <@Page MasterPageFile="..." %> during development and then rmeove it prior to checking the file back into source control. I know, it's crummy. Anyway, they say it will be fixed in the next release.
-Brock
http://staff.develop.com/ballen
Hi all,
I Followed these steps :
1. Added a .master file with 3 contentplaceholder controls.
2. Added an aspx file with the @Page directive parameter
'MasterPageFile' set to my .master file.
3. Added an asp:Content in the page.
intellisense in my .aspx file worked and the application ran and
compiled correctly.
1. Deleted the 'MasterPageFile' parameter from @Page directive and
added <pages masterPageFile="locationofthe.master file" > under the
<system.web> node of the web.config.
I couldnt get the intellisense work for my .aspx pages and the
previous <asp:Content> controls are marked 'red'. Intellisense could
not recognize 'asp' namespace inside the .aspx file and intellisense
itself is compromised. However, i could compile entire solution and
the application still ran correctly.
Is this a bug ??
Thanks in advance.
.
- References:
- Prev by Date: Re: Master Page in Asp.Net
- Next by Date: Re: Master page/content page asp control ID's
- Previous by thread: Global application Masterpages and Intellisense
- Next by thread: Intercepting asp call and talking with Browser and IIS
- Index(es):
Relevant Pages
|