Closed adamralph closed 9 years ago
thanks
though I am not 100% convinced if there's value in packaging the common assembly as nuget too or whether we just go with the 2 language specific engines
Yeah, we could just link the files into both projects.
I've set up a build at codebetter CI - http://teamcity.codebetter.com/viewType.html?buildTypeId=Scriptcs_ScriptCsEngines
At the moment, I can't add GitHub status reporting, or enable a TravisCI build, since the core team are not permissioned on this repo.
The submodule caused some problems, which I managed to workaround, but I think you can remove this now and just use the NuGet packages. We just need https://github.com/scriptcs/scriptcs/pull/969 to be merged to remove the breaking changes currently in the dev branch.
fixes #4