Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have an Asp.Net background and trying to learn Silverlight.
Can you explain, what is the difference between x:Name=”someName” in Silverlight, XAML and ID=”someID” in Asp.Net markup?
(If they both make a element unique, why one is called Name and the other is called ID ? )
I gather compatibility with ASP.Net was not one of the requirements considered when they designed Silverlight (which derived in turn from WPF) 🙂
“ID” is a very technical term whereas “Name” is a bit more human readable. They are after all just the matching name of a member of the code-behind class generated at compile time. ID as a term makes more sense for data keys etc.
Classic ASP, and then ASP.Net, date back to before WPF and way before Silverlight so the naming is going to be a bit more old-school. Being more recent the naming of most elements tends to be a bit more sensible in Silverlight (compared to ASP).
Note: This is all just my opinion based on working with all the above technologies for many years. Hope it helps.