-
as seen on Geeks with Blogs
- Search for 'Geeks with Blogs'
DRY (Don't Repeat Yourself) is a basic software design and coding principle.
But there is just no silver bullet. While DRY should increase maintainability by avoiding common design mistakes, it could lead to huge maintenance problems when misunderstood.
The root of the problem is most probably…
>>> More
-
as seen on Stack Overflow
- Search for 'Stack Overflow'
Hi All,
I'm trying to figure out how I can define validation rules for my domain objects in one single location within my application but have run in to a snag...
Some background: My location has several parts:
- Database
- DAL
- Business Logic Layer
- SOAP API Layer
- MVC website
The MVC website…
>>> More
-
as seen on Stack Overflow
- Search for 'Stack Overflow'
I periodically ponder how to best design an application whose every business rule exists in just a single location. (While I know there is no proverbial “best way” and that designs are situational, people must have a leaning toward one practice or another.) I work for a shop where they prefer to…
>>> More
-
as seen on Stack Overflow
- Search for 'Stack Overflow'
Hy,
I have a layout in the views/layout that has 2 cols and then in every view i have content_for :main_col and content_for :side_col. The problem is that i have more than 5 views with the same content in the content_for :side_col
You have a better idea on how to do this?thanks
>>> More
-
as seen on Stack Overflow
- Search for 'Stack Overflow'
This question was inspired by my struggles with ASP.NET MVC, but I think it applies to other situations as well.
Let's say I have an ORM-generated Model and two ViewModels (one for a "details" view and one for an "edit" view):
Model
public class FooModel // ORM generated
{
public int Id { get;…
>>> More
