Visual Studio 2010 and .NET Framework 4.0

dotnetfacts.blogspot.com — On Sept. 29, 2008, Microsoft announced the next generations of Visual Studio and .NET Framework. Visual Studio 2010 and .NET 4.0 are meant to simplify application’s life-cycle management by make it easier for all contributors of the software team (core programmers, UI designers, testers and project managers), to participate throughout the life-cycle. read more...

add a comment | category: Visual Studio | Views: 25

How to: Set the PropertyGrid as Read-Only

dotnetfacts.blogspot.com — The default PropertyGrid control provided by the WinForms collection doesn’t support a read-only functionality. Setting the PropertyGrid as read-only might be useful if you want to allow your users to fully inspect a rich property object exposed by the PropertyGrid without the possibility to change something. read more...

add a comment | category: Tips & Tricks | Views: 45

Workaround: The SplitContainer may crash your VS2008 Designer

dotnetfacts.blogspot.com — If use the default Split Container to build a Windows Form or create a new user control, and set some properties of that Split Container at design time using Visual Studio 2008, you may end up with a broken form or user control. I got that error using the Visual Studio 2008 - Professional Edition. read more...

add a comment | category: Visual Studio | Views: 28

Client coordinates and Screen coordinates

dotnetfacts.blogspot.com — The .NET Framework can provide the mouse coordinates using the client coordinates system or the screen coordinates system. In some mouse-based scenarios we need exactly to know which coordinates system is used in order to use the correct offset. read more...

add a comment | category: Windows Forms | Views: 24

How the Garbage Collector works - Part 1

dotnetfacts.blogspot.com — The Garbage Collector (GC) can be considered the heart of the .NET Framework. It manages the allocation and release of memory for any .NET application. In order to create good .NET applications, we must know how the Garbage Collector (GC) works. read more...

add a comment | category: Tips & Tricks | Views: 2

How to: Use strings in a secure manner with SecureString class

dotnetfacts.blogspot.com — The classic System.String type doesn’t provide enough security for storing sensitive data like passwords, credit card numbers or personal information. If a String object contains sensitive information, there is a risk the information could be revealed after it is used because your application cannot delete the data from computer memory. Starting with the .NET Framework 2.0 the SecureString class is available. It was designed to provide encryption for sensitive data and other useful functions. read more...

2 comments | category: Tips & Tricks | Views: 15

Things you MUST dispose

dotnetfacts.blogspot.com — When the .NET Framework instantiates an object, it allocates memory for that object on the managed heap. The object remains on the heap until it's no longer referenced by any active code, at which point the memory it's using is reclamed by the Garbage Collector (GC). Before the GC deallocates the memory, the framework calls the object's Finalize() method, but developers are responsible for calling the Dispose() method. read more...

add a comment | category: Tips & Tricks | Views: 6

The Infragistics’ user controls library review

dotnetfacts.blogspot.com — All my late .NET projects had a mandatory, common requirement: the Infragistics NetAdvantage control library. I have been using it since the 6.1 version came out, over one year of development period, on six different .NET projects. Considering this, I believe I have enough experience with this user control library to highlight all the goods and the beds that come out from it. read more...

add a comment | category: Products | Views: 27