Edited by Nancy Michell
MSDN Magazine June 2001
View Complete Post
Based on the turotial, it mention that if my sitemap have more than 150 node it will have impact on the performance.
Is the any option if i do have more than 150 mode to include in the xml file (with security node trimming=true, where i inserted role=ABC in every node.)
If the first Sitemap node is your homepage/default and all other nodes are supposed to be children / grandchildren of the first sitemap node in a web.sitemap, how do I set up my web.sitemap to enable me to display my cssFriendlyMenu with the homepage node along with the nodes that are 1 level down from it at the same time as in :
Home Products Services About us
...or is it not possible to have the first sitemap node displayed along with the nodes that are 1 level down from it? Do I need to have a different starting node rather than my homepage node?
I'm positive that, by now, a lot of people have run into this problem but even with all the forum posts with great answers, I still can't seem to get to the bottom of it. Here are some specs:
So here's the issue:
I have VS2008 installed on the server listed above. This is our development server and everything is created and tested here. I have created an asp.net application, tested it on the dev. environment and everything works great. When I try to migrate this application up to our Quality Assurance environment (which is Windows Server 2003), I get the error in the subject title.
I've read many things that can be the cause of this and I'm positive that I know 2 ways of fixing it. One is from this post: Simple web site problem on Vista, related to <providerOption>, and the other is making sure 3.5 framework is at least installed on the server in question. There are 2 reasons why I'm unable to use these 2 methods: