A newly created JsonFx Discussion Group is available as a public forum for accouncing new releases, and discussing JsonFx and its usage.
JsonFx example code can be found on Google Code and is available for SVN checkout.
JsonFx source code can be found on Google Code and is available for SVN checkout.
When developing JBST templates in Visual Studio, you can improve the experience greatly by mapping the *.jbst extension to the UserControl editor. The syntax is nearly identical so syntax coloring works with JBST templates as well.
jbst" and "jrpc" setting the editor to "HTML Editor" and hit "Apply":
*.jbst and *.jrpc extensions.If you are using the MVC Template for JsonFx, make sure to also note the server requirements for ASP.NET MVC:
Note: In IIS7 Integrated Mode this is automatically done for you via the project's web.config.
The only major server requirement differences between an ASP.NET Web App and an ASP.NET MVC app is setting up a wildcard script mapping to support ASP.NET MVC Routing.
If using the ASP.NET MVC template for JsonFx with IIS 6.0, you will want to add a wildcard script mapping. See the last section of Using ASP.NET MVC with Different Versions of IIS for details. Doing this alleviates the need for the additional script mappings below as all URLs are routed to ASP.NET.
When hosting a JsonFx website in IIS 6.0 (or IIS 7 Classic Pipeline mode), you will need to map the following extensions to ASP.NET:
*.merge (auto-compacted client scripts, templates, JSON-RPC proxies and stylesheets)*.jrpc (JSON-RPC end-points)And optionally if you want to reference these directly outside of *.merge files:
*.css (auto-compacted style sheets)*.js (auto-compacted client script)*.jbst (compiled client-side templates)inetmgr)
