Lately there has been some noise around the lack of documentation on the Castle project.
I have expressed my view on the matter on the mailing list, and in short I'd say that having an undocumented feature is way better than not having that feature at all.
During the ALT.NET UK conference, one of the guys approached me and said that he has solid background in technical documentation, and that he is willing to put some effort to that end.
I'm terrible with names, so I forgot his (sorry ...), but if it's you dear reader (or if it's not you, but you are willing to help with that) then please do contact me should you need any help in kicking it off.
Thanks a bunch,
Ken.
Given the following code:
public void UpdatePerson(int id, string name)
{
Person p = peopleRepository.Get(id);
p.name = name;
peopleRepository.Update(p);
}
One answer would be (using a pseudo mocking framework):
Person p = new Person(); Expect.Call(peopleRepository.Get(0))
.Returns(p);
Expect.Call(peopleRepository.Update(p));
...
service.UpdatePerson(0, "MyName");
Other approach would be (using pseudo coding again):
Person p = CreateAndInsertToDB();
service.UpdatePerson(p.id, "New Name");
FlushAndRecreateTheSession();
Person updated = GetFromDB(p.Id);
Assert.Equal("New Name", updated.Name);
What would you do, and why?
(I'm tagging that also under altnetuk as it has been inspired by a session around test-granularity, mocking frameworks, etc.)
This weekend I've had to pleasure to attend the altnetuk conf in London. This has been quite an amazing experience. I have really liked the way it has ben organized into open-spaces, and I just wish I could've split myself to four, so I'd be able to be at all of the sessions (the F# one was greatly missed ...)
I have met great people, have discussed exciting things, and had a lot of fun.
Most of the people referred to me as "the MonoRail guy" which was quite amusing, as I am only the creator of AspView (which in turn is a shameless idea-and-code ripoff from Brail), and I have very little to do with the actuall coolness and usefulness of MonoRail ... I do hope though that I did manage to address pepole concerns regarding MonoRail, and the Castle Project as a whole.
Interesting (however not surprising) moment:
On the panel dealing with MVC frameworks for ASP.NET, about 25 people were around the table. When people who are actually using MonoRail/ASP.NET MVC for commercial production environment, only 4 have raised their hands. however, all the others said that they wish the could have done that, and the only reason they do not, is the reluctance from their bosses/clients.
After being told that MonoRail would not make his dreams come true, Dylan Beattie have answered:
"MonoRail would not make my dreams come true. It would however, make my nightmares disappear"
Brilliant.
Last Thursday I was informed by the organizers of alt.net UK conference that they have managed to squeeze me in, so I immediatly booked a flight to London, and have attendet.
I was superb, and I've written a few posts, but since I was not online during the last few days I had no chance of publishing 'em. Hopefully they'll get during the next few days.
A lot have also been piling up on my MonoRail and AspView "desktops" so I appreciate the patience of the users, and I promise to do my best to keep up with the requests and patches being sent to me ...