You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 18, 2018. It is now read-only.
Hello,
I made a change that I dont want the generic json receiver to check for the code parameter in the url , but when ever I am trying to deploy the new dll's to my app I am getting this error
"Could not load file or assembly 'Microsoft.AspNet.WebHooks.Common' or one of its dependencies. Strong name signature could not be verified. The assembly may have been tampered with, or it was delay signed but not fully signed with the correct private key. (Exception from HRESULT: 0x80131045)"
so I decided to run the original genericreceiver in the samples , and apparently the original one is also having the same error , any ideas?
This is the change I made by commenting these lines
if (string.IsNullOrEmpty(code))
{
//string msg = string.Format(CultureInfo.CurrentCulture, ReceiverResources.Receiver_NoCode, CodeQueryParameter);
//request.GetConfiguration().DependencyResolver.GetLogger().Error(msg);
//HttpResponseMessage noCode = request.CreateErrorResponse(HttpStatusCode.BadRequest, msg);
//throw new HttpResponseException(noCode);
}
The text was updated successfully, but these errors were encountered:
Hello,
I made a change that I dont want the generic json receiver to check for the code parameter in the url , but when ever I am trying to deploy the new dll's to my app I am getting this error
"Could not load file or assembly 'Microsoft.AspNet.WebHooks.Common' or one of its dependencies. Strong name signature could not be verified. The assembly may have been tampered with, or it was delay signed but not fully signed with the correct private key. (Exception from HRESULT: 0x80131045)"
so I decided to run the original genericreceiver in the samples , and apparently the original one is also having the same error , any ideas?
This is the change I made by commenting these lines
The text was updated successfully, but these errors were encountered: