Click here to Skip to main content
15,887,596 members
Please Sign up or sign in to vote.
4.00/5 (1 vote)
See more:
Hi,

I'm new to the millions of configurations that are possible in IIS Manager.

I have made a WCF service called calc. It is able to +, -, * and /. It *works* when I publish it on the VS-build-in Development/Webserver and call it from a Form-client I have, using a proxy.

IF however I change from "Use Visual Studio Development Server" to "Use Local IIS Server" I can't call it anymore - I don't understand why.

I CAN browse it from its virtual dir. but when i goto the calc.svc it says:

"The page you are requesting cannot be served because of the extension configuration. If the page is a script, add a handler. If the file should be downloaded, add a MIME map."

What does this mean?? I suppose a webserver can understand a svc-extension?!?!


I performed all the usual steps - rebuild, the service, published it, and (for the client) updated its ws-ref.

I've spend many hours on this now... could it be something inside the IIS configuration? Have been on Google - no luck.

I'm ate the point of reinstalling IIS...
(IIS came after VS and .Net 4.0 and I know I must run the fix-and-repair for VS to make them play together... cna it be that?)


Thanx' in advance,
Michael.
Posted

Thank you!

From the link you gave me I was able to figure out that it perhaps had something to do with configuration (I'm still a WCF/IIS-newbie). On the other hand the link was not Win7 specific so it was not a 100% match.

Never the less; problem seemed to be that my IIS7.5 came *after* .NET 4.0. But what really did the trick was:

MSIL
c:\Windows\Microsoft.NET\Framework\v4.0.30319>aspnet_regiis.exe -i
Start installing ASP.NET (4.0.30319).
..........
Finished installing ASP.NET (4.0.30319).


(as suggested here: http://forums.iis.net/p/1149449/1869918.aspx[^])

This I did after turning ON MS .NET Framework 3.51 in the "Turn Windows features on/off" dlg. This was still off after IIS installation. Not sure if this is necessary?

Along the road I also had a ManagedPipelineHandler error (???) and that suggested the aspnet_regiis.exe -i thing - thanks to Google.

So much ado about almost nothing. At this point I was able to - for the first time - see the "You have created a service."-page from the right server.

Then i rebuilded both the service and the client. Updated the clients service-config to have the right endpoint-address - AND I made a "Convert to Web application" from the ctx. menu of the service (think one *has* to do that from the link you suggested).

Then I was almost there... next thing was a warning from win. that someone tried to call my service. That someone was Admin :-)

Doing these thing for the first time is, I feel, exceedingly complicated... I have to practice a lot :-)

Thanx' again.a
 
Share this answer
 
Comments
Mark Salsbery 18-May-11 12:35pm    
FWIW, the aspnet_regiis thing is in the first section at that link. Yes it's not Windows 7 specific because IIS isn't windows 7 specific...it's actually part of Windows Server, but since Windows 7 is based on the same platform, IIS can be installed there as well.

Anyway, glad you got it working! Yes it's confusing the first time. I usually have to go back to that documentation when I do a fresh OS install as well :)

Cheers.
If you've done all the IIS configuration and deployment steps it should work...

Deploying an Internet Information Services-Hosted WCF Service[^]

Running from Visual Studio you shouldn't need to worry about deployment since IIS will use your hosting app project's bin folder directly. So I would focus on proper IIS configuration...
 
Share this answer
 
v2

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900