2 Problems (INDIGO + ASP.NET 2.0)

Hi all,
I will highly appreciate your help to me if you help me with one (or both)
of the following 2 problems:

I have the following on my machine (Windows Vista build 5308) successfully
installed:
1) VS 2005 Standard
2) Sql Server 2005 Standard
3) Windows SDK February CTP (5308)
4) Microsoft Visual Studio Code-named orcas CTP preview-development tools
for winFX
5) Visual Studio 2005 Extensions for WWF

I have two small problems:
I) I've read and fully understood Clemens Vasters article about INDIGO [

http://msdn.microsoft.com/winfx/tech...l=/library/en-

us/dnlong/html/introtowcf.asp ] and I also read your "HELLO WCF" example

[http://windowscommunication.net/coll...ages/howto.htm ]; so I wanted
to ONLY re-write

your "Hello WCF" example on my machine (without making any changes to the
code), I wrote

the service, and then, chose Build -> success, I've run the sample, yes it's
working, but

as mentioned in the explanation of "Hello WCF" I must be able to open [

http://localhost/hello ] and see a welcome page ! this is what freaks me !!
i can't find

anything in the www root directory altough i specified this directory [

http://localhost/hello ] when i defined the new URI in code !! so when I
open [

http://localhost/hello ] it gives me this error : "..Not Found..".

Note that I haven't developed any website before on ASP.NET 2.0, that's why
when i open : [

http://localhost ] it gives me "under construction page" !! Tell me please
why there's NOT

nothing in the root after I build the solution or why the browser gives me
"..Not Found.."

error !!

II) When I try to create a new ASP.NET 2.0 (on the above machine), and
choose to save it on

"http", and press on "Browse" button to choose the "Local IIS" option, then
oops, I can't

use this option , DISABLED !! it tells me that "...you must be a member of
the

Administrators group on the local computer to access the IIS metabase...",
what's the hell

is that thing ?! I logged on using my own account and it's of course an
Administrator

account (i checked that from Control Panel), and to be also sure, I logged
on with the user

name "Administrator" which is the built-in administrator account with
Windows Vista, and it

also showed up the above message ! I opened the IIS, tried to play with
security settings, but couldn't do anything to enable the "local IIS" option
(mentioned above) !! is there

specific thing that i must do to enable that option ! so i can create ASP.NE
2.0 websites on [ http://localhost/ ] ?

Thanx so much in advance !!

Thus wrote Murad,

> Hi all,
> I will highly appreciate your help to me if you help me with one (or
> both)
> of the following 2 problems:
> I have the following on my machine (Windows Vista build 5308)
> successfully
> installed:
> 1) VS 2005 Standard
> 2) Sql Server 2005 Standard
> 3) Windows SDK February CTP (5308)
> 4) Microsoft Visual Studio Code-named orcas CTP preview-development
> tools
> for winFX
> 5) Visual Studio 2005 Extensions for WWF
> I have two small problems:
> I) I've read and fully understood Clemens Vasters article about INDIGO
> [
> http://msdn.microsoft.com/winfx/tech...on/default.asp
> x?pull=/library/en-
>
> us/dnlong/html/introtowcf.asp ] and I also read your "HELLO WCF"
> example
>
> [http://windowscommunication.net/coll...ages/howto.htm ]; so I
> wanted to ONLY re-write
>
> your "Hello WCF" example on my machine (without making any changes to
> the code), I wrote
>
> the service, and then, chose Build -> success, I've run the sample,
> yes it's working, but
>
> as mentioned in the explanation of "Hello WCF" I must be able to open
> [
>
> http://localhost/hello ] and see a welcome page ! this is what freaks
> me !! i can't find
>
> anything in the www root directory altough i specified this directory

HelloWCF uses a ServiceHost, not IIS...

> Note that I haven't developed any website before on ASP.NET 2.0,
> that's why when i open : [
>
> http://localhost ] it gives me "under construction page" !! Tell me
> please why there's NOT
>
> nothing in the root after I build the solution or why the browser
> gives me "..Not Found.."
>
> error !!

Well, there will be nothing. The sample doesn't use ASP.NET or IIS. You have
to run the host application to access the service description page from a
browser.

That doesn't mean that the sample cannot be hosted in IIS (it's actually
trivial), but you didn't mention that you've tried that and if, what you did.

Cheers,
--
Joerg Jooss
news-reply@joergjooss.de

well, thanx Mr. Joerg for your reply, BUT, i hosted my service using a
service host not IIS, but the browser gives me an error "...Not Found" ..
About hosting the service on IIS, what's the main difference in procedure to
host a simple service on IIS ??
I repeat and say, in the "Hello WCF service" they say that you will find
your service on "http://localhost/hello" this means that it's hosted using
IIS !!! isn't it ?? but practically i used a service host object in code !!
so im confused with that !

and regarding the 2nd problem, I don't know what's going on !! something
really weird !!

"Joerg Jooss" wrote:

> Thus wrote Murad,
>
> > Hi all,
> > I will highly appreciate your help to me if you help me with one (or
> > both)
> > of the following 2 problems:
> > I have the following on my machine (Windows Vista build 5308)
> > successfully
> > installed:
> > 1) VS 2005 Standard
> > 2) Sql Server 2005 Standard
> > 3) Windows SDK February CTP (5308)
> > 4) Microsoft Visual Studio Code-named orcas CTP preview-development
> > tools
> > for winFX
> > 5) Visual Studio 2005 Extensions for WWF
> > I have two small problems:
> > I) I've read and fully understood Clemens Vasters article about INDIGO
> > [
> > http://msdn.microsoft.com/winfx/tech...on/default.asp
> > x?pull=/library/en-
> >
> > us/dnlong/html/introtowcf.asp ] and I also read your "HELLO WCF"
> > example
> >
> > [http://windowscommunication.net/coll...ages/howto.htm ]; so I
> > wanted to ONLY re-write
> >
> > your "Hello WCF" example on my machine (without making any changes to
> > the code), I wrote
> >
> > the service, and then, chose Build -> success, I've run the sample,
> > yes it's working, but
> >
> > as mentioned in the explanation of "Hello WCF" I must be able to open
> > [
> >
> > http://localhost/hello ] and see a welcome page ! this is what freaks
> > me !! i can't find
> >
> > anything in the www root directory altough i specified this directory
>
> HelloWCF uses a ServiceHost, not IIS...
>
> > Note that I haven't developed any website before on ASP.NET 2.0,
> > that's why when i open : [
> >
> > http://localhost ] it gives me "under construction page" !! Tell me
> > please why there's NOT
> >
> > nothing in the root after I build the solution or why the browser
> > gives me "..Not Found.."
> >
> > error !!
>
> Well, there will be nothing. The sample doesn't use ASP.NET or IIS. You have
> to run the host application to access the service description page from a
> browser.
>
> That doesn't mean that the sample cannot be hosted in IIS (it's actually
> trivial), but you didn't mention that you've tried that and if, what you did.
>
> Cheers,
> --
> Joerg Jooss
> news-reply@joergjooss.de
>
>
>

Hi,

So, you've got IIS installed which is listening on port 80 (http://localhost:80/hello).
You run the sample service (which uses the ServiceHost) but you are accessing
IIS. Try to configure the service to use port 8080 (you can do it in <endpoint
address="..." /> in the app.config file if it already isn't configured to
use this port) and use the following url http://localhost:8080/hello to access
your web service. Does it solve your problem?

Regarding your second problem - sorry I don't have a clue.

Best regards,
Robert Wilczynski.

> well, thanx Mr. Joerg for your reply, BUT, i hosted my service using
> a
> service host not IIS, but the browser gives me an error "...Not Found"
> ..
> About hosting the service on IIS, what's the main difference in
> procedure to
> host a simple service on IIS ??
> I repeat and say, in the "Hello WCF service" they say that you will
> find
> your service on "http://localhost/hello" this means that it's hosted
> using
> IIS !!! isn't it ?? but practically i used a service host object in
> code !!
> so im confused with that !
> and regarding the 2nd problem, I don't know what's going on !!
> something really weird !!
>
> "Joerg Jooss" wrote:
>
>> Thus wrote Murad,
>>
>>> Hi all,
>>> I will highly appreciate your help to me if you help me with one (or
>>> both)
>>> of the following 2 problems:
>>> I have the following on my machine (Windows Vista build 5308)
>>> successfully
>>> installed:
>>> 1) VS 2005 Standard
>>> 2) Sql Server 2005 Standard
>>> 3) Windows SDK February CTP (5308)
>>> 4) Microsoft Visual Studio Code-named orcas CTP preview-development
>>> tools
>>> for winFX
>>> 5) Visual Studio 2005 Extensions for WWF
>>> I have two small problems:
>>> I) I've read and fully understood Clemens Vasters article about
>>> INDIGO
>>> [
>>> http://msdn.microsoft.com/winfx/tech...tion/default.a
>>> sp
>>> x?pull=/library/en-
>>> us/dnlong/html/introtowcf.asp ] and I also read your "HELLO WCF"
>>> example
>>>
>>> [http://windowscommunication.net/coll...ages/howto.htm ]; so I
>>> wanted to ONLY re-write
>>>
>>> your "Hello WCF" example on my machine (without making any changes
>>> to the code), I wrote
>>>
>>> the service, and then, chose Build -> success, I've run the sample,
>>> yes it's working, but
>>>
>>> as mentioned in the explanation of "Hello WCF" I must be able to
>>> open [
>>>
>>> http://localhost/hello ] and see a welcome page ! this is what
>>> freaks me !! i can't find
>>>
>>> anything in the www root directory altough i specified this
>>> directory
>>>
>> HelloWCF uses a ServiceHost, not IIS...
>>
>>> Note that I haven't developed any website before on ASP.NET 2.0,
>>> that's why when i open : [
>>>
>>> http://localhost ] it gives me "under construction page" !! Tell me
>>> please why there's NOT
>>>
>>> nothing in the root after I build the solution or why the browser
>>> gives me "..Not Found.."
>>>
>>> error !!
>>>
>> Well, there will be nothing. The sample doesn't use ASP.NET or IIS.
>> You have to run the host application to access the service
>> description page from a browser.
>>
>> That doesn't mean that the sample cannot be hosted in IIS (it's
>> actually trivial), but you didn't mention that you've tried that and
>> if, what you did.
>>
>> Cheers,
>> --
>> Joerg Jooss
>> news-reply@joergjooss.de

Thank you Mr. Robert for your nice idea, i will give it a try in the coming
hours, 'coz im not working on the other OS (XP SP2) i will switch to vista
after 7 to 8 hours, thank you so much.. but keep looking at this thread plzzz
tomorrow !!

"Robert Wilczynski" wrote:

> Hi,
>
> So, you've got IIS installed which is listening on port 80 (http://localhost:80/hello).
> You run the sample service (which uses the ServiceHost) but you are accessing
> IIS. Try to configure the service to use port 8080 (you can do it in <endpoint
> address="..." /> in the app.config file if it already isn't configured to
> use this port) and use the following url http://localhost:8080/hello to access
> your web service. Does it solve your problem?
>
> Regarding your second problem - sorry I don't have a clue.
>
> Best regards,
> Robert Wilczynski.
>
> > well, thanx Mr. Joerg for your reply, BUT, i hosted my service using
> > a
> > service host not IIS, but the browser gives me an error "...Not Found"
> > ..
> > About hosting the service on IIS, what's the main difference in
> > procedure to
> > host a simple service on IIS ??
> > I repeat and say, in the "Hello WCF service" they say that you will
> > find
> > your service on "http://localhost/hello" this means that it's hosted
> > using
> > IIS !!! isn't it ?? but practically i used a service host object in
> > code !!
> > so im confused with that !
> > and regarding the 2nd problem, I don't know what's going on !!
> > something really weird !!
> >
> > "Joerg Jooss" wrote:
> >
> >> Thus wrote Murad,
> >>
> >>> Hi all,
> >>> I will highly appreciate your help to me if you help me with one (or
> >>> both)
> >>> of the following 2 problems:
> >>> I have the following on my machine (Windows Vista build 5308)
> >>> successfully
> >>> installed:
> >>> 1) VS 2005 Standard
> >>> 2) Sql Server 2005 Standard
> >>> 3) Windows SDK February CTP (5308)
> >>> 4) Microsoft Visual Studio Code-named orcas CTP preview-development
> >>> tools
> >>> for winFX
> >>> 5) Visual Studio 2005 Extensions for WWF
> >>> I have two small problems:
> >>> I) I've read and fully understood Clemens Vasters article about
> >>> INDIGO
> >>> [
> >>> http://msdn.microsoft.com/winfx/tech...tion/default.a
> >>> sp
> >>> x?pull=/library/en-
> >>> us/dnlong/html/introtowcf.asp ] and I also read your "HELLO WCF"
> >>> example
> >>>
> >>> [http://windowscommunication.net/coll...ages/howto.htm ]; so I
> >>> wanted to ONLY re-write
> >>>
> >>> your "Hello WCF" example on my machine (without making any changes
> >>> to the code), I wrote
> >>>
> >>> the service, and then, chose Build -> success, I've run the sample,
> >>> yes it's working, but
> >>>
> >>> as mentioned in the explanation of "Hello WCF" I must be able to
> >>> open [
> >>>
> >>> http://localhost/hello ] and see a welcome page ! this is what
> >>> freaks me !! i can't find
> >>>
> >>> anything in the www root directory altough i specified this
> >>> directory
> >>>
> >> HelloWCF uses a ServiceHost, not IIS...
> >>
> >>> Note that I haven't developed any website before on ASP.NET 2.0,
> >>> that's why when i open : [
> >>>
> >>> http://localhost ] it gives me "under construction page" !! Tell me
> >>> please why there's NOT
> >>>
> >>> nothing in the root after I build the solution or why the browser
> >>> gives me "..Not Found.."
> >>>
> >>> error !!
> >>>
> >> Well, there will be nothing. The sample doesn't use ASP.NET or IIS.
> >> You have to run the host application to access the service
> >> description page from a browser.
> >>
> >> That doesn't mean that the sample cannot be hosted in IIS (it's
> >> actually trivial), but you didn't mention that you've tried that and
> >> if, what you did.
> >>
> >> Cheers,
> >> --
> >> Joerg Jooss
> >> news-reply@joergjooss.de
>
>
>

Thus wrote Murad,

> well, thanx Mr. Joerg for your reply, BUT, i hosted my service using
> a
> service host not IIS, but the browser gives me an error "...Not Found"
> ..

Are you running the host when navigating to the service URL?

> About hosting the service on IIS, what's the main difference in
> procedure to
> host a simple service on IIS ??

Check out the first hands-on-lab on www.windowscommunication.net for more
information on IIS hosting. When hosting services in IIS, you don't need
to use a ServiceHost -- that's taken care of by IIS. The model is quite similar
to ASP.NET Web services with ASMX files -- you write a SVC file that references
the actual service implementation, and access that file with your service
client.

> I repeat and say, in the "Hello WCF service" they say that you will
> find
> your service on "http://localhost/hello" this means that it's hosted
> using
> IIS !!! isn't it ?? but practically i used a service host object in
> code !!

The article doesn't even mention IIS hosting, so please forget about IIS
for the moment. In that sample, HelloService provides both the service and
the service host, and it's HelloService.exe that listens for requests on
http://localhost/hello -- assuming that neither IIS nor any other web server
is occupying port 80. The sample will also work if you switch to an arbitrary
port like http://localhost:8080/hello.

Cheers,
--
Joerg Jooss
news-reply@joergjooss.de

Well, Thanx Joerg for your awesome link to the hands on lab im gonna register
for it very soon, I almost got the idea after being confused between Sevice
Host and IIS hosting, but to answer you question above, Yes, I do run the
service host when i navigate to the service URL..
but what's the point of using INDIGO technology (in case of IIS hosting)
instead of Web Services itself !!?

"Joerg Jooss" wrote:

> Thus wrote Murad,
>
> > well, thanx Mr. Joerg for your reply, BUT, i hosted my service using
> > a
> > service host not IIS, but the browser gives me an error "...Not Found"
> > ..
>
> Are you running the host when navigating to the service URL?
>
> > About hosting the service on IIS, what's the main difference in
> > procedure to
> > host a simple service on IIS ??
>
> Check out the first hands-on-lab on www.windowscommunication.net for more
> information on IIS hosting. When hosting services in IIS, you don't need
> to use a ServiceHost -- that's taken care of by IIS. The model is quite similar
> to ASP.NET Web services with ASMX files -- you write a SVC file that references
> the actual service implementation, and access that file with your service
> client.
>
> > I repeat and say, in the "Hello WCF service" they say that you will
> > find
> > your service on "http://localhost/hello" this means that it's hosted
> > using
> > IIS !!! isn't it ?? but practically i used a service host object in
> > code !!
>
> The article doesn't even mention IIS hosting, so please forget about IIS
> for the moment. In that sample, HelloService provides both the service and
> the service host, and it's HelloService.exe that listens for requests on
> http://localhost/hello -- assuming that neither IIS nor any other web server
> is occupying port 80. The sample will also work if you switch to an arbitrary
> port like http://localhost:8080/hello.
>
> Cheers,
> --
> Joerg Jooss
> news-reply@joergjooss.de
>
>
>

Thus wrote Murad,

> Well, Thanx Joerg for your awesome link to the hands on lab im gonna
> register
> for it very soon, I almost got the idea after being confused between
> Sevice
> Host and IIS hosting, but to answer you question above, Yes, I do run
> the
> service host when i navigate to the service URL..

Then it should work. I hacked the sample up again once more after reading
your first post and had no problem with it.

> but what's the point of using INDIGO technology (in case of IIS
> hosting)
> instead of Web Services itself !!?

