Am currently listening to Ron Cundiff's webcast (#3 of 22!) on Visual Basic .NET: Class Libraries.
This is a Microsoft Office Live Meeting (free training). This is a 200-level 1 hour lecture. Might be a bit below me, but it's always good to "fill the gaps."
I'm going to ask the following question: "I have been a VB programmer for years, and recently bowed to peer pressure and created my first C# app. What's the fuss about? Why is C# seen as something special? I couldn't find any extra features to give C# its reputation as a more robust programming language."
(Private Answer: nah, it's mostly because of the c/c++ programmers, and it's the most commonly used language in college...)
Go to http://msdn2.microsoft.com/en-us/netframework for free downloads.
.NET Framework 3.0 is now available.
The Software Development Kit (SDK) is necessary to create .NET applications.
You must install the Framework first.
The SDK comes with QuickStart Tutorials.
The CLR Debugger is the heart of the .NET Framework. This is what runs your apps.
- The System namespace has a manifest (observable from the IL DASM) which references multiple external assemblies.
- a way to have a unique library name
- Separated by "." notation
- System namespace
- is the top-level namespace
- contains all base objects
- data types
- Other System.* Namespaces
- Divided by functional area
- My Namespace
- New in Microsoft(R) Visual Basic(R) 2005
- Speed-dial into commonly used functions (e.g. My.Computer.Clock = Microsoft.VisualBasic.Devices.Clock)
- Reduces the amount of code you have to write
- Discoverable through IntelliSense(R)
- Reduces the amount time spent researching base classes or application programming interfaces (APIs)
- Custom Class Libraries
- User-defined namespaces
- Contain functions
- Add references
- "Imports" statement
- Are used just like System.* classes
- Session Summary
- System namespace
- Other system.* namespaces
- Custom class libraries