if you’ve already loaded the .Net Framework 3.0, then, download the VS 2005 Extensions for .Net 3.0 at :
http://www.microsoft.com/downloads/details.aspx?FamilyID=f54f5537-cc86-4bf5-ae44-f5a1e805680d&DisplayLang=en
(if not, download the .Net Framework 3.0 here:
http://msdn2.microsoft.com/en-us/netframework/bb264589.aspx
(Thanks to Juan Libre)
If your submit button fires twice, it usually happens when you have a ‘Handles’ clause after the sub, along with an ‘Onclick’ event in the button tag itself.
Just remove the onclick event from the tag and it will be ok
If you’re using AJAX, and control (inside an UpdatePanel) causes a postback that would normally run Javascript, AND you find the Javascript is not running, add a Postback Trigger to the UpdatePanel using the ID of the control that causes the postback.
Always remember, if you’ve been debugging your application, during development and testing, MAKE SURE you change your web.config file, in your compilation section, set:
debug="true"
This will greatly increase the speed of your application, once it’s been put into production.
Open up your web.config file – then, somewhere in the system.web section, put this :
<trace enabled="true" pageOutput="true" localOnly="false"/>
Set it to ‘false’ when you don’t want it to show up.
If you need to completely clear a Gridview quickly, create a sub like this:
Protected Sub ClearGrid(ByVal gv As GridView) gv.DataSource = Nothing gv.DataSourceID = Nothing gv.DataBind() End Sub
Then, you can use it by using your Gridview ID:
ClearGrid("YourGridViewID")
In order to make all dates before the current date, not able to be selected, in the onDayRender event for your Calendar:
If (Args.Day.Date < DateTime.Today) Then Args.Day.IsSelectable = False End If
To make it more obvious to the end user, also add:
Args.Cell.BackColor = Drawing.Color.GhostWhite Args.Cell.ForeColor = Drawing.Color.Gainsboro
Thanks to the idea from Peter Blum
It is sometime unavoidable to get rid of javascript errors. To get rid of it just go through following code.
<head>
<script language="javascript">
function stoperror()
{
return true
}
window.onerror=stoperror
</script>
</head>
DotNetGuts (DNG)
Logon to http://www.DotNetGuts.Blogspot.com
In order to persist a datatable, you can easily add it to the Viewstate, by creating a property in your class:
What I do in many circumstances, is, like the last post said, pass the DataTable to viewstate as a property of the class:
Private Property EmployeeData() As System.Data.DataTable
Get
Dim o As Object = ViewState("EmployeeData")
If o Is Nothing Then
Return Nothing
Else
Return o
End If
End Get
Set(ByVal value As System.Data.DataTable)
ViewState("EmployeeData") = value
End Set
End Property
Now, whenever you need to repopulate, or add a row, remove a row, etc – just refer to the property “EmployeeData”
If you have popup messages in multiple places in your website, you can create one global routine, so that you can build them dynamically, wherever you want in the site, with whatever message you need. Just create a separate class (or add to an existing class in your app_code folder) and put this code in it:
Public Sub DisplayMessage(ByVal webPage As Object, ByVal Message As String) Dim msgDisplay As String = "alert('" & Replace(Message, "'", "\'") & "');" webPage.ClientScript.RegisterStartupScript(Me.GetType, "DisplayMessage", msgDisplay) End Sub
To use it, just put something like this, in your code:
DisplayMessage(me,”YourMessageGoesHere”)
That’s all there is to it!