disclaimer: this article covers the most powerful links in IML, when action ( directajaxsubmit ) is performed and findings (with or with no template) are in DOM-element. This method has appeared in different examples in other articles, but today I’m going to make a review of all possibilities of this links in the Incoding Framework context 

Note: article code examples are available on GitHub.


The first unit of our links is Do. It may seem to be a “noise”. But when you understand all aspects of its work that influence on browser event service it will become clear that:

  • Do ( sandbox ) – does not influence on behavior
  • DoWithPreventDefault ( sandbox )cancels event, nullifying  it but does not stop continuing to spread the event.

Note: it is used for Submit form event to prevent a send with no Ajax and for Anchor to block transition on Href

  • DoWithStopPropagation – stops continuing event spreading (propagation) but does not cancel the event.

Note: is used for Submit event if an output agent is tied to input (type submit).

  • DoWithPreventDefaultAndStopPropagation  –  cancels and annuals event and stops continuing spreading (propagation) event.


The base element in work of our links is Action. It helps to get information using different ways, but all of them are united by the form that contains objects.

Incoding Result

This is a successor from JsonResult, where on default included JsonRequestBehavior.AllowGet and prepared factory designers for creating a desired result type.

  • Success – json объект { data:setData, success:true, redirectTo:string.Empty }

примечание: someData может быть null, тогда результат просто сигнализирует об удачном завершении action

  •  Error  – json object{ data:setData, success:false, redirectTo:string.Empty }

Note: someData could be null. In this case the result just gives a signal about successful action completion.

  •  RedirectTo – json object{ data:null, success:true, redirectTo:someUrl }

Note: if after realization of any ( Ajax, Submit or etc ) action  as the result bring back redirectTo, window.location = url actuates on the client

Each type-result puts back call (On callback ). There is a comparison table below

[table caption=”Compare incoding result”]
Result,On Success,On Complete,On Error,On Begin,On Break
IncodingResult.Success,Yes,Yes,No,Before Action,No
IncodingResult.Error,No,Yes,Yes,Before Action,No
IncodingResult.RedirectTo,No,No,No,Before Action,No

Integration with Controller

Factory methods  IncodingResult  are low-level, therefore it’s better to use methods from basic IncControllerBase class

  • IncJson– is an alternative to Success

  • IncView – realize render View in line and brings back through  IncodingResult.Success

Note: IncView works by an algorithm 

  • IncPartialView–is an analog to  IncView, but with a chance to show the way to  View

  • IncRedirect –  is an alternative to  RedirectTo

  • IncRedirectToAction – redirect on the concrete  Action in Controller

How to get data?

  • Direct ( sandbox ) – is more often used as free action, but supports a possibility to inform

Note: Error, Redirect could be used as data


Data as Model

Note: script is used if client template, but data are got Ajax

Static Content Setting in

 Note: the script is used, if it is necessary to set in data, that are permanent (empty line setting in, adding form elements,  etc.)

  • Ajax ( sandbox ) – request to the server

Note: AjaxGetAjaxPost  is “named” version of Ajax

  • Submit On ( sandbox) – send mentioned  form through ajax ( requires connection to  jquery form )

Note: this example shows a script, when Submit is realized on behalf of button. In this case as event service we choose Stop Propagation to stop event progress “Click” above (up to form)

  • Submit  – is similar to  SubmitOn, but has no possibility to indicateform, and always sends a nearest (closest ) form in the hierarchy Dom elements or self  if it is form

Note: example shows a script, when form intercepts “Submit” event and further realizes Submit action, that’s why as event service we choose Prevent Default to annual form send by standard browser methods

  • Events (sandbox ) – getting data from event, realization consists of two elements:
    • The source– “throws” data through trigger

Note: any of them  could be used as Action

    • The receiver –the element, which the invoke is directed at.

Note: work with data is constricted as with other Action

Events by itself has no sense, but together  with Where allows  building up  complex  scripts, e.g. chat window


The term: on a single page N-th amount of chat windows could be opened. They are tied up with chosen contact, where messages are shown.

