-
|
Hello Everyone, I have a small support problem with a high school robotics team that can not execute programs or scripts from the "user" folder ( EX: c:\Users\Public\wpilib\ ). They also do not have administrative access on their domain accounts.
They can however run programs as normal if they are installed into traditional locations by an Admin.
I have tried to move things around to see if I can get it working after the full install + VSCode, and am having partial success. I moved the install folder from C:\Users\Public\wpilib\ to C:\Program Files\wpilib. FRC Shuffleboard and FRC Smart Dashboard seem to launch with no problems, but FRC VS Coder 2020 (Code.exe) will not launch unless it is "Run as administrator". Students do not have a problem running Microsoft VSCode 1.52 installed to C:\Program Files\Microsoft VS Code, and does not need administrative elevation. Any thoughts of file edits or work arounds to get WPILib to operate in a locked down environment would be great. Thank You for your Time and Energy. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
The reason it's failing to launch is vscode is setup to be in portable mode. This means it stores the data next to the executable, which if it's in program files that won't work. You can remove portable mode by deleting the For everything to work right, you will still need a copy of at least the maven folder in the original location, as that is where all artifacts are grabbed from. Nothing is executed from there, but the tooling depends on things being there. You also will need to make sure a Java 11 is set to JAVA_HOME or in PATH. You can use the one from the wpilib install that you copied just fine for that purpose. |
Beta Was this translation helpful? Give feedback.
-
|
More PATH changes:
I also had to make a "Projects" folder at c:\Program Files\wpilib\2020\Projects to serve as a place to store projects created.
|
Beta Was this translation helpful? Give feedback.
The reason it's failing to launch is vscode is setup to be in portable mode. This means it stores the data next to the executable, which if it's in program files that won't work. You can remove portable mode by deleting the
datafolder that is next to the executable. Note if you do this, you'll have to manually reinstall all the extensions, as those are normally part of the portable issue.For everything to work right, you will still need a copy of at least the maven folder in the original location, as that is where all artifacts are grabbed from. Nothing is executed from there, but the tooling depends on things being there. You also will need to make sure a Java 11 is set to JAVA_HOME or…