Re: VS 2005 Pro and Unit Tests etc.

Tech-Archive recommends: Fix windows errors by optimizing your registry

Why? I am not sure, but I believe MS is focusing those tools on the
Enterprise space. A great deal of R&D money went into the Suite and they are
trying to recoup. IMO, it is no different than Intel initially
"overcharging" for a new chip or nVidia for a new graphics chip.

Will the tools filter down over time? I don't know, but I would guess they
would have to, as ISVs will eventually provide them for the lower SKUs of
the 2005 product and become competition in one sphere.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***********************************************
Think Outside the Box!
***********************************************
<peter.moss@xxxxxxxxx> wrote in message
news:1132670098.975460.264260@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Can anyone explain to me MS's strategy behind the unit test/code
> coverage, analysis etc. tools?
>
> All MS has done is blatantly stolen a set of best practices and a set
> of corresponding products that have been available in the community for
> about 5+ years (in Java as well). MS has NO intellectual property on
> these concepts and have only just started adopting them.
>
> I did feel it a very good thing when MS picked up the TDD best
> practices etc. (though they'd be fools not to) though I was
> disappointed they didn't just work closely with the NAnt, NUnit, NCover
> etc. guys to integreate (in a similar fashion to Sun and IBM sponsored
> community developments).
>
> However, for the life of me, I cannot understand why MS's versions of
> these tools are only avaible with Team System - the most expensive
> product. What are MS playing at? How can their versions of free
> products be only available at the top end? It's like making Media
> Player (their answer to Winamp etc.) or IE (FireFox) available only
> with Windows 2003 Enterprise Server.
>


.