Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error 500.30 at runtime (publish time) on version 6.4.0 #2523

Closed
amin720 opened this issue Oct 22, 2022 · 4 comments
Closed

Error 500.30 at runtime (publish time) on version 6.4.0 #2523

amin720 opened this issue Oct 22, 2022 · 4 comments
Labels
responded Responded with solution or request for more info

Comments

@amin720
Copy link

amin720 commented Oct 22, 2022

hi
I recently updated to version 6.4.0, but the runtime gives an error of 500.30 in the publish?!
Windows server specifications:
windows server 2016
microsoft net core runtime v6.0.10
microsoft net core sdk v6.0.402

@domaindrivendev
Copy link
Owner

I can't possible help with such little information. Please provide clear repro steps as per the issue guidelines

@domaindrivendev domaindrivendev added the responded Responded with solution or request for more info label Nov 15, 2022
@Rubenisme
Copy link

Rubenisme commented Dec 6, 2022

We also had this after upgrading to .NET 7, this resulted in:

Unhandled exception. System.IO.FileNotFoundException: Could not load file or assembly 'Swashbuckle.AspNetCore.Annotations, Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified.

The stack trace indicates that this happens at time of calling AddControllers in our code.

We had trimming on <PublishTrimmed>true</PublishTrimmed> with copyused mode <TrimMode>copyused</TrimMode>.

And these 2 packages:
<PackageReference Include="Swashbuckle.AspNetCore" Version="6.4.0" />
<PackageReference Include="Swashbuckle.AspNetCore.Annotations" Version="6.4.0" />

After turning trimming off, things worked fine again. For some reason this was not an issue in .NET 6 with the same package versions.

@Havunen
Copy link

Havunen commented Mar 5, 2024

I believe this is fixed in DotSwashbuckle

@martincostello
Copy link
Collaborator

Duplicate of #2550

@martincostello martincostello marked this as a duplicate of #2550 Apr 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
responded Responded with solution or request for more info
Projects
None yet
Development

No branches or pull requests

5 participants