alexeymarkov

There are some problems which I could not resolve but the idei is clear. 0: Error compiling function: HttpSignalRNegotiate.cs(167,101): error CS0012: The type 'IServiceManager' is defined in an assembly that...

Yes, this will be ignore. Alternatively you can also use a custom IClaimsPrincipalAuthorization implementation and apply it to anonymous endpoints `public class AllowAnonymousClaimsAuthorization : IClaimsPrincipalAuthorization { public Task IsAuthorized(ClaimsPrincipal claimsPrincipal,...

It seems the parameter "--netcore21" is not necessary anymore.

should be At the moment I removed the task completely and now the build works.

It seems you removed ConvertErrors from publish completely. This will work however this won't throw errors if there are any. As a consequence at out DevOps build this may produce...

I will check again,

You are right. The build is called before. But recently I got a corrupted functions.dll The error in ___fm__errors.json_ `{"Severity":0,"Message":"Unexpected error: Could not load file or assembly '*****, Version=1.1.0.0, Culture=neutral,...

I think the following code should be changed catch(System.Exception ex) { {{#if HasHttpResponseHandler}} var responseTask = pluginFunctions.CreateResponseFromException(command, ex); var handledResponse = responseTask != null ? (await responseTask) : null; return...

My custom ResponseHandler just throws an original exception and it works well (Failure in App Insights as expected). The problem with the handler is that it hides the origin of...

I just found out this is already possible to generate an instance of SignalRConnectionInfo using existing SignalR extension implementation. Have a look at the [sample](https://github.com/Azure/azure-functions-signalrservice-extension/blob/dev/samples/simple-chat/csharp/FunctionApp/Functions.cs#L33l).