best place to put .xsd for deployment?

[Jiho Han]

I have .asmx that uses .xsd schema to validate an incoming xml string and
spits out transformations.
Basically I am wondering where to put the .xsd schema and how to get to it
at run-time.

I tried
vReader.Schemas.Add(null, "test.xsd");

and it reports that it could not find C:\WINDOWS\system32\test.xsd. Then I
tried using,

Assembly.GetExecutingAssembly().CodeBase

and it returned c:\inetpub\wwwroot\bin\MyAssembly.DLL - almost there. Then
I just chopped off the dll name and appended my xsd to it, resulting in
c:\inetpub\wwwroot\bin\test.xsd.

I mean this works but I was wondering if there is a better way. Should I
embedded it in my dll? Or what's a better approach so that the client does
not have access to the schema file?

Thanks

[Steven Livingstone]

Why not refer to the schema by a Url?

vReader.Schemas.Add(null, http://myuri/schemas/test.xsd);

Other than that use Server.MapPath()

vReader.Schemas.Add(null, Server.MapPath("test.xsd"));

Doesn't look like you're doing that yet.

Steven
Founder, http://venturetogether.com
"Jiho Han" <ji******@infinityinfo.com> wrote in message
news:O0**************@TK2MSFTNGP11.phx.gbl...

I have .asmx that uses .xsd schema to validate an incoming xml string and
spits out transformations.
Basically I am wondering where to put the .xsd schema and how to get to it
at run-time.

I tried
vReader.Schemas.Add(null, "test.xsd");

and it reports that it could not find C:\WINDOWS\system32\test.xsd. Then I tried using,

Assembly.GetExecutingAssembly().CodeBase

and it returned c:\inetpub\wwwroot\bin\MyAssembly.DLL - almost there. Then I just chopped off the dll name and appended my xsd to it, resulting in
c:\inetpub\wwwroot\bin\test.xsd.

I mean this works but I was wondering if there is a better way. Should I
embedded it in my dll? Or what's a better approach so that the client does not have access to the schema file?

Thanks

[Jiho Han]

I could but like I said, what if I didn't want the user to have access to
the .xsd file necessarily?
What would you do then?

Just looking for some ideas.
Thanks.

"Steven Livingstone" <s.***********@nospam.btinternet.com> wrote in message
news:%2****************@tk2msftngp13.phx.gbl...

Why not refer to the schema by a Url?

vReader.Schemas.Add(null, http://myuri/schemas/test.xsd);

Other than that use Server.MapPath()

vReader.Schemas.Add(null, Server.MapPath("test.xsd"));

Doesn't look like you're doing that yet.

Steven
Founder, http://venturetogether.com
"Jiho Han" <ji******@infinityinfo.com> wrote in message
news:O0**************@TK2MSFTNGP11.phx.gbl...

I have .asmx that uses .xsd schema to validate an incoming xml string and spits out transformations.
Basically I am wondering where to put the .xsd schema and how to get to it at run-time.

I tried
vReader.Schemas.Add(null, "test.xsd");

and it reports that it could not find C:\WINDOWS\system32\test.xsd. Then

I

tried using,

Assembly.GetExecutingAssembly().CodeBase

and it returned c:\inetpub\wwwroot\bin\MyAssembly.DLL - almost there.

Then

I just chopped off the dll name and appended my xsd to it, resulting in
c:\inetpub\wwwroot\bin\test.xsd.

I mean this works but I was wondering if there is a better way. Should

I embedded it in my dll? Or what's a better approach so that the client

does

not have access to the schema file?

Thanks

[Steven Livingstone]

Use XmlResolver and protect the Xml file :)

http://sightkeys.com?183

Steven
Founder, http://venturetogether.com

"Jiho Han" <ji******@infinityinfo.com> wrote in message
news:#R**************@TK2MSFTNGP10.phx.gbl...

I could but like I said, what if I didn't want the user to have access to
the .xsd file necessarily?
What would you do then?

Just looking for some ideas.
Thanks.

"Steven Livingstone" <s.***********@nospam.btinternet.com> wrote in message news:%2****************@tk2msftngp13.phx.gbl...

Why not refer to the schema by a Url?

vReader.Schemas.Add(null, http://myuri/schemas/test.xsd);

Other than that use Server.MapPath()

vReader.Schemas.Add(null, Server.MapPath("test.xsd"));

Doesn't look like you're doing that yet.

Steven
Founder, http://venturetogether.com
"Jiho Han" <ji******@infinityinfo.com> wrote in message
news:O0**************@TK2MSFTNGP11.phx.gbl...

I have .asmx that uses .xsd schema to validate an incoming xml string and spits out transformations.
Basically I am wondering where to put the .xsd schema and how to get to

it

at run-time.

I tried
vReader.Schemas.Add(null, "test.xsd");

and it reports that it could not find C:\WINDOWS\system32\test.xsd. Then

I

tried using,

Assembly.GetExecutingAssembly().CodeBase

and it returned c:\inetpub\wwwroot\bin\MyAssembly.DLL - almost there. Then

I just chopped off the dll name and appended my xsd to it, resulting

in c:\inetpub\wwwroot\bin\test.xsd.

I mean this works but I was wondering if there is a better way.

Should I embedded it in my dll? Or what's a better approach so that the client

does

not have access to the schema file?

Thanks

[Jiho Han]

Thanks! I'll look into it and let you know how it goes.

"Steven Livingstone" <s.***********@nospam.btinternet.com> wrote in message
news:uK****************@TK2MSFTNGP11.phx.gbl...

Use XmlResolver and protect the Xml file :)

http://sightkeys.com?183

Steven
Founder, http://venturetogether.com

"Jiho Han" <ji******@infinityinfo.com> wrote in message
news:#R**************@TK2MSFTNGP10.phx.gbl...

I could but like I said, what if I didn't want the user to have access to

the .xsd file necessarily?
What would you do then?

Just looking for some ideas.
Thanks.

"Steven Livingstone" <s.***********@nospam.btinternet.com> wrote in

message

news:%2****************@tk2msftngp13.phx.gbl...

Why not refer to the schema by a Url?

vReader.Schemas.Add(null, http://myuri/schemas/test.xsd);

Other than that use Server.MapPath()

vReader.Schemas.Add(null, Server.MapPath("test.xsd"));

Doesn't look like you're doing that yet.

Steven
Founder, http://venturetogether.com
"Jiho Han" <ji******@infinityinfo.com> wrote in message
news:O0**************@TK2MSFTNGP11.phx.gbl...
> I have .asmx that uses .xsd schema to validate an incoming xml string

and

> spits out transformations.
> Basically I am wondering where to put the .xsd schema and how to get

to

it

> at run-time.
>
> I tried
> vReader.Schemas.Add(null, "test.xsd");
>
> and it reports that it could not find C:\WINDOWS\system32\test.xsd.

Then

I
> tried using,
>
> Assembly.GetExecutingAssembly().CodeBase
>
> and it returned c:\inetpub\wwwroot\bin\MyAssembly.DLL - almost

there. Then
> I just chopped off the dll name and appended my xsd to it, resulting

in > c:\inetpub\wwwroot\bin\test.xsd.
>
> I mean this works but I was wondering if there is a better way.

Should

I

> embedded it in my dll? Or what's a better approach so that the client does
> not have access to the schema file?
>
> Thanks
>
>

[Jiho Han]

I read on the topic of XmlResolver and it sounds like a good thing. But I
guess it all comes down to how to store the password securely. I mean I
guess you probably don't want to hard-code the password so you'd probably
read it off of a config file and proper steps must be taken to make sure
that the config file is secured.

What other options are available?
Thanks much.

"Steven Livingstone" <s.***********@nospam.btinternet.com> wrote in message
news:uK****************@TK2MSFTNGP11.phx.gbl...

Use XmlResolver and protect the Xml file :)

http://sightkeys.com?183

Steven
Founder, http://venturetogether.com

"Jiho Han" <ji******@infinityinfo.com> wrote in message
news:#R**************@TK2MSFTNGP10.phx.gbl...

I could but like I said, what if I didn't want the user to have access to

the .xsd file necessarily?
What would you do then?

Just looking for some ideas.
Thanks.

"Steven Livingstone" <s.***********@nospam.btinternet.com> wrote in

message

news:%2****************@tk2msftngp13.phx.gbl...

Why not refer to the schema by a Url?

vReader.Schemas.Add(null, http://myuri/schemas/test.xsd);

Other than that use Server.MapPath()

vReader.Schemas.Add(null, Server.MapPath("test.xsd"));

Doesn't look like you're doing that yet.

Steven
Founder, http://venturetogether.com
"Jiho Han" <ji******@infinityinfo.com> wrote in message
news:O0**************@TK2MSFTNGP11.phx.gbl...
> I have .asmx that uses .xsd schema to validate an incoming xml string

and

> spits out transformations.
> Basically I am wondering where to put the .xsd schema and how to get

to

it

> at run-time.
>
> I tried
> vReader.Schemas.Add(null, "test.xsd");
>
> and it reports that it could not find C:\WINDOWS\system32\test.xsd.

Then

I
> tried using,
>
> Assembly.GetExecutingAssembly().CodeBase
>
> and it returned c:\inetpub\wwwroot\bin\MyAssembly.DLL - almost

there. Then
> I just chopped off the dll name and appended my xsd to it, resulting

in > c:\inetpub\wwwroot\bin\test.xsd.
>
> I mean this works but I was wondering if there is a better way.

Should

I

> embedded it in my dll? Or what's a better approach so that the client does
> not have access to the schema file?
>
> Thanks
>
>