David Medine

> Relevant documentation is here: https://docs.microsoft.com/en-us/nuget/create-packages/creating-a-package#include-msbuild-props-and-targets-in-a-package Hiding in plain sight.

Nope. Still doesn't work. I put the native .dll in the correct folder, I copied the .props and .targets files from obj to the correct target directory for lsl_csharp, and...

Ah yes, that seems to have done the trick! I would propose the following 1. approve and merge this PR 2. open a new issue to discuss the following: 1....

> I can think of at least one: they don't link against a static library and have someone who will sent out the source code for this specific library on...

> Do I understand it correctly that one nuget package has to contain the native libraries for all target platforms? It it is so, I'd rather have the C# wrapper...

> One thing I'd like to see is a way to tell "I want to use liblsl_wrapper, but I have my own lsl.dll/.so/.dylib". Is there an attribute (e.g. ) to...

@cboulay, I am sure you don't ;-). I need a little more context, though. I am not very familiar with appveyor etc. so I am not really sure what I...

Yes, that is the link I meant. Had the wrong copy in my clipboard. OK, so it looks like I can just bash out the travis stuff and setup a...

I think we should disable what is currently there as it doesn't seem to work anyway. You are right that it does verify that a PR at least doesn't fail...

Is the path to the folder that holds all the compiled .mex files on your path? On my machine this is `\Matlab\liblsl-Matlab\mex`. I have my Matlab environment set up so...