NewBie (add amendment & background)
I'm doing my first steps with a Trial Version of Entity Developer.
Of course I have a special idea of the functionality and a set of results from the programmers.
Hopefully someone can give me a solution / an answer of my questions.
First I’m not able to work with Entity Developer as a plugin of Visual Studio 2015. I’ve no option to create a new Diagram/Model. Is it necessary to select a special kind of project type?
Our project has already been created by the programming and I have taken over the structure and all existing files/setting via git.
I create Complex Types with a list of columns/properties and other Complex Types and insert them in an entity.
Is it possible to list the properties of all Complex Types in every entity in a diagram – like the view in Property Editor -> Mapping?
All entities in a diagram should view all properties/columns because only DBA knows the properties of Complex Types.
Is it possible to use a Complex Type as inheritance – like:
public class Person : InsertDataBase ?
I wouldn’t define separate tables. I’d like to define properties once and include them in every entity – so I have the same definition/attributes in every entity.
Is it possible to customize a different class path to all “normal” entities and Complex Types and …?
Is it possible to define different templates for entities e.g. to specify different using directives? If I can set the template for every entity I also can decide which path will be used.
Next questions will be come and so I will come back soon. :)
It seems to cause difficult problems…?
Amendment & background:
I’m a DBA and also a newbie in Visual Studio and C#. For this I didn’t find the correct terms :)
The requirement for our developers in Visual Studio is the “Code first” approach. Therefore, the idea arose that the DBA provides the classes. I came across the Entity Developer looking for a graphical interface.
The programmers like to have POCO classes – for this I mean that all properties are on the same "Level" in an entity like: Person.<fieldname> and not in a separate instance like: Person.InsertDataBase.<fieldname>.