Tell me more ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.
up vote 0 down vote favorite

This used to work fine, and I'm guessing it's because we had a web project with the web.config in the project itself.

With a sharepoint solution in visual studio, we had a tag declared in the (iis web 80 folder) web.config like:

<add tagPrefix="ourControls" namespace="MyProject.WebControls" assembly="MyProject.WebControls, Version=1.0.0.0, Culture=neutral, PublicKeyToken=xxecf07b2ad6582c" />

but when you create a tag for a control in a user control markup file it is not recognised and you need to declare the prefix at the top of every user control instead

this means the designer files can't work properly, and the code fails as we have loads of not declared protected control variables.

ive tried just adding the the web.config to the root of the deployment project and have tried the same with an App.config to no avail.

any work around?

share|improve this question
Hi There. What you are trying to do, should work. I think the issue is a Assembly reference typo or a different Public key token. So I suggest is that you remove the markup from your controls and add only to the web.config. Then, try and access the control and check your ULS Logs (Use ULSVIEWER) and try and figure out what the exception is. – Fox Jul 15 '11 at 9:43
Have you tried @Fox's suggestion? Do you have any more information you can provide? – Alex Angas Jul 27 '11 at 3:12
Its certainly not a typo, the token is the same when copied to the usercontrol directly and works. The other instructions don't really make sense – BobTodd Aug 2 '11 at 15:16

Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.