This small fix prepends the `INCLUDE` environment variable instead of
overriding it.
This is important if one has already added paths to this environment,
for example, in cases where one needs a common set of codebase that gets
included in all C/C++ projects (such as utility functions and such).
nu_msvs doesn't work at all on my setup, vswhere return empty string
when called from nushell, the only way i made it to work is calling it
from powershell
on json parsing side
installationPath is not an array, and vswhere return an array of
installations is not correct
e.g
```json
[
{
"instanceId": "406fd398",
"installDate": "2024-04-25T13:16:29Z",
"installationName": "VisualStudioPreview/17.14.0-pre.5.0+36025.13",
"installationPath": "C:\\Program Files (x86)\\Microsoft Visual Studio\\2022\\Preview",
"installationVersion": "17.14.36025.13",
"productId": "Microsoft.VisualStudio.Product.BuildTools",
"productPath": "C:\\Program Files (x86)\\Microsoft Visual Studio\\2022\\Preview\\Common7\\Tools\\LaunchDevCmd.bat",
"state": 4294967295,
"isComplete": true,
"isLaunchable": true,
"isPrerelease": true,
"isRebootRequired": false,
"displayName": "Visual Studio Build Tools 2022",
"description": "Visual Studio Build Tools vous permet de générer des applications MSBuild natives et managées sans passer par l'IDE Visual Studio. Il existe des options pour installer les compilateurs et bibliothèques Visual C++, ainsi que la prise en charge d'ATL, de MFC et de C++/CLI.",
"channelId": "VisualStudio.17.Preview",
"channelUri": "https://aka.ms/vs/17/pre/channel",
"enginePath": "C:\\Program Files (x86)\\Microsoft Visual Studio\\Installer\\resources\\app\\ServiceHub\\Services\\Microsoft.VisualStudio.Setup.Service",
"installedChannelId": "VisualStudio.17.Preview",
"installedChannelUri": "https://aka.ms/vs/17/pre/channel",
"releaseNotes": "https://go.microsoft.com/fwlink/?LinkId=661273#17.14.0-pre.5.0",
"resolvedInstallationPath": "C:\\Program Files (x86)\\Microsoft Visual Studio\\2022\\Preview",
"thirdPartyNotices": "https://go.microsoft.com/fwlink/?LinkId=661288",
"updateDate": "2025-04-29T20:49:54.8401699Z",
"catalog": {
"buildBranch": "d17.14",
"buildVersion": "17.14.36025.13",
"id": "VisualStudioPreview/17.14.0-pre.5.0+36025.13",
"localBuild": "build-lab",
"manifestName": "VisualStudioPreview",
"manifestType": "installer",
"productDisplayVersion": "17.14.0 Preview 5.0",
"productLine": "Dev17",
"productLineVersion": "2022",
"productMilestone": "Preview",
"productMilestoneIsPreRelease": "True",
"productName": "Visual Studio",
"productPatchVersion": "0",
"productPreReleaseMilestoneSuffix": "5.0",
"productSemanticVersion": "17.14.0-pre.5.0+36025.13",
"requiredEngineVersion": "3.14.2074.57458"
},
"properties": {
"campaignId": "",
"channelManifestId": "VisualStudio.17.Preview/17.14.0-pre.5.0+36025.13",
"includeRecommended": "0",
"nickname": "",
"setupEngineFilePath": "C:\\Program Files (x86)\\Microsoft Visual Studio\\Installer\\setup.exe"
}
}
]
```
I like to activate nu_msvs in my config by default and don't need a
message that tells me the command has been run when doing this. This
commit adds a --silent option so there's no message displayed when
running the command.
This PR makes the location of vswhere more programmatic by looking where
it's supposed to be located on the file system instead of relying on it
being in your path.
I changed `export-env {}` at the beginning to a custom command to avoid
having `export-env` run when loading the module
because:
1. I couldn't use `nu_msvs activate` because it depends on env vars
being set that were hidden with `nu_msvs deactivate`
2. It seems that `export-env` executed at `use`, leaves `$env.FILE_PWD`
available in the environment which I think may be
a bug. So, putting it in a custom command avoids that.
This updates the nu_msvs module. There were several things that I didn't
think looked proper for Windows so I changed them an hopefully made this
module a tiny bit better.
1. fix: update `(sys).host` to `sys host` to work for 0.94.x
2. fix: handle incorrect behaviors when re-importing nu_conda or nu_msvs
3. doc: update minimum requirements of nushell in README.md
1. feat(nu_conda): add `nu_conda list` to list available envs
2. fix: use `print` instead of `echo` to print warnings
3. doc: change minimum support version to 0.83.0
* refactor: ✨ move in one commit
Eveything in modules should probably be changed to `exported` defs.
The idea is to move everything first to keep proper history.
* refactor: 📝 add modules readme (wip)
* refactor: ✨ small move
* refactor: 📝 changed nestring, updated modules readme
* refactor: 📝 to document or not to document
* fix: 🐛 themes
replaced the template to use `main` and regenerated them
from lemnos themes.
* Revert "fix: 🐛 themes"
This reverts commit 4918d3633c8d2d81950a0ed0cfd9eb84241bc886.
* refactor: ✨ introduce sourced
- Created a source `root` in which sourcable demos are stored.
Some might get converted to modules later on.
- Moved some files to bin too.
* fix: 🐛 fehbg.nu
* fix: 🐛 modules/after.nu
* moved some other stuff around
---------
Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-04-25 17:56:25 -05:00
Renamed from virtual_environments/nu_msvs/nu_msvs.nu (Browse further)
