By Scott Percy on
Wednesday, July 09, 2008 4:18 PM
Sarah and I were on vacation this past weekend in Charleson, SC. We stopped in at this local seafood resteraunt called Hyman's Seafood for a bit of lunch (it's a great place, and if you're in the area you should go). In the sweetner tray at your table, there are these little cards that have different things on them. Most of them are pretty funny - a woman-speak translation guide for men, definitions of success at different stages of your life, etc. The one that really caught both of our attention was one which taked about attitude. Basically, it said that attitude is the most important quality in a person. It affects everything you do and say, and (more importantly) how you handle different situations.
I never really considered it, but I believe this is true. In business (and in life, really), your attitude says a lot about you. If you've got a defeatest attitude, then you're never going to g ...
Read More »
|
By Scott Percy on
Thursday, July 03, 2008 7:49 AM
...change it. Technically, I'm talking about Visual Studio templates, but apply that sentiment however you see fit.
I'm a big fan of adding some common comments to my code when I create class files, and up until now, I've just been adding them manually. I knew the VS had templates that it was using, but I didn't quite know how to use them properly, let alone find them. That is, until I ran across this article:
http://www.dev102.com/c/how-to-get-visual-studio-to-create-new-classes-public-by-default/
The point of the article is changing the templates to make classes public by default, which is definatly a good change. However, once you're in the template directory, the sky is the limit.
That's all for now. Have a safe and happy 4th! Until ne ...
Read More »
|
By Scott Percy on
Friday, June 20, 2008 12:14 PM
As Gordon and I were working on a project together, we noticed that the version of an assembly we had set up was not the one that was being used in the application. We use a number of third party assemblies and controls, so keeping track of a specific version is crucial (especially, when that assembly references specific versions of other assemblies). Apparently, when you set up a reference to an assembly by selecting a file on your file system, Visual Studio may not choose that file when building. Actually, it only looks for that file based on the path as a second to last resort (the last being looking in the GAC). In fact, if you look at the properties of a referenced assembly, you'll see the "Path", but if you look at the XML of the project file, the property is called "HintPath". So, it's basically saying, "if you really can't find this file anywhere else, look here" instead of (what I thought it meant) "this is ...
Read More »
|
By Scott Percy on
Monday, June 16, 2008 11:39 AM
Welcome to my "professional" blog. I'm going to make a concerted effort to actually blog things here. So, stay tuned for some more interesting content.
If you're interested, you can check out my "personal" blog at www.scottlpercy.com.
I use "professional" and "personal", since the two usually mix and can be interchangeable. :)
Anyways, until next time...
|