Software Development - { Coding && Architecture }

When importing any kind of data into an application simply using a text file is sometimes not sufficient, especially if the users already have information in an Excel file. Using an Excel file in C# is like connecting to a database. You provide a connection string (which, among other things, include the file path) and use SQL statements to read the file. The following snippet of code connects an Excel file to a DataGridView form component. OleDbConnection connection = new OleDbConnection(Provider=Microsoft.Jet.OLEDB.4.0;Data Source=foo.xls;Extended Properties=\"Excel 8.0;HDR=Yes;IMEX=1\";); try {   connection.Open();   OleDbCommand cmd = connection.CreateCommand();   cmd.CommandText = "SELECT * FROM [Sheet1$]";   DataSet dataSet = new DataSet();   OleDbDataAdapter dataAdapter = new OleDbDataAdapter(cmd);   dataAdapter.Fill(dataSet, "ImportData");   dataGridView_Sheet1.DataSource = dataSet.Tables["ImportData"].DefaultView; }

When listening to KeyPress events in a DataGridView , you will only listen to events when the actual DataGridView control has focus, and not when you are typing text in a column (e.g. DataGridViewTextBoxColumn ) in the grid. If you want to listen to key events (or any event) in the column, you need to first listen to an event that will fire when the DataGridViewTextBoxColumn control is entering editing mode. FooDataGridView += DataGridViewEditingControlShowingEventHandler(FooDataGridView_EditingControlShowing); Then you will be able to listen for the KeyPress event: private TextBox areaValueTextBox = null; void FooDataGridView_EditingControlShowing(object sender, DataGridViewEditingControlShowingEventArgs e) {     if (e.Control is TextBox)     {         if (areaValueTextBox == null)         {             areaValueTextBox = e.Control as TextBox;             areaValueTextBox.KeyPress += new KeyPressEventHandler(areaValueTextBox_KeyPress);         }         else            

The Hibernate lazy associations is a wonderful feature which minimize the database communication when loading (large) sets of data. But sometimes you need to load the full dataset, and you don't want to set the lazy flag in the mapping files to false. The solution is to use the static method NHibernate.NHibernateUtil.Initialize() , but the problem is that this method doesn't cascade to associated objects, you only initialize the current object, and no underlying collection. The following is a snippet of code that initialize all collections, and their collections, and so on.  protected void InitializeWithCascade(object rootObject) {   PropertyInfo[] propInfos = rootObject.GetType().GetProperties();   foreach (PropertyInfo property in propInfos)   {    MethodInfo mi = property.GetGetMethod();    System.Collections.ICollection collection = mi.Invoke(rootObject, null) as System.Collections.ICollection;    if (collection != null)    {     // This is a collection     Sys

When building a project in Borland Builder (version 5) you can get a linker error such as: [Linker Error] Fatal: Error detected (LME351) [Linker Warning] Cannot reserve virtual memory at addr 461A0000 for -1703936 bytes (errcode 87) This is a known bug in Borland Builder, and the reason is that the debug information file is too big. Every project with forms create a debug file (a *.tds file), when the size of this file exceeds roughly 32 MB the linker throws an error. The solution is to disable the debugging ability of forms with many controls: Right-click a form in the "Project Manager", select "Edit local options..." and un-check the "Debug information" checkbox. Delete the project's *.tds file and the vcl50*-files in the Borland installation directory (e.g. C:\Program Files\Borland\CBuilder5\Lib\vcl50.*). Re-compile all files you have changed debug settings on.