We're pleased to announce the immediate availability of a new release of SphinxConnector.NET! Among other things, we've been busy to add support for Sphinx 2.1 in the course of which we've made several optimizations that should improve performance and reduce memory usage with SphinxQL and the fluent API.

The latter now properly supports enums and has gotten support for JSON attributes that are going to be introduced with Sphinx 2.1. The methods First() and FirstOrDefault() can now also be executed as futures, and we've added the possibility to perform operations like attaching and flushing indexes to the fluent API.

There are several other additions, improvements, and bugfixes which are listed in the version history.

I’ve been asked a few times if there’s a quick way to get logging output from SphinxConnector.NET without setting up a “real” logging framework like NLog. Here’s one: Common.Logging comes with two adapters named TraceLoggerFactoryAdapter and ConsoleOutLoggerFactoryAdapter. The latter (obviously) logs messages to the console, while the former logs messages via .NET’s Trace class. One nice thing about the trace log is that it can be accessed via Visual Studio’s ‘Output’ window (CTRL+ALT+O) if your application is running with a debugger attached (F5).

Here is the relevant code:

[Conditional("DEBUG")]
private static void SetupLogging()
{
    LogManager.Adapter = new TraceLoggerFactoryAdapter
    {
        Level = LogLevel.All,
        ShowLevel = true,
        ShowDateTime = true,
    };
}

I also added a Conditional attribute to the setup method to ensure that it is only being called in a debug configuration.