Only Content controls are allowed directly in a content page that contains Content controls

Question

0.00/5 (No votes)

See more:

I have a site that I previously developed in VWD 2008 and for reasons associated with a dying computer I am moving everything to a new box and to VWD 2010.

Nearly all the pges are using a MasterPage most of which contain two <ContentPlaceholder> tags: one for the head and one for the body.

On most pages the only content in the header <content> is a <Meta> tag with the pages description for search engines to find. This has been working fine since the site was first posted in 2009 and the production site with that code, which has been moved to an IIS7 server with .Net4, is also still workng just fine.

However, when I try a site build in VWD 2010 I get the error mentioned in the title everywhere and they are pointing at the <Meta> tag in the header! This is despite the fact that the <Meta> tag is correctly located inside <Content> tags and the <Content> tags are correctly aligned with their respective <ContentPlaceholder> tags in the MasterPage.

Any suggestions would be gratefully recieved - I don't want to have to modify every page to remove the declarative <Meta> tag and replace it with something programmatic. This code is in the page templates I use to build the site and it has been fine until this week, the new machine and VWD 2010!!

Thanks

Alistair

Posted 31-Jul-12 9:45am

agillanders

Updated 31-Jul-12 9:50am

v2

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Dan Steuer · Accepted Answer · 2012-07-31T10:01:00

Solution 1

I cont see any code, very difficult to guess what is going on here... can we see example code from one of the content pages?

In some cases unrelated issues can cause VS to incorrectly parse the page and give this error, if you can, try to remove all content from a content page and just run with a try/catch in the code behind to see if one of your assemblies needs to be updated...

Posted 31-Jul-12 10:01am

Dan Steuer

Comments

agillanders 31-Jul-12 16:42pm

THANK YOU

...unrelated issues can cause VS to incorrectly parse the page and give this error...

That was the secret...I plowed through the forest of error messages and low and behold one jumped out that was unrelated. I still had the links in my development web.config for some playing I had done with the release of the .Net 3.5 Data Visualization component - which of course is now a core part of the .Net 4 framework and in the GAC.

I removed the tagprefix configuration for:
<add assembly="System.Web.DataVisualization, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" namespace="System.Web.UI.DataVisualization.Charting" tagprefix="asp">
And magically everything is compiling again!

Good catch.

Dan Steuer 31-Jul-12 16:54pm

Gotta love those unrelated items... caught me more than a few times. Glad it helped.