Rafael Zuniga, Stephen Cave
Summary:
In an effort to expose an endpoint via website, we first make some modifications to the supplied solution, adding a new website "IISHostedService", clearing the service implementation, modifying the @ServiceHost directive to associate with our service type, and making small changes to the web.config file regarding endpoint and service tags.
Summary:
In an effort to expose an endpoint via website, we first make some modifications to the supplied solution, adding a new website "IISHostedService", clearing the service implementation, modifying the @ServiceHost directive to associate with our service type, and making small changes to the web.config file regarding endpoint and service tags.
The next portion had us try to browse the metadata on the website. Unfortunately, due to some unknown issue, we could not get the website to display after about an hours worth of troubleshooting(notes are listed in the problems section). This may be an issue with windows 7 or my version of visual studio, which has worked alright up till now.
If I can figure out what the issue is, I will return and finish the last portion of the lab.
...
After enabling every IIS function under the sun, then going back to the FAQ on our class website and running ServiceModelReg -i on the 64bit v3.0 WCF framework, I think we finally have what we were looking for... Or maybe not.
Finally nailing down the issue, the book has another inconsistency in that at the behavior name flip flops in 2 example points between "ServiceBehavior" on page 54 and "returnFaults" on page 56, neither is really mentioned as a change in bold or anything to be aware of, but having swapped it, a mismatch is created. Lovely. Finally getting the correct output, though weirdly enough I must still have the svc file focused in VS for it to load the correct web address.
While as in the book there is now a link to the wsdl, clicking on it unfortunately brings us to another empty page. I shudder to think what may be behind this problem, or how to find it, as there is nothing left to enable, nor clues in the class FAQ.
Attempting to run svcutil for the last portion of this lab yields what appears to be results in cmd, but nothing is generated in visual studio, and I am unable to complete the lab.
Notes on Usefulness:
The intended effect of the lab seems very beneficial, but more and more it becomes frustrating working through errors in the book, and contradictions between my system and the books system, as well as the limited vision the book provides of what is supposed to be in the solution. Unfortunately no errors were generated in this lab, so the best we could muster was to poke around making changes here and there, hoping to stumble upon the issue.
Differences/problems/mistakes -> troubleshooting:
-when attempting to add a website to the solution, we get "Unable to create the website 'http://localhost/IISHostedService'. To access local IIS Web sites, you must install the following IIS components: IIS 6 Metabase and IIS 6 Configuration Compatibility Windows Authentication. In addition you must run Visual Studio in the context of an administrator account." Trying again brings another error, demanding Windows Authentication for IIS. After another enabling spree, the web site was added
-The book wants you to run the new website in debug mode (f5) but debugging is not enabled in Web.config and a prompt is supplied as a result. We enable debugging.
-When launched in either debugging or non-debugging, only a blank browser window is displayed, not the supposed metadata publishing. Weirder still, found debugging normally opens page http://localhost/IISHostedService/ but if we hit debug while looking at Service.svc, it fails to debug, and if we run without debugging, it loads the intended http://localhost/IISHostedService/Service.svc but there is no page to be displayed.
-apparently not all components of IIS were installed, and once installed they needed to be configured with the frustratingly obscure method described on the school website.
-Finally, a book inconsistency was found, that when fixed seems to let the website function properly as long as one debugs while the svc file is currently being focused. Still weird.
-once the website functioned, it still failed to properly generate wsdl for some unknown reason. The link is there, but it returns a blank page.
No comments:
Post a Comment