Microsoft has released a terrific open source, multi-platform code editor called Visual Studio Code. If you want to get started with VS Code, I would recommend watching the videos provided here and then watch this excellent video about replacing PowerShell ISE with Visual Studio Code by Mike Robbins.
What about the PowerShell profile?
While Visual Studio Code can use PowerShell as its terminal, it does not use any previously setup PowerShell profile. In order to create a VS Code PowerShell profile (or VSCPP for short), select the Terminal (make sure it says PowerShell Integrated in the drop down on the right) and type $profile.
In order to create this file, you can type PS>notepad $profile in the terminal. This will open notepad and let you create the file. You can add whatever settings you prefer to in PowerShell. Once you save the profile, hit F1 or Ctrl+Shift+P to bring up the Command Palette and type Reload Window.
When the reload completes, create a new PowerShell file in VS Code and you should see the Terminal switch to PowerShell Integrated and load your newly created VSCPP (this assumes you have installed the PowerShell extension into VS Code).
NOTE: The PowerShell version that is installed as an extension into VS Code, has its own version.
If you have modules, scripts, or functions that have a dependency on a certain version of PowerShell, you will have to change, comment, or remove the dependency in order to use them in Visual Studio Code.
Citrix’s software developers are hard at work and have rolled out version 4.4 of Workspace Environment Manager. You can now download the new version here (requires Platinum licenses and login to Citrix.com). I’ve provided the release notes below.
Workspace Environment Management 4.4 includes the following new features. For information about bug fixes, see Fixed issues (below).
From this release, the Workspace Environment Management infrastructure service sends anonymous usage data to Google Analytics. For more information, and for opt-out instructions, see Infrastructure services.
From this release, Workspace Environment Management supports Citrix Profile Management 7.15. The following new options are now available in the administration console:
- Enable Logon Exclusion Check (options controlling file system exclusions)
- Enable Profile Streaming Exclusion List – Directories (option controlling user profile streaming)
In the Infrastructure Services Configuration utility, the Database Maintenance tab has a new option Agent registrations retention period. This allows agent registration logs to be deleted after a set time, which reduces the size of the database. It also reduces lag in populating the Registrations tab in the administration console.
At this release, Workspace Environment Management documentation is updated to reflect current product behavior. The documentation has also been remodeled as a single “versionless” documentation set describing the “current release.” This approach reduces duplication in the online documentation set, gives more focused search results, and is better suited to agile release processes. Associated changes include:
- A top level “current release” article contains links to previous documentation sets in PDF format only. (HTML documentation for previous releases is no longer provided.)
- “What’s new” summarizes the new functionality at the current release, and in previous releases.
- A new “Reference” section gathers reference information in one location. Port information previously in the introductory article is relocated to “Reference.”
The following issues have been fixed since Version 4.4
- If you run the Workspace Environment Management administration console as a standard Windows user, and you attempt to start the Modelling Wizard, the wizard does not start. [#WEM-187]
- When you attempt to add a user group, which is in a different AD domain to the infrastructure server, as a processed group in the Citrix User Profile Management tab in the administration console, the exception *IndexOutOfRangeException is raised, and the group is not processed. #WEM-210]
- Links in “This PC” in Windows 10 do not reflect folder redirection, and still point to local folders. [#WEM-234]
- The Agent Host waits about 5 minutes before starting if Workspace Environment Management is installed on Windows version 8, or Server 2012, and a language pack is installed. [#WEM-244]
- If you launch or refresh a UI session agent when it is not bound to a configuration set, keyboard and mouse locks which are active during the agent refresh are not released. [#WEM-321]
- If you attempt to add an agent host machine to a configuration set when the agent host machine is in a different domain to the infrastructure service, the machine is not added in the administration console Active Directory Objects tab. This happens regardless of the actual AD topology involved (parent/child domains, multi-forest setups, one- or two-way trust relationships, and so on). [#WEM-326, #WEM-299]