SharePoint developers and IT pros are familiar with the “sign in as different user” menu option in SharePoint 2010. However, in Microsoft SharePoint Server 2013, you will notice that this menu option is missing.
Passwords are the first line of defense against cyber criminals. They are the most vital secret of every activity we do over the internet and also a final check to get into any of your user accounts. If you’re a web developer, you’ve probably had to make a user account system. User account databases are hacked frequently, so you must do something to protect your users’ passwords if your website is ever breached. Password hashing is the best way to do this.
Most Linux systems have a default bash prompt in one color that tells you your user name, the name of the machine you’re working on, and some indication of your current working directory. This is all useful information, but you can do much more with the prompt. All sorts of information can be displayed. You can even change the colors either to make it look interesting, or to make certain information stand out. You might also want to customize your bash prompt if you have difficulties using the terminal because the prompt isn’t visible enough.
When we write code to handle the ItemUpdating or ItemUpdated list item events, we may sometimes need to take different actions based on whether the event was triggered by a regular item update or by a version restore operation.
Say you have a SharePoint workflow which runs whenever a list item changes (ItemUpdated). You also have some custom code to do some manipulation on the same list item at the end of which you need to perform an item update using one of the SPListItem update methods: Update(), Systemupdate() and UpdateOverwriteVersion(). You will quickly notice that this update will trigger another instance of the workflow for this item once the current workflow terminates. You have just hit an infinite loop.