The Bolla Blog - All Comments

re: An ASP.NET site to add DVDs to your Netflix queue via your camera phone

yyIMSHAkspaTuJJ — Fri, 25 Sep 2009 19:22:11 GMT

doors.txt;3;9

re: Who is Jim Bolla?

Amy — Tue, 03 Mar 2009 15:47:24 GMT

Where do I find someone to help me put together a Medical Wikipedia? Can you help me with this?

Що ми чекаємо від C# 4.0?

Краковецький Олександр - персональний блог — Tue, 18 Nov 2008 11:07:29 GMT

Спробую підсумувати все, що мені вдалось знайти на тему "що ми чекаємо від C# 4.0". Отже, Feature

re: C# 4.0 Feature Request: "??=" the Lazy load operator...

boj — Mon, 10 Nov 2008 20:38:20 GMT

nice:)

Що ми чекаємо від C# 4.0?

Alex Krakovetskiy's blog — Fri, 24 Oct 2008 20:47:31 GMT

Спробую підсумувати все, що мені вдалось знайти на тему "що ми чекаємо від C# 4.0". Отже, Feature

NHibernate 2.0: Changes Overview - taccato! trend tracker, cool hunting, new business ideas

Fri, 05 Sep 2008 12:28:30 GMT

Pingback from NHibernate 2.0: Changes Overview - taccato! trend tracker, cool hunting, new business ideas

NHibernate 2.0: Changes Overview

Mirrored Blogs — Fri, 05 Sep 2008 04:42:11 GMT

My post .NET Framework 3.5 SP1: Changes Overview on analysis evolution, structure and quality of the

NHibernate 2.0: Changes Overview

Community Blogs — Tue, 26 Aug 2008 17:45:45 GMT

My post .NET Framework 3.5 SP1: Changes Overview on analysis evolution, structure and quality of the

NHibernate 2.0: Changes Overview - taccato! trend tracker, cool hunting, new business ideas

Tue, 26 Aug 2008 17:14:55 GMT

Pingback from NHibernate 2.0: Changes Overview - taccato! trend tracker, cool hunting, new business ideas

NHibernate 2.0: Changes Overview

Patrick Smacchia [MVP C#] — Tue, 26 Aug 2008 17:01:07 GMT

My post .NET Framework 3.5 SP1: Changes Overview on analysis evolution, structure and quality of the

View to Presenter Communication(转)

江南白衣 — Sat, 02 Aug 2008 11:41:38 GMT

Alright, I've purposely hid the View to Presenter communication in my previous posts on Supervising Controller and Passive View because I thought that subject was worthy of its own post. As I see it, there are 2 1/2 basic ways to communicate screen events

re: C# 4.0 Feature Request: "??=" the Lazy load operator...

AK — Sat, 12 Apr 2008 03:40:24 GMT

Dude we are already so close with C# , dont add FLUFF.

Add STUFF

return _MYSERVICECLASS ?? (_MYSERVICECLASS = new MyService());

public class MyService

{

public int Count()

{

return 10;

}

public partial class Form1 : Form

{

MyService _MYSERVICECLASS;

public Form1()

{

InitializeComponent();

}

private int GetCount()

{

return MYSERVICECLASS.Count();

}

private MyService MYSERVICECLASS

{

get

{

return _MYSERVICECLASS ?? (_MYSERVICECLASS = new MyService());

}

private void Form1_Load(object sender, EventArgs e)

{

MessageBox.Show(string.Format ("{0} count , service is null {1}",GetCount(),_MYSERVICECLASS==null ));

}

re: A Better Continuous Integration + Version Control System?

Sean Chambers — Sun, 06 Apr 2008 15:51:09 GMT

I feel the need to chime in here as well. Interesting ideas but like everyone else I think auto-commit is a very bad idea.

The last step of the TDD mantra is refactor. Therefore, if an auto-commit is happening every green step, then you never have an opportunity to refactor your tests/code to support the new test. In addition, I write 10-20 tests between commits because one commit from my workstation often includes a set of tests that test a specific portion of the project, but just a single test per commit.

Some of your ideas are great though, opening your IDE and it automatically getting the most current revision from SC is a good idea, maybe with an alert window in case you don't want the most recent revisions however.

re: A Better Continuous Integration + Version Control System?

Greg Young — Fri, 04 Apr 2008 21:57:04 GMT

While this sounds pretty good and reasonable you are asking your development environment to do the equivalent of realizing when you want a beer and walking over to the kitchen to bring you one.

btw: commit on tests pass only works if I write tests first ;-)

re: A Better Continuous Integration + Version Control System?

keith — Fri, 04 Apr 2008 18:21:18 GMT

"The other scenario is when Dev A and Dev B are editing the same block of code, which leads to merge conflicts. In this scenario "CIVCS" wound't be able to not automerge the changes but instead could indicate the merge conflict by putting a "merge confilct" icon in the gutter to the left of the relevant lines of code."

but then i'm forced to resolve the conflict _now_ instead of when i'm ready to (when my code is finished and ready, by my definition of ready, for integration)

disruption and context switches lower productivity substantially, on average.