Saturday, March 4, 2017

Javascript - Find elements by the "for" attribute

            function findLableForControl(el) {
                var idVal = el;
                labels = document.getElementsByTagName('label');
                for( var i = 0; i < labels.length; i++ ) {
                    if (labels[i].htmlFor == idVal)
                        return labels[i];
                }
            }

This function is handy when working with C# CheckBoxList (or really any of the C# lists). When creating javascript to manipulate the list, C# does not provide ID to the label, rows, nor columns. Thus to find the label, only the "for" attribute can be used to search.

Reference

http://stackoverflow.com/questions/285522/find-html-label-associated-with-a-given-input/285575

C# DataBinding does not contain a property with the name with custom class object and CheckBoxList

I get the error "DataBinding: class1 does not contain a property with the name prop1"

public class1 {
  public string prop1;
  public string prop2;
}


My setup was an object array of class1 which has a property prop1 and prop2:

class1[] arrClass = new class1[arraySize];

Then I set the DataTextField and DataValue:
checkboxlist1.DataSource = arrClass;
checkboxlist1.DataTextField = "prop1";
checkboxlist1.DataValueField = "prop2";
checkboxlist1.DataBind();

This throws the error above. The fix is the lack of accessors in the class, class1. The class should be corrected to the following:
public class1 {
  public string prop1 { get; set; }
  public string prop2 { get; set; }
}
 Technically, set is not needed.


Reference

https://msdn.microsoft.com/en-us/library/aa287786%28v=vs.71%29.aspx

Tuesday, February 28, 2017

Buggish: VS2013 Unable to debug and intellisense haywire

1. The breakpoint will not currently be hit. The source code is different from the original version.

I tried a bunch of different methods suggested in stackoverflow, but none seemed to have worked except to make additional changes to global.asax to force VS to recompile the code. I believe what may have caused the problem is that I was updated global.asax while I was still running the application in debug mode. Normally this is not a problem, but may be a timing of when I updated the code while the page was refreshing.


2. After the problem above, I had issues with intellisense in code-behind not recognizing objects in the aspx page. The red squiggly line comes up, but I am still able to compile and run the application with no compile errors. If I type out the object name, intellisense will not find the object.

Restarting VS fixed this problem. I do not know what caused this as I have restarted VS several times to fix the problem above. Either the problem came up after the fix above, or somehow keeping the files open when I closed VS before restarting somehow fixed the issue.


Reference

http://stackoverflow.com/questions/2468852/the-breakpoint-will-not-currently-be-hit-the-source-code-is-different-from-the