# Visual Studio changing plug-in from V6 to V7

**URL:** <https://discourse.mcneel.com/t/visual-studio-changing-plug-in-from-v6-to-v7/136384>\
**Category:** Rhino Developer\
**Tags:** windows, visualstudio, rhinocommon\
**Created:** [January 15, 2022, 9:12am UTC](https://discourse.mcneel.com/t/visual-studio-changing-plug-in-from-v6-to-v7/136384 "2022-01-15T09:12:17Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![stevebaer](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/stevebaer/32/473567_2.png) [@stevebaer](https://discourse.mcneel.com/u/stevebaer)\
**Post date:** [January 17, 2022, 11:32am UTC](https://discourse.mcneel.com/t/visual-studio-changing-plug-in-from-v6-to-v7/136384/4 "2022-01-17T11:32:17Z")

</div>

This is not possible for Rhino 7. Rhino 7 loads and runs all plugins into .NET Framework 4.8.

The Rhino 8 WIP for Mac is using .NET 6 and we are investigating the possibility of using .NET 6 on Windows as well.

---

_[View the full topic](https://discourse.mcneel.com/t/visual-studio-changing-plug-in-from-v6-to-v7/136384)._