Karl Seguin - All Comments

re: Resharper 4

Valued Customer — Mon, 13 Oct 2008 15:24:53 GMT

Anyone having a bad taste in their mouth from 4.0, definitely give the new 4.1 a try - the performance and stability have improved tremendously.

re: What's Up Doc

Manoj Waikar — Fri, 10 Oct 2008 15:52:56 GMT

Thanks Karl, that worked :)

And thanks for the "Foundations of Programming" e-book too, it had some real practical guidance.

Regards,

Manoj.

re: What's Up Doc

karl — Fri, 10 Oct 2008 01:09:03 GMT

Manoj:

Try checking out your the ItemCache, I think templates are cached there and that might be what you're saying. Not 100% sure though:

C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\ItemTemplatesCache

re: What's Up Doc

Manoj Waikar — Thu, 09 Oct 2008 16:44:56 GMT

Hi Karl,

It might be a dumb question, but I changed the Class.cs file in the Class.zip file, in the folder "C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\ItemTemplates\CSharp\Code\1033" folder to get a modified template, but it doesn't work.

When I add a new class, VS still generates the definition based on the old template. Any idea why?

Thanks and regards,

Manoj.

re: Password : You're doing it wrong

Laere — Thu, 09 Oct 2008 13:13:21 GMT

I know it's a little late, but banks are champions of absurd limitations.

In France, the LCL Bank has a rather strange policy on passwords:

they must be exactly 8 characters long, only number, but passwords which are valid dates are forbidden, as passwords which contains twice the same number.

yes, 12345678 is a valid password

but 15331456 is not.

I never found such an awful password policy.

NHibernate Collections - Dschungelcamp für Einsteiger

Rainer Schuster — Tue, 07 Oct 2008 16:16:24 GMT

Ich beschäftige mich ja jetzt schon seit zwei bis drei Wochen mit NHibernate, aber über die Verwendung

links for 2008-09-29 | the markfr ditherings

links for 2008-09-29 | the markfr ditherings — Tue, 30 Sep 2008 01:04:44 GMT

Pingback from links for 2008-09-29 | the markfr ditherings

Reflective Perspective - Chris Alcock » The Morning Brew # 189

Reflective Perspective - Chris Alcock » The Morning Brew # 189 — Mon, 29 Sep 2008 07:11:25 GMT

Pingback from Reflective Perspective - Chris Alcock » The Morning Brew # 189

2008 September 29 - Links for today « My (almost) Daily Links

2008 September 29 - Links for today « My (almost) Daily Links — Mon, 29 Sep 2008 06:52:39 GMT

Pingback from 2008 September 29 - Links for today « My (almost) Daily Links

Arjan`s World » LINKBLOG for September 27, 2008

Arjan`s World » LINKBLOG for September 27, 2008 — Sat, 27 Sep 2008 21:07:51 GMT

Pingback from Arjan`s World » LINKBLOG for September 27, 2008

Dew Drop - September 27, 2008 | Alvin Ashcraft's Morning Dew

Dew Drop - September 27, 2008 | Alvin Ashcraft's Morning Dew — Sat, 27 Sep 2008 11:57:36 GMT

Pingback from Dew Drop - September 27, 2008 | Alvin Ashcraft's Morning Dew

re: Password : You're doing it wrong

sisakat — Sat, 27 Sep 2008 05:53:11 GMT

I just signed up for my bank's online thing, and I have to use a pin that is a four to ten digit number. Now that I've read this I'm bothered that the place I expect to store my money safely is doing such a shody job of it. I think I'll bug them about it.

re: Simplicity is key to successful unit testing

Jeremy D. Miller — Fri, 26 Sep 2008 17:24:42 GMT

The "ShouldEqual(xxx)" and ShouldBeTheSameAs(xxx) extension methods from SpecUnit help make unit tests simpler and easier to read as well.

For what you're doing in your BaseFixture, you might just use the RhinoAutoMocker<CLASSUNDERTEST> class in StructureMap, but it does assume that you're using DI for the CLASSUNDERTEST

re: Simplicity is key to successful unit testing

karl — Fri, 26 Sep 2008 16:43:37 GMT

@Ryan:

Good question. I left those details out on purpose for simplicity. In the last 2 examples (the controller code) I probably should have renamed repository to _repository so that it's a bit more clear its being loaded externally to the method (possibly through injection). In real life, I'd probably do:

XXXRepository.CreateInstance() which would call out to StructureMap (perhaps through additional abstractions).

As for the unit test, I use a BaseFixture class that has methods like:

protected T Dynamic<T>()

{

var mock = Mocks.DynamicMock<T>();

if (typeof(T).IsInterface)

{

ObjectFactory.InjectStub(typeof (T), mock);

}

return mock;

}

re: Simplicity is key to successful unit testing

Kevin Gao — Fri, 26 Sep 2008 15:40:03 GMT

Good examples. Granularity is important for unit test cases. Or else, your cases are too easy to be broken.