Kevin and Patrick,

If I coud add on more to this; HTML View Intellisense requires an XSD schema that describes the control in question. For example you can find such file that is done for built-in ASP.NET controls. The file is asp.xsd and you can find it in VS.NET's folders. See it for example how such schema is done. After you have the schema you would need to set it into VS.NET's folders (the same where you'll find this schema that is $VSNET Folder$\Common7\Packages\schemas\xml) for it to work.

Here is also some articles that covers this topic:
http://www.ondotnet.com/pub/a/dotnet/excerpt/aspdotnetian_6/index3.html?page=4

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vsintro7/html/vxconAuthoringandUsingCustomSchemasBackgrounder.asp


>Patrick,
>
>>Is intellisense supposed to work in the HTML view of an .aspx file for components? Say, ?
>>
>>Also, the properties window doesn't follow components in HTML view, only in Design view.
>
>I just talked about this with resident Wizard of the Web (W.O.W), Rick Strahl, and he said:
>
>Intellisense only works on built-in components, not on custom components. Not even inherited properties. Problem is that MS is doing the Intellisense of the schema.
>
>Regards,

-----------------------------------------

Cathi Gero, CPA
Prenia Software & Consulting Services
Microsoft C# / .NET MVP
Mere Mortals for .NET MVP
cgero@prenia.com
www.prenia.com
Weblog: blogs.prenia.com/cathi