This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
This looks very promising, however I couldn't find how to do the following:
Have I missed something, or are these features missing from the first release? Any plans to add these features?
|
|
|
|
|
These aren't in the first release, I'm afraid. We've already had a request to generate separate hbm mapping files so we'll probably look into that shortly. Separate file for each entity isn't currently a priority (because you're not meant to be touching the generated code anyway) but we'd be very interested to hear the use case. Common (undiscriminated) entity base class is definitely on the agenda and we'll try to get that out reasonably soon. We hadn't planned for multiple namespaces but we can certainly look into that. Again, if you can say a bit more about your use case then that would help us get it right! Thanks very much for your feedback -- it really helps us prioritise! |
|
|
|
|
I was about to ask same thing... but in my case, I didnt find a way to generate c# classes... |
|
|
|
|
I would like to see the designer create two files per entity, e.g. Customer.cs - empty partial class that can be edited Customer.Generated.cs - partial class with the properties, similar to the one that is currently generated The two files can be dependent upon each other by adding the following to the project file:
<Compile Include="Customer.cs" /> <Compile Include="Customer.GeneratedCode.cs"> <DependentUpon>Customer.cs</DependentUpon> </Compile> For the namespace support, this is just the usual way of structuring code for any reasonably sized project, for example having a Purchasing namespace containing Supplier, PurchaseOrder entities and a Sales namespace containing Customer, SalesOrder entities.
|
|
|
|
