Stuart Laughlin's Library tagged no_tag →  View Popular

feature-rich

LXR (formerly "the Linux Cross Referencer") is a software toolset for indexing and presenting source code repositories.

I figured out to 1) get Log4Net configured for a console app and 2) get it to write all entries to a log file and console and write just errors to the Event log on the server.

When may one legitimately copy a page from a book or a photograph of a person or a recording of a song? What ethical principles come to bear on these questions? These questions have grown in importance, and will continue to grow in importance, because the amount of available information is growing, and the ease of copying is growing.

The answers may be surprising. I would ask you to bear with me as I try to think carefully about principles of right and wrong.

I run FreeBSD on my computers. A lot of my friends run Linux, or at least one of the distributions of it. Naturally, then, we agree that a Unix-style operating system is the right choice, but we disagree on which to use.

It's been my impression that the BSD communit{y,ies}, in general, understand Linux far better than the Linux communit{y,ies} understand BSD. I have a few theories on why that is, but that's not really relevant. I think a lot of Linux people get turned off BSD because they don't really understand how and why it's put together. Thus, this rant; as a BSD person, I want to try to explain how BSD works in a way that Linux people can absorb.

While there's overwhelming similarity between the operating systems in most cases, there are also a lot of differences. As you probe more into the differences, you find that they emerge from deep-seated disagreements. Some are disagreements over development methodology, some over deployment and usage, some about what's important, some about who's important, and some about which flavor of ice cream is superior. Just comparing the surface differences doesn't tell you anything; it's the deeper differences that both explain and justify why each group does things the way they do.

StoryVerse is a web-based application for agile project management for software development projects.

This page, and the pages it links to, contain text of the Common Lisp book Practical Common Lisp published by Apress These pages now contain the final text as it appears in the book. If you find errors in these pages, please send email to book@gigamonkeys.com. These pages will remain online in perpetuity—I hope they will serve as a useful introduction to Common Lisp for folks who are curious about Lisp but maybe not yet curious enough to shell out big bucks for a dead-tree book. However, don't let that stop you from buying the printed version available from Apress at your favorite local or online bookseller. For the complete bookstore browsing experience, you can read the letter to the reader that appears on the back cover of the treeware edition of the book.

Domain Driven Design - Table of contents and source code

Introduction

I promised you the source code for both the 'Building your own ORM' and 'Domain Driven Design' series, besides the source code I believe a table of contents with links to all the different articles would serve you as well.

Downloads

The framework source code.
The example implementation.

Domain Driven Design introdcution

Not a pattern, a lifestyle
The path to enlightment
Entities, identity matters
Maintain model integrity with value objects and aggregates
Managing the object lifecycle

Building your own ORM

Introduction
Identity Map
Snapshot
Proxy
Unit of work
Query object
Data mapper
Repository

Full example

A Full example Part I
A Full example Part II
A Full example Part III

Related design patterns

Strategy
Decorator

The example code is depending on the presence of a database, I've included the script to generate the schema as well, but you still have to run the script and adjust the application configuration files to match your environment.

Remember that the source code comes with no warranty what so ever, but if you have questions or suggestions just send me a message ... enjoy the code

Microsoft OLEDB Provider for DB2

The Microsoft OLE DB Provider for DB2 is a COM component for integrating vital data stored in IBM DB2 databases with new solutions based on Microsoft SQL Server 2005 Enterprise Edition and Developer Edition. SQL Server developers and administrators can use the provider with Integration Services, Analysis Services, Replication, Reporting Services, and Distributed Query Processor. Run the self-extracting download package to create an installation folder. The single setup program will install the provider and tools on x86, x64, and IA64 computers. The package includes product updates in the form of an integrated Service Pack 1. Read the installation guide and Readme for more information.

Microsoft SQL Server 2005 Command Line Query Utility

The SQLCMD utility allows users to connect, send Transact-SQL batches, and output rowset information from SQL Server 7.0, SQL Server 2000, and SQL Server 2005 instances. SQLCMD is a replacement for ISQL and OSQL, but can coexist with installations that have ISQL or OSQL installed.

Note: Microsoft SQL Server 2005 Command Line Query Utility requires Microsoft SQL Server Native Client, also available on this page.

The SQL Server 2005 Best Practices Analyzer (BPA) gathers data from Microsoft Windows and SQL Server configuration settings. BPA uses a predefined list of SQL Server 2005 recommendations and best practices to determine if there are potential issues in the database environment.

One of the greatest features of the Linux® operating system is its networking stack. It was initially a derivative of the BSD stack and is well organized with a clean set of interfaces. Its interfaces range from the protocol agnostics, such as the common sockets layer interface or the device layer, to the specific interfaces of the individual networking protocols. This article explores the structure of the Linux networking stack from the perspective of its layers and also examines some of its major structures.

Windsor is the Inversion of Control (IoC) container piece of the Castle Project, the same guys that bring you MonoRail. In the short, IoC containers act as a holding structure for the components of your application allowing you to easily decouple them from one another. This gives you the flexibility to refactor as necessary, replace live implementations of objects with mocked ones, and basically do whatever is necessary to get your system running well in the shortest amount of time. Although we'll be talking about Windsor exclusively, you may want to check out other .Net IoC containers such as Spring.NET or Jeremy Miller's StructureMap.

SLIME is a new Emacs mode for Common Lisp development. Inspired by existing systems such Emacs Lisp and ILISP, we are working to create a fresh new environment for hacking Common Lisp in.

This frugal page is an invitation to learn more about what's going on.

O’Reilly just published Beautiful Code. I was invited to contribute, but I just could not go along with the premise. I disagree that beauty is a guiding principle of programming. Here is how I responded.