Releases: mcneel/RhinoVisualStudioExtensions
Releases · mcneel/RhinoVisualStudioExtensions
8.10.0
This release updates the templates to default to multi-targeting for Rhino 8.
- Now multi-targets to net48 and net7.0 for Rhino 8.
- When targeting Rhino 7 or 6,
net48
will reference RhinoCommon 7,net45
will reference RhinoCommon 6.
- When targeting Rhino 7 or 6,
- Specified target Rhino version is now minimum version. The templates will always compile for Rhino 8.
- Added references to compile with Windows Forms and System.Drawing in .NET 7 on Mac when using the
-winforms
option. -winforms
is now default to true for Grasshopper projects.- Add Visual Studio and VS Code debug targets for Rhino 8 netfx/netcore, and Rhino 6 / 7.
- Added
-vscode=true/false
option to include VS Code tasks.json/launch.json files (default true). - Added
-yak=true/false
option to include a target in the project to build yak packages for Rhino 7 and/or 8. - Added Build Yak Package and Include VS Code tasks/launch files options to new project wizard.
- Grasshopper project templates default to running the
_Grasshopper
command at startup when launching Rhino - VS for Mac is no longer supported
8.0.0-Mac
Visual Studio for Mac 2022 Release
8.0.0
7.28.0
- Adds support for Rhino 8 in Visual Studio for Mac
- Uses launchConfig.json for templates when running on Windows
- Drops support for VS for Mac 2019
Full Changelog: 7.21.0.0...7.28.0
7.21.0
7.13.0
Added support for Visual Studio 2022
Full Changelog: 7.5.0.4...7.13.0.0
7.5.0.4
Update to Rhino 7
- Now includes both Visual Studio for Windows and Mac extensions.
- Update Mac debugger to automatically detect v7 and v8 versions correctly, so you don't have to specify the application path manually
- Added a 'Browse' button when selecting the .app to use on Mac
- Added template options for all plugin types (utility, digitizer, renderer, file import/export).
- Added VB templates to Mac
- Use SDK-style projects for Windows
v6 Updates
This release contains the following enhancements to better support 3rd party plugin development:
-
When referencing v6 RhinoCommon, it will automatically use /Applications/RhinoWIP.app (vs. Rhinoceros.app)
-
Added new UI to Project Options > Build > Rhino to configure the following options:
- Plugin type (Autodetect, Rhino Plugin, Grasshopper Component, or Library)
- Launcher (Autodetect, Rhinoceros.app, RhinoWIP.app, or custom path)
- Supports
<RhinoPluginType>
and<RhinoMacLauncher>
.csproj properties which can be set by the above UI - Can now select v5 or v6 when creating a new Rhino Plugin or Grasshopper Component.
- For new v6 projects, it will use nuget packages instead of hard links to Rhinoceros.app
- Properly renames .pdb to
MyPlugin.rhp.pdb
orMyComponent.gha.pdb
to enable debugging 3rd party libraries - Pass Project Options > Run > Configurations > Default > Arguments to rhino when launching, e.g.
-nosplash
- Enable running Rhino without the mono debugger while still registering the plugin.
- Preliminary support for sdk-style projects and
<PackageReference>
Fixes creating new commands/components.
Adding new commands/components to an existing project didn't fill out the GUID properly. Also, creating a Grasshopper component didn't use the file name as the class name.