Skip to main content

How to disable validation for a submit button

Pornim de la o aplicate MVC 3 pe care avem o forma cu mai multe controale de tip input-submit. Se doreste ca unul sau mai multe butoane care fac submit sa nu facă și validarea modelului client-side.
<form ... >
<input id="bSave" type="submit" value="Save" />
<input id="bAddToy" type="submit" value="Add toy" />
O solutie care pare la indemana este ca la al doilea buton din exemplu sa fie transformat într-un link (ancora). Din CSS poate sa fie făcut sa arate exact ca un buton de input iar la click poate sa apeleze un jQuery care apelează acțiunea dorita făcînd submit și la model.
O a doua soluție găsita, care mi s-a părut extrem de simpla și care rezolva aceasta problema este adăugarea class="cancel" la butonul de input la care dorim sa nu facem validarea:
<input id="bAddToy" type="submit" value="Add toy" class="cancel" />
Voi ce propuneri aveți?


  1. Pentru ultimele versiuni de browsere care suporta HTML5, pe unele din ele, merge atributul 'formnovalidate':
    si care se refera la atributele de validare introduse in HTML5..

    Din pacate multi useri nu au inca ultimele versiuni, asa ca probabil ar trebui un mecanism de fallback la validarea clasica folosind JS daca validarea din HTML5 nu e suportata ..


Post a Comment

Popular posts from this blog

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

GET call of REST API that contains '/'-slash character in the value of a parameter

Let’s assume that we have the following scenario: I have a public HTTP endpoint and I need to post some content using GET command. One of the parameters contains special characters like “\” and “/”. If the endpoint is an ApiController than you may have problems if you encode the parameter using the http encoder.
using (var httpClient = new HttpClient()) { httpClient.BaseAddress = baseUrl; Task<HttpResponseMessage> response = httpClient.GetAsync(string.Format("api/foo/{0}", "qwert/qwerqwer"))); response.Wait(); response.Result.EnsureSuccessStatusCode(); } One possible solution would be to encode the query parameter using UrlTokenEncode method of HttpServerUtility class and GetBytes method ofUTF8. In this way you would get the array of bytes of the parameter and encode them as a url token.
The following code show to you how you could write the encode and decode methods.

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…