Windows Scripting
  Home arrow Windows Scripting arrow Page 6 - Silverlight 2.0 Application Development wi...
ASP Free Forums 
.NET  
ASP  
ASP Code  
ASP.NET  
ASP.NET Code  
BrainDump  
C#  
Code Examples  
Database  
Database Code  
IIS  
Microsoft Access  
MS SQL Server  
Silverlight  
Visual Basic.NET  
Windows Scripting  
Windows Security  
XML  
Mobile Linux 
App Generation ROI 
IBM® developerWorks 
ASP Web Hosting  
ASP.NET Web Hosting 
Windows Web Hosting
 
Weekly Newsletter
 
Developer Updates  
Free Website Content 
 RSS  Articles
 RSS  Forums
 RSS  All Feeds
Write For Us Get Paid 
Request Media Kit
Contact Us 
Site Map 
Privacy Policy 
Support 
 USERNAME
 
 PASSWORD
 
 
  >>> SIGN UP!  
  Lost Password? 
WINDOWS SCRIPTING

Silverlight 2.0 Application Development with LINQ to SQL and a WCF Service
By: Jagadish Chaterjee
  • Search For More Articles!
  • Disclaimer
  • Author Terms
  • Rating: 5 stars5 stars5 stars5 stars5 stars / 6
    2008-11-12

    Table of Contents:
  • Silverlight 2.0 Application Development with LINQ to SQL and a WCF Service
  • Creating a Visual Studio 2008 solution to work with “LINQ to SQL”, WCF and Silverlight 2.0
  • WCF development
  • Silverlight development
  • Troubleshooting configurations
  • Troubleshooting configurations: continued

  • Rate this Article: Poor Best 
      ADD THIS ARTICLE TO:
      Del.ici.ous Digg
      Blink Simpy
      Google Spurl
      Y! MyWeb Furl
    Email Me Similar Content When Posted
    Add Developer Shed Article Feed To Your Site
    Email Article To Friend
    Print Version Of Article
    PDF Version Of Article
     
     
    ADVERTISEMENT


    Silverlight 2.0 Application Development with LINQ to SQL and a WCF Service - Troubleshooting configurations: continued


    (Page 6 of 6 )

    These troubleshooting configurations are continued from the previous section.

    Silverlight application configurations:

    • Configure the Silverlight application (DemoSL.Web) to the same IIS root as the WCF service discussed above (and also with the same options). This is just to minimize errors during development. However, it could be totally different during deployment.

    • Make sure that MIME types are added as shown below

    • Make sure that you add “Service reference” to the WCF project in the current solution for better debugging capabilities.

    • Make sure that “ClientAccessPolicy.xml” is added to IIS root (usually, c:inetpubwwwroot) as follows:


    <?xml version="1.0" encoding="utf-8" ?>

    <access-policy>

    <cross-domain-access>

    <policy>

    <allow-from http-request-headers="*">

    <domain uri="*" />

    </allow-from>

    <grant-to>

    <resource include-subpaths="true" path="/" />

    </grant-to>

    </policy>

    </cross-domain-access>

    </access-policy>



    • Make sure that “ServiceReferences.ClientConfig” is provided as shown below:


    <configuration>

    <system.serviceModel>

    <bindings>

    <basicHttpBinding>

    <binding name="BasicHttpBinding_IEmpService" maxBufferSize="65536"

    maxReceivedMessageSize="65536">

    <security mode="None" />

    </binding>

    <binding name="BasicHttpBinding_IEmpService1" maxBufferSize="65536"

    maxReceivedMessageSize="65536">

    <security mode="None" />

    </binding>

    <binding name="BasicHttpBinding_IEmpService2" maxBufferSize="2147483647"

    maxReceivedMessageSize="2147483647">

    <security mode="None" />

    </binding>

    </basicHttpBinding>

    </bindings>

    <client>

    <endpoint address="http://localhost/DemoEmpService/EmpService.svc"

    binding="basicHttpBinding" bindingConfiguration="BasicHttpBinding_IEmpService"

    contract="DemoSL.EmpService.IEmpService" name="BasicHttpBinding_IEmpService" />

    <endpoint address="http://vwin2k3/DemoEmpService/EmpService.svc"

    binding="basicHttpBinding" bindingConfiguration="BasicHttpBinding_IEmpService2"

    contract="EmpService.IEmpService" name="BasicHttpBinding_IEmpService1" />

    </client>

    </system.serviceModel>

    </configuration>



    • “vwin2k3” is my machine name. You need to replace to yours.

    • Make sure that the debug is set to true in web.config (in DemoSl.Web)


    In my upcoming articles, we will see more and more examples of Silverlight 2.0 development together with LINQ to SQL and WCF. I hope you enjoyed the article and any suggestions, bugs, errors, enhancements etc. are highly appreciated at http://jagchat.spaces.live.com


    DISCLAIMER: The content provided in this article is not warranted or guaranteed by Developer Shed, Inc. The content provided is intended for entertainment and/or educational purposes in order to introduce to the reader key ideas, concepts, and/or product reviews. As such it is incumbent upon the reader to employ real-world tactics for security and implementation of best practices. We are not liable for any negative consequences that may result from implementing any information covered in our articles or tutorials. If this is a hardware review, it is not recommended to open and/or modify your hardware.

       · Thanks for a great article! Nice explanation!One issue I had was after I added...
     

    WINDOWS SCRIPTING ARTICLES

    - More Windows Scripting Workarounds from Nilpo
    - Overloading Methods and More in VBScript
    - Improving MFC for Windows Vista
    - Regular Expressions in VBScript
    - Working with Dates in WMI
    - Completing Calendars with VBScript Date Func...
    - Building Calendars with VBScript Date Functi...
    - Working With Dates and Times in VBScript
    - Designing WCF DataContract Classes Using the...
    - Understanding Dates and Times in VBScript
    - Working With Arrays in VBScript
    - Compressed Folders in WSH
    - Using .NET Interops in VBScript
    - Nilpo`s Scripting Secrets, Vol I
    - Database operations using Silverlight 2.0 WC...





    © 2003-2009 by Developer Shed. All rights reserved. DS Cluster 5 Hosted by Hostway
    For more Enterprise Application Development news, visit eWeek