forked from Unity-Technologies/com.unity.ide.vscode
-
-
Notifications
You must be signed in to change notification settings - Fork 5
CHANGELOG
Abdul-Kadir Coskun edited this page Aug 6, 2023
·
12 revisions
- Remove omnisharp config generation from package
- Clean up code and remove unused directives
- Update
.gitignore
to remove.omnisharp.json
ignore
- Added ignore
IDE0051
to.editorconfig
default configuration
- Fix the asmdef name to not conflict with the official package - Thanks @mifreundorfer
- Remove TSKDoNotDelete Generation
- No longer can one's configuration be taken from them on import of this package.
- User must use
Preferences > External Tools > Generate config files for:
to generate their config files.
- Fix possible deadlock caused by not reading stdout
- Restrict Shell Compatibility for Project Generation's Dotnet Build (Mac/Linux)
- Added .jslib to default extensions for VSCode.
- Refactored configuration defaults and removed redundant options from omnisharp.json. - Thanks @ershn
- Added support for renaming methods and classes using Omnisharp.
- Updated settings.json to correctly utilize useModernNet, sdkIncludePrereleases, and organizeImportsOnFormat.
- Refactored code to improve platform compatibility
- .csproj files are separated into their own folders within a main folder called "CSProjFolders" - Thanks @frarees
- The ProjectReference element now includes a direct path to the file.
- Project element added
- Name element added
- Compile element now includes a direct path to the file.
- GenerateAssemblyInfo property set to false
- Start of
dotnet build
support
- Added the option to disable adding Analyzers to all packages
- This means that it will only be added to .csproj files originating from the Assets Folder.
- Added config section to Externals Tools
- Added Foldouts to remove visual clutter
- A "TSKDoNotDelete" text file is generated when the package is first added. This was done to counter the constant auto-generation that occurred when you would delete the config files.
- Added Configurable Config Settings
- Minimum Unity version is now 2021.3
- Added support for 2021/2022 NetStandard Editor Assemblies Compatibility Level (Not really, it's just a workaround until users start using 2023)
- Added toggle for preferred default arguments for opening VSCode (You can choose between user or workspace)
- Restructured the repository to be more in line with Unity's architecture (See https://github.com/Unity-Technologies/com.unity.cinemachine for more info)
- Removed koalafied Microsoft.Unity.Analyzers dll
- Removed LocationPaths option from omnisharp.json
- Added support for Nuget package Microsoft.Unity.Analyzers (See ProjectGeneration.cs for more info)
- Moved .omnisharp, .editorconfig, and analyzer generation to ProjectGeneration.cs to be in line with the rest of the project
- Simplified XElement creation in ProjectGeneration.cs to be more readable
- Added complete SDK support, this allows you to use Omnisharp's useModernNet in your project (Special thanks to Andrew Spiering @wackoisgod)
- Added more predefined variables for the omnisharp.json file
- Going forward, 2021.3 and below will only be able to use .Net Framework API compatibility level
- Added support for .Net 4.8 API compatibility level for 2022.1 and above
- Fixed failure while loading the analyzer reference 'Unity.SourceGenerators'
- Added Unity Roslyn analyzers support (See https://code.visualstudio.com/docs/other/unity#_enabling-unity-warnings)
- Added Formatting support (See CreateOmniSharpConfig() in VSCodeScriptEditor.cs)
- Removed Rider Package (Spits)
- Updated Text-Framework to 1.3.3
- Start of Community Support
- Added workspace file generation
- End of Unity Support
- Introduce OnGeneratedCSProjectFiles, OnGeneratedCSProject and OnGeneratedSlnSolution callbacks.
- Always use forward slash in source paths
- Analyzers use absolute paths
- Ruleset files for roslyn analyzers
- Extra snap search paths on Ubuntu
- Specific c# language version for specific unity versions
- No longer hide .gitignore in VSCode file explorer
- Remove workaround for VSCode omnisharp (as of https://github.com/OmniSharp/omnisharp-vscode/issues/4113, we no longer need to disable the referenceoutputassemblies).
- VSC-14 - synchronize solution file when adding new assembly
- Source filtering adds support for asmref
- Do not reference projects that has not been generated (case 1211057)
- Only open files that exists (case 1188394)
- Add individual toggle buttons for generating csprojects for packages
- Add support for Roslyn analyzers in project generation through csc.rsp and compiled assembly references
- Remove the Release build target from csproj and sln
- Delta project generation, only recompute the csproj files whose script modified.
- Exe version of vscode will use Normal ProcessWindowStyle while cmd will use Hidden
- Fixing OSX open command arguments
- Support for Player Project. Generates specific csproj files containing files, reference, defines,
- etc., that will show how the assembly will be compiled for a target platform.
- Adds support for choosing extensions to be opened with VSCode. This can be done through the GUI in Preferences.
- Avoids opening all extensions after the change in core unity.
- Fix various OSX specific issues.
- Generate project on load if they are not generated.
- Fix path recognition.
- Ensure asset database is refreshed when generating csproj and solution files.
- Add support for generating all csproj files.
- Fix relative package paths.
- Fix opening editor on mac.
- Add %LOCALAPPDATA%/Programs to the path of install paths.
- This is the first release of Unity Package vscode_editor
- Using the newly created api to integrate Visual Studio Code with Unity.