-
-
Notifications
You must be signed in to change notification settings - Fork 11
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
IQueryableObjectSource not found exception #30
Comments
Do you have VS 17.9? |
The IQueryableObjectSource.dll is included in the VSIX and should be available in the following folder: C:\Users\voffka\AppData\Local\Microsoft\VisualStudio\17.0_e12c492d\Extensions\5kiuggqj.gub\netcoreapp Can you check if it's there? |
Can you run Procmon and see if the DLL is accessed or not? |
No, procmon doesn't capture any attempts to load IQueryableObjectSource FWIW, getting "System.MissingMethodException thrown when loading the VisualizerAssemblyLoadContext. Message: Cannot dynamically create an instance of type 'Microsoft.VisualStudio.NetCoreAssemblyResolution.VisualizerAssemblyLoadContext'. Reason: No parameterless constructor defined." in the debugger output Also this VS Community Edition running as an admin |
@otryshko I have no idea why VS doesn't load the Can you post your steps to reproduce at https://developercommunity.visualstudio.com/t/SystemMissingMethodException-thrown-whe/10612094 ? |
Can you share a repro project? |
Figured it out; @Giorgi you were correct that it's related to the access denied to the extension folder (dll/Resources). The project is the asp.net core app running under the IIS AppPool identity. Once I granted the identity account access to the folder, it started to work. Not sure if it's possible to check for it in advance/show better error message. |
Nice to hear that it's working now! I'm also not sure if it's possible to detect that but as the issue is now solved for you I'll close this issue. |
The text was updated successfully, but these errors were encountered: