namespace?

[cj]

What does the line
<System.Web.Ser vices.WebServic e(Namespace:="h ttp://tempuri.org/")_
do in the example below?

Imports System.Web.Serv ices
Imports System.Web.Serv ices.Protocols
Imports System.Componen tModel

' To allow this Web Service to be called from script, using ASP.NET
AJAX, uncomment the following line.
' <System.Web.Scr ipt.Services.Sc riptService()_
<System.Web.Ser vices.WebServic e(Namespace:="h ttp://tempuri.org/")_
<System.Web.Ser vices.WebServic eBinding(Confor msTo:=WsiProfil es.BasicProfile 1_1)>
_
<ToolboxItem(Fa lse)_
Public Class Service1
Inherits System.Web.Serv ices.WebService

<WebMethod()_
Public Function HelloWorld() As String
Return "Hello World"
End Function

End Class

And why don't I see a similar line in the C# example at
http://dotnetjunkies.com/Tutorial/4D...7B5757564.dcik
?

[Scott M.]

What you are referring to is a compiler attribute. These attributes appear
in angle brackets (<>) and precede a code definition, such as a class. They
inform the compiler about details of the item they precede. In this case,
it informs the compiler that this class is no ordinary class and that the
XML that should be sent back from the service should exist within the
http://temuri.org (temporary uri - you are supposed to change it) namespace.
You are supposed to replace this with a namespace of your own.

In addition, notice that your HelloWorld function is also marked with a
compiler attribute. This one tells the compiler that this method is no
ordinary method, but a WebMethod and therefore should be callable remotely
over http and soap via xml.

-Scott
"cj" <[e-mail] amwrote in message
news:%2******** ********@TK2MSF TNGP02.phx.gbl. ..

What does the line
<System.Web.Ser vices.WebServic e(Namespace:="h ttp://tempuri.org/")_
do in the example below?

Imports System.Web.Serv ices
Imports System.Web.Serv ices.Protocols
Imports System.Componen tModel

' To allow this Web Service to be called from script, using ASP.NET AJAX,
uncomment the following line.
' <System.Web.Scr ipt.Services.Sc riptService()_
<System.Web.Ser vices.WebServic e(Namespace:="h ttp://tempuri.org/")_
<System.Web.Ser vices.WebServic eBinding(Confor msTo:=WsiProfil es.BasicProfile 1_1)>
_
<ToolboxItem(Fa lse)_
Public Class Service1
Inherits System.Web.Serv ices.WebService

<WebMethod()_
Public Function HelloWorld() As String
Return "Hello World"
End Function

End Class

And why don't I see a similar line in the C# example at
http://dotnetjunkies.com/Tutorial/4D...7B5757564.dcik
?

[Steven Cheng[MSFT]]

Hi Cj,

Actually, for WCF, it support both binary and XML format of message
transfering, just depend on your context. If you use WCF to communicate
with another XML webservice side, you certain will need to use XML format
underlying.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
Date: Wed, 16 Jan 2008 11:35:07 -0500
From: cj <[e-mail] am>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
Subject: Re: namespace?

To be honest I don't care for XML. It's too verbose. I'd have stuck
with comma delimited or fixed width files but it all depends on the
application. I think it's a bit funny that the new MS stuff, I forget
the name maybe it was WCF?, was almost back to comma delimited and they
talked about cutting down on the data being sent across the net in
comparison to XML.
Scott M. wrote:

No problem CT - - You are not alone when it comes to getting over the
confusion of using URL's as namespace names. My company is an IT

training

company and whenever I am teaching XML, this issue winds up being the

single

biggest source of confusion. But, once you get your head around the

idea,

other things become much clearer.

Good luck!

-Scott