Ah, of course. Thank you so much.
dino t socrates
Posts
-
Enum.GetValues missing -
Enum.GetValues missingSo far, I've been able to find a workaround for any missing functionality in Silverlight, until now. Anyone have any idea how I can get all of the values of an enumeration? And please don't suggest that I iterate from 0 to X and use the IsDefined method - that's simply not a practical solution. Thanks in advance! Terry
-
VS2008 stability [modified]It's definitely not just you. I'm finally learning ASP.NET after years of straight C# and Windows Forms programming, and VS 2008 crashes on me all the time - up to a few times a day sometimes. I have no idea how stable VS 2005 was when it came to ASP.NET, but I could probably count on one or two hands how many times VS has ever crashed on me before doing ASP. Terry
-
What do you think?When my company started working with a third-party C# library a year or two ago, we noticed underscores for all the private fields. Some of our developers started doing the same thing and while I was a little skeptical at first, I decided to give it a try. It didn't take me very long to notice some really nice benefits to using them and now I don't think I will ever go back. In fact, we have since made it a "highly suggested" guideline for our developers, with nothing but praise for it. Here are some of the niceties I can think of: 1. Immediate differentiation between member fields and local/parameter variables. 2. As a result of #1 above, there is never clutter or confusion by needing to qualify member fields with the 'this' (or 'Me') keyword when setting them with local/parameter variables of the same name (typically done in constructors). 3. All private fields get grouped in Intellisense. With all that being said, I don't really understand how it makes reading code a pain. I think it does maybe take a little getting used to, but none of our developers have mentioned any problems with readability. Quite the contrary. Terry