Boolean operators and TryGet method

[Paxol]

Implementation of true/false operators, boolean implicit conversion and TryGet method to extract the content of a successful Result

Closes #44

[marcominerva]

Could you provide a sample of the usage of this feature? You can update the samples included in the project.

[Paxol]

I've added the example, but there is a runtime error. I will look more into this later.

fail: Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware[1]
      An unhandled exception has occurred while executing the request.
      System.MissingMethodException: Method not found: 'Boolean OperationResults.Result`1.op_Implicit(OperationResults.Result`1<!0>)'.
         at OperationResults.Sample.BusinessLayer.Services.PeopleService.GetWithImageAsync(Guid id)
         at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[TStateMachine](TStateMachine& stateMachine)
         at OperationResults.Sample.BusinessLayer.Services.PeopleService.GetWithImageAsync(Guid id)
         at Program.<>c.<<<Main>$>b__0_4>d.MoveNext() in /home/mirko/tmp/OperationResults/samples/MinimalApis/OperationResults.Sample/Program.cs:line 80
      --- End of stack trace from previous location ---
         at Microsoft.AspNetCore.Http.RequestDelegateFactory.ExecuteTaskResult[T](Task`1 task, HttpContext httpContext)
         at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext)
         at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext, ISwaggerProvider swaggerProvider)
         at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddlewareImpl.Invoke(HttpContext context)

[Paxol]

I found what the problem is. Basically some references problem present both in the minimal api sample and in the controller sample.

The main project references OperationResults.Sample.BusinessLayer.csproj and OperationResults.AspNetCore.Http.csproj.
While the BusinessLayer references the local OperationResults.csproj, the OperationResults.AspNetCore.Http.csproj references the OperationResultTools nuget package.

This causes some problems to the runtime that searches the method to use in the wrong assembly.

I found that going into the OperationResults.AspNetCore.Http.csproj project and referencing the local OperationResults.csproj "solves" the issue (or makes it more ugly).

So I thing that the solution to this exception goes bejond the scope of this PR.