Element '[xxx]' is not a known element?!

[Ahrensberg]

Hi guys,

I'm often get the "Element '[xxx]' is not a known element"-warning in VS 2008.

I have added the line beneath, the site built and all works fine, but there is just no intellisense.

<%@ Register TagPrefix="telerik" Namespace="Telerik.Web.UI" Assembly="Telerik.Web.UI" %>

I've found the thread which probably should be the same problem, but since it is recommend in another thread (which I can't found now) not to do it this way and I besides this doesn't know where to find my PublicKeyToken, I wan't to hear if there are any other ideas.

Some times the intellisens is there and some times it isn't.

[Veselin Vasilev]

Hi Ahrensberg,

Does the Bin folder and the Telerik assembly resides locally on your machine?

The problem can occur if the files are on a shared network location. 

Kind regards,
Veselin Vasilev
the Telerik team

Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.

[Ahrensberg]

Hi Veselin,

Yes, both bin-folder and Telerik assembly resides locally...?

Best regards,
Kenneth

[Veselin Vasilev]

Hi Ahrensberg,

Do you use 2009.2.826 version? Please make sure there are no references to any older versions.
Also, check for any references to the Telerik.Charting assembly - you do not need these. 

All the best,
Veselin Vasilev
the Telerik team

Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.

[TonyG]

This seems to be a very common topic but the answers we see are always in terms of solutions to specific issues, without a definitive document somewhere stating "here is how Telerik Corp recommends the environment to be configured". Most web pages and forum postings here tell how to change from v1 to v2, and it's very difficult (impossible?) to filter out old and useless information on this site from that which is current and pertinent.  I wish we could include our version like "2009.3" in searches and just get results that apply to the current release, before we start to back-track through lots of pages of results of issues that don't apply to current releases anymore.

OK, back on topic:  I used to put Register tags in all of my pages, but of course upgrading that is a royal pain.  I uninstalled the 2009.2 trial when I bought 2009.3, removed all the Register tags, and use the Upgrade context menu option to upgrade my VS project.  I also have squiggly lines all over my ASPX markup now, and "not a known element" errors.  After install of 2009.3 I find Telerik.Web.UI 2009.2.701.20 is still in the GAC. The assembly reference in my project points to the install directory (Bin35), where the DLL is 2009.3.1103.35 .

Should I GAC the DLL to avoid explicit versioning in Register tags?
Why is the old version still in the GAC but the new version isn't?
Should web.config include explicit version information under system.web/pages/controls/tagPrefix="telerik"?
I can make guesses but I'd rather see this info in a page dedicated to proper configuration for the current product.

Thanks for your time.

(Edit: BTW, I did GAC my 2009.3.1103.35 DLL and provide full version info at tagPrefix="telerik"... and the sqigglies are gone and IntelliSense is back, etc) I just don't know if that's the right solution or why the environment doesn't set that up for us.

[Schlurk]

I know that through most of my uninstalls/installs the GAC references tend to update, but there has been a few times where I had to use the steps outlined in this article in order to ensure that all references were pointing to the latest version. I think this GAC issue is something that occurs when the installer sees everything as OK from the GAC however the replacing step has messed up somehow. Like I said, I've only had to do this a handful of times and the rest of them have been taken care of through the installer.

[Kevin]

I love and 2nd the idea - "I wish we could include our version like "2009.3" in searches and just get results that apply to the current release, "

I love the suggestion and I think it would take some time to get it up and running, but make it a priority for Q2 2010!!

--Kdc