This tutorial demonstrates the techniques needed to build a Web service in C# that accesses an IBM DB2 Universal Database using the DB2 managed data provider.The DB2 managed data provider offers capabilities similar to the SQL Server managed data provider as well as providing a high performance, secure way to access a DB2 database from any .NET programming language. The DB2 managed data provider was written in C# by the DB2 Development organization to combine the best features and function of DB2, while exploiting the database neutral facilities included in the .NET Framework.
I didn’t read the whole thing, but glanced at it, and I didn’t see a single line of code through the whole thing.
I guess whether this is a good thing or a bad thing depends on your perspective
With these technologies, hardly any code has to be written. It’s mostly point’n’click.
Whether that’s a good thing, again depends on your perspective
I just checked and there is sample code as you read through it.
actually .NET _is_ a language where i find myself doing a whole lot with very few lines of code
Actually the question is:
Do you actually know what you are doing? To much gui coding
can lead to untransparancy and unreadable code…ok i must addmit that also depends on you gui program.
I prefer the old style but i recently tried kylix and Gamba’s (was included with click and run from Lindows) and they worked fine but needed a fair amount of hand work to make the apps work as i wanted them to work.
“actually .NET _is_ a language where i find myself doing a whole lot with very few lines of code ”
actually .NET isn’t a language! – it’s a platform.
And you still have to write huge gobs of code – you’re probably just using Visual Studio .NET, which handles a lot of it for you.
Try importing a DataAdapter from the Server view, and check the code it autogenerates. The Select/Insert/Update/Delete commands that are generated are HUGE!!! Performance wise it “sux”, but maintainance wise, it’s a good thing.
“And you still have to write huge gobs of code – you’re probably just using Visual Studio .NET, which handles a lot of it for you. ”
i’m using Visual studio as well as emacs/mono. i didn’t mean you don’t have to write code for eventhandlers because vs does that for you, the code is still there. I meant there are plenty of methods and objects in this very rich framework that allow you to get things done with fewer lines of code (you still have to write some off course)
“Try importing a DataAdapter from the Server view, and check the code it autogenerates. The Select/Insert/Update/Delete commands that are generated are HUGE!!! Performance wise it “sux”, but maintainance wise, it’s a good thing.”
or try it from code. the autogenerated code is not all that clean, but generated code never really is i guess.
“Do you actually know what you are doing? To much gui coding
can lead to untransparancy and unreadable code…ok i must addmit that also depends on you gui program. ”
the gui editor in vs .NET is actually just a visual representation of your code file. Make some changes in your code file manually and your gui is updated. There is no way that the gui in VS .NET gets in the way of writing clean code.
i do have to agree though that when you take over a project that has been created “dragging and dropping”, it’s a bloated pig, but sloppy coding is a problem with the developer, not the environment because this environment really lets you write clean code if you want to
>actually .NET _is_ a language where i find myself doing a whole lot with very few lines of code
Actually, .NET is NOT a LANGUAGE.