rachelreese's blog - All Comments

re: Registry Cleaners

John Smith — Thu, 12 Nov 2009 10:00:10 GMT

<a href="http://www.download-registry-cleaners.com">Registry cleaners</a> scan the PC registry and delete outdated entries that are not in use anymore and remove faulty uninstall process. Moreover also detect and remove the embedded keys that are generated in the registry by malware programs like Trojans, viruses and spyware etc.

re: Registry Cleaners

Jennifer — Mon, 17 Aug 2009 12:55:17 GMT

This is a nice website were u can download registry cleaners software to remve errors & invalid entries on operating system.

re: Microsoft Application Blocks

SticK — Wed, 14 Jan 2009 03:05:54 GMT

the links are broken

re: Upcoming Phoenix Events!

Jeff Moriarty — Tue, 28 Oct 2008 20:59:06 GMT

Thanks for the event postings, Rachel! Both Ignite and PodcampAZ should be amazing, and make for one heck of an interesting week in Phoenix!

re: OrElse and AndAlso

pelesl — Fri, 30 May 2008 17:10:06 GMT

Regarding array declaration:

I agree that the array declarations "adding" an element is confusing at first. I was writing a serial communication program and the extra element was screwing things up.

I believe the reason they did it is because then you can use either 1-based arrays or 0-based arrays easily. That means all us 0-based people have to remember to declare the array with the index of the last element in parentheses, rather than the size.

Regarding AndAlso and OrElse:

I recently discovered these, after I wrote a whole program with And's and Or's everywhere. I don't think they are fully interchangeable. There are some situations where AndAlso is essential. For example:

If listbox.SelectedItem <> nothing AndAlso listbox.SelectedItem.ToString = "the item"

is an absolute must if you have Option Strict turned on, because if you don't, this will generate an exception if the first test is omitted or AndAlso is replaced with And (because you'll get a null reference exception on the "ToString")

Listbox behavior, in this respect, is quite annoying. If you start using AndAlso and OrElse from the beginning, you avoid a lot of problems like these if you suddenly switch to Strict = On (like I did).

re: Fixing WCF/WPF VS 2005 Extensions installation after installing VS 2008 or .NET 3.0 SP1

Andy — Mon, 12 May 2008 09:05:05 GMT

many thanks I had this problem and it fixed it cheers.

More Google Magic!

TrackBack — Wed, 11 Aug 2004 07:54:00 GMT

More Google Magic!

TrackBack — Wed, 11 Aug 2004 06:25:00 GMT

re: Reflection

Charles M. Carroll — Tue, 10 Aug 2004 21:50:00 GMT

http://www.learnasp.com/freebook/learn/cs_firstlib.aspx
has reflectin sample like what you want as well.

re: OrElse and AndAlso

Rhorc — Thu, 29 Jul 2004 17:46:00 GMT

Until .Net arrived I always wrote short-circuit'd code statements.

I would take the original example;
If myInteger=4 And myString=“Hello” then
CallFunction()
End If

And write;
If myInteger=4 Then
If myString=“Hello” then
CallFunction()
End If
End If

It always resulted in better performing code.