Open SahFari opened 2 months ago
@SahFari
Could you let me know if you're only using the terminal in VSCode?
I am unable to reproduce this.
What OS version are you running?
In the past, I have seen inconsistencies in dependency/package resolution between the terminal in VSCode and the PowerShell Console. Could you try again using the PowerShell console outside of VSCode?
@rynardtspies
I mostly use Editor in VsCode.
I will do new tests tomorrow:
I use WIN 10: Major Minor Build Revision
10 0 19045 0
@rynardtspies Hi, I installed 1.9 on my PC and on a lab server. I removed all other versions from my pc not on the lab server. The lab server is on PowerShell 7.4.4. Mine PC is on PowerShell 7.4.5.
This screenshot is from the lab server
These screenshot is from my pc
Update: don't need to import the module each time I start VSCode/PowerShell Console!
Don't know if it's customary to run Import-Module after an Update-Module or Install-Module -RequiredVersion or not, however, this is what I have done.
P.s. I am on PowerShell 7.4.5. using the latest version of vsCode. D.s.
I updated the module
I have been able to connect to RSC, once afer that has other RSC commands failed, including Connect-Rsc.
I have closed and reopend vsCode, more than 5 times yesterday and I think another 5 times today. I have rebooted my PC as well.
I have uninstalled all other versions leaving 1.7. Same behavier after an import-module. Reinstalled version 1.5, uninstalled 1.7. New import-moudle, closed and reopend vsCode.
I have now reinstalled 1.7 and 1.8 without running import-module, closed and reopened vsCode. RSC commands I have tested works.
These are the errors: