I have an ASP.NET WebAPI project where I am attempting to replace our old XmlDocumentationProvider page with Swagger UI. I am using the swashbuckle swagger for webAPI 5.3.1
I had the same issue. Finally I could leave my [ResponseType()] as is with an ORM entity as I wanted to, but I managed to make swagger not freeze by adding another model in [SwaggerResponse()]
Here is more info in that: https://mattfrear.com/2015/04/21/generating-swagger-example-responses-with-swashbuckle/