MSDN Search shows Mono results

  • Today I accidentaly MSDN searched for Win32SetClipboardData (our P/Invoke method name in Mono WinForms) instead of SetClipboardData and guess what… I ended up with 5 Mono results in front of me. I found it amusing considering the fact that this was MSDN Search after all. A screenshot in case they “fix” it. (Click bottom-left “Full Size” after the pop-up shows)

MSDN Search shows Mono results

  • You might think I have a lot of tabs opened in Firefox, but I should mention that I closed twice more prior to taking the screenshot. BTW, thank you, Tab Mix Plus guys, for the multi-line tab bar.
  • Holy cow! GNOME’s Nautilus with tabs (still looks butt ugly, but oh well)…
  • Fixed my last Mono WinForms regression caused by my recent parented forms fixes.
  • Have been poking Mono WinForms Clipboard code all day trying to get my head around it and see how it would be best to implement custom formats support. On X11 I can implement that reasonably “easy” with some minor XPlatUI API change and some extra cases to binary serialize/deserialize the clipboard, which will surely involve some trickery. For Win32 the one important question, which probably Jonathan Chambers can answer best (he worked/works on our COM support), is whether we support MS COM. It seems when Win32 DnD support was written that wasn’t the case, so if you want to see some impressive code that does COM without actually doing COM (yes, you heard me) take a look at our Win32DnD.cs.
  • I felt loved today. Last week I received a Mono T-Shirt and stuffed mono monkey (thanks Jonathan), an openSUSE 11 box (thanks openSUSE guys for valuing my quite small contribution of filing bugs) and today I almost got another UPS package. I am saying almost, because I missed the delivery. I am wondering what’s it going to be. I haven’t ordered anything and I have a very pure guess that it might be an openSUSE T-Shirt. Can’t wait to see what it is and then make a photo session of all my new stuff, hehe.
  • I promised my girlfriend I will be running with her tomorrow bright and early morning. Holy spaghetti monster, please help me.
  • Twitter
  • Facebook
  • FriendFeed
  • StumbleUpon
  • Digg
  • del.icio.us
  • Google Bookmarks
  • Reddit
  • Tumblr
  • PDF
  • Print
  • email
Rating: (1 votes, average: 3.00 out of 5)
Loading ... Loading ...
Comments
Published: Jul 9th, 2008 (Views: 77)
Categories: Coding
Tags:
  • 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.

    With a blank file, we always search the entire Web. You might have also noticed that search refinements (e.g. the "Win32 & COM Development" you'd normally see when searching for SetClipboardData) were also missing.

    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! :-)
  • Ivan,
    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.

    - Jonathan
  • 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.
  • 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.
blog comments powered by Disqus