Skip to content

SendGrid.Extensions.DependencyInjection signature issue #1045

Description

@daiplusplus

Issue Summary

I tried to use SendGrid.Extensions.DependencyInjection in an ASP.NET WebForms application (the project already has a DI container) and the .csproj builds fine, however aspnet_compiler.exe complains:

D:\git\me\project\WebApp\web.config(214): error ASPCONFIG: Could not load file or assembly 'SendGrid.Extensions.DependencyInjection, Version=1.0.0.0, Culture=neutral, PublicKeyToken=4f047e93159395ca' or one of its dependencies. Strong name signature could not be verified.  The assembly may have been tampered with, o
r it was delay signed but not fully signed with the correct private key. (Exception from HRESULT: 0x80131045)

[FileLoadException]: Could not load file or assembly 'SendGrid.Extensions.DependencyInjection, Version=1.0.0.0, Culture=neutral, PublicKeyToken=4f047e93159395ca' 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)

Steps to Reproduce

  1. Create an ASP.NET WebForms project.
  2. Add the NuGet package SendGrid.Extensions.DependencyInjection to the project and build.
  3. Perform precompilation with aspnet_compiler.exe
  4. You'll get that error message.

Technical details:

  • sendgrid-csharp version: 9.21.0
  • SendGrid.Extensions.DependencyInjection version: 1.0.0.
  • csharp version: 8.0 (VS2019)

Activity

  1. eshanholtz commented on Sep 18, 2020

    @eshanholtz
    Contributor

    This issue has been added to our internal backlog to be prioritized. Pull requests and +1s on the issue summary will help it move up the backlog.

  2. childish-sambino commented on Sep 18, 2020

    @childish-sambino
    Contributor

    @iammichelleau

    +1s on the issue summary

  3. daiplusplus commented on Sep 19, 2020

    @daiplusplus
    Author

    @eshanholtz This is not an issue I believe I can submit a PR for because it involves a delay-signed assembly, which would be part of your build system's secrets-management.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions