[Solved] Property builder adding UI: not telerik: in asp

[Simon Maystre]

After using the update wizard in Visual Studio 2008 SP1 to update to 2009.3.1208.35 when using the property builder any new items are added into the asp code start with UI: and not telerik: see example below: (notice existing items OK but new ones added through the property builder are added as UI:)

 

<telerik:RadAjaxManagerProxy ID="RadAjaxManagerProxy1" runat="server">

 

 

<AjaxSettings>

 

 

<telerik:AjaxSetting AjaxControlID="btnLogon">

 

 

<updatedcontrols>

 

 

<telerik:AjaxUpdatedControl ControlID="lblInvalid" />

 

 

<telerik:AjaxUpdatedControl ControlID="lblPasswordEmailed" />

 

 

</updatedcontrols>

 

 

</telerik:AjaxSetting>

 

 

<UI:AjaxSetting AjaxControlID="btnPasswordPrompt">

 

 

<updatedcontrols>

 

 

<UI:AjaxUpdatedControl ControlID="lblInvalid" />

 

 

<UI:AjaxUpdatedControl ControlID="lblPasswordEmailed" />

 

 

</updatedcontrols>

 

 

</UI:AjaxSetting>

 

 

</AjaxSettings>

 

 

</telerik:RadAjaxManagerProxy>

 

[Erjan Gavalji]

Hi Simon,

For some reason the IDE was unable to properly resolve the tagprefixes. We are researching for a fix for that behavior. Currently the workaround is to change the <control> registration in your web.config to contain the fully qualified assembly name of the Telerik.Web.UI assembly, e.g.

<add tagPrefix="telerik" namespace="Telerik.Web.UI" assembly="Telerik.Web.UI, Version=2009.3.1208.35, Culture=neutral, PublicKeyToken=121fae78165ba3d4" />

Please note, that you should add the exact version version of the Telerik.Web.UI assembly, which is located in the website bin folder.

Kind regards,
Erjan Gavalji
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.

[Simon Maystre]

I have now tried the above but still getting the same problem. Its not a major issue as I can just rename but slows things down slightly.

[Erjan Gavalji]

Hi Simon,

Indeed, while not a big problem, it is annoying and we prefer having this fixed. Unfortunately we were not able to reproduce it locally so far. I would be glad if you could open a formal support ticket (to keep your private information) and send us your project for a review.
If we are able to reproduce that locally, it would mean that some project setting is causing the problem and we would fix it as soon as possible. On the other hand, if we are not able to reproduce the problem with your project, that would mean that a Visual Studio/computer configuration is causing the problem, which will again shed some light.

Us it convenient for you to send us the project through a formal support ticket (including the Telerik.Web.UI assemblies)?

Looking forward to your reply,
Erjan Gavalji
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.

[Simon Maystre]

Erjan,

Sorry the issue seems to have resolved itself, I opened a different solution and saw that it was functioning as expected so re-opened the solution with the issue and this is now functioning correctly although i am sure I closed down VS completely and restarted again to test before.

Anyhow thanks for your quick responses.

Simon