JSPool
Metadata
Authors | Daniel Lo Nigro |
---|---|
Copyrights | Copyright 2014 Daniel15 |
Description | JSPool facilitates easy integration of JavaScript scripting into a .NET application in a scalable and performant manner. It does so by creating a pool of engines that can be reused multiple times, making it easy to use JavaScript libraries that have long initialisation times without having to create a new engine every time. |
LicenseUrl | https://github.com/Daniel15/JSPool/blob/master/LICENSE |
Owners | Daniel Lo Nigro |
ProjectUrl | http://dan.cx/projects/jspool |
RequireLicenseAcceptance | False |
Summary | Pooling of JavaScript engines in .NET |
Tags | javascript js javascriptengineswitcher msiejavascriptengine v8 clearscript |
Dependencies | JavaScriptEngineSwitcher.Core:1.2.4 |
Title | JSPool |
PackageSize | 44987 |
PackageHashAlgorithm | SHA512 |
PackageHash | 5ZUV4UbZ061ebyzp8+PrglBzAdRniNks6yZsJNI1VB9QiKLUrK4gZ0qmksKpKpQ85ot3uxdhR3ByAE2szD99sw== |
DownloadCount | 000000 |
CreatedDate | 2015-04-13T00:15:10 |
Access
You can access data for this project using the tools and addresses described below.
NuGet (nuget.exe)
- Installing the package (HTTP Basic authentication):
-
nuget install JSPool -Source http://nuget.gw.symbolsource.org/Public/NuGet/FeedService.mvc
- Installing the package (pre-authenticated):
-
nuget install JSPool -Source http://nuget.gw.symbolsource.org/Public/%login%/%key%/NuGet/FeedService.mvc
NuGet (Package Manager Console)
- Installing the package (search all configured feeds):
-
Install-Package JSPool
- Installing the package (HTTP Basic authentication):
-
Install-Package JSPool -Source http://nuget.gw.symbolsource.org/Public/NuGet/FeedService.mvc
- Installing the package (pre-authenticated):
-
Install-Package JSPool -Source http://nuget.gw.symbolsource.org/Public/%login%/%key%/NuGet/FeedService.mvc
- Uinstalling the package:
-
Uninstall-Package JSPool
OpenWrap
- Installing the package:
-
o add-wrap JSPool
- Uninstalling the package:
-
o remove-wrap JSPool
Versions
A version is snapshot of a project's source code. It does not need to follow the Major.Minor.Revision.Build numbering pattern. It can be an arbitrary string of text that identifies a release or a build, in particular including meaningful words like beta, RC or RTM.