Post questions, tips, tricks, and suggestions here

9 Responses to Post questions, tips, tricks, and suggestions here

1. szulak says:

   August 1, 2013 at 5:19 am

   I have write nice article about caching object in C#. You can find it here:
   Caching objects in C#

   Reply
2. Fernando says:

   October 13, 2015 at 1:50 pm

   This is one question, and sorry to bother you. I’m trying to develop a Radial Menu for a customer. I cannot see how to check if a point is inside a Pie.
   I appreciate any help.
   Best regards. Fernando

   Reply
   • RodStephens says:

     October 14, 2015 at 9:38 am

     See this post:

     Determine which pie slice is under the mouse in C#

     Reply
     • Fernando says:

       October 15, 2015 at 8:57 am

       Thank you so much, Rod.

       Reply
3. Ello says:

   February 8, 2018 at 10:14 am

   If you could do a post on winmm.dll in PInvoke.net. Specifically the timeBeginPeriod,timeSetEvent,timeKillEvent, and timeEndPeriod methods. Having a hard time understanding how to use them. Some background:

   The precision of multithreaded timers depends on the operation system, and is typically in the 10-20 ms region. If you need greater precision, you can use native interop and call the Windows multimedia timer. This has precision down to 1 ms and it is defined in winmm.dll.

   Reply
4. Ello says:

   March 24, 2018 at 5:34 pm

   Can you explain when I should WPF vs Windows Form?

   Reply
   • RodStephens says:

     March 25, 2018 at 9:32 am

     This is mostly a matter of style. WPF provides a rich set of appearances. It allows you to customize how a particular kind of control. It also includes features that let you animate properties. For example, you could make controls move or change size when the user clicks on something. You can also customize the way some controls work. For example, you can change how and where a ListBox displays its values. WPF also has a really easy-to-use media control and some nice layout controls.

     The downside is that WPF is much slower to load and modify in Visual Studio and it’s much harder to make it do the fancy things that make it desirable.

     Both use the same C# code behind the scenes. (That’s why most of the examples on the C# Helper web site are in Windows Forms. They use the same code and Windows Forms is faster and easier.)

     When I just want to get something done that works, I use Windows Forms. If I want to make something look really glitzy with lots of animation (like some of the fancier web sites), I use WPF.

     Microsoft’s original line was, “Old programs would be maintained in Windows Forms and all new development would be in WPF.” I don’t think that has happened. All of the early adopters have moved to WPF, but I think a lot of people are still using Windows Forms. In particular, if you were building a large multi-person project with lots of code behind, would suggest prototyping in Windows Forms and then porting to WPF because Windows Forms is so much easier.

     I hope that helps.

     Reply
     • Ello says:

       March 25, 2018 at 3:56 pm

       So what your saying is that it would still be wise to learn Windows Forms?

       Thanks your feedback. Greatly appreciate it

       Reply
       • RodStephens says:

         March 26, 2018 at 8:56 am

         My thought is that you would ideally learn Windows Forms when you are learning C# so WPF doesn’t slow you down. Then after you have some practice with C#, you can pick up WPF.

         Also note that experience with C# will help you with C++ or Java. Windows forms may help a little, but I don’t think WPF will help you much with other languages.

         Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.