So I finally updated my portfolio! Not only did I update it with the projects I’ve worked on for the last 2 years but I made it dynamic so now all of the projects pull from a database. I created an admin section to add/edit/delete clients & projects that way I won’t have to put off updating it anymore. From now on, any time I finish a project I can quickly add it via the admin section and it will show up on my portfolio. I’m very excited about this as it’s something I’ve been wanting to do for a couple years and I finally broke down and did it! I also migrated the existing dynamic content from ASP.NET to PHP with a MySQL backend. Anyway, now it’s time to find some work!
SQL stands for Structured Query Language. It is a programming language designed to allow the viewing and manipulation of data within a database (Wikipedia – SQL, 2006). There several proprietary versions of the Structured Query Language, primarily because each major database system vendor has created their own version. For instance, Microsoft has created Transact-SQL or T-SQL which is used to interact with SQL Server databases (Wikipedia – Transact-SQL, 2006) and Oracle has created SQL*Plus which is used to interact with Oracle databases, but all versions have certain similarities and share syntax to some extent (Basic Introduction to SQL*Plus, 2006). Understanding the fundamentals of SQL is typically all that is needed in order to understand and use SQL statements.
A SQL statement is a string of text, which is interpreted to build a command that is run against a database or database system. There are many SQL commands available, which allow you to perform a variety of actions. For instance, using various SQL statements, you can view, edit, and delete data within tables as well create and delete entire databases. The four most common SQL commands used to query databases are SELECT, INSERT, UPDATE, and DELETE. Other commands allow you to perform complex statements, such as the JOIN command, which allows running queries against multiple tables simultaneously. A typical SELECT statement specifies a column or columns and a table or tables using a JOIN statement. You can also use keywords such as WHERE and LIKE to specify parameters, which limit the data that is returned.
The following SQL statement would return all rows of data from a table called tblUsers where the fldFirstName is equal to “John”.
SELECT * FROM tblUsers WHERE fldFirstName = ‘John’
If I were interviewing an ASP.NET programmer as a candidate for an ASP.NET development position, I would most likely expect them to have a working knowledge of SQL and at least one major database system such as SQL Server or Oracle. ASP.NET is used primarily to create dynamic web applications, many of which interact with backend database systems. It is important that the developer of an ASP.NET web application be accustomed to working with databases. This will most definitely require knowledge of SQL (W3Schools – Web Building, 2006).The main difference between a web designer and a web developer is that a web designer focuses primarily on the interface design of a website; therefore, they would not necessarily need experience programming in ASP.NET or SQL. However, a web developer is typically responsible for creating the code, which makes a website functional and dynamic. By virtue of the term “ASP.NET programmer”, it is assumed that the duties, which would fall under such a title, would include web development as well as web design. I would expect any seasoned web developer to have experience writing applications, which interact with databases using SQL statements.
Resources:
Wikipedia – SQL. (2006). Retrieved on July 19, 2006 from http://en.wikipedia.org/wiki/SQL
Wikipedia – Transact-SQL. (2006). Retrieved on July 19, 2006 from http://en.wikipedia.org/wiki/Transact-SQL
Basic Introduction to SQL*Plus. (2006). Retrieved on July 19, 2006 from http://www-it.desy.de/systems/services/databases/oracle/sqlplus/sqlplus.html.en
W3Schools – Web Building. (2006). Retrieved on July 19, 2006 from http://www.w3schools.com/site/site_intro.asp
An event is a message that signifies that something has happened (MSDN – Events in Visual Basic, 2006). Once an Event occurs, the Event can be handled by using an Event Handler. An Event Handler is a method that contains code, which is executed when a specific event occurs (TopXML : Handling Events, 2006). Events can be based on user input or they can be raised manually by writing code to do so. The .NET Framework contains several built in Events such as the Click event. When a user clicks on an object, if the object contains an Event Handler for the Click event, then the code within the Event Handler will be executed. Custom Event Handlers can also be created by the developer (MSDN – Raising an Event, 2006).
Although there are some similarities in the way events are handled using WebForms vs. WinForms, there are also some significant differences. Some events that are available for WinForms controls are not available for WebForm controls and vice versa, however, like WinForms, WebForms can be coded using any .NET language. (WDVL: WebForms, 2006). The main difference between events in WebForms vs. WinForms has to do with the way controls interact with the application. For instance, in WinForms applications the controls are always client-side, but with WebForms, the controls can be run on the server but rendered on the client. Similarly to WinForms, code can be added “behind” WebForm pages and controls based on Events (Find Tutorials, 2006).
Just like WinForms, when an event is raised on a WebForm, the Event Handler executes the code within the Event Handler Method. The difference is that, instead of executing immediately on the client, a message is sent to the web server, the event is handled on the server and then a message containing the output is sent back to the client from the server (TAKempis – ASP.Net Fundamentals, 2006).
Resources:
MSDN – Events in Visual Basic. (2006). Retrieved July 14, 2006 from http://msdn2.microsoft.com/en-us/library/ms172877.aspx
TopXML : Handling Events. (2006). Retrieved July 14, 2006 from http://www.topxml.com/dotnet/handling_events.asp
MSDN – Raising an Event. (2006). Retrieved July 14, 2006 from http://msdn2.microsoft.com/en-us/library/wkzf914z.aspx
WDVL: WebForms. (2006). Retrieve July 14, 2006 from http://www.wdvl.com/Authoring/Tools/NET/net2_4.html
Find Tutorials. (2006). Retrieve July 14, 2006 from http://tutorials.findtutorials.com/read/category/85/id/162
TAKempis – ASP.Net Fundamentals. (2006). Retrieved July 14, 2006 from http://www.takempis.com/aspnet_fundamentals.asp
ADO.NET is a newer version of ADO or ActiveX Data Objects. Microsoft created the ADO object model as a way to connect to databases from within programs (Wikipedia – ActiveX Data Objects, 2006). Although ADO.NET is based on ADO, there are some significant differences. Most of the changes made to ADO.NET are improvements such as better XML integration, disconnected data access, and .NET Framework integration (MSDN – ADO.NET for the ADO Programmer, 2006). ADO.NET is used to connect to a variety of different data sources such as MySQL and MS SQL Server. The data can be viewed and manipulated in different ways. For instance, it is possible to view, update, and delete data using different queries (MSDN – Overview of ADO.NET, 2006). The advantages of using ADO.NET are its improvements over ADO as mentioned above, as well as performance and its ease of implementation (ADO.NET Pros and Cons, 2006).
ADO.NET consists of two main components: the Data provider and the DataSet. The Data provider objects are classes that are used to connect to and communicate with a database. Five common objects are used as part of the Data provider. The Connection object is used to connect to a data source. The Command object is used to run a command against a data source, such as a query. The Parameter object is used to send a parameter with a command, such as a stored procedure. The DataAdapter object is used to send data back and forth between the DataSet and the data source. The DataReader object is used to process a large amount of data but only one record can be read at a time. The DataSet is the other main component of ADO.NET. DataSet objects contain classes, which represent an actual database and the data within it. A DataSet object can contain other objects such as a DataTable, a DataRelation and a Constraint. The DataTable object can contain objects such as a DataColumn and a DataRow. All of these objects are used to represent the data and structure in a database (Wikipedia – ADO.NET, 2006).
Knowing how to take advantage of the features of ADO.NET is essential when developing business applications. Many business applications contain or communicate with a backend database. Some standalone applications might include with it a small Access or dBase database. For instance, a bug tracking program or a low-end customer relations management application would need to store information in a database. That information may need to be viewed and/or updated. The application would be designed to limit the control that users have over the backend database. If necessary, a custom application could be developed using .NET to connect to the backend database, which could offer more or less functionality based on the needs of the users. ADO.NET features could be used in the custom .NET application to provide access to the data within the database. Some larger organizations might have huge database systems that contain much more information than a smaller Access database would be able to support. These organizations require higher end database systems, such as Oracle or MS SQL Server. ADO.NET could be used within a client/server .NET application to connect to these higher end systems as well (W3Schools, 2006).
Resources:
Wikipedia – ActiveX Data Objects. (2006). Retrieved June 3, 2006 from http://en.wikipedia.org/wiki/ActiveX_Data_Objects
MSDN – ADO.NET for the ADO Programmer. (2006). Retrieved June 3, 2006 from http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndotnet/html/adonetprogmsdn.asp
MSDN – Overview of ADO.NET. (2006). Retrieved June 3, 2006 from http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconOverviewOfADONET.asp
ADO.NET Pros and Cons. (2006). Retrieved June 4, 2006 from http://www.vbip.com/books/1861005563/chapter_5563_06.asp
Wikipedia – ADO.NET. (2006). Retrieved June 4, 2006 from
http://en.wikipedia.org/wiki/ADO.NET
W3Schools – ASP.NET – Database Connection. (2006). Retrieved June 4, 2006 from http://www.w3schools.com/aspnet/aspnet_dbconnection.asp
It seems there are several answers to the question “What is .NET?” Over time, through using .NET, I have come to realize that .NET seems to be Microsoft’s answer to Java. I have not used Java extensively; however, I do know that one of its major appeals is that it is platform independent (Manageability, 2006). You can run Java applications on just about any operating system, by using what is known as a Java Virtual Machine. The Java Virtual Machine can be installed on an operating system and then Java applications run within the JVM, making it platform independent (Wikipedia – Java Virtual Machine, 2006). Microsoft created the Common Language Runtime or CLR, which is language independent and comprised of several components but functions more or less as an application sub layer to run in between the operating system and the actual application. In essence, it works in very much the same way as the Java Virtual Machine (Wikipedia – .NET Framework, 2006). Interestingly, the architecture on which .NET is built, is not the only similarity it has to Java. I have recently begun learning bits and pieces of Java and have noticed that even some of the syntax within .NET can be compared to that of Java. For instance, the Try, Catch, and Finally exception handling is very similar in both .NET and Java. Visual Basic .NET is unique in that it can be used to create Windows applications as well as Web applications. Not many languages are as versatile and yet easy to implement as Visual Basic .NET is.
I would really like to learn more about Visual Basic.NET code security as well as Web services using XML. This is actually something that I have wanted to learn more about for a quite a while now. I would like to become a master with regard to the .NET Framework and underlying architecture. I believe that more and more applications written in .NET will be popping up in the corporate structure and these applications will need to be improved upon and supported. One of the most, if not the most important aspect to developing business applications is security. Knowing how to secure an application at the code level would be an invaluable and highly marketable skill. This would involve understanding how applications are written at the deepest level.
Learning Visual Basic.NET has already been useful to me in many ways, therefore I expect it to continue to be useful throughout my career as a software developer. One of the major benefits that I have noticed using Visual Basic.NET, is the fact that it has considerably simplified the process of application development, thereby making the learning process less challenging. Before dabbling in .NET, I had struggled immensely in learning how to write code and develop applications. Using .NET has not only made it easier for me to understand how to write applications in .NET languages, but it has helped me to understand the basics of other languages as well, including Perl, C, and Java. If it were not for .NET, I am not sure that I would have ever been able to grasp some of the most basic programming concepts. I believe .NET technology and specifically Visual Basic .NET will continue to improve and gain popularity as a language, if for no other reason than that of its overall simplicity to use and understand.
Before using Visual Basic .NET, I had used Visual Basic 6 to create a couple unfinished applications. I would always reach a point where I would be stuck on something and eventually give up. This was very discouraging to me and I nearly gave up programming for good as a result. It was not until I began using Visual Basic .NET that I was actually able to create a complete, useful, working program from design to deployment. I should also mention that in my experience, it seems to take much less time to create functional applications in Visual Basic .NET than it did in Visual Basic 6. There were some aspects to using Visual Basic 6, of which I can barely recall at this point, that made it a rather cumbersome language to use. For instance, creating a Multiple Document Interface (MDI) application was something I never could figure out in Visual Basic 6 but it is fairly straight forward in Visual Basic .NET (Dev Articles, 2006).
Resources:
Manageability. (2006). Retrieved June 3, 2006 from http://www.manageability.org/blog/archive/20030108%23101_reasons_why_java_is/view
Wikipedia – Java Virtual Machine. (2006). Retrieved June 3, 2006 from http://en.wikipedia.org/wiki/Java_virtual_machine
Wikipedia – .NET Framework. (2006). Retrieved June 3, 2006 from http://en.wikipedia.org/wiki/.NET_Framework
Dev Articles. (2006). Retrieved June 3, 2006 from http://www.devarticles.com/c/a/VB.Net/Migrating-to-Visual-Basic.NET-from-Visual-Basic-6/5/
Prior to enrolling in AIU’s IT – Software Development Bachelor’s program, I had developed an interest in programming and specifically in Visual Basic .NET. I had tried for several years to learn programming concepts but always struggled. It wasn’t until I stumbled across a little book called Learn Microsoft Visual Basic .NET in a Weekend that I actually began to grasp the basics of programming. The book’s title alone held much appeal, considering that a weekend is not that much time to have to spend learning something new, especially a computer programming language. The physical size of the book drew me in as well; being that it is so small compared to most of the twenty pound, thousand page programming books you see. The book itself only covers very basic features of Visual Basic but is written in plain English and contains many illustrations (Work & Miller, 2002). These factors make it very easy to read and understand.
Another book I own that I have found to be quite helpful is called Visual Basic .NET Complete. It’s nearly a thousand pages, which makes it rather intimidating but it is not necessarily a book that you would sit down to read cover-to-cover. It is more useful as a reference. Some of the topics covered include Visual Basic .NET essentials, ASP.NET essentials, XML integration, and database programming as well as application deployment. The book does not go into great detail of these topics however, there is enough information provided to give the reader a basic understanding of what is being discussed.
I have another book called Sams Teach Yourself Visual Basic .NET Web Programming in 21 Days. I have read several Sams books and highly recommend them because they are typically very easy to read and the way they are organized makes reading them almost fun. I have not finished reading this one yet but I have used it several times as a reference book to perform specific actions or to find snippets of code. For instance, when I was developing a website for a company I used to work for, I needed to create a database connection and I was able to find out how by reading the section on working with ADO.NET (Aitken & Syme, 2002). Another resource I have found to be infinitely useful when it comes to finding snippets of code is a website called Planet Source Code. The website contains sample source code for several different languages including Visual Basic, Perl, and Java (Planet Source Code, 2006)
Finally, to discuss the differences between Object-Oriented Programming (OOP) and Object-Oriented Design (OOD), it should be noted that they are closely related. OOD is a way of developing the methods and concepts that will be used to define how an object-oriented program will be designed and implemented. Advantages of using OOD include simplified management, reusability, and reduction of complexity which in turn reduces cost and saves resources (Object-Oriented Design, 2006). When it comes to using Object-Oriented Programming to develop a system, CASE tools can be used to represent objects in the design process (Using Object-Oriented CASE Tools, 2006). Object-Oriented Programming (OOP) is the method used to implement the design.
OOD is used to simplify the development of complex programs and systems. An example of this can be seen by examining how AT&T Bell Labs implemented reusable design objects and code in their Call Attempt Data Collection System (CADCS) program. OOD and OOP, specifically C++ were used to develop the system, which contained over 350,000 lines of code and was distributed amongst several different systems (Object-Oriented Design, 2006). A large programming project such as this would be a good candidate for the use of OOD.
References:
Work, L., & Miller, J. (2002). Learn Microsoft Visual Basic .NET in a Weekend.
United States of America: Premier Press
Grider-Carlyle, K. (2002). Visual Basic .NET Complete. United States of America: Sybex
Aitken, P., & Syme, P. (2002). Sams Teach Yourself Visual Basic .NET Web Programming in 21 Days. United States of America: Sams Publishing.
Planet Source Code. Retrieved March 24, 2006, from http://www.planet-source-code.com/
Object-Oriented Design. Retrieved March 24, 2006, from http://www.sei.cmu.edu/str/descriptions/oodesign_body.html
Using Object-Oriented CASE Tools. Retrieved March 24, 2006, from http://www.microgold.com/Stage/WithClassTutorial/WCTutP1S3.htm
