SharpKit is a Web Toolkit that enables you to write C# and convert it to JavaScript during compilation.
SharpKit was designed for web development teams that maintain C# and JavaScript code, most commonly within the ASP.NET platform and Visual Studio.
Writing and maintaining JavaScript code can be very expensive.
Migrating from JavaScript to C# enables you to:
SharpKit Express edition is free, and is intended for small projects, this means that you can can convert up to 2500 lines of code per project.
No, SharpKit converts code during compilation, when you deploy you web app, you deploy it with the generated JavaScript files, in fact, SharpKit also helps you optimize your JavaScript files using minification and consolidation.
No.
SharpKit was designed to be a nonintrusive, pure compile-time solution with minimal impact during development and zero impact during production.
This non-lock-in model enables you to stop using SharpKit at any time, simply by excluding the client-side C# files and treating the JavaScript files as the source.
Simply download SharpKit and install it on your development machine.
Then visit our Learning Center to help you get started quickly.
No. SharpKit compiler is an executable that can be used with or without Visual Studio.
It is up to you. SharpKit provides standard support for many C# language features without including any additional files. Advanced support for features such as reflection, LINQ and generics require a small include of the SharpKit JS Kernel (about 60K compressed).
You can, but you don't have to.
SharpKit assemblies contain many interfaces for JavaScript, HTML, jQuery and other web libraries. In order to use them you can either add them as a reference, or integrate the .cs header file directly into your project. All of SharpKit header files and assemblies are completely open-source, and you can modify them anytime.
No. Since SharpKit generates native JavaScript that is identical to hand-written code, there is no performance penalty for the automation process.
No. SharpKit is fully compliant with all language features of JavaScript.
Yes. SharpKit does not implement JavaScript functionality for: yield, ref and out keywords, explicit interface implementations, non-native structs and operator overloading.
Nothing. You can simply exclude the C# files used for client-side code generation and treat the generated JavaScript files as the source files.
Yes. You can feed the SharpKit compiler with C# code during runtime, and generate JavaScript on the fly.
Yes. Most modern mobile phones support HTML5 so you can use SharpKit's HTML5 interface to develop mobile browser applications in C#, and compile them into JavaScript.