Lloyd Ho 95944820b0 Fix aspnet-mono-ngx-my tests (#5010) 6 years ago
..
aspnet-mono-ngx 95944820b0 Fix aspnet-mono-ngx-my tests (#5010) 6 years ago
aspnetcore fc1e2e42b7 Updating to dotnet core 3.0 (#4955) 6 years ago
aspnetcore-corert 17f48388e4 Marking core-rt as stripped (#4998) 6 years ago
aspnetcore-mono 971de70d68 Update projects to use ref-asm nuget (#4923) 6 years ago
beetlex 4f176be94f beetlex-core update .net core to v3.0 (#5006) 6 years ago
carter 7dd3c03941 Update .NET Dockerfiles to use Microsoft Container Registry (#4919) 6 years ago
evhttp-sharp eb67470bd1 Make HTTP header verification more strict (#3643) 7 years ago
nancy 971de70d68 Update projects to use ref-asm nuget (#4923) 6 years ago
revenj 80831b7327 Try to fix Revenj build on Citrine (#3791) (#3798) 7 years ago
servicestack b472c2f4dd Remove source_code files, count all files instead (#3715) 7 years ago
tetsuweb 36cdd4d91b Update Tetsu.Web to v0.1.5 (#4971) 6 years ago
.gitignore 7dd3c03941 Update .NET Dockerfiles to use Microsoft Container Registry (#4919) 6 years ago
README.md 4322cacaef Update documentation links (#4541) 6 years ago

README.md

C# (CSharp) Frameworks

The information below contains information specific to C#. For further guidance, review the documentation.

Infrastructure Software Versions

Adding a New C# Framework

Different Mono Versions

While we have not currently run into the need to have multiple simultaneous Mono installations, it is possible

Debugging Mono + NuGet

Mono understands an environment variable MONO_LOG_LEVEL=debug that is helpful for checking that mono is properly working e.g. loading necessary DLL's.

Most NuGet commands understand a -Verbosity flag, which is great because the error messages can be completely mystifying when working with Mono too. Use this would enable all the debugging you can:

$ MONO_LOG_LEVEL=debug mono NuGet2.exe update -Verbosity "detailed" -self

For example, aspnet was constantly failing with this message:

Could not connect to the feed specified at 'https://www.nuget.org/api/v2/'. Please verify that the package source (located in the Package Manager Settings) is valid and ensure your network connectivity.`. 

Using -Verbosity "detailed" shows that the real error is actually a Mono library problem, as so:

System.InvalidOperationException: Could not connect to the feed specified at 'https://www.nuget.org/api/v2/'. Please verify that the package source (located in the Package Manager Settings) is valid and ensure your network connectivity. ---> System.Net.WebException: libMonoPosixHelper.so ---> System.DllNotFoundException: libMonoPosixHelper.so
  at (wrapper managed-to-native) System.IO.Compression.DeflateStreamNative:CreateZStream (System.IO.Compression.CompressionMode,bool,System.IO.Compression.DeflateStreamNative/UnmanagedReadOrWrite,intptr)
  <snip>

More helpful info is here, here

Limited Travis-CI Verification

Because the verification system uses the linux-only Travis-CI service, verifying Windows-only tests has to be done manually and is very time consuming.

Consider including an additional test, likely based on Mono and FastCGI (e.g. xsp), that can run on Linux when submitting a new framework. This will drastically speed up our ability to merge in your pull request.

Get Help

C# Experts

There aren't any C# experts listed, yet. If you're an expert, add yourself!

C# Community

We don't have any community links added. Add some to help further guide future contirbutors.

Resources

If you stumble upon some helpful links or discussions, add them for easy reference for future contributors.

Note about this ServiceStack test

Only the default ngnix test for linux remains in the benchmark_config as it is the only one that has consistently appeared in final round results. The xsp tests and nginx database tests are not currently working, though the supporting files remain. Pull requests to fix these implementations are welcome!