Originally posted by: GilletteCat
You need to download ODP.Net from Oracle. It stands for Oracle Data connectivity Provider for .Net. Install it on both, your dev box and the web server that host the website. ODP.Net comes with documentation and samples for both VB.Net and C#.
Good luck!
I read on some blog that there were issues with the latest release of ODP.NET when it runs on top of .NET Framework 3.5 and 10g. Oracle advertises the latest release for use with 11g and Framework 3.5. I think in the OP's case he's using 10g. So you might want to check compatibility before you start developing using ODP.NET.
If it's a concession, I have been using LINQ to DataSet in .NET 3.5 for extracting data from a 10g back-end. The system hasn't gone live yet, but one of the things I plan to do (if I get enough time) is to compare the performance of MS's default provider for Oracle and ODP.NET. In the past, ODP.NET outperformed MS's provider, but I didn't use it this time around because of the above mentioned compatibility issue.
EarthWillShake: Don't get carried away because you have heard "AJAX is cool." In my opinion, concentrate more on modularity, re-usability, and functionality - you're probably not going to be dealing with 1000's of Web requests in your corporate environment. The goal should be to deliver the pilot (effectively), not using AJAX. Even more so, since you're dealing with many newer technologies... you can always go back and embed AJAX in your existing pages if you have the time at a later point in time.
Also, if you use Oracle's documentation, be wary of some of the examples... they do a poor job of disposing objects and closing connections (things like connections being closed/disposed outside of the finally block, objects not being disposed properly, etc.). But then, it isn't their job to demonstrate "how to program" (I guess, I am just being comparative... for example, IBM is still an *outsider* but does a great job of compiling examples for things like Websphere).