You can use this method to add a new error to an existing validation summary control from your code-behind page. Don't forget to use the proper ValidationGroup that your validation summary is using.
protected void AddErrorToValidationSummary(string errorMessage)
CustomValidator custVal = new CustomValidator();
custVal.IsValid = false;
custVal.ErrorMessage = errorMessage;
custVal.EnableClientScript = false;
custVal.Display = ValidatorDisplay.None;
custVal.ValidationGroup = "MyValidationGroup";
I always seem to be looking this up. So here it is:
ALTER TABLE TableName
ADD CONSTRAINT ConstraintName
UNIQUE NONCLUSTERED (ColumnName)
var allowEnterKey = false;
window.document.onkeydown = CheckEnter;
var keyID = (window.event) ? event.keyCode : e.keyCode;
if (!allowEnterKey && keyID == 13)
Then my search box (or whatever) can be wrapped in a Panel control like so:
<asp:Panel ID="pnlSearch" runat="server" DefaultButton="btnSearch">
<asp:TextBox ID="txtSearch" runat="server" Columns="60"
onfocus="allowEnterKey=true" onblur="allowEnterKey=false" />
<asp:Button ID="btnSearch" runat="server" Text="Search"
onclick="btnSearch_Click" onfocus="allowEnterKey=true" onblur="allowEnterKey=false" />
Notice the DefaultButton property set on the Panel as well as the onfocus and oblur properties of the TextBox.
Today I was adding the new HTML Editor control (newly added to the AJAX Control Toolkit) to an Intranet page. Whenever I would mouse click into the HTML Editor it would continue to expand. This would only occur in IE 8. When using Firefox or IE 8 in compatibility mode it wouldn't happen. I tracked it down to the following declaration in my CSS file:
I removed this declaration and instead used the cellpadding attribute for the table. This solved the issue. Very strange.
Today, while attempting to build a class library on our build box I received the following error in Visual Studio 2008:
"Build failed due to validation errors in [FileName].dbml. Open the file and resolve the issues in the Error List, then try rebuilding the project."
However, when I went to the dbml file no errors were shown in the error list. To resolve this I deleted the .designer.cs file associated with the dbml file. Then in Solution Explorer I right-clicked on the dbml file and selected "Run Custom Tool." This regenerated the .cs file and I was then able to see the error, which was the following:
"DBML1005: Mapping between DbType 'Date' and Type 'System.DateTime' in Column '[ColumnName]' of Type '[TypeName]' is not supported."
This was easy enough to fix. The Server Data Type just needed to be changed to DateTime. Strangely enough having just Date on my development machine did not break the build.
I believed the root of the problem may be that the version of Visual Studio on my development machine was 9.0.30729.1 SP and the build machine was 9.0.21022.8 RTM.
So the other day while attempting to drag a stored procedure onto the LINQ Designer in Visual Studio I received the following error:
The stored procedure was rather complex including a call to FREETEXT and for some reason the LINQ Designer would not accept it, so I manually mapped the stored procedure for the DataContext. For future reference, here is some sample code:
public partial class MyDataContext
[Function(Name = "dbo.MyStoredProc")]
public ISingleResult<MyClass> MyProcName(
[Parameter(Name = "Parameter1")] int? parameter1,
[Parameter(Name = "Parameter2")] ProductCategory? parameter2,
[Parameter(Name = "Parameter3")] bool? parameter3)
IExecuteResult result = this.ExecuteMethodCall(this,
parameter1, parameter2, parameter3);
Then you can call the stored procedure in code like so:
var results = myDC.MyProcName(parameter1, parameter2, parameter3);
I don't expect anyone will read this blog. It is being created for completely selfish reasons. As a Web developer I frequently run into issues that require research in order to solve. I hope to document my findings here, so that I can return to them as needed. Who knows, maybe I'll even blog about other things too. We shall see...