-
Notifications
You must be signed in to change notification settings - Fork 1
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 dropping schema #3
Comments
Did you ever figure this out? I ran into this when trying to reference Microsoft.SqlServer.SqlManagementObjects in a .NET Core context (the nuget.org package says it supports .NET Standard). I logged an issue here: https://github.com/microsoft/sqltoolsservice/issues/927 |
@jzabroski I will have to look into it. I have been working a lot on other modules and a lot of stuff has changed in the mean time. I will let you know |
@sanderstad ShueyBubbles from Microsoft agreed with my root cause analysis and adds more details in the above linked issue. |
@sanderstad If you're using PowerShell, then behavior probably depends on what .net runtime PowerShell is running on: PowerShell Core uses .net core (and will error) and PowerShell 5 uses .net framework |
Describe the bug
When removing the schemas you can get this error
WARNING: [21:08:56][Invoke-DbrDbRefresh] Something went wrong dropping the schema | Exception calling "EnumOwnedObjects" with "0" argument(s): "Constructor on type 'Microsoft.SqlServer.Management.Smo.SqlObjectUnion' not found."
Expected behavior
To remove all the schemas
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: