Attention: We are retiring the ASP.NET Community Blogs. Learn more >

Frans Bouma's blog

The blog of Frans Bouma, creator and lead developer of LLBLGen Pro and ORM Profiler.

  • VS.NET 2003 C# code-editor tip of the day

    Three tips actually. All color coding related. Open VS.NET, click Tools - Options and then Environment - Fonts and Colors

    1. Under display items, browse down to Operator. Select 'Maroon' for foreground color and check 'Bold'.
    2. Under display items, browse down to String. Select 'Dark Blue' for foreground color.
    3. Under display items, browse down to Xml Doc Comment. Select 'Custom' for background color and select a very light grey, like RGB 245, 245, 245. Do this also for Xml Tag
    Hit OK. Your code will now be more readable, routines are more recognizable, operators are more recognizable.

  • SqlServer 2005 and VS.NET 2005 delayed

    From theserverside.net:

    Microsoft has decided to delay the release of SQL Server 2005 from the first half of 2005 until later in the summer of that year. A Community Technical Preview will be released as an interim beta with possibly more to come before the final beta and the product’s eventual release.

  • Solving the Data Access problem: to O/R map or not To O/R map

    On the www.asp.net forums (the architecture section), a person asked in the 'Your favorite O/R mapper' thread, why someone would use a 3rd party component for data-access and why would that be an O/R mapper and if so, which one? I've tried to answer these questions in that thread, but because I think it can be of benefit for more people than just the readers of that long forum thread, I've reworked the text into an article you'll find below. Keep in mind I've tried to keep things simple to understand, so perhaps I've left out a detail here and there, however I don't think these details will matter much to the overall conclusions and descriptions. As I've addressed a couple of questions, which I think are related to each other, I've re-written the forum response as a Q & A.

  • Major upgrade of LLBLGen Pro released!

    After 3 months of hard work, today, a major upgrade of one of the leading O/R mappers for .NET, LLBLGen Pro, has been released! . A large amount of new features are added to the new runtime libraries and templates, among them: MS Access 2000/XP/2003 support, prefetch paths, paging in entity collections and lists, aggregate function support and sql expression support and much more. Below is the full list of new things.

    This upgrade is of course free for our customers .

  • Killing a Yukon myth

    About once a week or so I get the question what the strategy will be with our O/R mapper LLBLGen Pro in relation with Yukon (SqlServer 2005): will the O/R mapping code run totally inside the database server or will it be running outside the database, like with SqlServer 2000. This is actually a question that I can imagine is puzzling a lot of developers, also the ones not using any O/R mapper at all: will we be able to run the DAL inside Yukon and with that benefit from the close connections between DAL code and database server, and how do we call this DAL?