-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
Document: Port to portable mode #53653
Comments
Yes that should do it. Not sure this warrants a docs section. If we get more questions/requests, I'll put it in the docs. |
@schlamar |
Reopening for documentation. |
@joaomoreno They are both win10 x64, the only different is vscode install in Driver C in my work PC . Which need admin right to copy files into, may be by this ? |
Portable mode is not supported if you install VS Code. It is only supported if you get the ZIP download. |
No, it sopport both installed and zip version actually . Everything is fine after moving to |
I have all of that working but I still can't run dotnet commands like dotnet new console without installing the CLI on the host machine. I have downloaded the CLI zip and have it on my drive but when I try to run the commands through the integrated terminal it errors stating that dotnet is not a cmdlet function etc. How do I get the integrated terminal or VS code or OmniSharp or whatever to look at the CLI on the portable drive and not just look for it in the default location on the C: drive? |
To port from zipped 1.24 to real portable mode 1.25 I
C:\Users\<username>\AppData\Roaming\Code
to<VSCode>\data\user-data
C:\Users\<username>\.vscode\extensions
to<VSCode>\data\extensions
For now, everything seems to be working fine.
Is this the recommended way to port an existing setup to real portable mode? If yes, you should consider adding this to the docs.
The text was updated successfully, but these errors were encountered: