Have you missed the Heroes Happen Here event in Ft Lauderdale? Do you want to revisit some of the topics? Then don't miss today's Mini-Launch at Devry University in Miramar. I will be showcasing the demos from the "Reach End-Users with Next Generation Web Applications" session. My friend, Max Trinidad, will be talking about Server Core and the Entity Framework.

Join me and Joe Healy, aka the DevFish, for the Microsoft Heroes Happen Here event in Ft Lauderdale. There will be a lot of content regarding Visual Studio 2008, SQL Server 2008, and Windows Server 2008. The event is at the Broward Convention Center:

1950 Eisenhower Blvd,
Fort Lauderdale, FL 33316

See you there!

I noticed that my outlook RSS feeds were not synching. After verifying the feeds were ok I search for a solution and found a hotfix for it. As of today you have to request the hotfix to Microsoft support since it is not publicly available yet. Follow the instructions on how to obtain it.

http://support.microsoft.com/kb/950282

Two days ago I got an email from Tony Davis letting me know that Simple-Talk is coming out with an eBook. The book will include a combination of the best ASP.NET articles published by simple-talk. My article, Take Row-Level Control of Your GridView is part of the eBook.

My coworker, John Papa, is a co author along with many other authors.

Stay tuned for more info on where to download the book.

When you query the WSDL of a WCF service that is hosted with HTTPS the location of the service will be pointed to the machine name by default. So if a client is querying your service by pointing to https://www.yourdomain.com/YourService/Service.svc?wsdl the WSDL will come back with something like this:

<wsdl:service name="ServiceName">

    <wsdl:port name="HttpService" binding="tns:HttpService">

        <soap12:address location="https://MachineName/YourService/Service.svc" /> 

        <wsa10:EndpointReference>

            <wsa10:Address>https://MachineName/YourService/Service.svc</wsa10:Address> 

        </wsa10:EndpointReference>

    </wsdl:port>

</wsdl:service>

Therefore the client machine will not be able to generate the appropriate proxy because it will never be able to query the service using the MachineName (it is most likely sitting outside of the server's internal network).

To fix this all you have to do is add an HTTPS Host Header to the correct website. Unfortunately, this is not doable through the GUI, but it can be done in command line. To do so in IIS 6.0 run the following script by replacing the <website id> with your website id (usually it is 1) and <host header> with your fully qualified domain:

%systemroot%\system32\cscript.exe //nologo %systemdrive%inetpub\adminscripts\adsutil.vbs set /w3svc/<website id>/SecureBindings ":443:<host header>"

After that just reset iis by running an iisreset.

If you browse to your wsdl file you should find that the address changed to the fully qualified domain.

Happy Configuring!