<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearchrss/1.0/" xmlns:georss="http://www.georss.org/georss" version="2.0"><channel><atom:id>tag:blogger.com,1999:blog-2403430606101974989</atom:id><lastBuildDate>Thu, 05 Nov 2009 07:58:48 +0000</lastBuildDate><title>DotNetMind :: WCF Silverlight WPF</title><description>Manpreet Grewal and his .NET experiences expressed through this blog</description><link>http://dotnetmind.blogspot.com/</link><managingEditor>noreply@blogger.com (MP Grewal)</managingEditor><generator>Blogger</generator><openSearch:totalResults>29</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" href="http://feeds.feedburner.com/Dotnetmind" type="application/rss+xml" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com" /><item><guid isPermaLink="false">tag:blogger.com,1999:blog-2403430606101974989.post-2996234004303481876</guid><pubDate>Wed, 20 May 2009 03:28:00 +0000</pubDate><atom:updated>2009-05-20T08:58:24.225+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">JavaScript</category><title>Stop hyperlink href browse</title><atom:summary type="text">Suppose a scenario comes where you have a Javascript onclick event defined on a hyperlink which performs some action and you want to prevent the hyperlink to browse the URL specified in the href. By default, first onclick script is executed then hyperlink takes you to the href webpage. If you want to suppress the later, the technique to do this is using jQuery. In the post, I assume you know ABC </atom:summary><link>http://dotnetmind.blogspot.com/2009/05/stop-hyperlink-href-browse.html</link><author>noreply@blogger.com (MP Grewal)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-2403430606101974989.post-1052109580477850419</guid><pubDate>Wed, 20 May 2009 02:57:00 +0000</pubDate><atom:updated>2009-05-20T08:27:11.203+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">JavaScript</category><title>Stop JavaScript event bubbling</title><atom:summary type="text">JavaScript performs event bubbling in the sense that when an event like omouseover, onclick, etc occurs in the child controls it is raised for the containing controls also till the outermost parent containing control. Suppose we have a HTML structure like this             1:  &lt;div id="blockDiv"&gt;        2:       &lt;span&gt;&lt;a href="http://www.example.com/"&gt;The quick brown fox jumps over the lazy dog.</atom:summary><link>http://dotnetmind.blogspot.com/2009/05/stop-javascript-event-bubbling.html</link><author>noreply@blogger.com (MP Grewal)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-2403430606101974989.post-8744630302417482076</guid><pubDate>Sun, 13 Jul 2008 06:55:00 +0000</pubDate><atom:updated>2008-07-13T12:34:37.176+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">WCF</category><title>Message Contracts Vs Data Contracts in WCF</title><atom:summary type="text">There's a big confusion among WCF developers while understanding the concept of Message Contracts. Are they really required? Why were they included in WCF when Data Contracts can do everything. 
Well the truth is that both Message Contracts and Data Contracts possess their own niche in SOAP messaging. In the below table, I'll be drawing a thick line to show differences between Message Contracts </atom:summary><link>http://dotnetmind.blogspot.com/2008/07/message-contracts-vs-data-contracts-in.html</link><author>noreply@blogger.com (MP Grewal)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-2403430606101974989.post-9194403892528575514</guid><pubDate>Sat, 12 Jul 2008 16:16:00 +0000</pubDate><atom:updated>2008-07-12T21:46:53.644+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">WCF</category><title>Multiple interfaces in a WCF contract</title><atom:summary type="text">Well most of the time we have requirement of having one ServiceContract for an endpoint. But sometimes we get into a situation when the implementation is spread across multiple interfaces and we need to include the functionality spread into both the implementations into our WCF class. To suffice such a requirement we can use the concept of Interface Aggregation. Suppose we have two interfaces</atom:summary><link>http://dotnetmind.blogspot.com/2008/07/multiple-interfaces-in-wcf-contract.html</link><author>noreply@blogger.com (MP Grewal)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-2403430606101974989.post-5855622937692686486</guid><pubDate>Sat, 12 Jul 2008 09:32:00 +0000</pubDate><atom:updated>2008-07-12T15:39:42.039+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">.NET 3.5</category><category domain="http://www.blogger.com/atom/ns#">WCF</category><title>IIS hosted Duplex WCF Service</title><atom:summary type="text">Today, I'm showing you how to create a Duplex Contract WCF service which will be hosted in the IIS and called from various console App clients. We will be understanding the WCF Duplex Services and Contracts concept from the classic Stock Exchange example. In this example we are having a WCF Duplex service named DuplexStock1. This service will receive subscription requests from various clients for</atom:summary><link>http://dotnetmind.blogspot.com/2008/07/iis-hosted-duplex-wcf-service.html</link><author>noreply@blogger.com (MP Grewal)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-2403430606101974989.post-7745779878922281150</guid><pubDate>Tue, 08 Jul 2008 19:08:00 +0000</pubDate><atom:updated>2008-07-09T01:04:15.781+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">WCF</category><title>WCF bare unwrapped Response</title><atom:summary type="text">Many times we have seen that a WCF method of return type string spits Response which is wrapped in a String element e.g. the one shown below&lt;string xmlns="http://schemas.microsoft.com/2003/10/Serialization/"&gt;&lt;Company&gt;Nucleus&lt;/Company&gt;&lt;/string&gt;We may want it to return pure Xml Response, the unwrapped one like&lt;Company&gt;Nucleus&lt;/Company&gt;These are steps you should use to achieve it1. Change the </atom:summary><link>http://dotnetmind.blogspot.com/2008/07/wcf-bare-unwrapped-response.html</link><author>noreply@blogger.com (MP Grewal)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-2403430606101974989.post-3403024893359531278</guid><pubDate>Tue, 08 Jul 2008 18:59:00 +0000</pubDate><atom:updated>2008-07-09T01:04:41.163+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">WPF</category><category domain="http://www.blogger.com/atom/ns#">Silverlight</category><title>Differences between WPF and Silverlight</title><atom:summary type="text">Nowadays, two terms are mostly heard in Windows Graphics sphere, WPF and Silverlight. Many of us presume they are one and the same thing. But actually there are fundamental differences between the two. In this post, I'm posting the basic differences between the two (primarily Silverlight 1.x) WPFSilverlight 1.xWPF is the complete graphics framework written from the scratch by MicrosoftSilverlight</atom:summary><link>http://dotnetmind.blogspot.com/2008/07/differences-between-wpf-and-silverlight.html</link><author>noreply@blogger.com (MP Grewal)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-2403430606101974989.post-1559447443571215205</guid><pubDate>Tue, 08 Jul 2008 18:53:00 +0000</pubDate><atom:updated>2008-07-09T01:04:58.699+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">WCF</category><title>Resolving Download Failure in WebClient</title><atom:summary type="text">Today I was developing a Silverlight client program which reads cross-domain content when I started facing Download Failure exception. This is code I was using, which resulted in exceptionprivate void btnSearch_Click(object sender, RoutedEventArgs e){string strTopic=txtSearchTopic.Text;string strUrl = "";            WebClient wc = new WebClient();            wc.DownloadStringCompleted += new </atom:summary><link>http://dotnetmind.blogspot.com/2008/07/resolving-download-failure-in-webclient.html</link><author>noreply@blogger.com (MP Grewal)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-2403430606101974989.post-8423051481732620542</guid><pubDate>Tue, 08 Jul 2008 18:46:00 +0000</pubDate><atom:updated>2008-07-09T01:05:15.450+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">Silverlight</category><title>Silverlight HyperlinkButton turns page blank</title><atom:summary type="text">Today when I was using the HyperlinkButton control on a Silverlight page and supplying it proper values for NavigateUri and Content attributes, I found that the control was not behaving properly and made the page blank while rendering in the browser. It threw browser exception saying InvalidOperationException. This was the code which I was using&lt;HyperlinkButton x:Name=”lnkSports” Content="Sports </atom:summary><link>http://dotnetmind.blogspot.com/2008/07/silverlight-hyperlinkbutton-turns-page.html</link><author>noreply@blogger.com (MP Grewal)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-2403430606101974989.post-3035199042859242043</guid><pubDate>Tue, 08 Jul 2008 18:34:00 +0000</pubDate><atom:updated>2008-07-09T01:05:22.701+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">Silverlight</category><title>Handle Silverlight event in javascript</title><atom:summary type="text">This post will show you how to throw events from Silverlight controls in managed code and catch them in javascript. Such a scenario comes while building HTML bridge in Beta 2, when you need to catch the events from Silverlight UserControls in the aspx page hosting them. We'll take the example of ListBox SelectionChanged Event. Whenever Listbox's selection is changed in the SL user control we'll </atom:summary><link>http://dotnetmind.blogspot.com/2008/07/handle-silverlight-event-in-javascript.html</link><author>noreply@blogger.com (MP Grewal)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-2403430606101974989.post-791844168645400821</guid><pubDate>Tue, 08 Jul 2008 18:20:00 +0000</pubDate><atom:updated>2008-07-09T01:05:59.253+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">WPF</category><category domain="http://www.blogger.com/atom/ns#">XAML</category><category domain="http://www.blogger.com/atom/ns#">Silverlight</category><title>Essential XAML Simplified 2</title><atom:summary type="text">As we have seen in the previous post XAML provides new generation of opportunities by which we can describe an object. Here we'll cover the remaining two conceptsAttached Properties Markup Extensions Going back to previous example of TextBlock which is shown below&lt;TextBlock Text="Title:" Style="{StaticResource TextBlockStyle}" Grid.Row="0" Grid.Column="0" HorizontalAlignment="Right"&gt;&lt;/TextBlock&gt;</atom:summary><link>http://dotnetmind.blogspot.com/2008/07/essential-xaml-simplified-2.html</link><author>noreply@blogger.com (MP Grewal)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-2403430606101974989.post-2461515424680015523</guid><pubDate>Sun, 06 Jul 2008 19:01:00 +0000</pubDate><atom:updated>2008-07-09T01:06:23.526+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">Silverlight</category><category domain="http://www.blogger.com/atom/ns#">WCF</category><title>ProtocolException 404 Silverlight WCF</title><atom:summary type="text">This is blog entry will help those who understand Cross Domain restrictions in Silverlight while calling a WCF service in another domain. If you already tried many prescribed things to allow Cross Domain Access like placing the clientaccesspolicy.xml in wwwroot folder and putting a crossdomain.xml on the IIS root (wwwroot folder). But still you are getting the same obstinate 404 error. Then you </atom:summary><link>http://dotnetmind.blogspot.com/2008/07/protocolexception-404-silverlight-wcf.html</link><author>noreply@blogger.com (MP Grewal)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-2403430606101974989.post-9165603489562087597</guid><pubDate>Sat, 05 Jul 2008 08:48:00 +0000</pubDate><atom:updated>2008-07-09T01:06:32.043+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">WCF</category><title>Step into WCF service</title><atom:summary type="text">This article addresses a common problem encountered while debugging a WCF service hosted in IIS from a client like a Console App or a Win App. Even if you put break points in the WCF service but you are not able to step into the service by pressing F11. Instead you a get an error dialog as show below saying "Unable to automatically step into the server. The remote procedure could not be debugged.</atom:summary><link>http://dotnetmind.blogspot.com/2008/07/step-into-wcf-service.html</link><author>noreply@blogger.com (MP Grewal)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-2403430606101974989.post-5892334887215772110</guid><pubDate>Wed, 02 Jul 2008 15:41:00 +0000</pubDate><atom:updated>2008-07-09T01:07:31.429+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">WCF</category><title>How to read post request in WCF</title><atom:summary type="text">Sometimes we have requirement in which we have to read data from request body / payload instead of its Querystring. Though it can be easily done in .NET 2.0 but it is hard to find in WCF. In this post, we'll see how to do it.Here's the code to perform this//Code Listing 1public void MyPostHandler(Stream input){ StreamReader sr = new StreamReader(input);  string str = sr.ReadToEnd();  sr.Close();/</atom:summary><link>http://dotnetmind.blogspot.com/2008/07/how-to-read-post-request-in-wcf.html</link><author>noreply@blogger.com (MP Grewal)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-2403430606101974989.post-6196245478187848889</guid><pubDate>Wed, 02 Jul 2008 15:39:00 +0000</pubDate><atom:updated>2008-07-09T01:07:37.663+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">REST</category><title>Why REST is called Representational State Transfer?</title><atom:summary type="text">The extension of the acronym REST is Representational State Transfer. This extension was wisely chosen by Roy Fielding because it says a lot in just three words. Many of us might have wondered why REST is called so?So here's a small explanation based on My UnderstandingThe definition goes back in 1990s when REST was being invented and Web was a very nascent creature.The word Representational </atom:summary><link>http://dotnetmind.blogspot.com/2008/07/why-rest-is-called-representational.html</link><author>noreply@blogger.com (MP Grewal)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-2403430606101974989.post-1330454875406318389</guid><pubDate>Wed, 02 Jul 2008 06:25:00 +0000</pubDate><atom:updated>2008-07-09T01:02:14.526+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">Silverlight</category><title>Adding multiple Silverlight user controls on aspx</title><atom:summary type="text">Sometimes we have requirement of adding multiple Silverlight UserControls over same ASP.NET web page (aspx). Like when you want to host silverlight web parts on a single aspx page in separate areas.All silverlight controls are zipped into a single .xap file. And the &lt;?xml:namespace prefix = asp /&gt;tag refers to xap file using source attribute as shown in the below code&lt;asp:Silverlight ID="Xaml1" </atom:summary><link>http://dotnetmind.blogspot.com/2008/07/adding-multiple-silverlight-user.html</link><author>noreply@blogger.com (MP Grewal)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-2403430606101974989.post-2375465875948600926</guid><pubDate>Tue, 01 Jul 2008 21:05:00 +0000</pubDate><atom:updated>2008-07-09T01:07:04.794+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">.NET 3.5</category><category domain="http://www.blogger.com/atom/ns#">LINQ</category><title>Read XML into string using LINQ</title><atom:summary type="text">LINQ has made programmer’s life much easier and taken away pains of parsing XML nodes using XPath or Xml DOM. In this thread, we’ll see an example of reading XML contents into string variables using LINQ. Suppose we have sample XML Message which looks like this &lt;Input&gt;&lt;City&gt;Ludhiana&lt;/City&gt;&lt;State&gt;Punjab&lt;/State&gt;&lt;Country&gt;India&lt;/Country&gt;&lt;Phone&gt;01613535366&lt;/Phone&gt;&lt;/Input&gt;Now you want to parse the </atom:summary><link>http://dotnetmind.blogspot.com/2008/07/read-xml-into-string-using-linq.html</link><author>noreply@blogger.com (MP Grewal)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-2403430606101974989.post-886000820312469785</guid><pubDate>Tue, 01 Jul 2008 20:53:00 +0000</pubDate><atom:updated>2008-07-09T01:03:56.918+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">Silverlight</category><title>InitializeFromXaml &amp; XamlReader.Load in Silverlight Beta 2</title><atom:summary type="text">In this post, we’ll discuss how to resolve two common issues which come while migrating Silverlight Beta 1 Apps to Beta 2. Below I am showing Beta 1 code and its equivalent code in Beta 2Compile time error1. Does not contain a definition for InitializeFromXaml //Beta 1 System.IO.Stream s = this.GetType().Assembly.GetManifestResourceStream("MyNamespace.UserControl1.xaml");     FrameworkElement </atom:summary><link>http://dotnetmind.blogspot.com/2008/07/initializefromxaml-xamlreaderload-in.html</link><author>noreply@blogger.com (MP Grewal)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-2403430606101974989.post-2891864279590294966</guid><pubDate>Tue, 01 Jul 2008 19:47:00 +0000</pubDate><atom:updated>2008-07-09T01:08:09.770+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">IIS</category><title>Allow PUT in IIS</title><atom:summary type="text">I was having a WCF webservice which was supposed to be called via HTTP PUT method. I wrote my PUT method handlers using REST support in WCF ie WebInvoke(method="POST") and was hoping that things will go smooth. But suddenly I started getting 403 forbidden errors from IIS whenever I started making requests to this service using Fiddler.I ensured that IIS is having “Scripts and Executables” </atom:summary><link>http://dotnetmind.blogspot.com/2008/07/allow-put-in-iis.html</link><author>noreply@blogger.com (MP Grewal)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://bp2.blogger.com/_ti-E_cYJf0c/SGqKsuL8TNI/AAAAAAAAACs/eiJO-jn_ZP4/s72-c/ext.jpg" height="72" width="72" /><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-2403430606101974989.post-6591323342610951049</guid><pubDate>Tue, 01 Jul 2008 19:30:00 +0000</pubDate><atom:updated>2008-07-09T01:08:40.375+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">AJAX</category><title>Non-postback dropdownlist using AJAX</title><atom:summary type="text">In this article, we’ll use the excellence of AJAX to create a non-postback dropdownlist which pulls its data from the server without refreshing entire page. Primarily, we will leverage the core functionality of the UpdatePanel ASP.NET AJAX control which makes it possible.I have kept this article developer friendly which means you don’t need to write much Javascript and will be writing .NET code </atom:summary><link>http://dotnetmind.blogspot.com/2008/07/non-postback-dropdownlist-using-ajax.html</link><author>noreply@blogger.com (MP Grewal)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://bp0.blogger.com/_ti-E_cYJf0c/SGqJbmQqytI/AAAAAAAAACk/R6XYBSTeNQA/s72-c/capture.jpg" height="72" width="72" /><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-2403430606101974989.post-2436002957902424313</guid><pubDate>Tue, 01 Jul 2008 16:13:00 +0000</pubDate><atom:updated>2008-07-09T01:10:34.211+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">VS 2008</category><title>Difference between WCF Service Reference and Web Reference</title><atom:summary type="text">Previously, I wrote a post about Adding Service Reference in VS 2008. Adding Web Reference has been deprecated in VS 2008, as Microsoft now wants to promote WCF's Add Service Reference only. In this post we'll see basic differences in client proxy which have implemented Add Web Reference ( AWR ) and Add Service Reference ( ASR )First difference is that to create AWR resources (proxy class and </atom:summary><link>http://dotnetmind.blogspot.com/2008/07/difference-between-wcf-service.html</link><author>noreply@blogger.com (MP Grewal)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-2403430606101974989.post-7355493346719021339</guid><pubDate>Thu, 19 Jun 2008 14:55:00 +0000</pubDate><atom:updated>2008-07-09T01:10:53.680+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">C#</category><title>IsNumber IsNaN in C# .NET</title><atom:summary type="text">Many times we get the requirement to find out where the input is a valid integer or not. In C#, there is no straight forward method for this. Although many basic languages like JavaScript provide IsNaN() function for the same purpose. Anyway, I will show how to suffice this requirement writing minimum amount of code possibleThe magic code to do this isint dummyInt;if(Int32.TryParse(months,out </atom:summary><link>http://dotnetmind.blogspot.com/2008/06/isnumber-isnan-in-c-net.html</link><author>noreply@blogger.com (MP Grewal)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-2403430606101974989.post-6985715679644386118</guid><pubDate>Sun, 08 Jun 2008 19:12:00 +0000</pubDate><atom:updated>2008-07-09T01:11:12.171+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">REST</category><category domain="http://www.blogger.com/atom/ns#">WCF</category><title>Creating REST web service using WCF</title><atom:summary type="text">During last two weeks, I was working on a niche area when I was given a task to create a REST service in .NET. Upon my initial exploration, I found that REST support is only provided by Framework 3.5. I found out that finding REST in WCF articles over the net was not easy as very few and obsure links are available.So here I'm publishing few links which will give you quick start if you want to </atom:summary><link>http://dotnetmind.blogspot.com/2008/07/creating-rest-web-service-using-wcf.html</link><author>noreply@blogger.com (MP Grewal)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-2403430606101974989.post-6222933148308828154</guid><pubDate>Sun, 08 Jun 2008 18:16:00 +0000</pubDate><atom:updated>2008-07-09T01:09:54.281+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">WPF</category><category domain="http://www.blogger.com/atom/ns#">XAML</category><category domain="http://www.blogger.com/atom/ns#">Silverlight</category><title>Essential XAML Simplified 1</title><atom:summary type="text">Today we'll touch the three most lauded concepts introduced by the XAML (eXtensible Application Markup Language). XAML to me seems like XML + .NET. By that I mean XAML provides you the best of both worlds by leveraging descriptive nature of XML and object-oriented nature of .NET. It allows you to instantiate a .NET object like WatermarkedTextbox and describe it properties using pure XML driven </atom:summary><link>http://dotnetmind.blogspot.com/2008/07/essential-xaml-simplified-1.html</link><author>noreply@blogger.com (MP Grewal)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-2403430606101974989.post-2928090025418076574</guid><pubDate>Sun, 01 Jun 2008 21:10:00 +0000</pubDate><atom:updated>2008-07-09T01:11:46.719+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">REST</category><title>Differences between SOAP and REST</title><atom:summary type="text">This article compares SOAP style web services with REST style web services. It highlights key business areas where REST scores over SOAP. The idea here is not to belittle SOAP which has been a strong pillar of distributed computing over the past decade but to bring its dark side to light.SOAPRESTSOAP clients call every SOAP operation on the server using only Http GETREST clients leverage true </atom:summary><link>http://dotnetmind.blogspot.com/2008/07/differences-between-soap-and-rest.html</link><author>noreply@blogger.com (MP Grewal)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></item></channel></rss>