What are we discussing now -- hosting or Web Services? The idea of IIS hosting
is to get an application server infrastructure for free instead of creating
one yourself using ServiceHost.

Regarding Web Services -- Indigo *is* the future WS-* stack -- and much more,
if you need stuff like message queueing, TCP or IPC transport channels, yada
yada.

Cheers,
--
Joerg Jooss
news-reply@joergjooss.de

I appreciate your cooperation with me Mr. Joerg, i've been so busy the past
days, and i will start the "Hellow WCF" over again and feedback you ..
I got the idea that INDIGO is the future of WS* thank you.
i might feedback soon ...

"Joerg Jooss" wrote:

> Thus wrote Murad,
>
> > Well, Thanx Joerg for your awesome link to the hands on lab im gonna
> > register
> > for it very soon, I almost got the idea after being confused between
> > Sevice
> > Host and IIS hosting, but to answer you question above, Yes, I do run
> > the
> > service host when i navigate to the service URL..
>
> Then it should work. I hacked the sample up again once more after reading
> your first post and had no problem with it.
>
> > but what's the point of using INDIGO technology (in case of IIS
> > hosting)
> > instead of Web Services itself !!?
>
> What are we discussing now -- hosting or Web Services? The idea of IIS hosting
> is to get an application server infrastructure for free instead of creating
> one yourself using ServiceHost.
>
> Regarding Web Services -- Indigo *is* the future WS-* stack -- and much more,
> if you need stuff like message queueing, TCP or IPC transport channels, yada
> yada.
>
> Cheers,
> --
> Joerg Jooss
> news-reply@joergjooss.de
>
>
>