Karl Seguin - All Comments

re: 2 years ago I gave up on Silverlight

Houston Web design — Wed, 01 Jul 2009 04:21:24 GMT

I don't any developer who uses silverlight, its either flash or nothing.

re: NHibernate : Some Naked Thoughts

Fabio Maulo — Wed, 24 Jun 2009 23:43:18 GMT

Btw, friends, NH is a working reality but I'm pretty sure that EF will be the standard in .NET

Each time this matter rises what I say is always the same:

2 dogs and 3 or 4 cats, working on his free time can't do the same of a monster as Microsoft is.

#.think.in infoDose #34 (18th June - 24th June)

#.think.in — Wed, 24 Jun 2009 12:23:38 GMT

#.think.in infoDose #34 (18th June - 24th June)

re: NHibnerate : Handling the Special Cases

Martin — Sun, 21 Jun 2009 18:35:51 GMT

There's a typo in the title of the post: NHibnerate -> NHibernate

re: code better - use string.format

Matthew — Fri, 19 Jun 2009 18:17:31 GMT

By the way, String.Format does not have a monopoly on string formatting. You can also specify a format for a single object to its ToString() method. So, for instance, this:

string s = "0x" + 16.ToString("x");

accomplishes the same thing as:

string s = String.Format("0x{0:x}", 16);

re: code better - use string.format

Matthew — Fri, 19 Jun 2009 09:12:20 GMT

Really? You love String.Format that much? Put performance aside for a moment. I contest that readability is not improved by String.Format, even though I am a die-hard C programmer who used to love printf().

The problem with these substitution routines is that they separate the symbol from the variable. You're stuck seeing cryptic {0}, {1}, {2}, {3}, {4}, ... and then you only find out at the end of the statement which variables mean what. Order is critical. If you mess up that, then you can introduce some subtle bugs.

Really, I do think this:

Console.WriteLine(

"number: " + i.ToString() + "." +

"number + 1: " + (i + 1).ToString() + "." +

"number + 2: " + (i + 2).ToString() + "."

);

is more clear than this mess:

Console.WriteLine(

String.Format(

"number: {0}.number + 1: {1}.number + 2: {2}.",

i, i + 1, i + 2

)

);

NHibnerate : Handling the Special Cases - Karl Seguin - CodeBetter.Com

DotNetShoutout — Thu, 18 Jun 2009 20:27:32 GMT

Thank you for submitting this cool story - Trackback from DotNetShoutout

re: NHibnerate : Handling the Special Cases

karl — Thu, 18 Jun 2009 18:32:23 GMT

@Bill:

Because they rollback the transaction in the case of an exception, something you can't do with a using.

re: NHibnerate : Handling the Special Cases

Bill Sorensen — Thu, 18 Jun 2009 18:01:31 GMT

Why did they use a try..finally with the transaction rather than a using statement?

re: NHibnerate : Handling the Special Cases

karl — Thu, 18 Jun 2009 15:35:59 GMT

@Paco:

That repository snippet comes from FluentNhibernate. Seems to be flavor of the day in order to achieve really simple/small implementations for basic CRUD sites without having to write a lot of infrastructure. The approach definitely works for a number of use case, and not for others.

New and Notable 333

Sam Gentile's Blog (if (DeveloperTask == Communication && OS == Windows) — Thu, 18 Jun 2009 15:07:07 GMT

Visual Studio 2010/.NET 4 Visual Studio 2010 .net debugging resource Visual Studio 2010: Web application packaging and publishing WPF Data Binding: Lookup Tables Software Development Tools NHibernate: Handling the Special Cases TestDriven.Net 2.22: What

re: NHibnerate : Handling the Special Cases

Paco — Thu, 18 Jun 2009 15:02:23 GMT

Why do you manage the transaction in the repository? What if you need 2 queries on the same transaction?

NHibnerate : Handling the Special Cases

Karl Seguin — Thu, 18 Jun 2009 14:04:50 GMT

In my last NHibernate post I mentioned that NHibernate is great because it does the heavy lifting for

re: Get SOLID: Single Responsibility Principle

dfgd — Thu, 18 Jun 2009 10:43:02 GMT

dfg

re: Get SOLID: Single Responsibility Principle

ffghfgh — Thu, 18 Jun 2009 10:33:58 GMT

gfhfgh