Elements doesn't appear to the target designer (SDK June CTP)

Hot Topic

Get Latest from IDE doesn't always Get Latest
Can't uninstall MSDN Library for Visual Studio 2005 Beta
Is this possible with VSTO 2005?
BizTalk Deployment
Object reference not set to an instance of an object trying to save a change to an xsd
msbuild build errors
VS 2005 Express & Indigo
Formatting a String
MDI Threading issues?
VSTO add-in setup error accessing registry

Visual Studio

Where do I get the Access Developers Toolkit
Custom task with assembly reference
Getting started with WPF. What do I need?
Master-Detail Reports
A question on xbap
p2p session lifetime
Hosting xbap in a non-asp.net web site?
IsOneWay and IIS host bug?
Set ReportViewer Parameter
VSS Add-in Missing after Installation

Elements doesn't appear to the target designer (SDK June CTP)

Hi!
I've created a simple DSL and a diagram with two compartment shapes and one GeometryShape. Everything goes fine, no errors/warnings when building the dsldefinition solution, and the target debugging solution runs fine. But when I drag elements from the toolbox to the drawing surface, I cannot see them. They appear to the dsl explorer but no to the drawing surface.

Any ideas how to resolve this issue Thanks in advance..

Risto

Answer this question

Elements doesn't appear to the target designer (SDK June CTP)

  • norax

    That's correct. The link paths in an EMD always end with the object-to-link segment. That's because you're telling it what link to create.

    If there are more than two segments in a path, you just repeat the pattern:
    CarHasEngine.Engine / !Engine / EngineHasPiston . Pistons / !Piston / PistonConnectsToAxle . Axle ....

    The rule is that the segments must be navigable: each segment must take you to a relationship or class from which the next step can be made. So we couldn't miss out any of the above segments.

    The rule about missing out the relationship name is that you can do so if it's the same as the previous segment. So normally that only applies where you're taking the link-to-object hop that follows the object-to-link hop. Yes, there's lots of redundancy here and path expressions end up rather verbose, but this is V1 ...



  • Davidarh

    Hi Gareth,

    Can you explain us the domain path syntax

    Thank you,

  • Vikas Bindra

    Thanks Alan,

  • Stephanie Barulic

    Did that answer the question, guys

  • WN3335

    I happen to be writing some material around this at present, so I'll have a go at answering this.

    I've posted it in a separate thread:

    http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=464793&SiteID=1

    Hope it helps!



  • Matt Michuta

    Hi Risto,

    Can you do a Validate All on your diagram Unfortuantely the code generators aren't running validation yet in this CTP.

    The most usual cause for this is an incorrect ParentElementPath in the ShapeMap for your shape.

    The path has to go from

    the MEL that maps to the Shape

    to

    the MEL that maps to the shape's desired parent shape



  • Mo_Fya

    Hi Alan,

    Thank you for your answer.

    Just a precision, in your last EMD path syntax, the last segment is just a object-to-link hop but there is not the associated link-to-object segment.

    What are the mandatory segments and what is the syntax when there is more than 2 segments

    Thanks,
  • Elements doesn't appear to the target designer (SDK June CTP)
Answer this question