This has been driving me nutty for years in C#...

...but I finally figured out how to prevent the damn Visual Studio IDE from inserting asterisks into EVERY DAMN LINE of comments I put in a C# file (guess I should have Googled this.)

Simply disable:

Text Editor > C# > Advanced > Generate XML documentation comments for ///

I know, bizarrely unobvious considering there are a myriad of settings for comment templates where you basically specify 'do not do anything when I create a comment' which are blithely ignored by this #$)(#@$* setting.

I hope this makes someone else's day better like it did mine :).

I guess this is where I lean...

My Political Views
I am a center-left moderate social libertarian
Left: 1.1, Libertarian: 3.06

Political Spectrum Quiz

If you need to see the MSJVM console in IE7...

...then there are two things you need to do (or you may be able to skip step #1 and proceed directly to step #2 depending upon your current settings.)

(1)Go to the menu bar (enable it if you've hidden it) and choose Tools|Internet Options|Advanced, scroll down to "Microsoft VM" and enable "Java console enabled". You need to close and re-open your browser after this.

(2)When running an applet, go to the menu bar and choose View|Java Console (it should be the item right after 'Full Screen' on the menu.)

Hope this helps people testing applets on the MSJVM like I am currently.

A little bit of magic from Fernando Torres...

Enjoy! (Benayoun's pass wasn't too shabby either)

If "Open in New Window" is not working...

...for you or "Open in New Tab" with IE8, it turns out that there's a strong likelyhood that (for some unknown reason) the installation forgot to register a particular component so:

(1)Open a command prompt as Administrator
(2)Type 'regsvr32 actxprxy.dll' and press Enter.

You should get a small dialog popping up telling you that the DLL was registered properly.

Now try IE8 again.

I cannot fathom how Micro$oft has not found and eliminated this problem in IE8. It has existed since the early betas. Ridiculous.

Annoying issue with Eclipse...

...for some reason you can't really export/import your preferences between installations of Ganymede (a version of the Eclipse IDE), and I've been using it on several machines lately and having to set all kinds of crap up to be the same manually. This wouldn't be much of an issue except that the options are spread out rather willy-nilly in the application (although that is likely a residual of the very plugin based architecture.) So, I finally tracked down where the most annoying options for me to setup are located - syntax coloring for Java (your annoyances will likely differ :).)

After looking all over the place for them, I finally found them stored with each work space, not as settings for the application itself - weird (to me...)

Anyhow, for syntax coloring there are two files you want to copy into your workspace's folder in order to equate them to those in another folder, the folder in question being:

<Your Workspace>\.metadata\.plugins\org.eclipse.core.runtime\.settings\

org.eclipse.jdt.ui.prefs
org.eclipse.ui.editors.prefs

Update to services in Android...

...it turns out that what you really should do, if your code is in separate projects, is to declare a global (I presume) service moniker like this (in your service's manifest):

<action android:name="com.android.TestService.TEST_SERVICE" />

Then, change the method by which you call startService to call like this:

startService( new Intent( "com.android.TestService.TEST_SERVICE" ) );

NOTE: The argument is a string, which is the key. (Don't forget to change your invocation to stopService if you call that as well.)

Google might want to think about software less for tinkerers and more for real software engineers who will need to organize their code and look for opportunities to re-use, especially regarding services, and mention in their documentation that they recommend you add this naming schema to your service manifests for good reason. I'm just glad I noticed it in the remote services sample code.