More often than not, I reach for .NET in Max just because there's that one property or method not exposed to MAXScript, yet everything else could be easily done MAXScript-side. Using compiled libraries and the inconvenience that comes with that as well as the workarounds needed to make hot reloading possible make that an obvious overkill, especially since these are usually cases of quick experiments and prototyping. For a while, I took advantage of the on-the-fly compilation, but it means you wind up with a big piece of string – you lose syntax highlighting and error offsets become a math puzzle – and now with the CodeDomProvider.CompileAssemblyFromSource vs CSharpUtilities.CSharpCompilationHelper split, the boilerplate even often dwarfs the actual logic.
.NET in MAXScript: The Easy Way A Practical Guide to the native↔managed interop
Subscribe to:
Comments (Atom)
