Hello,
It is possible to create more tha one dm an dd in the same DSLTools proyect to do different models during the debugging and after merge its wit T4
Thanks a lot!
Rafael Cabedo
rcabedo@dsic.upv.es
Diferents Domain Models an Designer Definitions in the same project
Hot Topic
- grouping/placement in CR 10
- Having issues with debugging in VS 2005
- FaultException
- Get Latest Source from VSS using MSBuild.
- Working with Microsoft Excel
- Pre/Post Operation Invokation Extensibility
- Server-side VSTO scalability and licensing
- How to: Generate many files from one template?
- Accessing a Control on a Outlook Custom Form in VSTO 2005
- access [contextual||context||right-click] [menu||commandbar] of chart?
Visual Studio
- SVCUTIL.EXE Error
- EXCLUDE-like command for labeling sources in VSS
- VSTO Excel Binding a dataset from a webervice
- How to add custom control to Visual Studio 2005 Toolbox?
- Visual Basic 2005 and MSWord Rule Bar
- Conversion to expression trees
- Replacing the +/- in a TreeView
- Using IXmlSerializable interface in the ServiceContract
- Setting a breakpoint that only stops one thread?
- MSBuild Task and TargetOutputs
Diferents Domain Models an Designer Definitions in the same project
jmiller76
It is not possible to create more than one dsldd file at present in a single project.
Technically it is possible to create more than one dsldm file, as long as only one is pointed at in the .dsldd file (lets call that the "main" one). The other .dsldm files could be referenced by the guids of their substores in the main .dsldm file's Model.Extends property (which would be better named Model.References). You'd then be able to reference elements in them by adding copies of the elements (with the same name and namespace, but no property data) in the main dsldm file and setting the IsLoaded property on the copies to false.
As you can tell from that (very brief) explanation, this is pretty yucky in the present CTP, but its something we're looking into for future CTPs.
This yucky mechanism exists primarily at present to allow us to build the tools using the tools as a bootstrap. Unfortunately, this means that some yuckiness escapes to customers, as we're shipping you the same version that we use internally. However, the inherent goodness of bootstrapping makes us feel this is a price (just about) worth paying while we're still a CTP release.