Jeff Borden
Jeff Borden

Reputation: 1419

Azure Error Referencing Local Path

I've got a web app deployed on Azure and I'm getting an error on the Azure deployment that shows the reference to a class library in the same solution.

But the error message shows a file path on my local:

Object reference not set to an instance of an object. XXX.Domain.Concrete.EFBusinessRepository.PrepForConversionToHtml(XXX x) in c:\dev\repos\Jeff\ClassLibrary\Concrete\EFBusinessRepository.cs:1280

and not one more typical to Azure:

Object reference not set to an instance of an object. XXX.Domain.Concrete.EFBusinessRepository.PrepForConversionToHtml(XXX x) in E:\sitesroot\0\bin.....

Am I overreacting on this? It just seems dumb that it's showing a path on my local. I'm in the midst of tracking down all of the errors of a new Azure deployment, so apologies if this is expected behavior.

Upvotes: 2

Views: 374

Answers (1)

allen
allen

Reputation: 4647

Adding in the resolution as answer here.

The pdb files contain additional debug information wrt your binaries. Any failures that show up on a machine with pdbs deployed will show a richer stack information referring back to the source code files with line numbers etc. Deleting out the pdbs will resolve your issue. Plus you ideally should not be deploying pdbs with your retail product bits unless you are actively debugging something in production.

Upvotes: 1

Related Questions