Theory
A billing app for Mehta Stores
A small Surat storekeeper wants what every shop wants: click the item, type the quantity, print the bill, save it. A Windows desktop app.
This semester you build exactly that: ShopKeeper, a billing application with real buttons, grids and a database.
You will write it in Visual Basic .NET. But before the first line, one lesson on the machine underneath: what exactly is this ".NET Framework" your code will live inside?
Theory
An engine and a parts shop
Think of .NET as a car factory that gives you 2 things.
An engine: the CLR (Common Language Runtime), which actually runs whatever you build, managing its memory and safety while it runs.
And a parts shop: the class library (FCL), thousands of pre-built components (buttons, file readers, database connectors) so you assemble instead of forging every screw.
Every .NET program is parts from the shop, running on the engine.
Theory
The .NET Framework, formally
The .NET Framework is Microsoft's platform for building and running applications on Windows. Its 2 pillars:
- CLR (Common Language Runtime): the execution engine. Your compiled code runs under its supervision: memory, security, exceptions.
- .NET Framework Class Library (FCL): a huge, organised collection of ready-made classes for UI, files, network, data.
One sentence for the exam: .NET = CLR + class library, a managed environment where programs written in many languages build on shared components and run under one runtime.
Theory
Many languages, one runtime
Here is .NET's famous trick: VB.NET, C#, F# and more all compile to the same intermediate language and run on the same CLR.
Two agreements make that possible:
- CTS (Common Type System): all languages share one set of types; a VB.NET Integer and a C# int are the SAME underlying type
- CLS (Common Language Specification): the rules a language follows so its code can be used from any other .NET language
So a C# team can use classes your VB.NET ShopKeeper defines, unchanged.
Quiz
What are the 2 main components of the .NET Framework?
- The CLR and the .NET Framework Class Library
- Visual Studio and Visual Basic
- MSIL and metadata
- Windows Forms and ADO.NET
Show the answer
The CLR and the .NET Framework Class Library
Engine plus parts shop: the CLR executes managed code, the class library supplies the building blocks; that pair IS the framework. Visual Studio (option B) is the IDE you work in, a tool, not part of the framework itself. MSIL and metadata (option C) are what your code compiles INTO, next lesson's subject. Windows Forms and ADO.NET (option D) are 2 sections inside the class library, parts, not the pillars.
Think first
You have seen this movie
Last semester's subject ended weeks ago, but think: where have you already met the pattern "compile to an intermediate form, run on a managing engine"? And what were its names there?
Show the answer
BCA403's Java: source compiled by javac to bytecode, executed by the JVM. .NET is the same architecture from Microsoft: source compiled to MSIL, executed by the CLR. One honest difference to remember: Java's promise was one language on many operating systems; classic .NET's promise was many languages on one OS (Windows). Carry the mapping javac to vbc, bytecode to MSIL, JVM to CLR through this whole unit and it will feel like revision.
Watch out
Name things precisely
Three mix-ups cost marks in this unit:
.NET is not a language: it is the platform; VB.NET and C# are languages on it.
Visual Studio is not .NET: it is the editor/IDE; programs run on .NET even on machines with no Visual Studio installed.
VB.NET is not old VB: it is a fully object-oriented .NET language; answers written in VB6 style (no classes, no CLR) date your paper badly.
Theory
Where ShopKeeper fits
Map the semester onto the 2 pillars now: Units 1 and 2 are about the engine and the language it runs; Unit 3 raids the parts shop's UI shelf (Windows Forms controls) to build ShopKeeper's actual billing screen; Unit 4 makes your own parts (Item and Bill classes); Unit 5 uses the data shelf (ADO.NET) to save bills. Every unit is either the engine or the parts shop; nothing else exists.
Summary
Key takeaways
- .NET Framework = CLR (the execution engine) + the .NET Framework Class Library (the ready-made parts).
- Many languages (VB.NET, C#, F#) compile to one intermediate language and share one runtime.
- CTS gives all .NET languages one common type system; CLS gives the interoperability rules.
- .NET is a platform, not a language; Visual Studio is the IDE, not the framework.
- This subject's language is Visual Basic .NET; the semester project is the ShopKeeper billing app.
- The architecture mirrors Java: source to intermediate code to managing runtime.
- Memory hook: one engine, one parts shop, many languages.