Comments by Kubajzz (Top 40 by date)

It would increase your chance to get an answer if you could provide the piece of code that made it work in WinForms and the piece of code that doesn't work in WPF.

DrawingBrush allows you to combine multiple geometric shapes together and paint each of the shapes with a different gradient brush. I believe that is enough to create the texture you need... Both ImageBrush and DrawingBrush are kind of heavy-weight to create such a simple effect, but I'm afraid there is no other way.

I would have given you the links if I had them...

...and I assume you expect somebody to provide the complete solution here. No, it doesn't quite work that way. Not speaking about the fact that demanding code without even saying "please" is simply rude.

Yes, when looking at the front side of the triangle the points must be assigned in counter-clockwise order.

Reason for my vote of 1:
does not answer the question at all.

Just create an Image control and a Viewport3D control and put these 2 on the same position.

Something like:

<Image ... />
<Viewport3D ... />

And make sure the Viewport3D control is placed over the Image control. There is nothing more to explain here...

Actually your last sentence is not exactly true. It will compile, but it will not execute, because an exception will be thrown at runtime... Good answer anyway, have my 4.

Oh, that's another story... See this article for some information on embedded files in a WinForms assembly: http://www.codeproject.com/KB/audio-video/PlayWavFiles.aspx

Yes, but if your Excel file is embedded in the assembly, then you won't be able to edit it. As far as I understand you need to be able to edit the Excel file, so embedding is not an option.

If you keep the file separate, encrypt it and change its name, it will be visible to the user, but the contents and the purpose of the file will be hidden and your program will be able to edit it.

Reason for my vote of 1
Yet another homework? Show some effort first, then there will be many people willing to help you.

Your question is the same like "Why do XML tags start and end with '<' and '>' instead of '{' and '}'" or "Why is C# case-sensitive"...

It's because it was designed that way. You may not like it, but that's all you can do about it.

Every array implements the IEnumenrable interface and therefore the foreach statement should work. Otherwise your code wouldn't even compile. The problem must be somewhere else... Unfortunately I can't give you more help.

Reason for my vote of 1
What an answer!

This sounds pretty weird. Are you compiling your project using debug configuration, without optimizations disabled etc? A line of code can't just get skipped, especially a control-flow statement such as foreach. Maybe the debugger steps over the line, but that doesn't mean that the line is not executed.

When you are asking for help make sure you don't make it difficult for those who are willing to help you. The link you posted contains a lot of advertisements including pop-up windows. I originally wanted to leave the page instantly, but in the end I decided to give you a chance and downloaded the .zip file... And the file was corrupted. Do you really expect to get any help?

I sugget posting a few screenshots of the game, that would increase the chance that you will get an answer.

If I posted my answer, it would be very similar to what Pallini and Sandeep Mewara posted. There is no need to have duplicate answers here. However, the fact that I didn't post my answer doesn't mean that I don't have the right to point out that your answer is wrong. (huh, what a wonderful sentence!)

I don't want to start an argument here, so I apologize if I spoiled your day... Bye

Reason for my vote of 5
The best answer in my opinion

Reason for my vote of 1
Voting 1 to everyone else's replies seems to be a wrong thing to do, especially because your reply is not correct.

If NullReferenceException occurs at the following statement: "SmsPdu smsrec = message.Data;", then it is most probably because "message" is null. Again, I have no idea how to fix it since I have no knowledge of your application and the library you use... Use the debugger to track the state of your variables and I'm sure you'll find the source of your problem.

Huh... I would like to answer this question, but it doesn't make any sense.

Reason for my vote of 2
Your method is not efficient. There is no need to read the whole file if you read it line-by-line... The following is better:

private string ReadLine(int lineNum) {
int count=0;
using (StreamReader sr = new StreamReader("C:\SampleFile.txt")) {
string line;
while ((line = sr.ReadLine()) != null) {
count++;
if (count == lineNum)
return line;
}
}
return null; // It might be appropriate to throw an exception here...
}

The ArrayList class was introduced in early versions of .NET long before generics were added. List(T) is a newer generic class that provides pretty much the same functionality. The advantage is that List(T) is type safe, therefore brings better performance and decreases the probability of various bugs...

I think you will never ever need to use ArrayList unless you need to work with an old version of .NET (older than 2.0).

You need to provide more information to get an answer... First of all, which technology do you use? WinForms? WPF? Silverlight? ASP.NET?

Reason for my vote of 1
Makes no sense...

Reason for my vote of 1
Answers should not be used to ask more questions... Anyway, search for "WPF Styles and Templates", that's what you need.

Reason for my vote of 5
Simply perfect answer

Reason for my vote of 1
This is not an answer, comments should be used for this stuff...

Reason for my vote of 3
A good solution, but far from perfect...

I know all that.

1. That's why there's a comment saying it's not a thread-safe way to raise the event. I only provided the simplest and most basic solution.

2. I know the method should be protected virtual according to the recommended practices. However, I'll say it again: I wanted to provide the simplest possible solution just to show the basics, because the guy who originally asked the question obviously doesn't know anything about events... That's why I ignored this rule.
You are right though that my OnSomeValueChanged method should take an EventArgs parameter (although it's useless) to keep the common pattern... Your solution is somewhat more complete.

Reason for my vote of 1
Your question is way too general... I recommend that you read a tutorial about datagrid and then, if you have a specific problem, ask a question here.

Reason for my vote of 1
This question does not make any sense and doesn't belong here since it is probably supposed to be a reply to an article (possibly this one: http://www.codeproject.com/KB/miscctrl/WinformsDirtyTracking.aspx)

Your question is too general... please specify which platform/technology you use (WPF, Silverlight, WinForms, ASP.NET...)