If I could suggest: Winity.io has some cheap Windows VPSs. If it's tricky to setup a build environment and we need a snowflake in the interim, we could make one there.
AppVeyor is pretty inexpensive as a build service, and perhaps we could talk them into a freebie for Open Source. Best case, we could PowerShell a build environment setup script. We were able to build our custom "await" patched log4net build pretty easily. I don't think we had all the tests running though, especially the "impure" unit tests that require a working SQL server or other ADO.NET target etc. It would be best if we could make a test ADO.NET driver for testing logging to ADO.NET and do something similar for other tests with external dependencies. > On Nov 23, 2015, at 2:55 AM, Dominik Psenner <dpsen...@gmail.com> wrote: > > Hey Stefan, > > I blindly assume that you have some virtual machines that allow you to build > log4net against ancient .NET frameworks. Are you willing to share your build > environments? Maybe then you are not the one and only who can build a log4net > release. > > Cheers > >> On 2015-11-20 14:27, Stefan Bodewig wrote: >> Hi all >> >> I assume nobody other than me has got an environment to build a new >> release. I can't say I enjoy the process and it takes quite a bit of >> time so I'd prefer to avoid building more archives than necessary. >> >> So far we know there is a problem with the ADO.NET appender that >> requires a new release. And I recall Jeremiah wanted to give 1.2.14 a >> more thorrough testing. Is there anything else we are waiting for? >> >> Stefan >
