-
Notifications
You must be signed in to change notification settings - Fork 508
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
Startup fails when incorrect Serilog assembly picked up from the GAC #2538
Comments
Update; |
Thanks for the info! Can you also attach the logs here so we can get a better idea of what's going on? |
Logs attached. The issue appears to only happen with the most recent version. |
This looks like something to go on! |
This is quite mysterious. Perhaps we're picking up the wrong version of a dependency from the GAC? |
@Robbie-sys can you try following the steps in #2397 (comment) and letting me know if that helps with your issue? |
Hey @rjmholt - after installing the Powershell preview and disabling the Powershell extension the problem persists. |
@Robbie-sys Can you set the log level to diagnostic in your configuration and grab the logs again? That will help me work out if the reason Serilog is getting the MissingMethodException is that it’s coming from somewhere else |
@rjmholt - Oops, please find the new logs attached. |
Thanks for that! There it is:
Compare that to the same line in my log:
Here's the method we depend on being there and here's where we call it. It doesn't yet make sense to me though why an assembly with the same name, version and public token is failing like this, but it does seem somehow that the GAC assembly is missing that method. I can tell you that this isn't an issue in PS 6 and 7, since they have much better mechanisms for dependency resolution. |
Ok our csproj specified Serilog.Sinkgs.File version 4.1.0, so something seems amiss here |
serilog/serilog#1319 (comment) The 2.0.0 assembly version seems to be very much by design... |
by design between 2.7 and 2.8... but we're on 4.1 now. Surely that should use an assembly version update |
over on #2526 @rjmholt asked to repo with the preview extension so here it is: |
Can you all give the PowerShell Preview extension a try? We just did a release of it. Don't forget to disable the regular PowerShell extension for VS Code when you enable the PowerShell Preview extension for VS Code |
@TylerLeonhardt vscode\extensions\ms-vscode.powershell-preview-2020.5.0\modules' -EnableConsoleRepl -StartupBanner "=====> PowerShell Preview Integrated Console v2020.5.0 <===== |
What were you doing that caused |
The extension has gone through a major rewrite since this was originally reported and I've not seen the same bug report crop back up, so going ahead and marking this resolved. Thanks! |
This issue has been labeled as resolved, please verify the provided fix (or other reason). |
This issue has been labeled as needing fix verification and has not had any activity a week. It has been closed for housekeeping purposes. |
Joke's on me, this problem is still very much around and cropped up again after we updated Serilog. |
This issue has been labeled as resolved, please verify the provided fix (or other reason). |
The fix for this is merged, it will be in the next pre-release (coming out today). PowerShell/PowerShellEditorServices#2197 |
System Details Output
Issue Description
Hey everyone, running into an issue where I can't execute from the editor.
Powershell works as expected from the terminal. I've uninstalled and reinstalled the extension as well as Visual Studio Code. Any help would be greatly appreciated!
The text was updated successfully, but these errors were encountered: