2.0.24 https://github.cds.internal.unity3d.com/unity/com.unity.ide.visualstudio/pull/221

Integration:

- Remove support for `Visual Studio for Mac`. Please use `VS Code` going forward.
- Performance optimizations.

Project generation:

- Allow customization of `langversion` when using a `rsp` file.
- Move to `slnx` solution generation when using `SDK-Style` projects.
- Both `VS Code` and `Visual Studio 2026` are now using `SDK-Style` projects by default.

Author: simonferquel

.gitattributes

@@ -2,4 +2,5 @@
 
 # Denote all files that are truly binary and should not be mergeable.
 *.dll binary
-*.exe binary
+*.exe binary
+*.png binary

.gitignore

@@ -8,14 +8,16 @@ ValidationSuiteResults
 Assets/Plugins**
 obj/
 /UserSettings/
+/ProjectSettings/*.asset
 /*.csproj
 /*.sln
+/*.csproj.user
+/*.slnx
 /Temp
 *.bak
 *.bak.meta
 .DS_Store
 
+Packages/packages-lock.json
 Packages/com.unity.ide.visualstudio/Editor/COMIntegration/Release/build/
 Packages/com.unity.ide.visualstudio/Editor/COMIntegration/Release/COMIntegration.exe
-Packages/com.unity.ide.visualstudio/Editor/Plugins/AppleEventIntegration.bundle/
-!Packages/com.unity.ide.visualstudio/Editor/Plugins/AppleEventIntegration.bundle/**/*.meta

.scripts/build-appleeventintegration.sh

@@ -40,28 +40,11 @@ build_cpp_win:
         - "Packages/com.unity.ide.visualstudio/Editor/COMIntegration/Release/COMIntegration.exe"  
 
 
-build_native_mac:
-  name: Build Apple Event Integration
-  agent:
-    type: Unity::VM::osx
-    image: test-platform/macos-10.15:stable
-    flavor: b1.large
-    config:
-      env_vars:
-        - PATH=/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin
-  commands:
-    - .scripts/build-appleeventintegration.sh
-  artifacts:
-    appleeventintegration:
-      paths:
-        - "Packages/com.unity.ide.visualstudio/Editor/Plugins/AppleEventIntegration.bundle/**"  
-
-
 pack:
   name: Pack
   agent:
     type: Unity::VM
-    image: package-ci/win10:stable
+    image: package-ci/win10:v4
     flavor: b1.large
   commands:
     - npm install upm-ci-utils@latest -g --registry https://artifactory.prd.cds.internal.unity3d.com/artifactory/api/npm/upm-npm
@@ -72,7 +55,6 @@ pack:
         - "**/upm-ci~/packages/**/*"
   dependencies:
   - .yamato/CI.yml#build_cpp_win
-  - .yamato/CI.yml#build_native_mac
 
 
 commit_ci_release:
@@ -119,11 +101,6 @@ run_vetting_test_project_{{ editor.version }}:
     PATH: /home/bokken/bin:/home/bokken/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/sbin:/home/bokken/.npm-global/bin::/home/bokken/npm-global/bin
     DISPLAY: ":0"
   commands:
-{% if platform.name == "linux" -%}
-    - pip install unity-downloader-cli --index-url https://artifactory.prd.it.unity3d.com/artifactory/api/pypi/pypi/simple --upgrade --user
-{% else -%}
-    - pip install unity-downloader-cli --index-url https://artifactory.prd.it.unity3d.com/artifactory/api/pypi/pypi/simple --upgrade
-{% endif -%}
     - npm config set prefix '~/npm-global'
     - npm install upm-ci-utils@latest -g --registry https://artifactory.prd.cds.internal.unity3d.com/artifactory/api/npm/upm-npm
     - unity-downloader-cli -u {{editor.version}} -c editor --fast --wait --published-only
@@ -152,11 +129,6 @@ run_feature_test_project_{{ platform.name }}_{{ editor.version }}:
     DISPLAY: ":0"
   {% endif %}
   commands:
-{% if platform.name == "linux" -%}
-    - pip install unity-downloader-cli --index-url https://artifactory.prd.it.unity3d.com/artifactory/api/pypi/pypi/simple --upgrade --user
-{% else -%}
-    - pip install unity-downloader-cli --index-url https://artifactory.prd.it.unity3d.com/artifactory/api/pypi/pypi/simple --upgrade
-{% endif -%}
     - {{ platform.envsetup }}
     - unity-downloader-cli -u {{editor.version}} -c editor -c linux -c macos -c windows --fast --wait --published-only
     - npm install upm-ci-utils@latest -g --registry https://artifactory.prd.cds.internal.unity3d.com/artifactory/api/npm/upm-npm

.yamato/CI.yml

@@ -6,7 +6,7 @@
 # How to contribute (for everyone)
 
 - Please create a PR against the latest `version-x.y.z` branch.
-- In the [`.scripts`](.scripts) folder, you should find how to build IDE integrations with VS and VS for Mac. Make sure to remove all build artifacts if needed, given we do not want Unity to import unwanted files. You can find as well extra notes regarding building the MacOS part [here](Packages/com.unity.ide.visualstudio/Editor/AppleEventIntegration~/howtobuild.txt), and the Windows part [here](https://github.cds.internal.unity3d.com/unity/com.unity.ide.visualstudio/blob/next/master/Packages/com.unity.ide.visualstudio/Editor/COMIntegration/COMIntegration~/howtobuild.txt).
+- In the [`.scripts`](.scripts) folder, you should find how to build IDE integrations with VS and VS for Mac. Make sure to remove all build artifacts if needed, given we do not want Unity to import unwanted files. You can find as well extra notes regarding building the Windows specific part [here](https://github.cds.internal.unity3d.com/unity/com.unity.ide.visualstudio/blob/next/master/Packages/com.unity.ide.visualstudio/Editor/COMIntegration/COMIntegration~/howtobuild.txt).
 - Please add Microsoft folks on all PRs.
 
 # How to publish new version (for Microsoft)

Internal/README.md

@@ -3,7 +3,7 @@
   "name": "com.unity.ide.visualstudio.tests",
   "displayName": "Visual Studio Editor",
   "description": "Code editor integration for supporting Visual Studio as code editor for unity. Adds support for generating csproj files for intellisense purposes, auto discovery of installations, etc.",
-  "version": "2.0.22",
+  "version": "2.0.24",
   "unity": "2019.4",
   "unityRelease": "25f1",
   "dependencies": {

Packages/com.unity.ide.visualstudio.tests/package.json

@@ -1,5 +1,33 @@
 # Code Editor Package for Visual Studio
 
+## [2.0.24] - 2025-09-04
+
+Integration:
+
+- Remove support for `Visual Studio for Mac`. Please use `VS Code` going forward.
+- Performance optimizations.
+
+Project generation:
+
+- Allow customization of `langversion` when using a `rsp` file.
+- Move to `slnx` solution generation when using `SDK-Style` projects.
+- Both `VS Code` and `Visual Studio 2026` are now using `SDK-Style` projects by default.
+
+
+## [2.0.23] - 2025-02-03
+
+Integration:
+
+- Monitor `additionalfile` extension by default.
+- Try opening a Visual Studio Code workspace if there's one (`.code-workspace` file in the Unity project).
+
+Project generation:
+
+- Identify `asset`, `meta`, `prefab` and `unity` files as `yaml` (Visual Studio Code).
+- Add `sln`/`csproj` file nesting (Visual Studio Code).
+- Improve SDK style project generation.
+
+
 ## [2.0.22] - 2023-10-03
 
 Integration:

Packages/com.unity.ide.visualstudio/CHANGELOG.md

@@ -2,7 +2,7 @@
 
 To use the package, go to **Edit** > **Preferences** > **External Tools** > **External Script Editor** and select the version of **Visual Studio** you have installed. When you select this option, the window reloads and displays settings that control production of .csproj files.
 
-![External Tools tab in the Preferences window](Images/external-tools-tab.png)
+![External Tools tab in the Preferences window](Images/vs-external-tools.png)
 
 ## Generate .csproj files
 
@@ -20,4 +20,4 @@ These settings control whether to generate .csproj files for any installed packa
 |       **Built-in packages** | Any package that is already installed as part of the default Unity installation. |
 |       **Tarball packages** | Any package you install from a GZip tarball archive on the local machine, outside of your Unity project. |
 |       **Unknown packages** | Any package which Unity cannot determine an origin for. This could be because the package doesn’t list its origin, or that Unity doesn’t recognize the origin listed. |
-|       **Player projects** | For each player project, generate an additional .csproj file named ‘originalProjectName.Player.csproj’. This allows different project types to have their code included in Visual Studio’s systems, such as assembly definitions or testing suites. |
+|       **Player projects** | For each player project, generate an additional .csproj file named ‘originalProjectName.Player.csproj’. This allows different project types to have their code included in Visual Studio’s systems, such as assembly definitions or testing suites. |