Unit tests will make sure the code does what the tests expect it to.
Setting users free to [ab]use software and checking database/expected output will surely show you whether or not the software works
Recently I started messing with page methods and after a lot of research (google) I think I've found a way to implement this which requires the least amount of code.
Code Behind
Protected Shared _Value As String
Protected Shared Property Value() As String
Get
Return _Value
End...
Ok i'm assuming that a browser has just navigated to http://www.somesite.com/bounce.aspx?name1=aaaa&name2=bbbb
In code behind..
Dim name1 as String = Request.QueryString("name1")
Dim name2 as String = Request.QueryString("name2")
'name1 = aaaa
'name2 = bbbb
or if you have to get...
The problem is cltGrid.FindControl("GridView1") returns nothing.
I think you should check the code in your user control and confirm that a control with that ID actually exists, and if you declared it programmatically, ensure you aren't missing 'new' on instantiation
So, you want to find all repeaters on a page, find all the controls for each repeaterItem, and then do something depending on the controls type?
This is my untested unverified thought pattern..
Perhaps you can do something along the lines of..
For Each c as Control In Me.Controls
Dim rpt as...
Floating element's are perfectly predictable. You may find it helpful to insert <div style="clear:both;"></div> after setting up floating elements to stop your next element being affected by the floating elems before it.
Have you looked at using 'em' to set font sizes?
Personally I rarely use...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.