Debugging with Source and Symbols is not working

[garora]

Documentation is sufficient to setup repository to work local here is the link: Debugging with Source and Symbol. After following all steps, I tried to run Bitbucket receiver sample. Unfortunately, after several tries I am getting exception 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)

Any help on this will be highly appreciated.

Update (on Sept 09, 2017): Updated link for ASP.NET WebHooks debugging.

Note: Issue#62 does not work for me.

[HenrikFrystykNielsen]

ok, will have a look.

[garora]

@HenrikFrystykNielsen - I am still facing this issue. Any alternatives to this till we got a solution of this issue?

[HenrikFrystykNielsen]

I also can't make it work -- trying to ask the VS guys about what might be going on.

[garora]

Thanks, looking forward a positive response 👍

[garora]

Any response from VS guys on this? This looks like showstopper for development

[garora]

@HenrikFrystykNielsen - any updates on this? Still getting same issue even on a new dev box.

[LuisPignataro]

Same problem Here!! Any WorkAround?

[garora]

@LuisPignataro - No, its not at our end. I hope this issue will resolve sooner.

[garora]

@HenrikFrystykNielsen - any news on this front?

[PoulTur]

I ran across same issue today.

[garora]

@PoulTur - Still waiting on it.

[PoulTur]

@garora Actually all went ok, by just importing the Webhooks package to a fresh solution and then copying the code from sample project.

[garora]

@PoulTur - nice to hear that. But, actual issue was something related to DEBUG symbols.

[garora]

Still facing same issue even on clean install on new box.

[garora]

What is the best way to connect with VS guys?

[dougbu]

Discussions about symbol servers, inclusion of symbols in released packages, and source linking for .NET are ongoing. The plan is for WebHooks packages to take the same approaches in our next release.

In the meantime however, we'll investigate.

[garora]

I will be start working on #15 as soon as the aforesaid issue get resolved.

[dougbu]

I tested breakpoints in my handler, function breakpoints e.g. on Microsoft.AspNet.WebHooks.BitbucketWebHookReceiver.ReceiveAsync(...), and moving around from each. I also did similar testing with a Stripe handler. Other than landing in disassembly instead of source code when using function breakpoints, I didn't hit any snags. (I could reach source for the same classes navigating in the call stack from other breakpoints.) I even debugged a Release handler and lost only a few locals.

Deploying to Azure (regular Publish from Visual Studio 2017), using Application Insights (see https://docs.microsoft.com/en-us/azure/application-insights/app-insights-asp-net), and debugging (see https://docs.microsoft.com/en-us/aspnet/webhooks/diagnostics/debugging) all seems fine. In particular the http://srv.symbolsource.org/pdb/Public symbol server worked well.

What exactly is failing for others these days? I'm wondering if for example older Web API templates configured handler applications differently. Or I may not have tried the actions others have had problems with.

[dougbu]

@garora what exactly is blocking work on #15? That is, what debugging aspect isn't working for you?

[garora]

@dougbu - Thanks for the heads up on the issue. I will try to replicate the same in couple of ours from now and will be keep here posted.

[garora]

@dougbu - Now, its working for me as well. I will start work and make PR . You can close this issue.

[dougbu]

Something external likely changed. Issue is no longer valid.