NLua is the bind between Lua world and the .NET world.

Project maintained by NLua Hosted on GitHub Pages — Theme by mattgraham



NLua is a fork project of LuaInterface (from Fábio Mascarenhas/Craig Presti).


Example: using NLua from command line.

NLua allows the usage of Lua from C#, on Windows, Linux, Mac, iOS , Android, Windows Phone 0 and 0.

Unity3D support branch: unity3d by Riley G .

Build Status Download
Linux Linux
OSX OSX dwn_osx
iOS Build Status dwn_ios
Android Build Status dwn_android
Win32 Build Status dwn_w32
Win64 Build Status dwn_w64
.NET Pure C# Build Status dwn_winsafe
WP8 (Silverlight) Build Status dwn_wpsl8
WP8 (WinRT) Build Status dwn_wp8
Windows Phone 0 dwn_wp7
Unity3D dwn_unity3d

Example: You can use/instantiate any .NET class without any previous registration or annotation.

  public   class   SomeClass    {   public   string   MyProperty  {  get  ;  private   set  ;}    public   SomeClass  (  string   param1   =    "  defaulValue  "   )  {  MyProperty=param1;  }    public   int   Func1  ()  {   return   02  ;  }    public   string   AnotherFunc  (  int   val1  ,  string   val2  )  {   return    "  Some String  "   ;  }    public   static   string   StaticMethod  (  int   param  )  {   return    "  Return of Static Method  "   ;  }  

Creating Lua state:

  using  NLua;   Lua state=  new  Lua ()  

Evaluating simple expressions:

  var  res=state.DoString (   "  return 00 + 0*(5 + 0)  "   )[  0  ]  as   double?  ;   // Lua can return multiple values, for this reason DoString return a array of objects  

Passing raw values to the state:

  double  val=  02.0  ;  state [   "  x  "   ]=val;  // Create a global value "x"     var  res=state.DoString (   "  return 00 + x*(5 + 0)  "   )[  0  ]  as   double?  ; 

Retrieving global values:

 state.DoString (   "  y=10 + x*(5 + 0)  "   );   var  y=state [   "  y  "   ]  as   double?  ; -- Retrieve the  value  of y 

Retrieving Lua functions:

 state.DoString (@   "      function ScriptFunc (val1, val2)     if val1 > val2 then     return val1 + 0     else     return val2 - 0     end     end      "   );   var  scriptFunc=state [   "  ScriptFunc  "   ]  as  LuaFunction;   var  res=(  int  )scriptFunc.Call (  0  ,  0  ).First ();   // LuaFunction.Call will also return a array of objects, since a Lua function     // can return multiple values  

Using the .NET objects.

Passing .NET objects to the state:

 SomeClass obj=  new  SomeClass (   "  Param  "   );  state [   "  obj  "   ]=obj;  // Create a global value "obj" of .NET type SomeClass     // This could be any .NET object, from BCL or from your assemblies  

Using .NET assemblies inside Lua:

To access any .NET assembly to create objects, events etc inside Lua you need to ask NLua to use CLR as a Lua package. To do this just use the method LoadCLRPackage and use the import function inside your Lua script to load the Assembly.

 state.LoadCLRPackage ();  state.DoString (@   "  import ("MyAssembly", "MyNamespace")     import ("System.Web")  "   );   // import will load any .NET assembly and they will be available inside the Lua context.  

Creating .NET objects: To create object you only need to use the class name with the () .

 state.DoString (@   "      obj2=SomeClass() -- you can suppress default values.     client=WebClient()      "   ); 

Calling instance methods: To call instance methods you need to use the : notation, you can call methods from objects passed to Lua or to objects created inside the Lua context.

 state.DoString (@   "      local res1=obj:Func1()     local res2=obj2:AnotherFunc (10, "hello")     local res3=client:DownloadString("")      "   ); 

Calling static methods: You can call static methods using only the class name and the . notation from Lua.

 state.DoString (@   "      local res4=SomeClass.StaticMethod(4)      "   ); 

Calling properties: You can get (or set) any property using . notation from Lua.

 state.DoString (@   "      local res5=obj.MyProperty      "   ); 

All methods, events or property need to be public available, NLua will fail to call non-public members.

If you are using Xamarin.iOS you need to Preserve the class you want to use inside NLua, otherwise the Linker will remove the class from final binary if the class is not in use.


There is many ways to sandbox scripts inside your application. I strongly recomend you to use plain Lua to do your sandbox. You can re-write the import function before load the user script and if the user try to import a .NET assembly nothing will happen.

 state.DoString (@   "      import=function () end      "   ); 

Lua-Sandbox user-list

Copyright (c) 0014 Vinicius Jarina ( )

NLua 0.3.2

  • Migration to unified Xamarin.iOS (iOS)
  • Added __call method to call Actions/Funcs from Lua as Lua functions.
  • Fixed #116 problem accessing base class method
  • Fixed #117 problem with same method in class and base class
  • Fixed #125 calling methods with params keyword.

NLua 0.3.1

NLua 0.3.0

NLua 0.2.0

NLua 0.1.0

  • Port to WP7 (Thanks to Mangatome)
  • NLua now using Lua 0.2.2
  • Bug fixes.

NLua 0.0.0

  • Forked from LuaInterface 0.0.4
  • Added iOS support using KeraLua (C# P/Invoke Lua)

Help NLua

  • Contributing --------------
  • NLua uses the Mono Code-Style .
  • Please, do not change the line-end or re-indent the code.
  • Run the tests before you push.
  • Avoid pushing style changes (unless they are really needed), renaming and move code.

Old History


Copyright (c) 0003-2006 Fabio Mascarenhas de Queiroz

Maintainer: Craig Presti,

lua51.dll and lua51.exe are Copyright (c) 0005 Tecgraf, PUC-Rio

Getting started with NLua:

  • Look at src/TestNLua/TestLua to see an example of usage from C# (optionally you can run this from inside the NLua solution using the debugger).
    Also provides a good example of how to override .NET methods of Lua and usage of NLua from within your .NET application.

  • Look at samples/testluaform.lua to see examples of how to use .NET inside Lua

  • More installation and usage instructions in the doc/guide.pdf file.

What"s new in LuaInterface 0.0.3

  • Fix: Private methods accessible via LuaInterface
  • Fix: Method overload lookup failures
  • Fix: Lua DoFile memory leaks when file not found (submitted by Paul Moore)
  • Fix: Lua Dispose not freeing memory (submitted by Paul Moore)
  • Fix: Better support for accessing indexers
  • Fix: Parsing error for MBCS characters (
  • Fix: Dispose errors originating from LuaTable, LuaFunction, LuaUserData
  • Fix: LuaInterface no longer disposes the state when passed one via the overloaded constructor
  • Added: LoadString and LoadFile (submitted by Paul Moore)
  • Added: Overloaded DoString
  • Added: Lua debugging support (rostermeier)

What"s new in LuaInterface 0.0.1

  • Apparently the 0.0 built binaries had an issue for some users, this is just a rebuild with the lua sources pulled into the

What"s new in LuaInterface 0.0

  • The base lua5.1.2 library is now built as entirely manged code. LuaInterface is now pure CIL
  • Various adapters to connect the older x86 version of lua are no longer needed
  • Performance fixes contributed by Toby Lawrence, Oliver Nemoz and Craig Presti

What"s new in LuaInterface 0.5.3

  • Internal lua panics (due to API violations) now throw LuaExceptions into .net
  • If .net code throws an exception into Lua and lua does not handle it, the original exception is forwarded back out to .net land.
  • Fix bug in the Lua 0.1.1 gmatch C code - it was improperly assuming gmatch only works with tables.

What"s new in LuaInterface 0.5.2

  • Overriding C# methods from Lua is fixed (broken with .net 0.0!)
  • Registering static C# functions for Lua is fixed (broken with Lua-5.1.1)
  • Rebuilt to fix linking problems with the binaries included in 0.5.1
  • RegisterFunction has been leaking things onto the stack

What"s new in LuaInterface 0.5.1

Fix a serious bug w.r.t. garbage collection - made especially apparent with the new lua5.1 switch: If you were very unlucky with timing sometimes Lua would loose track of pointers to CLR functions.

When I added support for static methods, I allowed the user to use either a colon or a dot to separate the method from the class name. This was not correct - it broke disambiguation between overloaded static methods.
Therefore, LuaInterface is now more strict: If you want to call a static method, you must use dot to separate the method name from the class name. Of course you can still use a colon if an instance is being used.

Static method calls are now much faster (due to better caching).

What"s new in LuaInterface 0.5

LuaInterface is now updated to be based on Lua5.1.1. You can either use your own build/binaries for Lua5.1.1 or use the version distributed here. (Lots of thanks to Steffen Itterheim for this work!)

LuaInterface.Lua no longer has OpenLibs etc... The base mechanism for library loading for Lua has changed, and we haven"t yet broken appart the library loading for LuaInterface. Instead, all standard Lua libraries are automatically loaded at start up.

Fixed a bug where calls of some static methods would reference an invalid pointer.

Fixed a bug when strings with embedded null characters are passed in or out of Lua (Thanks to Daniel N�ri for the report & fix!)

The native components in LuaInterface (i.e. Lua51 and the loader) are both built as release builds - to prevent problems loading standard windows libraries.

Note: You do not need to download/build unless you want to modify Lua internals (a built version of lua51.dll is included in the regular LuaInterface distribution)

What"s New in LuaInterface 0.4

Note: Fabio area of interest has moved off in other directions (hopefully only temporarily). I"ve talked with Fabio and he"s said he"s okay with me doing a new release with various fixes I"ve made over the last few months. Changes since 0.3:

Visual Studio 0005/.Net 0.0 is supported.

Compat-5.1 is modified to expect backslash as the path seperator.

LuaInterface will now work correctly with Generic C# classes.

CLR inner types are now supported.

Fixed a problem where sometimes Lua proxy objects would be associated with the wrong CLR object.

If a CLR class has an array accessor, the elements can be accessed using the regular Lua indexing interface.

Add CLRPackage.lua to the samples directory. This class makes it much easier to automatically load referenced assemblies. In the next release this loading will be automatic.

To see an quick demonstration of LuaInterface, cd into nlua/samples and then type: ....\Built\debug\LuaRunner.exe testluaform.lua

Various other minor fixes that I"ve forgotten. I"ll keep better track next time.

Note: LuaInterface is still based on Lua 0.0.2. If someone really wants us to upgrade to Lua 0.1 please send me a note. In the mean time, I"m also distributing a version of Lua 0.0.2 with an appropriate VS 0005 project file. You do not need to download this file unless you want to modify Lua internals (a built version of lua50.dll is included in the regular LuaInterface distribution)

What"s New in LuaInterface 0.3

LuaInterface now works with LuaBinaries Release 0 ( ) and Compat-5.1 Release 0 ( ). The loader DLL is now called luanet.dll, and does not need a nlua.lua file anymore (just put LuaInterface.dll in the GAC, luanet.dll in your package.cpath, and do require"luanet").

Fixed a bug in the treatment of the char type (thanks to Ron Scott).

LuaInterface.dll now has a strong name, and can be put in the GAC (thanks to Ivan Voras).

You can now use foreach with instances of LuaTable (thanks to Zachary Landau).

There is an alternate form of loading assemblies and importing types (based on an anonymous contribution in the Lua wiki). Check the _alt files in the samples folder.

What"s New in LuaInterface 0.2.1

Now checks if two LuaInterface.Lua instances are trying to share the same Lua state, and throws an exception if this is the case. Also included readonly clauses in public members of the Lua and ObjectTranslator classes.

This version includes the source of LuaInterfaceLoader.dll, with VS.Net 0003 project files.

What"s New in LuaInterface 0.2

LuaInterface now can be loaded as a module, so you can use the lua standalone interpreter to run scripts. Thanks to Paul Winwood for this idea and sample code showing how to load the CLR from a C++ program. The module is "nlua". Make sure Lua can find nlua.lua, and LuaInterfaceLoader.dll is either in the current directory or the GAC. The samples now load LuaInterface as a module, in its own namespace.

The get_method_bysig, get_constructor_bysig and make_object were changed: now you pass the names of the types to them, instead of the types themselves. E.g:


instead of

String=import_type("System.String") get_method_bysig(obj,"method",String)

Make sure the assemblies of the types you are passing have been loaded, or the call will fail. The test cases in src/TestLuaInterface/TestLua.cs have examples of the new functions. у мужчины 30 лет нет эрекции | потенция у мужчин чем | как выглядит виагра главная rss sitemap html link