asp.net - repeater or listview vs concatenated html -

After spending a very small amount of time changing a page using contatted HTML such as

  string output = ""; Output + = " ul & gt;"; Forex Currency (in MyClass Item Mites) {Output + = "and Lt; Li> + Item Name + "-" + item Some Properties Toaster () + ""; } Output + = "& lt; / ul & gt;"; LiteralPlaceHolder.Text = output;  

To use the ListView control, I have just discovered that the original developer went back and changed the page to use a concerted HTML Gave. My personal impression is that list-review and repeater lend themselves to cleaner, more informative markup, which can be edited by someone with less experience with C #, and that they are faster and less memory At the very least the page should use stringbilders rather than string. Does anyone have a good argument for this? I am feeling that when I bring it up, then this is a big struggle.

First of all, I think it is not very cooperative for any other developer, just this There is no discussion about changing your code in the way. If you want to be dominant in this one, you definitely have to make a good case for your situation.

I believe standard ASP.NET control is easy to deal with with less-experienced developers, if this is a matter of concern in your situation.

I am not sure that I agree about stringbilders, which has often been the source of debates and elsewhere. If your list is not long, there will not be enough justification for stringbuilder here.

One aspect is that an experienced developer can appreciate about this particular approach that it is easy to take this step and seeing that each object is getting populated, it is not easy with a ListView - You have to add an event to add the item, and then it will put a breakpoint in it.

And in the end, I encourage you to choose your fight carefully this particular example is not a major design issue. If you look at the big differences of other differences in the future opinion, then you can decide to start here with a small issue to establish a way to resolve these kinds of conflicts with your fellow developer. Alternatively, you can consider that there is not a great deal to fight about it, and waiting for the key importance (and I suspect you have to wait long) how do you go ahead Choose, it depends on the individuals involved.