How to use ASP. net mvc to save user information of e-commerce websites

The payment function page of an e-commerce website usually contains a lot of information. The storage of such information is often completed step by step, so Ajax is the most suitable, for example, the receiver information module. Ajax is used to create and edit and save the information. There are several ways to complete this operation, I think of the following methods.

Let's take a look at this feature:

Generally, this information corresponds to an object class and is named ReceiverInfo. For simplicity, I define ReceiverInfo as follows:

1. splice the required values into json text and process them in the Action column.

First, you need to splice the value to be saved into a json text, similar:

 
 

  
  
var test = "{ ReceiverId: 5, ReceiverName: 'will', Sex: 'F', CreateDate: '2011-02-21' }"; 
 
 

Then save it to the database using Jquery. The Code is as follows:

 
 

  
  
$.ajax({    
  
  
url: "/Home/test1",    
  
  
type: "post",    
  
  
cache: false,    
  
  
data: test}); 
 
 

Then you perform the following operations in the Action:

 
 

  
  
StreamReader reader = new StreamReader (Request. InputStream );
  
  
String bodyText = reader. ReadToEnd ();
  
  
JavaScriptSerializer js = new JavaScriptSerializer ();
  
  
ReceiverInfo receiver = js. Deserialize <ReceiverInfo> (bodyText );
  
  
// Save...
 
 

2. Use custom ModelBinder

JsonBinder

 
 

  
  
public class JsonBinder<T> : IModelBinder   
  
  
{   
  
  
 public object BindModel(ControllerContext controllerContext, ModelBindingContext bindingContext)   
  
  
   {   
  
  
    StreamReader reader = new StreamReader(controllerContext.HttpContext.Request.InputStream);   
  
  
     string json = reader.ReadToEnd();   
  
  
       if (string.IsNullOrEmpty(json))   
  
  
            return json;  
  
  
         JavaScriptSerializer serializer = new JavaScriptSerializer();  
  
  
        object jsonData = serializer.DeserializeObject(json);  
  
  
return serializer.Deserialize<T>(json);  
  
  
    }  
  
  
 } 
 
 

We inherit the IModelBinder interface to implement its method:

 
 

  
  
public object BindModel(ControllerContext controllerContext, ModelBindingContext bindingContext) 
 
 

You can. We can use the following in Action:

 
 

  
  
public ActionResult Test1([ModelBinder(typeof(JsonBinder<ReceiverInfo>))] ReceiverInfo receiverInfo) 
 
 

In this way, the custom IModelBinder replaces defamodelmodelbinder to complete data binding.

3. directly pass a Json object

The above two methods do not use MVC's System. ComponentModel. DataAnnotations for effective data verification. You may need to manually verify it, which will undoubtedly increase the workload.

Let's try this method.

Frontend writing

 
 

  
  
var b = {      
  
  
ReceiverId: 5,      
  
  
ReceiverName: "will",      
  
  
Sex: "F",      
  
  
CreateDate: "2011-02-21"};$.ajax({    
  
  
url: "/Home/test1",      
  
  
type: "post",      
  
  
cache: false,      
  
  
data: b,      
  
  
success: function(data) { alert(data.message); },      
  
  
error: function(xhr, a, b) { alert  
  
  
(xhr.responseText); }}); 
 
 

Action Statement:

 
 

  
  
public ActionResult Test1(ReceiverInfo receiverInfo) 
 
 

We can normally get the bound data. We can also use System. ComponentModel. DataAnnotations for data verification. Make the following changes for ReceiverInfo:

 
 

  
  
[System. ComponentModel. DataAnnotations. Required
  
  
(ErrorMessage = "")] public string ReceiverName {get; set ;}
 
 

And assign a blank string to ReceiverName at the front end. Execute the code again. The following message is displayed:

Good, but we have new requirements, that is, to pass more complex objects, such as object nesting objects and objects with set attributes, this method is not competent.

4. Use JsonValueProviderFactory of MvcFutures

Each version of MVC has an MvcFutures, which has some additional features, some of which will be added to the next version, and these features are useful in some cases. I checked the classes and found that a class JsonValueProviderFactory is used to process the submission and data verification of complex objects. The default defamodelmodelbinder can be used for json objects only after specific parsing, And This parsing process needs to be completed in the ValueProvider stage. Therefore, a specific ValueProvider must be implemented to defamodelmodelbinder. We need to implement a ValueProviderFactory and IValueProvider, while the DictionaryValueProvider in MVC <TValue> inherits IValueProvider) is enough, so we only need to inherit ValueProviderFactory to implement its method: public override IValueProvider GetValueProvider (ControllerContext controllerContext). For specific code, see JsonValueProviderFactory.

We define another class:

ReceiverInfoChild

 
 

  
  
Public class ReceiverInfoChild {
  
  
[System. ComponentModel. DataAnnotations. Required
  
  
(ErrorMessage = "ChildId required")]
  
  
Public string ChildId {get; set ;}}
 
 

Add a public List <ReceiverInfoChild> ReceiverInfoChild {get; set;} to the class ReceiverInfo ;}

We put JsonValueProviderFactory out in the project, and then register it in Global. asax to use it.

 
 

  
  
protected void Application_Start(){      
  
  
AreaRegistration.RegisterAllAreas();      
  
  
RegisterRoutes(RouteTable.Routes);      
  
  
ValueProviderFactories.Factories.Add(new   
  
  
JsonValueProviderFactory());} 
 
 

Because JsonValueProviderFactory contains: if (! ControllerContext. HttpContext. Request. ContentType. StartsWith ("application/json", StringComparison. OrdinalIgnoreCase) to determine whether the Request is a json object. Therefore, we need to write the following when submitting data:

 
 

  
  
var ReceiverInfo = [              
  
  
{                  
  
  
ReceiverInfoChild: [{ ChildId: "1" }, { ChildId: "11"}],                  
  
  
ReceiverId: 5,                
  
  
ReceiverName: "will",                
  
  
Sex: "F",                  
  
  
CreateDate: "2011-02-21"            
  
  
  },              
  
  
{                 
  
  
 ReceiverInfoChild: [{ ChildId: "2" }, { ChildId: "22"}],                  
  
  
ReceiverId: 5,                
  
  
ReceiverName: "will",                
  
  
Sex: "F",                  
  
  
CreateDate: "2011-02-21"            }             
  
  
 ];$.ajax({    
  
  
url: "/Home/test1",    
  
  
type: "post",    
  
  
cache: false,    
  
  
contentType: "application/json;charset=utf-8",    
  
  
data: JSON.stringify(ReceiverInfo),    
  
  
success: function(data) { alert(data.message); },   
  
  
 error: function(xhr, a, b) { alert(xhr.responseText); }}); 
 
 

JSON. stringify (ReceiverInfo) converts a json object to a string. You can download this class library here.

In the Action, we can write it like this:

 
 

  
  
public ActionResult Test1(List<ReceiverInfo> receiverInfo) 
 
 

Let's take a look at the debugging results:

The value is fully bound. Let's take a look at data verification:

So far, we have experimented with four solutions:

The first solution is the most troublesome and error-prone, which may be related to my personal dislike of concatenating strings );

The second scheme has a certain degree of universality, but is not conducive to data verification;

The third solution is generic and can be used for effective data verification. It is sufficient to deal with general requirements, but it cannot handle more complex objects;

The fourth solution can handle almost all the situations we encounter

In addition, this is used in ASP. NET MVC2. in ASP. NET MVC3, Microsoft has made JsonValueProviderFactory a built-in function.

Edit recommendations]