For millennia, mankind has looked to the stars and wondered, “How can I create a generic Dictionary in .NET that allows me use case insensitive strings as keys?” Well today that age old question will be answered with this neat trick.
Simply put, all you need to do is add a StringComparer object when constructing a generic Dictionary that uses a string key, and make sure to use on of the IgnoreCase StringComparers that are offered. Below is some sample code to illustrate just how easy this is.
// Create a generic dictionary with a string comparer that ignores case sensitivity.//// This includes the following:// - CurrentCultureIgnoreCase// - InvariantCultureIgnoreCase// - OrdinalIgnoreCaseDictionary<string, string> stringMap =
stringMap.Add("Test Key", "Some value");
// Now try to access or change the corresponding value with the key.// The case of the key string no longer matters.
stringMap["test key"] = "This will work";
stringMap["TEST KEY"] = "And also this";
stringMap["tEsT kEy"] = "And this as well";
stringMap["tEST kEY"] = "And finally this";
// This can be done with any dictionary that uses a string as the keyDictionary<string, int> numberMap =
numberMap.Add("Test Key", 0);
// Same deal here, you can use any case to get or set the values in the map
numberMap["test key"] = 1;
numberMap["TEST KEY"] = 2;
numberMap["tEsT kEy"] = 3;
numberMap["tEST kEY"] = 4;
And that’s all there is to it. I hope you enjoy and find this useful.
“Now the headlights they was another sight
We had two on the left and one on the right
But when we pulled out the switch all three of ‘em come on.”
– Johnny Cash “One Piece at a Time”
Many years ago, Johnny Cash sang a song called “One Piece at a Time”, in which he describes an automobile assembly plant worker stealing parts and pieces of various automobiles and assembling them into a very distinctive, one-of-a-kind car.
Given the nature of software, the essence of which is some form of code, building software is somewhat like putting that car together. Technology evolves over time, operating systems change, and new tools all contribute to the complex process of building an application. Code is pieced together in files and modules, and the output of the code in the form of log files and/or visual display on a monitor are the effects of the code. When building an engine, putting on the heads and bolting up the crankshaft before attaching the pistons and connecting rods isn’t recommended. Similarly, software designers aren’t always able to see all the parts until there is a basic framework constructed, and limitations of the system come to light. Re-designing components and restructuring development schedules are not uncommon. Continue reading →
In ILINX Capture, the most basic unit is a batch profile. A batch profile is a container that includes batch fields, one or more document types and a workflow. It is unique, self-contained and completely independent from each other. In general, you would want to create a batch profile for each unique workflow process in the system.
If you have multiple doc types that mostly follow the same process, you should think about creating a single batch profile to hold all the doc types. With this setup, you can then use permissions to give users access to their specific doc types. Furthermore, within the workflow designer you want to break your workflow logic into common processes, shared by all doc types and specific doc type sub-flows. If you find that you need to create too many sub-flows, re-evaluate the relationship between a batch and doc types and see if you can fix the problem.
The goal is to create unique workflow processes so that system maintenance is easy; and one way to deal with that is to avoid duplicating batch profiles that are performing the same tasks.
Sometimes you need to insert a data to your database. Here is the safer way to insert a row using SQL parameter.
Passing parameters to SQL prevents you build dynamic SQL statement. Building a dynamic SQL statement is a security risk such as SQL injection.
Here is the sample code for insert statement using parameters.
public void InsertRowToDatabaseUsingParams()
//create SQL connection.
using (SqlConnection conn = new SqlConnection(connectionString))
//open sql connection.
string sqlCommand = "Insert into TestTable (column1,column2) Values(@column1,@column2);";using (SqlCommand cmd = new SqlCommand(sqlCommand, conn))
//add column value to parameters of SqlCommand
SqlParameter param = new SqlParameter("@column1", SqlDbType.VarChar, 50);
param =new SqlParameter("@column2", SqlDbType.VarChar, 50);