Hi All

I am trying to generate classes from XSD which looks like this

namespace WindowsFormsApplication1.Something.Some
{
public class Address
{

public Address()
{
}


[FormMapper("TextBox2")]

public string StreetAddress { get; set; }
[FormMapper("TextBox3")]
public string UnitNumber { get; set; }
[FormMapper("TextBox4")]
public string City { get; set; }
[FormMapper("TextBox5")]
public string State { get; set; }
[FormMapper("TextBox6")]
public string zip { get; set; }

}
}




How do i represent the FormMapper Attribute in the xsd.

Please Help and thanks

On Mar 3, 11:53 am, parez <psaw> wrote:
[..]
> [FormMapper("TextBox6")]
> public string zip { get; set; }
>
> }
>
> }
>
> How do i represent the FormMapper Attribute in the xsd.
>
> Please Help and thanks

Where are the C# Jedis?

parez <psawant> wrote:

<snip>

> Where are the C# Jedis?

Perhaps if you gave more information in your question - like how your
code currently works - you'd be more likely to get an answer.

On Mar 3, 2:36 pm, Jon Skeet [C# MVP] <sk> wrote:
> parez <psaw> wrote:
>
> <snip>
>
> > Where are the C# Jedis?
>
> Perhaps if you gave more information in your question - like how your
> code currently works - you'd be more likely to get an answer.
>
> --
> Jon Skeet - <sk>[..] Blog:[..]
> World class .NET training in the UK:[..]

I dont have currently working code. I have been recommended to use
XSD.exe to generate the code instead of typing it in.


The auto generated code should have custom attributes (in my example
it its FormMapper)


public class Address
{

public Address()
{
}


[FormMapper("TextBox2")]

public string StreetAddress { get; set; }
[FormMapper("TextBox3")]
public string UnitNumber { get; set; }
[FormMapper("TextBox4")]
public string City { get; set; }
[FormMapper("TextBox5")]
public string State { get; set; }
[FormMapper("TextBox6")]
public string zip { get; set; }

}








What I am trying to do is.
I have to send XML requests to the server based on the events on my
winform applications. They could add/update/get requests. I will have
70-80 different requests types and hence 70-80 XSDs (or Classes) to
maintain.
I am planning to use reflection to populate fields on the winforms
using the FormMapper attribute.But that may not be the only reason why
i need custom attributes. I mite also need to get someinfo about the
fields(like readonly, enabled ) etc from the server.


TIA

Maybe this can help:

http://www.jondavis.net/blog/post/20...eneration.aspx

I'm not sure..but check it out.



"parez" <psawant> wrote in message
news:23a6
[..]

On Mar 3, 3:24 pm, "sloan" <sl> wrote:
> Maybe this can help:
>
> [..]
>
> I'm not sure..but check it out.
>
> "parez" <psaw> wrote in message
>
> news:23a6
>>
>>
>>

Thanks..That is the direction I mite have to go in..

I found more info here

http://msdn2.microsoft.com/en-us/library/aa302301.aspx

The problem is that xsd (either the format or the exe) isn't going to be in
the least bit interested in your attribute. Of couse, having your object
model dictate the UI also might not be the best idea... personally I'd
separate the two concepts completely, perhaps using xml generation if (and
only if) it made sense.

Marc

On Mar 4, 3:04 am, "Marc Gravell" <marcgrav> wrote:
> The problem is that xsd (either the format or the exe) isn't going to be in
> the least bit interested in your attribute. Of couse, having your object
> model dictate the UI also might not be the best idea... personally I'd
> separate the two concepts completely, perhaps using xml generation if (and
> only if) it made sense.
>
> Marc

Hi Marc,

I finally have a custom code generator which geneerates the
Attributes...
I am using the XSD to create classes because the server is going to
use the same XSD to process my request.
My classes are not part of the business tier. They are a part of the
presentation layer(well.. its sits between the winforms and Server).
I am planning to use reflection to populate the form fields.Thats why
I am using the FormMapper Attribute.