http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660Or, "Our larger community can benefit from this set of technologies. There are OSS implementations but they dont integrate with our tools at a level where we can stand behind them. We don't want to invest in a specific OSS project and build such integration because that will get us too deeply tied to that project and its politics. We don't want to take over a project because *everyone* will look to us to fail. So, its safer and simpler to duplicate effort, build good integration with Visual Studio, publish guidance, and push this technology out to the mainstream." In other words, Microsoft is too big a target and has too much influence to get involved in an OSS project. Its safer and most likely cheaper to build their own. Not arguing with your assertions, just providing a likely answer to your "why?" http://ayende.com/3000/whose-time-effort#comment3http://ayende.com/3000/whose-time-effort#comment3Mon, 03 Dec 2007 19:12:36 GMTThey should definitely provide integration with existing solutions including open source. http://ayende.com/3000/whose-time-effort#comment2http://ayende.com/3000/whose-time-effort#comment2Mon, 03 Dec 2007 13:46:52 GMTI wonder if its more about attitudes. Oren, when you wrote RhinoMocks, (I'm guessing) your attitude was something along the lines of "I need a tool to help me to solve problem X. That tool and its functionality doesnt exist, therefore I must write it myself" Whereas Microsofts attitude doesnt seem to be like that. Its more like "How can we write something similar, and make it better?" or "If we implement this technique, we can capture the community" http://ayende.com/3000/whose-time-effort#comment1http://ayende.com/3000/whose-time-effort#comment1Mon, 03 Dec 2007 11:39:10 GMT