Why do my controls get different naming conventions?

Question

I have a gridview with the following template field

<asp:TemplateField> <ItemTemplate> <asp:Button ID="btnLoad" runat="server" Text="Load" CssClass="inptBtn" OnClientClick="return loadPlans(this);" UseSubmitBehavior="false" /> <ItemTemplate> </asp:TemplateField> 

This is working fine. In onclick, we run some code that checks the ID generated by .NET for this control and does everything with it. In the past, the generated identifier looked like this:

gvPlans_ctl02_hdPlans

This is still what is generated in our test environments, but in prod it now looks like this:

gvPlans_hdPlans_0

In both environments, the code is definitely the same, but I'm not sure what causes the naming convention to change. I tried to answer google, but the search terms are a bit generalized for this problem, so I will move on to reliable SO. I guess the answer may have something to do with what kind of infrastructure works or something like that. Please let me know if you have any ideas, thanks!

Answer 1

Read this , I think this will help.

Answer 2

This is controlled by the ClientIDMode property of the control:

• http://msdn.microsoft.com/en-us/library/1d04y8ss.aspx
• http://msdn.microsoft.com/en-us/library/system.web.ui.control.clientidmode.aspx

The default value for this can be configured in the web.config file:

• http://msdn.microsoft.com/en-us/library/950xf363.aspx

Or it can be set for the page in the @Page directive:

• http://msdn.microsoft.com/en-us/library/ydy4x04a.aspx

Answer 3

You can experiment with ClientIDMode if you are using .NET4. But in general, the generated cliend identifier should not matter. You should be able to use control.ClientID in javascript and other places, so as not to refer directly to the generated client identifier, in which case, even if there is a difference in creating a test server with a label created by markup, your code logic should be able to adapt.

Answer 4

Check the application pool for this application and the target environment. The target structure seems to be different between prod and dev / text env. Also check the installed frameworks and SP.