tag:blogger.com,1999:blog-107486965713406362.post1301176989787335689..comments2023-04-02T09:54:30.093-05:00Comments on The DotNetDude Blog: .NET Testing FrameworksGaines Kergosienhttp://www.blogger.com/profile/08688616646232978891noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-107486965713406362.post-49045192838138326092015-06-02T21:03:47.189-05:002015-06-02T21:03:47.189-05:00This comment has been removed by the author.Sharda Hinkelhttps://www.blogger.com/profile/03049412878821578827noreply@blogger.comtag:blogger.com,1999:blog-107486965713406362.post-16080193153684076042012-09-19T09:45:02.011-05:002012-09-19T09:45:02.011-05:00Hey, Gaines. I used NUnit for years, but recently...Hey, Gaines. I used NUnit for years, but recently, I've been gravitating to MSTest for the reason you list above. Everything just works natively inside of Visual Studio. Don't have to install any plugins, setup custom short cuts, etc. Of course, I kinda think it stinks that MSTest isn't included in the express suite of MS development tools. If I didn't have VS pro, I would be back to NUnit. Marvinhttps://www.blogger.com/profile/01495563607954261958noreply@blogger.com