Delving further into my current ASP.NET 2.0 project I've found out that things from a database perspective have the possibility of being very different. After designing the project, doing the major documentation, and walking through a couple of tutorials for the DevExpress ASP.NET 2.0 grid I decided it would be best to start working on implementing the database layer first. Especially considering two factors; A) Oracle doesn't exactly like to work well with .NET (their 10g .NET 2.0 provider is still in Beta) and B) building the project from the ground up makes more sense at this point, not to mention the fact that it will make writing a conversion program for the data a little clearer.
Anyways, I am looking to figure out more information on best practices in ADO.NET 2.0 and some of the changes between the two.
Also, still looking for more MVC information.
Anyways, on the docket for today is further database coding (finishing off the stored procedures) then onto integrating the Data Block from Microsoft's Enterprise Library with the current table structure, at least making sure my recompiled version of the ELDB using Oracle's .NET 2.0 provider beta will communicate with the database properly. From there it's implementing the Membership Provider and getting to a point where I can write a data conversion app.
One interesting thing that came up in my discussions with coworkers recently was the use of Oracle Views and Functions. Essentially the advice came down like this: Views over 1,000 rows perform poorly, simple single "gets" (1 record, 1 column returned) are best done with functions. I found both pieces of input to be useful and extremely interesting. Particularly the views portion. I had been considering using a view but the size of the data returned would be too large to make it efficient, so back to the reliable stored procedure I went, and things have been going well so far.
Alright, back to it!