Social Bookmarking Platform Released

Earlier this year, I pointed you to a preview of a social bookmarking application.  This week we released v 1.0 of social bookmarking for MSDN, TechNet, and Expression enabling technical professionals to easily share their web favorites, find and connect with each other, and publish community-generated content directly to these sites.

This new version of the bookmarking application includes several new capabilities including the ability to subscribe to people and tags, support for 12 different languages, import tools from other bookmarking services you might already use, and new and improved design.

The new social platform release will also preview MSDN Code Search that has specialized features for finding code on various Microsoft sites including the MSDN Library by extending MSDN search.  In the future releases this will expand to cover MSDN Code Gallery, MSDN Forums, and more. For more details on MSDN Code Search including tips for how to search for code, see Rob Veliz's blog.

For more details on these features, check out Chris Slemp and Taylor Parsons’s blogs.


Comments (21)

  1. Some great information, feedback, and reviews of the new Social Bookmarking application for MSDN, TechNet,

  2. Mesan says:

    Why in the world do you have advertisements on your blog???  Doesn’t MS pay you enough?  Sheesh – I can understand ads on some loner geek’s site, but a Senior VP’s???

    Lose the ads, gain some credibility.

  3. Publicación del inglés original : Jueves, 11 de septiembre de 2008 10:33 AM PST por Somasegar En junio

  4. Steve says:


     A lot of bloggers use ads to support charities or other causes they support.  Don’t be so quick to assume Soma is pocketing the money, and even if he is, it’s not costing you anything, it is?

  5. mark gordon says:

    Hey Soma,

    Since you killed Visual FoxPro and Visual Basic why don’t you first try bringing visual studio up to VFP and VB standards before introducing more nonsense technology and calling Visual Studio a rapid application development tool….

    Case and point foxpro has a cool command called "copy to" and you pass in an argument the type of file you want to create excel, text file etc and it generate the files in approximately 3 lines of code. In .BLOAT best case about 50 lines of c# code to pull off the same trick… So please remind me again how VS in better ?

    I’m completely amazed as bloated the .NET framework is why you could not add a namepsace/class to export a dataset to an excel file? Why don’t you quit calling .NET a framework and instead call it api wrappers which is really what this bloated .NET mess is.

    Better yet continue developing the Visual Basic and Visual Foxpro true RAD tools so developers can be productive again . . .

    All my best


  6. Green says:

    Hey Mark,

               I have even a better ideal. How about your stop whinning like a politician trying to win the presidency and try to understand .NET better. They do what they do for good reasons. For example, forbiddening  multiple inheritance with classes stops the diamond problem (and thus, prevent developers badly hurting themselves due to it)- at the way lesser expense of developer having to work with interfaces for multiple inheritance. Understand principles like this prior to crying in a commentary and saying ".BLOAT". Use your brain other than for hogging oxygen and previewing porn.    

  7. Nikolay Raychev on SL and Localization, Chris Koenig on Style, WPF and SL, with developer

  8. Mark Gordon says:


    There are over 70,000 classes "api wrappers" in .NET how can any single developer grasp that amount of bloat. Being in the field and looking at .NET applications programmers are producing they are not getting it. Most application I have to straighten out are maintenance nightmares.

    Given there are 70k "api wrappers" it is amazing to me a common control like a textbox or masked textbox isn’t fully implemented. For example the control doesn’t handle currency data types properly amongst other things lacks "complete" support for all SQL Server data types. That is inexcusable.  

    Visual Studio also has stability issues, an application will compile and run just fine but the form designer will crash with Object reference not set to an instance of an object. This seems to occur when inheriting a base class that uses reflection and or generics.

    The entire issue is Microsoft had 2 technologies that worked VB and VFP, they were mature stable products. Msft stopped development on the tools and FORCED developers into Visual Studio and .NET which offers zero benefit and comes with increase cost to my customers just in terms of licensing SQL alone.  Then Soma in an interview insults the VB community by stating, VB developers are mad because we don’t want to learn a new technology. That is so not the case, we just want a technology that works and where the benefits of making the migration outweigh the learning curve. If Visual Studio was a great tool, VB developers would have crossed over and VB would have died a natural death due to lack of interest like so many other languages have. Since that didn’t happen MSFT had to issue a VB END OF LIFE to gain acceptance of the VS/.NET platform.

    It is real simple for "new" programmers that have only used VS to rave how great Visual Studio is when they have nothing to compare it to … I started programming on  decwriters and learned assembler on a pdp-11, I been around a long time and used a lot of different languages and development tools set. Visual Studio, while it has potential to be a great tool … Is far from the RAD tools Microsoft and their cheerleadering squad claim it to be and instead of fixing it Microsoft rather release more technology on an unstable foundation.

  9. Google Chrome no respeta mucho la privacidad de los usuarios : En fin, espero que saquen versiones modificadas

  10. For all the bloggers out there, you may like to use this plug-in for Windows Live writer which supports these extra add-ons.



  11. Sameer says:

    Hey Mark,

    Its been almost an hour still I am not able to stop laughing reading your comments. What do you mean by api wrappers, how do these wrappers works , Do me a favour, read some stuff in MSDN about .Net you will get better picture , how boring and how stuipid Visual Foxpro and VB were. I worked on both of them they had made robots of me without brains. I planned to shift to java to get some brain excercise but then .Net came and since then i am busy working in .Net. VB is for braindead oldies better get on your toes and start reading about .Net

  12. Nexus says:


    rest i agree with you. Compared to Java which was designed way back before microsoft even thought about C# its too ustable too much bloated and too much of talk and shout just like there CEO steve balmer(ja ja binks of star wars)..hahaha I think what should .Net focus on deployment issues, memory management and be content with the hardware they have rather asking for more all the time..

  13. Jalf says:

    Oh great, so *this* is why all my bookmarks on MSDN suddenly require me to log in? Thanks a lot, that is so much more useful. There’s nothing like launching your browser (which remembers the tabs I had open before), and then having to log in on 8 different browser tabs because I can see the documentation I actually wanted to look at earlier.

    That really makes developers feel welcome. I really get the sense that you *want* developers to see your documentation so they can write well-behaved Windows applications…. Or not.

  14. Good to see that there are humans out there with the same experiences I have had with .NET. Somehow, the easiest platform for deployment of database driven applications remains MS Access. One can write a fairly big MS Access application in under a week, but you wonder where the benefits in .NET really are.

    But, nevertheless, I am working on my C# now.

  15. Mark Gordon says:


    If you want  brain excerise I will give you something to work on.

    1) Learn C++ and assembler, which is where I started and this will give you exposure to dll files.

    2) Then do your research and find out what the windows api is after doing so my comment about api wrappers will make some sense to you. If not let me know and I will explain it.

    3) Learn the definition of a framework then compare the true defintion of a framework to .NET  doing so will expose the truth that .NET doesn’t meet the criteria.

    4) Study the C++ inheritance model then analyze inheritance in Visual studio and visual foxpro.  What you will learn is the FoxPro oop inheritance model is closer to c++ then Visual Studio.  On a side note if you like symbolism over substance then the VS class diagrams win hands down compared  to the vfp class browser. The only negative about the vs class browser is it doesn’t really work and lacks  support for UI controls. Given you know VFP then you are aware of this limitation since the VFP class browser actually works!

    5) Study n-tier programming and look at the Visual studio webforms implementation you will quickly discover webforms lacks seperation between layers – ui, controller, data. Which is why  Microsoft was forced to develop MVC. It is their attempt to follow N-TIER standards along with trying to keep up with ruby unforunately MVC, despite all the delays, is far from ready for production use.

    6) If you are really bored learn how object oriented ui containership works and ui control inheritance. It kinda sorta almost follows oop standards in vs and with enough work arounds you kind of can get it working enough to use it in an application.  Funny part is this worked in VFP correctly…

    7) Here is a real simple one create a form in vfp and drop a textbox on it then set the input mask and format properities to handle a  numeric datatype then try the same trick with winforms let know the amount of lines of code required in winforms compared to vfp. Then using the same form try databinding the control to a table let me know the lines of code and number of classes to pull that off between the two packages.

    Most programmers build frameworks to save time to avoid redundent coding by your own definition .NET is brain exercise isn’t that a contradiction? I suppose if you consider working with poorly designed unstable bloated technology and researching workarounds (Just look at gu’s blog)

    along with writing lots of code in visual studio (then wasn’t needed in vfp or vb) brain exercise then Visual studio is the product for you.  Most professional programmers are concerned about creating software that meets the clients needs and using completed stable development

    tools instead of playing. I suppose that is the difference between hobbiest/cheerleaders and professionals.

    After completing the steps above and you are able to convince us you have a clue what you are talking about then comment about visual studio and visual basic/visual foxpro instead of just sounding like a microsoft cheerleader trying to suck up to soma to get a mvp award.

    As long as poeple like you keep hyping visual studio instead of pointing out the flaws Microsoft has no incentive to release software that works.

    Microsoft new ad campaign is Life without walls. I cant wait for the day to come "Life without .NET" so developers can be productive again.

  16. Mark Gordon says:

    To those that supported my posts. I thank you. Since microsoft ignored the thousands of VB developers including mvps that signed the vb petition and took offense to soma’s comments about the VB community this is the only avenue left to be heard.

    People that make a living developing software don’t need 50 ways to do a task. (Linq falls into this category) we just need one way that works consistently. I dont write code to exercise my brain this is how I make my living.

    I will say this about soma’s blog and give credit were credit is due. While Soma remains completely silent about vfp and vb at least 90% of the comments will get posted positive or negative which is better then I can say for scott gu’s blog or most other Microsoft cheerleader.

    Thanks again everyone.


  17. [原文地址] Social Bookmarking Platform Released [原文发表时间] Thursday, September 11, 2008 10:33 AM 社交书签平台发布!

  18. Dale says:

    Pure childishness.  I’m not a 13-year old wannabe developer looking for a technical MySpace.  I am a professional developer with many years experience.

    What I want from MSDN, and truly miss from what MSDN was just a year or so ago, is simple:  Give me documentation and support/training for the professional development products that I have paid professional prices for.  

    Microsoft Developer group is losing touch with their mission.  Developer sites are amateurish, difficult to navigate, a lot of missing information and broken links,  cool gadget-or-fad-of-the-week websites, required tools for using documentation farmed out to community sites…  

    What a mess.

  19. Jack says:

    I don’t get the point of this. Why is this required? What value does this add over other Social bookmarking sites out there? To begin with Social bookmarking on MSDN looks like something that was rushed. There are many good sites out there like Digg, Delicious, DotNetKicks etc. It will be very easy for anyone to see why MSDN Social Bookmarking is a abysmal job.

    The more I look at Microsoft these days, the more confused they appear. You’ve got a Live platform and this clearly belongs in the Live bundle of products.

  20. Bruce says:

    OK, signed up and tried to find some value to this… Went to the WPF forum because I’ve been looking at it, the first first entry a "sticky" was for some controls I need to buy from a partner to get something of value.  No peer support but a venue for selling…typical Microsoft.

  21. Good to see that there are humans out there with the same experiences I have had with .NET. Somehow, the easiest platform for deployment of database driven applications remains MS Access. One can write a fairly big MS Access application in under a week, but you wonder where the benefits in .NET really are.

Skip to main content