07. Contribution
Any idea, feature request or implemented improvement is welcome. If you want to add a feature yourself, you should probably read the other Wiki pages to get a general idea of how the driver is structured and how is the repo built up.
I suggest you also cehck out the official documentation of how to create a driver.
If you want to contribute for v2 and after, you can use the v2 branch. Fork the repo, don't forget to update the submodules and start coding. When you're done, create a PR.
When in Debug build configuration, a post-build event automatically copies everything into the right LinqPad folder, so you don't have to manually build and update the assemblies for LinqPad to recognize them.
There is also a script for the Release mode, but I'll be the once doing the releases, so don't worry about that.
Also note that after v2 I didn't see any reason why I should sign the driver files with a self-signed certificate, so they are not signed anymore.
The first version of the driver had a much simple infrastructure. Fork, clone and use the v1 branch. No submodules, just the two VS projects in one solution.
Note that for v1 I did sign the driver with a self-signed certificate. There was no particular reason for this, I did it just for fun. But I didn't upload the key, so if you want to build the project, first disable assembly signing and then modify devdeploy.bat to copy to the "unsigned" folder of LinqPad (see the documentation for more details on that).
Also note that I don't have any plans for maintaining this version of the driver, so you probably shouldn't submit PRs for this branch :)