Hi Dave,
Apologies for taking so long to respond to your post. If you are still interested in digging into this, I'd like to help.
Frankly, I'm not sure what the problem might be. I need you to post more details. Perhaps you can provide the markup and code you are trying to use. Also, it would help to see the exact error messages you are getting.
I tried an experiment that seemed to show that the adapted TreeView can live on a simple master page. Here is what I tried:
- After installing the CSS friendly adapter kit, I used VWD to create a new web site based on the kit's "ASP.NET CSS Friendly Web Site" template.
- In the Walkthrough folder I make a copy of SimpleTreeView.aspx and called that copy SimpleTreeView.master.
- In this new master file I changed the @Page directive to @Master. Then, just before the close of the FORM element I added a content placeholder that looked like this:
<asp:contentplaceholder id="ContentPlaceHolder1" runat="server">
</asp:contentplaceholder>
Now I created a new page within the Walkthrough folder and called it test.aspx. Its content looks like this:
<%@ Page Language="C#" MasterPageFile="~/WalkThru/SimpleTreeView.master" Title="Untitled Page" %>
<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" Runat="Server">
This is a test
</asp:Content>
When I run this page everything works as I would expect. I see the TreeView from the master page and I see the "this is a test" text that was added through the content placeholder. I don't have any error messages or other problems.
I realize that this is a pretty simple test. Maybe it works because it is too simple! Still, it provides a good data-point to establish that fundamentally master pages and adapted TreeView instances are compatible at some basic level. Let's see how this differs from what you are trying to accomplish.
Best regards,