You may have to explain what XElement object is though, is that the
LINQ-XML XElement?
Exactly what it is. As far as showing input, what do you mean by this? I
haven't designed any of the .net code yet, but what is supposed to happen is
this: There is a 9 step asp.net wizard that takes a person through creating
a "blank contract". During each step, the xml being built is shown on the
page below the wizard so the user can see their progress as they go through
the wizard. I need to make edit/remove buttons next to the different
elements/attributes so they can be edited/removed as needed. A good example
of this would be this: On step 1 of the wizard, the user is asked to enter
in an editbox the contract type to create. Since it is freehand writing, it
can be anything they type up to 30 characters long. When they press the add
button, a new view in the step shows up saying that the new "type" has been
created. When they press next for step 2, it takes them to the glossary step
of the wizard. On this step, the user enters word/definition pairs to be
added to the section. Below the wizard, there is the contract view as it has
been created so far. In this step, it would have the contract type and
whatever word/definition pairs they have added so far. These word/definition
pairs as well as anything added to the contract would have these buttons
next to them.
Does this help?
