I want to add a text box into a template column during runtime. I can add a
boundcolumn but not with template column. I allow user to type in something
in the textbox in the datagrid. I wanna know if it's possible
public void AddNewColumn(DataGrid grid,string headerName)
You shouldn't be trying to display encrypted blocks in a TextBox - it's always binary until encoded in base64 or something else (base64 is most common, though).
See the ToBase64Transform and FromBase64Transform classes in the .NET base class library. The class documentation also includes a couple of good samples for how to use these two classes. You should then have no problems displaying cipher text.
Just as examples, consider PGP (http://www.pgp.com[^]): in order to send plain-text cipher text as email (it's primary use is for communications) it must be encoded. This is currently done using base64. Or when you sign-up for an SSL certificate your request must be sent using a base64 encoded public key.
I've built a fairly complex stored procedure that has a couple of selects in it that are only functional while I'm only interested in reading the resultset from the last select.
Now when I fill my dataset, apart from retrieving useless data from the database, I have to acess my data doing something like ds.Tables.Rows
I have thought of two possible solutions even though I don't know how to implement any of them.
1. Have the stored procedure return only the last recordset. If this is possible I'm missing some T-SQL command. Anybody on this?
2. Give a name to the table that I'm interested in reading so that I could access it disregarding it's index like ds.Tables["MyRecordset"].Rows
This is much more elegant than accessing with numeric index bacause if I change the stored procedure I don't have to change my code.
Anyway how does one give a name to a table from a stored procedure?
If you are using a DataAdapter to fill you dataset you can always create a strong typed dataset which allows you to access the data as:
dsMyStrongType.MyStrongTypeRow dr = myDs.MyTableName[row];
dr.MyField = something
Makes life a lot easier and less apt to have typos on field names (plus you get Intellesense). Just build your DataAdapter in the editor and the right click on it to generate a dataset. If your stored procedure returns multiple results it will build a table by name for each. You can also select the table mapping property to call the tables anything you like.
When using DataSets, try designing a strongly-typed DataSet by using the DataSet designer in VS.NET (there are other ways and tools, too, but I present the way in VS.NET). Right-click on your project or subfolder and select Add New Item. Find DataSet, give it a name, and click OK.
You'll see a component designer screen. Right-click to add elements (tables) and each element has rows and their types (the columns). You can even add relationships and primary keys. Just play around with it a little.
You can even use the Server Explorer if you have a database connection to drag-n-drop tables or stored procedures which returns tables to generate these automatically.
When you fill the strongly-typed DataSet, your DbDataAdapter derivative (like SqlDataAdapter) has to be configured to map the tables. This is done through DbDataAdapter.TableMappings and can easily be configured by using the data adapter designer in VS.NET as well.
Finally, you don't even need to use strongly-typed if you use the TableMappings property mentioned above. When selecting multiple result sets, the sequence of table names is "Table", "Table1", "Table2", etc. If you map these to other names, you can use DataSet.Tables["nameOfTable"].
I recommend using strongly-typed DataSets, though. You can easily refer to columns by name and don't have to worry about casting since those named rows return the appropriate Type.
I must have just skipped by it, but when I was checking out the 'switch' keyword, I noticed that C# has a "goto case" fucntionality inside of a switch block to go to another case statement. Not that I would have a need for it often, but if I do it is there
Funny thing is though, since moving to .NET I seldom use switch. Just have not had a lot of need for it.