.NET gives developers a lot of freedom. In every version new features are added to ease them in their daily work. One of the simplest things that have existed since the first versions of .NET framework are access modifiers. Using them one sets the access to a specific class/method. Public, private, protected… all are standard modifiers. If you have experience with an object-oriented language you must know them by heart. .NET provides another modifier – internal. It allows access to a method only in the parent assembly (the one the corresponding class resides in). Continue Reading…
When you write managed code you propably think “Hey, .NET manages the memory, so I don’t care about it”. But you are not right. When you write code, no matter what the programming language is, you should always think about memory, especially when it comes to performance optimization. Although .NET provides a managed environment, memory leaks can still occur if you are not cautious.
Here is a great video explaining .NET memory management in details.
- Why memory matters
- .NET Memory and Garbage Collection
- Generational Garbage Collection
- Temporary Objects
- Large Object Heap and Fragmentation
- Memory Problems