Nswag: Nswag studio: assembly specified YamlDotNet.Signed not found

[dylanvdmerwe]

Trying to use the ASP.NET Core via API Explorer functionality in NSwagStudio v12.0 and I get the following exception:

I can get the TypeScript to generate when using the Swagger Specification option. Not sure why I cannot use the API Explorer option.

In ConfigureServices I have added AddSwaggerDocument() after AddMvc() as well as set the compatibility version.

In Configure I have this after UseMvc:

    // Add OpenAPI/Swagger middlewares
            app.UseSwagger(); // Serves the registered OpenAPI/Swagger documents by default on `/swagger/{documentName}/swagger.json`
            app.UseSwaggerUi3(); // Serves the Swagger UI 3 web ui to view the OpenAPI/Swagger documents by default on `/swagger`

[RicoSuter]

Try to compile your app with

dotnet build /p:CopyLocalLockFileAssemblies=true

[RicoSuter]

Otherwise this looks like a publish bug, maybe i need to release a bug fix

[dylanvdmerwe]

I just tried with:
<CopyLocalLockFileAssemblies>true</CopyLocalLockFileAssemblies>

But I still get the same weird YamlDotNet.Signed error. I don't have a reference to this assembly/package in any of my projects.

[RicoSuter]

Yes, nswag has a dep to this package. It seems that is missing in the installer...

[RicoSuter]

I’m offline and cant check right now, but you could try to save the nswag.json config file and run it with the nswag npm package

[RicoSuter]

I just checked on my PC, after updating NSwagStudio the Yaml dll was indeed missing... Then I uninstalled and reinstalled NSwagStudio and now it looks good... It seems that there is a problem in the WIX installer upgrade...

[dylanvdmerwe]

Uninstall and reinstall fixed the missing dll issue.

[kevinandrewsde]

Can confirm that it is simply the missing dll after updating, i copied it from the .nuget folder into the NetCore21 folder and NSwagStudio resumed working.

[RicoSuter]

Very strange, there is no change on the installer project and i can't explain why there's now a file missing - but only after upgrade not normal install.

[stefan-schweiger]

Had the same problem after updateing, uninstalling and reinstalling NSwagStudio did the trick

[IvanJosipovic]

Same issue after upgrade, remove/re-install fixed it.

[ranouf]

@IvanJosipovic thanks, I had the same issue and your solution worked for me!

[SeriousM]

yep. that worked for me too! 👍

[RicoSuter]

Does this also happen with the new patch releases?

[SeriousM]

Just updated today and only a reinstall worked for me.

[RicoSuter]

Ok thanks for replying. I have no idea how to fix this without this “workaround”.

[Anderman]

Updated today and had the same problem. Uninstall and install nswagstudio worked for me.

[IvanJosipovic]

The upgrade worked fine for me this time.

[RicoSuter]

From v11 or v12?

[IvanJosipovic]

From v11 or v12?

From 12.0.0.0 to 12.0.4.0

[RicoSuter]

Yes, i expected/hoped that this works :-) thanks for reporting

[MadMonkey87]

For me it works in the studio, but not on the CLI...

I've checked the nswag bin directory and the YamlDotNet.Signed is actually there but it won't work, also not if I manually copy this dll into my applications bin folder.

Reinstalling the npm package didn't work either

(running on netcore22 btw)

[StevenSSparks]

Same issue today -

Error:
An assembly specified in the application dependencies manifest (dotnet-nswag.deps.json) was not found:
package: 'YamlDotNet.Signed', version: '5.0.1'
path: 'lib/netstandard1.3/YamlDotNet.dll'

Moving from 11 to 12

[coder8keyboard]

Uninstalling and reinstalling nswagstudio worked for me.

[StevenSSparks]

Yes - The uninstall and reinstall worked for me. I have noticed some of the default UI settings are causing the functionality of the NSWAG studio to produce c# code that is different that previous versions.

[RicoSuter]

I have noticed some of the default UI settings are causing the functionality of the NSWAG studio to produce c# code that is different that previous versions.

There are some breaking changes - hence the v12 tag. But with some tweaks you should be able to produce compatible code..