Enforcing Database Constraints In Application Code

I’m working on my first real asp.net web application and I’m kind of stumped on the best place and method to trap and handle database constraint violations. Suppose I have a unique constraint on a column and a user inputs something that would violate that unique constraint. Do I catch it in the business layer by making a call to the database to check of the value exists for that column or do I let it go all the way to the database and let it throw an exception and handle that in my application?

Best Practices for Building a Search App?

Is there a way to search all properties (without pulling all objects into memory – which I assume means building a list of each object’s properties with reflection, stringifying them, and then checking is out)? If not, this seems incredibly cumbersome as I’d have to build new logic for every new property I might add. Something like s.Contains(textFilter) in the above would be ideal.

Url Rewriting in asp.net but maintaining the original url

Page aspxHandler = (Page)PageParser.GetCompiledPageInstance(virtualPath, context.Server.MapPath(virtualPath), context); aspxHandler.PreRenderComplete += AspxPage_PreRenderComplete; aspxHandler.ProcessRequest(context); When you call Page.Request.Url after this, you get the Url of the page you rewrote to …what I’m looking for is to do a rewrite, but for Page.Request.Url to remain as the original url that was passed in. Is that possible? Answers: Thank you for … Read more