Your use of the packages on this site means you understand they are not supported or guaranteed in any way. Due to the nature of a public repository and unreliability due to distribution rights, these packages should not be used as is for organizational purposes either. Learn more.

  1. C:\> choco install windowsazurelibsfornet

    Package testing. See package page for more details. Windows Azure Libraries for .Net 2.9

    By:

    The Windows Azure SDK for .NET allows you to build Windows Azure applications that take advantage of scalable cloud computing resources.

  2. C:\> choco install lua53

    Package testing. See package page for more details. lua 53 Binaries 5.3.5

    By:

    Since Lua offers no standard set of libraries, many projects and teams have to build their own version of the Lua libraries and this can create binary incompatibilities among the resulting products. Tecgraf/PUC-Rio and Kepler Project teams have a lot of shared products, so it made no sense to keep maintaining two (incompatible) sets of Lua librarie... More information

  3. C:\> choco install windowsazurelibrariesfornet

    Package testing. See package page for more details. Windows Azure Libraries for .Net 2.2 2.2.20140119

    By:

    The Windows Azure SDK for .NET allows you to build Windows Azure applications that take advantage of scalable cloud computing resources.

  4. C:\> choco install lua51

    Package testing. See package page for more details. lua 51 Binaries 5.1.5

    By:

    Since Lua offers no standard set of libraries, many projects and teams have to build their own version of the Lua libraries and this can create binary incompatibilities among the resulting products. Tecgraf/PUC-Rio and Kepler Project teams have a lot of shared products, so it made no sense to keep maintaining two (incompatible) sets of Lua librarie... More information

  5. C:\> choco install lua52

    Package testing. See package page for more details. lua 52 Binaries 5.2.4

    By:

    Since Lua offers no standard set of libraries, many projects and teams have to build their own version of the Lua libraries and this can create binary incompatibilities among the resulting products. Tecgraf/PUC-Rio and Kepler Project teams have a lot of shared products, so it made no sense to keep maintaining two (incompatible) sets of Lua librarie... More information