Comments for Bernds blog http://rickenberg.dk/blog A .NET SharePoint Developer Blog Tue, 09 Mar 2010 18:47:07 +0000 http://wordpress.org/?v=2.8.6 hourly 1 Comment on DataContext.Connection.ConnectionString – No Password by Dean Ferreyra http://rickenberg.dk/blog/?p=122&cpage=1#comment-5355 Dean Ferreyra Tue, 09 Mar 2010 18:47:07 +0000 http://rickenberg.dk/blog/?p=122#comment-5355 I noticed that DataContext.Connection.ConnectionString *does* seem to preserve the password until you actually use the DataContext to access the database. One workaround I'm using is to squirrel away DataContext.Connection.ConnectionString in the OnCreate() while it still includes the password. Thanks for your blog entry! I noticed that DataContext.Connection.ConnectionString *does* seem to preserve the password until you actually use the DataContext to access the database. One workaround I’m using is to squirrel away DataContext.Connection.ConnectionString in the OnCreate() while it still includes the password.

Thanks for your blog entry!

]]> Comment on Run MSTests without Visual Studio 2008 by Bernd http://rickenberg.dk/blog/?p=130&cpage=1#comment-425 Bernd Fri, 11 Sep 2009 10:38:55 +0000 http://rickenberg.dk/blog/?p=130#comment-425 Hi Ronnie, I have always been working with NUnit and loved it. But Microsofts Team Foundation Server has only full support for MSTest. Like if you want to have unit test statistics in the TFS report you must use MSTest. Another advantage could be that you can use your MSTests for load testing and it is very easy to create data-driven tests. Kr., Bernd. Hi Ronnie,

I have always been working with NUnit and loved it. But Microsofts Team Foundation Server has only full support for MSTest. Like if you want to have unit test statistics in the TFS report you must use MSTest. Another advantage could be that you can use your MSTests for load testing and it is very easy to create data-driven tests.

Kr., Bernd.

]]> Comment on Run MSTests without Visual Studio 2008 by Ronnie Holm http://rickenberg.dk/blog/?p=130&cpage=1#comment-343 Ronnie Holm Thu, 03 Sep 2009 05:45:31 +0000 http://rickenberg.dk/blog/?p=130#comment-343 I'm curious as to why you chose MSTest to start with. Besides the fact that it comes baked into Visual Studio, I can't think of any reason for using MSTest over NUnit. Its user interface is bad compared to NUnit, its start-up time is significantly higher than NUnit, and, yes, it takes dependency on Visual Studio. I’m curious as to why you chose MSTest to start with. Besides the fact that it comes baked into Visual Studio, I can’t think of any reason for using MSTest over NUnit. Its user interface is bad compared to NUnit, its start-up time is significantly higher than NUnit, and, yes, it takes dependency on Visual Studio.

]]>