Decision 1: each window on the base of its Id (or other concrete) requests messages on Ajax

Problem: as the number of  windows increases, the number of  requests on the server would grow, which may  result in:

  • Overfill maximum limit of browser requests and there will be a delay between requests
  • Load the pool

Decision 2: the  previous solution variant had a problem with a huge amount of data sources, therefore a slight  modernization of code adding one more element, one  can do with a single request for any amount of windows

Note: now there is only one request, but we „add“ data to all elements with “window” class, but windows knows which Id should be used for  filtering.  

Структурное изображение решения

  • Ajax Hash– is an analog of Submit, not for  form, but for

Example with no Ajax Hash

Note: all parameters are obtained from hash, but we must indicate each of them

Example with Ajax Hash

Note: now the example works similar to  Submit form ( serialization hash ), but collect parameters from hash

 Ajax Vs Submit Or Ajax Vs Hash

All “action”, except Direct and Evetns , works with ajax, that’s why the question could come up: in what case which to use

  • If you fill N-th amount of input, put in form and further actionSubmit
  • If search parameters are kept in hash, use action AjaxHash
  • In all other cases could be realized with actionAjax

Examples of scripts for Ajax

Status change

 Loading drop down

And many other tasks (content for dialog, record deletion)


This is one of a set of executables that are available under On callback, that is why this is not an obligatory element of a line, but most of scripts are aimed to insert findings in Dom element. “Insert” repeatedly figured in examples from other articles, but now we are going to examine the work of this executable better


  • Content –  controller brings back IncView or IncPartialView



Note: IncView will look for Contact.cshtml in file View/$Controller$ 


Alternative variant on MVD without Controller


Note: realization on mvd dispense writing of controller

  • Object –  controller brings back IncJson


Code Controller

Code View

note:  urlTemplate must return  IncView

Alternative variant on MVD without Controller


Note: each method has its analog in jquery

Complex Model

All examples were constructed on one model, but there are could be other scripts when findings are “container”. To this effect in Insert is a chance to show with which part of model works through.

Note: as T for For must be showed a model that is in data

Examples of scripts

Note: each method has its analog in jquery

Condition: by Id records get its model and update form fields

Decision 1:  after loading to update the hole form, built it again, but sometimes this can complicate this task, of form has extra elements.

Decision 2: after loading to update only necessary fields

Note: you can use reflection and build Insert.For dynamically

One request, a lot of models

Condition:  update N-th amount of elements by different data

Decision 1: each element makes a request of its data, but it leads to increase load in server and slow page loading because of large amount of isochronic

Note: partially this problem could be solved by Ajax Asyc in false installation. In this case a page would be loaded by pieces. That is also permissible

Decision 2: one element load all data than through For “pointwise” to update

Note: for each For you can use its  template

Insert For Vs Trigger For

Method of Executor ( executable ) Trigger looks like Form ethos, but it coupled with  action events  and let delegate data to other elements but don’t make actions. Example:

Insert For ( sandbox )

 Trigger For ( sandbox )
  • The source

  •  The receiver

Note: realization with Events needs extra element

Decision with  Trigger looks more complicated, therefore if you need only put different parts of one model it would be better to use Insert For, but possibility of  Where for Events  lets realize scripts that couldn’t be solved with  Insert


This is the 1st part of planed cycle of articles about different links, but in fact it’s rather difficult to examine all possible tasks because IML is not so flexible. But this fact let us group in a completely different variations for complex scripts

I’ve picked out fundamental:

  • Do, Action, Insert
  • When, Trigger
  • Submit Form
  • Search hash

In the nearest future I’ll publish separate articles about each script.

P.S. if somebody has a script that he wants to be examined, how to solve in Incoding Framework, leave it in comments and I’ll make an article.

Vlad Kopachinsky

I am a Senior developer at Incoding Software in Russian Federation. I created the Incoding Framework for rapid development

More Posts - Website - Twitter - Facebook - LinkedIn

Leave a Reply