Characteristics of .NET Core
💡 Concept Name
.NET Core Characteristics
📘 Quick Intro
.NET Core is a modern, open-source, cross-platform framework for building apps. It brings modular architecture, improved performance, and platform independence to .NET developers.
🧠 Analogy / Short Story
Think of .NET Core as a Swiss Army Knife. Unlike older frameworks that were bulky and Windows-only, .NET Core is light, modular, and runs on any OS—just like a multipurpose tool that adapts to different jobs and environments.
🔧 Technical Explanation
- Cross-Platform: Works on Windows, Linux, macOS
- Open Source: Available on GitHub under MIT license
- Modular: Uses NuGet packages, lightweight runtime
- High Performance: Optimized for speed and scalability
- Flexible Hosting: Supports Kestrel, IIS, Docker, Azure, etc.
- Unified Development: Supports web, desktop, mobile, cloud apps
🎯 Purpose & Use Case
- ✅ Build cross-platform web APIs and microservices
- ✅ Create cloud-native and containerized applications
- ✅ Modernize legacy .NET Framework applications
- ✅ Ideal for performance-sensitive applications
💻 Real Code Example
// Example: Console App using .NET Core
using System;
namespace CoreAppDemo {
class Program {
static void Main(string[] args) {
Console.WriteLine("Hello from .NET Core!");
}
}
}
❓ Interview Q&A
Q1: Is .NET Core cross-platform?
A: Yes, it runs on Windows, macOS, and Linux.
Q2: Is .NET Core open-source?
A: Yes, it's hosted on GitHub under MIT license.
Q3: What makes .NET Core modular?
A: It uses lightweight NuGet packages instead of monolithic assemblies.
Q4: Can .NET Core apps run in Docker?
A: Yes, it's fully container-friendly.
Q5: How does .NET Core improve performance?
A: Through a new runtime, optimized JIT compiler, and reduced overhead.
Q6: Can you run ASP.NET Core on Linux?
A: Absolutely. Thanks to .NET Core's cross-platform support.
Q7: Where is the source code of .NET Core maintained?
A: On GitHub at github.com/dotnet
Q8: What web server comes with .NET Core?
A: Kestrel
Q9: How do you add dependencies in .NET Core?
A: Using NuGet packages
Q10: Is .NET Core suitable for microservices?
A: Yes, it’s ideal for microservice architectures.
📝 MCQs
Q1. What type of framework is .NET Core?
- Windows-only
- Proprietary
- Cross-platform and open-source
- Java-based
Q2. Which web server is built into .NET Core?
- IIS
- Kestrel
- Apache
- Nginx
Q3. Where is .NET Core source code hosted?
- Bitbucket
- GitHub
- Azure DevOps
- Google Code
Q4. What packaging system does .NET Core use?
- Maven
- NuGet
- NPM
- Composer
Q5. What is the licensing model of .NET Core?
- MIT
- GPL
- Apache
- BSD
Q6. Can .NET Core be used in Docker containers?
- No
- Only on Windows
- Yes
- Only with IIS
Q7. Which of these is true for .NET Core?
- Monolithic design
- Windows-only
- Supports modular architecture
- Supports only C++
Q8. Which is NOT a feature of .NET Core?
- High performance
- Runs only on Windows
- Cross-platform
- Open source
Q9. Is .NET Core suitable for microservices?
- No
- Only for desktop
- Yes
- Only with Azure
Q10. What is Kestrel?
- Windows-only browser
- IDE for .NET
- Cross-platform web server
- Logging tool
💡 Bonus Insight
.NET Core’s modular nature makes it lightweight and faster. You only include the packages you need, which reduces application footprint and improves maintainability.
📄 PDF Download
Need a handy summary for your notes? Download this topic as a PDF!