MVC Usage

The examples in this Help documentation will by default use .ASPX Web Form pages to do the spell checking work. If this is not desired, it is possible to use WCF or ASMX Web Services to do the spell checking work on the server. jQuery is required for inline spell checking, and additionally jQuery UI is required for dialog mode checking.

Dialog Mode

To use WCF web services for dialog based spell checking (note that this is only supported with jQuery DIV based dialog windows):

1. In Javascript, call rapidSpell.dialog_setUseDivDialog(true);
2. Ensure the project references Keyoti.RapidSpellWeb.ASP.NETv4.DLL
3. In the MVC project's RouteConfig class, add 2 ignore routes:
   routes.IgnoreRoute("{d}/{resource}.svc/{*pathInfo}");
   routes.IgnoreRoute("{d}/{resource}.svc");
   

Inline/as-you-type Mode

To use WCF web services for inline based spell checking:

1. Include jQuery on the page.
2. In Javascript, call rapidSpell.useAJAXWebService = true;
3. Ensure the project references Keyoti.RapidSpellWeb.ASP.NETv4.DLL
4. In the MVC project's RouteConfig class, add 2 ignore routes:
   routes.IgnoreRoute("{d}/{resource}.svc/{*pathInfo}");
   routes.IgnoreRoute("{d}/{resource}.svc");
   

ASMX .NET 2/3+

It is possible to use ASMX Web Services instead of WCF if required. To do that,reference Keyoti.RapidSpellWeb.ASP.NETv2.DLL and call (in Javascript):
rapidSpell.setServiceType('asmx');
Ensure the ignore routes (see above) are for .asmx instead of .svc.

Troubleshooting

If you get '500' server errors, please check:

• If the project uses Keyoti.RapidSpellWeb.ASP.NETv2.DLL, then the page scripts must call rapidSpell.setServiceType('asmx'), in order to use the .NET 2 compatible Web Service.
• That the memory usage on the machine is not up near 100%. It has been found that the web services shut down when overall system memory consumption is high (this is a 'feature' of IIS/IISExpress).
• Use the F12 tool's Network tab, to record traffic to the Web Services. Inspect the response from the server for more detail about what is going wrong.
• If you get this error "Request format is unrecognized for URL unexpectedly ending in ..." then you may need to add the HttpPost protocol to the webservices section of web.config, eg.

  <configuration>
      <system.web>
      <webServices>
          <protocols>
              <add name="HttpGet"/>
              <add name="HttpPost"/>
          </protocols>
      </webServices>
      </system.web>
  </configuration>
  

We don't want you to struggle, so please email support@keyoti.com if problems persist.