Warning

 

Close
Confirm Action

Are you sure you wish to do this?

Cancel Confirm
AR15.COM
1/2/2005 7:50:37 PM EDT
It's looking like I might get asked to do a fairly extensive project at work. I'm thinking I'll probably try to go with .NET, since it's pretty much up to me to do the programming, and they'd like it done in this lifetime. Basically, it's going to involve multiple SQL Server databases on the back end and a custom front end that I'll make.

I'm not a newbie or anything--I've done C++/MFC, Java Swing/AWT, C#, even VB6.  What I'm not strong on is how to design an application from the ground up to take advantage of the .NET architecture.

I'm looking for recommendations for resources about designing .NET apps, and also something about SQL server. I've done some basic SQL with Oracle, but haven't worked with SQL server. Also, I'm not real solid on database design--I kind of understand it as far as normal forms and such, but I'm far from a database designer, and I don't know much about optimizing SQL performance either.

Anybody have some suggestions on things to get me up to speed?
1/2/2005 10:54:20 PM EDT
[#1]
I can't help you.

I know nothing of .NET   (ok.. i know  a bit..Ms ripped off Java  )

As for DB design..  my project at work needs a oracle DB badly..  the DB is normalized will enough but  there DB has no rules to enforce data validation..  all the data validation is done at the app layer, and that is .. i'm told.. wrong.  the data validation code gets duplicated, and you have multiple sources to change if the data model ever changes.
1/2/2005 11:06:23 PM EDT
[#2]

Quoted:
I can't help you.

I know nothing of .NET   (ok.. i know  a bit..Ms ripped off Java  )

As for DB design..  my project at work needs a oracle DB badly..  the DB is normalized will enough but  there DB has no rules to enforce data validation..  all the data validation is done at the app layer, and that is .. i'm told.. wrong.  the data validation code gets duplicated, and you have multiple sources to change if the data model ever changes.



That makes some sense.
1/2/2005 11:36:36 PM EDT
[#3]
Google for some of Microsoft's best practices papers.