Releases: JetBrains/rider-efcore
Releases · JetBrains/rider-efcore
231.0.2-eap04
Added
- Cherry-pick changes from bugfix 223.3.2
223.3.2
231.0.1-eap01
Added
- Cherry pick changes from bugfix 223.3.1
223.3.1
Fixed
- DbContext is not persisted between dialogs
- EF Core Quick Actions popup is empty
- Exception when trying to call Drop Database dialog submit button
- Project-specific saved values are not restored when project in dropdown changes
231.0.0-eap01
Added
- Enable support for Rider 2023.1 EAP 1
223.3.0
Changed
- Use .NET CLI from Rider's settings instead of global "dotnet" one
Fixed
- Exception thrown when dotnet not installed or accessible bug
- Transitively available DbContexts in Migrations project are not visible in the dropdown
223.2.0
Changed
- Target migration in Update database dialog is now represented as a drop-down list instead of text input field (#130 by @unopcpavilion)
Fixed
- Target migration field selected oldest migration instead of newest as preselected value
223.1.0
Highlights
Save fields data between dialogs
The most requested feature, now the majority of commonly used options persisted between dialogs to reduce the time needed for the reconfiguration of defaults.
See this page about which values are persisted and which are not (and why).
Run EF Core commands in a terminal-like window
Now, by default EF Core commands will be executed more transparently in a dedicated console window
If you prefer the old "silent" behavior - you could disable this feature in settings.
Settings page
Since the new release has new feature flags, the plugin now has a settings page.
Full changelog
Added
- Most common values in dialogs are saved between instances
- Ability to run commands in the terminal-like tool window
- Support for a stable Rider 2022.3
Fixed
- DbContext class not showing up (#105)
223.0.0
Added
- Enable support for Rider 2022.3 EAP
222.2.0
Added
- F.A.Q. hyperlink near Startup project dropdown (#115 by @TheBottleCyber)
Fixed
- Abstract DbContexts are visible in DbContext dorpdown (#109 by @vova-lantsov-dev)
- Connection string is escaped improperly (#110 by @vova-lantsov-dev)
- Startup exception when dotnet tools cache is not yet initialized
NullRef
on invalid migration classes instead of ignoring