protobuf

Commit Graph

Author	SHA1	Message	Date
Romfos	09f094c811	[dotnet, csharp] Run tests for supported platforms .NET 6, .NET Framework 4.6.2 (#12378 ) What's changed? - Update some nuget packages (for test projects) - Run unit tests for supported platforms: .NET 6 + .NET Framework 4.6.2 Notes: .NET Framework 4.6.1 is out of support, .NET Framework 4.6.2 is the older version that is still supported https://devblogs.microsoft.com/dotnet/net-framework-4-5-2-4-6-4-6-1-will-reach-end-of-support-on-april-26-2022/ .NET 5 is out of support https://devblogs.microsoft.com/dotnet/dotnet-5-end-of-support-update/ .NET Core 3.1 is out of support https://devblogs.microsoft.com/dotnet/net-core-3-1-will-reach-end-of-support-on-december-13-2022/ Visual studio 2012 is out of support https://devblogs.microsoft.com/visualstudio/support-ends-for-older-versions-of-visual-studio-feb2022 Closes #12378 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/12378 from Romfos:main `227661e02c` PiperOrigin-RevId: 523196896	2 years ago
Mike Kruskal	ed5c57a574	Remove all autotools usage (#10132 ) * Bazelfying conformance tests Adding infrastructure to "Bazelify" languages other than Java and C++ * Delete benchmarks for languages supported by other repositories * Bazelfying benchmark tests * Bazelfying python Use upb's system python rule instead of branching tensorflow * Bazelfying Ruby * Bazelfying C# * Bazelfying Objective-c * Bazelfying Kokoro mac builds * Bazelfying Kokoro linux builds * Deleting all deprecated files from autotools cleanup This boils down to Makefile.am and tests.sh and all of their remaining references * Cleanup after PR reorganizing - Enable 32 bit tests - Move conformance tests back - Use select statements to select alternate runtimes - Add internal prefixes to proto library macros * Updating READMEs to use bazel instead of autotools. * Bazelfying Kokoro release builds * First round of review fixes * Second round of review fixes * Third round of review fixes * Filtering out conformance tests from Bazel on Windows (b/241484899) * Add version metadata that was previously scraped from configure.ac * fixing typo from previous fix * Adding ruby version tests * Bumping pinned upb version, and adding tests to python CI	2 years ago
James Newton-King	aa15931050	Update .NET SDKs to LTS versions	3 years ago
listonjesse	2ae7cf0e03	Auxillary -> Auxiliary	5 years ago
Paul Yang	e8016753e3	Maven requires https connection (#7110 ) (#7114 )	5 years ago
Paul Yang	39f4240856	Maven requires https connection (#7110 )	5 years ago
Brian Wignall	a104dffcb6	Fix typos (#7050 ) Uses https://en.wikipedia.org/wiki/Wikipedia:Lists_of_common_misspellings/For_machines to find likely typos, with https://github.com/bwignall/typochecker to help automate the checking.	5 years ago
Jie Luo	d1eeb852fc	compatibility test between last released and current for java python php (#6441 ) * compatibility tests between last released and the current version	5 years ago
Jie Luo	e399308ef0	Add csharp compatibility tests between last released and the current version (#6407 ) * Add csharp compatibility tests for 3.7.0 * Add compatibility test between last major version with current for C# * Update last version number * compatibility tests between last released and the current version * fix typo	5 years ago
Sydney Acksman	15fab9109d	Bump target frameworks of C# programs from netcoreapp1.0 to netcoreapp2.1 (#5838 ) * Bump target frameworks from netcoreapp1.0 to netcoreapp2.2. Move global.json up to root of repo, change SDK ver to 2.2.100 Change .net core sdk in dockerfile for kokoro to ver 2.2.100 * Re-add curl install * Change all exe target to 2.1 * Fix incorrect versions in global.json and Dockerfile * Downgrade version to 2.1 to match exe targets * introduce separate testing Dockerfile for C# * revert changes to the shared Dockerfile * use netcoreapp2.1 for C# conformance tests * use language specific dockerfile for testing C# * Edit compatibility tests script to use parameters instead of file copies * install dotnet SDK on windows before running the tests * update csharp_EXTRA_DIST	6 years ago
Jon Skeet	f26e8c2ae0	Convert C# projects to MSBuild (csproj) format This has one important packaging change: the netstandard version now depends (implicitly) on netstandard1.6.1 rather than on individual packages. This is the preferred style of dependency, and shouldn't affect any users - see http://stackoverflow.com/questions/42946951 for details. The tests are still NUnit, but NUnit doesn't support "dotnet test" yet; the test project is now an executable using NUnitLite. (When NUnit supports dotnet test, we can adapt to it.) Note that the project will now only work in Visual Studio 2017 (and Visual Studio Code, and from the command line with the .NET Core 1.0.0 SDK); Visual Studio 2015 does not support this project file format.	8 years ago
Jie Luo	7288689d8c	Add csharp compatibility tests against v3.0.0 and run on Travis.	8 years ago

4 Commits (ad2dd26ffc6858b7a0e991d75df55897cc24b2e5)