48 results found
- 
1 vote
- 
Entity developer model explorer improvementVisual Studio 2017 and .Net Core project. Model explorer nodes collapse every time you navigate to another document and go back to Entity Developer designer. To reproduce the issue: - Open an .efml file
- Make sure database model explorer is visible.
- Expand any nodes (Methods, Complex Types, etc.)
- Open another document (let's say some C# code)
- Go back to Entity Developer.
- Observe that all nodes are collapsed.
 This issue results in less productivity and frustration when you need to go back and forth between code and DB model. 1 vote
- 
Publish .Net5 compatible preview version of Devart.Data.Oracle.EFCoreIn order to test migration to .Net5 
 We need to have at least a preview version of Devart.Data.Oracle.EFCore compatible with .Net51 vote
- 
jsonExpand PgSqlJsonbFunctions to include JSON Processing Functions to allow for direct manipulation of Json data on the server. 1 vote
- 
Support Multiple Framework TargetingWhen generating content we are forced to pick the framework version. If we are creating a common business object library we may need to target multiple frameworks. The class generation is not affected, but the data context can be wrapped in #IF to indicate the framework we are compiling for. 1 vote
- 
Different platform database communicationDifferent platform database like,MS SQL. MY SQL and Oracle communicate with ASP.net application. Here my requirement is that do not want to use store procedure because all 3 database platform syntax different, so using entity framework create single *.edmx file and communicate. 1 vote
- 
1 vote
- 
Create complex type functionality in VS2010 Function Import DialogImplement support for Complex Type in Visual Studio Function Import Dialog for 
 dotConnect for Oracle.0 votes
- Don't see your idea?
