Discussions

http://undev.spaces.live.com/blog/cns!6526A337A687E45D!162.entry

Here is the default way. Unless you really want your own custom config provider.

Simply put use stored procs or an ORM. Validate everything at every step in the relay (each layer) that can modify a particulair entity. Client -> Business Object layer -> Data Access Layer -> to wherever. This is a fundamental to quality software. Specially but not limited to if you need to use query building in your stored proc.

Limiting your mutable footprint may be a valid option. Knowing is most of the battle.

Later you start planning for this issue the more costly the endeavor becomes. As most things in software egineering:)

Visit my blog undev.spaces.live.com. On my Tools I Use pane I have number of open source projects that you can learn from. Also Scott Hansleman has been doing a series lately called weekly 'The Weekly Source Code' lastest one is here (http://www.hanselman.com/blog/TheWeeklySourceCode22CAndVBNETLibrariesToDiggFlickrFacebookYouTubeTwitterLiveServicesGoogleAndOtherWeb20APIs.aspx)

There is also Codeplex, Code Gallery, Google Reader (subscribe to some blogs there are tons of them), Google Code Search, SourceForge, 2008 Virtual Launch, All the various new stuff for VS 2008, and the list goes on. I started keeping a list myself at del.icio.us.

I recommend the book for 70-536 (Foundations of .NET) from MS Press. It is very well written and if you do all the assignments in it you will pass with flying colors. Can't speak to the ramp up since I was already past needing to look at that when it was released.

Key to adding business logic is realizing the power of partial classes and partial methods (lightweight events).

So in a nutshell you want to add custom code to a new source file that was not originially generated by your OR product. Also realize what hooks exist out of the box with partial methods.

W3bbo wrote:



odujosh wrote: Yep do not use IFrames. By using them you do not really understand ASP.NET. Its a defunct tag.

Not necessarily, there are legitimate uses for inline frame behaviour.

OnErrorDoThis wrote:  I too was stuck in the iframe world. I recommend : It'll be hard but stop using iframes. Use <DIV> with IDs instead. Get your data by XMLHttpRequest ( http://en.wikipedia.org/wiki/XMLHttpRequest ) and fill your <DIV>(s) with data from the reuqeut via JavaScript for example with "innerHTML". This way, you will be able to control everything and "fill" "at will". If you need scrolling in your boxes, You can still do that without iframes, <DIV> tags are capable of having both H/V scrollbars.

Learn CSS first

a) the <div> element does not have an uppercase tagname
b) any element can have scrolling behaviour
c) your proposal breaks if client scripting is disabled, bad.

You using C++. Wait some people are masochist and do not think that is a bug.

ScanIAm wrote:

I found this guy's blog a few months ago and immediately printed out the .NET format strings cheat sheets.

Very handy since this stuff isn't always easy to remember.

http://john-sheehan.com/blog/index.php/net-cheat-sheets/

Yep do not use IFrames. By using them you do not really understand ASP.NET. Its a defunct tag.

WCF webservices can be bidirectional. So I why not 1