This has been asked before, and as I told the previous person, you should consider using Label controls below the DataGrid. If you have a data-bound DataGrid and programmatically add a row, you must do so to the DataGrid.DataSource, which will add the row. If you then update that data source (say, to a database or XML file), it will contain that summary row. This is hardly what you want, I assume.
So, just use some values below it. That's what we do in our application, and there are many other benefits as well. First, it separates the summary of columns making it easier to see, and it doesn't scroll or resize like a DataGrid could, thus hiding certain summations. Second, one rarely needs to summarize ALL fields (for example, how would you summarize a name field for a person, company, etc.?), so just include enough labels to summarize what you need.
To summarize columns, just enumerate the rows and keep track of what you need to, then assign that value (or whatever) to a label that shows the value (or, if you use one label for the text label and value, use String.Format or something to assign the "Label: Value", "Label=Value", or whatever format to the Label.Text property).
That utility sucks. Use a good - and free - one like NDoc[^]. A lot of people and companies use it. It can generate both HTML Help and Help 2 documentation (the latter is what VS.NET, MSDN Library, and a couple others use now), as well as a few other formats. By default, private and internal members are documented, but you can opt to include or exclude these individually (as well as protected and public members...and many, many other options!).
Thanks a lot for the info. i was trying to build the .sln provided by the
NDoc community but couldn't add the MSHelpCompiler.dll to the references.
Anyways, i installed it and could use it now; it's pretty cool.
thanks once again. if u have any idea of how to get the dll i mentioned plz
let me know.
i was busy with some thing else so couldn't let you know abt this early.
Just use the 1.2 installation at http://ndoc.sourceforge.net/download.html[^]. We're always updating features and testing new things, and building any open-source project with the latest non-stable code is at your own risk. I even use the installation for my actual documentation and I actually write code for the project (though it's been a while).
Look over the PowerPoint and Office APIs. You could use VBA in PowerPoint to write a macro that does something like this. If you want to read-in the PPT from your program, you'll have to interop the PowerPoint and Office assemblies (there are PIAs - primary interop assemblies - for Office apps on Microsoft's site). You should then read the Office Programming documentation. If I remember right, you can also use the Microsoft.VisualBasic.Compatibility assembly (even from C# - it's just IL after all) to use the IPicture (or is it IStdPicture? ...don't remember) if PowerPoint still uses that.
There was no ambiquity, I knew exactly what you were talking about. What I'm saying is that you should read the documentation for the property type that the image/picture properties return. That may have a Save method or something. Keep in mind, however, that you can't just serialize the type returned - you have to serialize the image represented by the property type, which is implementation specific. For example, I'm pretty sure you can save an image to a file but you might have to read that in and then base64-encode it. It probably supports writing to a stream, but this is a COM IStream, not a .NET Stream which works differently (so you'd have to define a COM-like IStream and implement that, perhaps wrapping the .NET Stream object).
What I can't figure out is how the Shape ties into this. Just looking at the interop assembly, it would seem that a picture is translated to a Shape, which might not preserve the actual image format (so, if you try to create an Image from a stream, it wouldn't work because it's no longer a JPG, BMP, GIF, etc.).
All I can say is read the PowerPoint and Office object model documentation. I couldn't find much, but I'm not sure I have the PowerPoint programming documentation installed (although I thought I specified a Complete install).
This is seema..I am intended to design user interface in C#.net for some hardware.For that I have to draw 24 filled rectangles on the form.I can do it simply using FillRectangle().But my aim is to draw one rectangle using some user defined function then when it will appear on the form then i want to copy it and past it on the form itself to creat more 23 rectangles and set there properties according to my wish(like length width and ID).Again I have to do specific event like mouse click event on those rectangles....So can anyone please suggest me how to do it?...I went through many site but not getting exactly what I want.PLZ PLZ tell me if anyone knows....
Your question is not clear for me,You want those Rectangles for some copy/pasting,width prperties.... why don't you simply use TextBox. But what ever your task is,youcan create a Windows Control and derive it from Control or TextBox class,and add properties in that or customize their existing properties,then it is easy to have 24 of it and set properties for each of them.
Den2Fly wrote: 1. How can I protect my code inside the .dll assembly (MSIL) from being decompiled and visible? there are some softwares out there that can reverse engineer a compiled .dll into a good source code.
Compilers that target the CLR ALL produce Intermediate Language, or IL. This - like Java bytecode - allows the system to JIT the IL to native code and execute it, so that it can be run on any OS (Microsoft's problem with .NET is that it relies too much on native OS resources, but it does provide a consistent UI). The Microsoft .NET Framework SDK even comes with a disassembler, ildasm.exe. For those of us who can read IL, we don't even need decompilers like .NET Reflector[^] (though it is nice at times!). There are just as many problems that can output this source code as well, although I have yet to see one that does an impeckable job with more advanced source code (using all the tricks of the languages).
All you can do - which is true of any program in any language - is make it hard and, therefore, costly to do so. I remember the words of Bruce Schneier with questions like these, who basically says that anything is crackable - it's just a question about the cost of resources to do so.
Make your program work well and hide your important code in complexity, or write native DLLs and P/Invoke or interop (use COM to make this easy) the functions and components in those native DLLs. Keep in mind, though, that they too can be decompiled (though decompiling C/C++ libs is more difficult, more expensive, and less correct than with IL and bytecode).
You can get obfuscators to obfuscate private members, but for every obfuscator there is a de-obfuscator (and they've really never stopped me - and I'm sure others - anyway, from seeing how something is done for academic reasons).
With ildasm.exe I can see functions and variables that are used in my assembly for each lines of codes,but not the VALUE of them. Does decomling with other tools are the same or they can show the value of them too?,for example Can I store a password in my codes in a varibale?
It does show the value, either in the static constructor (.cctor) or in an instance constructor (.ctor), depending on where you initialize the fields. So no, you shouldn't store a password in your code if it protected anything important. Same goes for private keys you use to decrypt values. If you store the private key, someone need only extract it and decrypt your values, whether they are in IL or your app.config (or proprietary) file.