Insane number of tags added when creating Local Resource

[Oscar Emiliano]

Hi Telerik Team,

I has been working with Telerik Controls for the last months and there is something that still I can't feel as something good. When I create the Local Resource (resx) file for my aspx page, a lot of tags are added to the aspx, and of course a lot of local resources entries in the resx file. I do understand the entries created on resx file, but the number of tags become kind on insane in the aspx file, for example for a simple RadTextBox that was originally like this:

<telerik:RadTextBox ID="ttxtFirstName" runat="server" Width="100%" ></telerik:RadTextBox>
(I do not define Skin as it is set on web.config for all the telerik controls)

And after creating the local resource my aspx ends like this:

<telerik:RadTextBox ID="ttxtFirstName" runat="server" Width="100%" 
                                    LabelCssClass="" LabelWidth="64px" 
                                    meta:resourcekey="ttxtFirstNameResource1" Resize="None" 
                                    ResolvedRenderMode="Classic">
                                    <EmptyMessageStyle Resize="None" />
                                    <ReadOnlyStyle Resize="None" />
                                    <FocusedStyle Resize="None" />
                                    <DisabledStyle Resize="None" />
                                    <InvalidStyle Resize="None" />
                                    <HoveredStyle Resize="None" />
                                    <EnabledStyle Resize="None" />
                                </telerik:RadTextBox>

So, as you can see a lot of tags (and lines, because each tag is using one line of code) are generated and if you ask me, it doesn't look simple and even can break the low "beauty" of the code that we can have.

Is this completely necessary?, when a local resource for a ASP.NET textbox is generated the only thing added to our code is the metarsourcekey. Is there a way to create the local resource different from using option inside Tools Menu that could be used to avoid this?

I will leave aside the number of entries generated in resx file, just cause those can be ignored or removed. But what bothers me is to mess up with the code, even if it is the aspx file.

Consider that we could have very long forms where the number of controls can be large and adding around 10 lines per each control is not pretty. Hope that you could share a solution.

Regards,

Oscar Ramirez

[Ianko]

Hi Oscar,

The same matter is already reported. You can find the same results discussed in this forum thread.

The described behavior is still being in research and a solution has not been found yet.

Regards,
Ianko
Telerik