Using Overloaded and Static Methods

Yesterday, we looked at what a method is and the various ways to call them. Today we are going to look at what is called an overloaded methods. Let’s take a look at the System.String class (https://msdn.microsoft.com/en-us/library/system.string(v=vs.110).aspx). Take a look at the method for Replace.

The replace method has two implementations. If you proved two single characters, the first implementation is used. If you provide to strings, the second implementation is used.

PS C:\> $String = "You are number 1 in my book."

PS C:\> $String.Replace("1","2")

You are number 2 in my book.

PS C:\> $String.Replace("book","world")

You are number 1 in my world.

You can also utilize what are called Static Methods. Take a look at the documentation for System.Math (https://msdn.microsoft.com/en-us/library/system.math(v=vs.110).aspx)

The purple box is the icon for a method. The yellow ‘S’ means that it is a static method. In short, you can call static methods without first creating an instance of the object. In our previous example, we needed a System.Datetime object to call the AddSeconds() method on. With static methods we do not. I like System.Math a lot because it provides advanced mathematical functionality without having to write the functions myself. For example, cosine.

PS C:\> [Math]::cos(40)

-0.666938061652262

We access these methods by first casting for System.Math. The System namespace is already loaded in memory by default so you only need to cast for Math. We then provide 2 colons and then the method name. Many of these methods are overloaded, so pay attention to the different ways to implement them. They will save you a lot of time.

Comments

Sticky Key problem between Windows Server 2012 and LogMeIn

This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this. First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .

With the AD Recycle Bin Turned on, What Happens when you Create a User Account with a Password that does not meet the Password Policy?

This was an interesting observation from one of my Windows Server 2012 classes. While working with the AD Recycle bin in a lab, one of my students discovered some interesting accounts that were created. When he created user accounts that did not meet password complexity requirements, an account is temporarily made and then deleted. When a new password is provided that meets the password requirements, then a new account is made. We discovered this in two places. First off in the Active Directory Administrative Center. This is what caused the initial confusion. Take a look. This is in the Deleted Objects OU. You can see multiple deleted accounts for Test2 and one for Test3. Test3 is a valid, functioning user account. Using the PowerShell command Get-ADObject –IncludeDeletedObjects –Filter * –Properties ObjectSID we can see that indeed, two accounts were created, with one of them deleted. Notice the RID portion of the SID is different. ...

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction. The code below is correct. My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...

Jason Yoder, MCT

Search This Blog