You searched for the word(s): userid:662461

More Search Options

RSS Available

• Validation on Nullable<T> types

  Good day. Having the following: [NotNullValidator(MessageTemplate = "ExpectedOnMissing")] [DateTimeRangeValidator("2009-01-01T00:00:00", RangeBoundaryType.Inclusive, "", RangeBoundaryType.Ignore, MessageTemplate = "ExpectedOnFormat")] public DateTime? ExpectedOn { get; set; } I am having the following behavior: if I input a valid datetime, validation passes; if I input a valid datetime outside the boundaries, validation returns the format error if I input an

  Posted to Microsoft Application Blocks (Forum) by Sgro on 11/16/2009

• DefaultModelBinder, working with sub properties

  Hi everyone. Considering this simple ViewData mode: public class ViewDataUser { public User User {get,set;} public int OtherStuffINeed {get;set;} } And setting my view of type <ViewDataUser>.. I am rendering my form input names like: name="User.Username", name="User.Password", etc The defaultmodelbinder, however, doesn't pick them up. When debugging, my ViewDataUserInstance.User is null. So I can't really understand how the defaultmodelbinder works with sub properties

  Posted to ASP.NET MVC (Forum) by Sgro on 11/12/2009

• Re: N-Layer architecture and Validation

  Well Scott, that's exactly how I am doing it, and what I am trying to have my co-worker understand. I DO have validation in the business layer, and intend to call it from the various application layers.

  Posted to Architecture (Forum) by Sgro on 11/6/2009

• Re: Reduce Page size in Asp.net

  That's right, I pointed to MVC without explaining the whole thing behind it. But when I usually do, a flame begins on these forums, so I thought this time to just point the direction, and let the reader discover what needs to be learned in order to use MVC. To make it quick, you can see webforms as "web for dummies" where no real web knowledge is needed to get a web application up and running, because the framework does all the "web" stuff for you (and does it pretty bad in

  Posted to Architecture (Forum) by Sgro on 11/6/2009

• Re: N-Layer architecture and Validation

  That's an interesting point of view indeed. But does it still hold true when our application has multiple application layers? I mean, we're going to develop a winforms interface, a mobile interface and a web interface. Doesn't using control integrated validation create some sync problems? I mean, If I change some validation rules, I have to go manually change them in every application layer, with the risk of forgetting something and having different validation on the same object/property

  Posted to Architecture (Forum) by Sgro on 11/5/2009

• Re: GUID vs STRING

  I had a similar need recently, but since my data layer was coded with Entity Framework, I just had to switch EF provider and make some minor tweaks to the db structure (for instance, sql GUIDS are recognized as varchar(36) on mysql). So my data layer hasn't changed a bit. Maybe try and take a look to Entity Framework. The mysql provider is available as part of MySql Connector.NET

  Posted to Architecture (Forum) by Sgro on 11/5/2009

• Re: Reduce Page size in Asp.net

  A little list of tips, in order of importance: Move to Asp.net MVC - drop the bloating webforms paradigm. Code proper (x)html using the correct tags for your need (i.e. don't use tables for layout, etc). You'll find yourself with much lighter and cleaner page structure Load all decorative images through css - only content images with img tags Don't use inline style - always put all styling rules in CSS files. Don't use inline JS - always put JS code in JS files. Minify your JS files

  Posted to Architecture (Forum) by Sgro on 11/5/2009

• Re: Linq - A design Question

  The first thing you should think of is, the relationships between tables. If two tables are linked to each other by a foreign key, they must stay within the same data context. If you do otherwise, the two classes representing the tables will have no navigation properties to each other, so you lose the relatiionship in your code. If you can, for instance, isolate two (ore more) blocks of tables, where none of the tables in block "A" has any relation to any table of the block "B"

  Posted to Architecture (Forum) by Sgro on 11/4/2009

• Re: n-tier architecture: Coding the Common Layer using Data Transfer Objects,

  I can tell you my experience. I always work with this pattern: Common layer: contains the POCO classes (or DTO in your case) and the interfaces shared between layers Application Layer: consumes the common layer and the business layer, and provides a user interface to interact with the user Business Layer: consumes the common layer, and implements business logic and validation Data Layer: consumes the common layer, and implements logic to talk to the data store The common layer will contain everything

  Posted to Architecture (Forum) by Sgro on 11/3/2009

• N-Layer architecture and Validation

  Good day. I am currently designin the architecture for a new, rather large application. I am making it N-Layered with late-binding approach for plugins, dependency injection for data layer and so on. The architecture could be summarized in DataBase -> DataLayer(s) -> Business Layer -> Application Layer(s) ------ All using a Common layer containing POCO classes, Facade interfaces and so on. For business entity validation (POCO objects) I am using Microsoft Application Blocks. A co-worker

  Posted to Architecture (Forum) by Sgro on 11/3/2009