Type comparisons fail because the dynamic assembly type doesn't match the usual assembly type. #1123
              
                Unanswered
              
          
                  
                    
                      DanielVernall
                    
                  
                
                  asked this question in
                Q&A
              
            Replies: 0 comments
  
    Sign up for free
    to join this conversation on GitHub.
    Already have an account?
    Sign in to comment
  
        
    
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi there,
We're using Asp.Versioning with OData on Asp.Net Core and we're struggling with type mismatch which I believe is caused by Asp.Versioning loading a new assembly for each api version (as described in the comments on DefaultModelTypeBuilder)
This StackOverflow question has more information about the problem (before we realised it was related to Asp.Versioning).
We're trying to ignore certain properties in the Swagger API but we can't compare our types against interfaces nor use them as dictionary keys to get cached information.
Here's some output from the immediate window showing the type mismatch.
Beta Was this translation helpful? Give feedback.
All reactions