<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Ivan N. Zlatev BLoG - Latest Comments in MSDN Search shows Mono results</title><link>http://ivanz.disqus.com/</link><description></description><language>en</language><lastBuildDate>Wed, 09 Jul 2008 22:05:35 -0000</lastBuildDate><item><title>Re: MSDN Search shows Mono results</title><link>http://i-nz.net/2008/07/09/msdn-search-shows-mono-results/#comment-848970</link><description>Hi Ivan - Yep, we had a publishing glitch yesterday.  We use a configuration file to define all the refinements and scopes used on MSDN Search. That file was updated yesterday but somehow a blank file got pushed out to two of our servers.&lt;br&gt;&lt;br&gt;With a blank file, we always search the entire Web. You might have also noticed that search refinements (e.g. the "Win32 &amp; COM Development" you'd normally see when searching for SetClipboardData) were also missing. &lt;br&gt;&lt;br&gt;Anyway, we fixed the problem a few hours ago and the default search scope, and refinements, are back to normal. Thanks for noticing and keeping us on our toes! :-)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Justin Grant</dc:creator><pubDate>Wed, 09 Jul 2008 22:05:35 -0000</pubDate></item><item><title>Re: MSDN Search shows Mono results</title><link>http://i-nz.net/2008/07/09/msdn-search-shows-mono-results/#comment-843105</link><description>I can guarantee you I did not use the "Search Entire Web". I never do. There's Google for that. I just tried it and it shows 12 results and the MSDN-only search no longer shows the 5 results in my screenshot. I guess this all was just a temporarily glitch.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ivanz</dc:creator><pubDate>Wed, 09 Jul 2008 11:23:42 -0000</pubDate></item><item><title>Re: MSDN Search shows Mono results</title><link>http://i-nz.net/2008/07/09/msdn-search-shows-mono-results/#comment-841532</link><description>Ivan,&lt;br&gt;      Yes, we support MS COM now so the DnD code could be rewritten. However, COM Interop does require runtime support. Theoretically, someone could compile a runtime without COM support (for size) and still expect Winforms to work. Although, this is less likely now that the WebBrowser uses COM extensively. If it makes life easier (and obviously is Windows only) I say go for it.&lt;br&gt;&lt;br&gt;- Jonathan</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jonathan Chambers</dc:creator><pubDate>Wed, 09 Jul 2008 03:11:58 -0000</pubDate></item><item><title>Re: MSDN Search shows Mono results</title><link>http://i-nz.net/2008/07/09/msdn-search-shows-mono-results/#comment-841489</link><description>You get these results only if you search the entire web (probably using live search) from msdn. If you search msdn only, no results whatsoever. See the drop down arrow button next to the search icon.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Cetin Sert</dc:creator><pubDate>Wed, 09 Jul 2008 03:06:17 -0000</pubDate></item></channel></rss>