When working with InfoPath, there are many scenarios where you may need to modify InfoPath XSN files. These include: fixing errors, changing web service urls, tweaking file names or SQL connection strings, removing/editing some value(s), etc. Thankfully, since InfoPath XSN files are just containers (cabinet or .cab files) of many other files, we can use built-in windows tools to break them open, make our changes, and then repackage them. This article explains the full process with an example.
My previous four-part series described how to set up a SharePoint development farm. Now, what if we want to take things a step further and configure our SharePoint farm to allow sending of outgoing emails? This article discusses everything you need to do to make this possible – from installing and configuring the SMTP service, to defining outgoing email settings in SharePoint Central Administration. I provide code examples as well.
CMD (or batch) script that helps you quickly reset the SharePoint timer service, the SharePoint administration service, and Internet Information Services (IIS). Works without modification for On-Premise versions of SharePoint 2010, SharePoint 2013, SharePoint 2016, and SharePoint 2019.
Businesses around the world are using Intranets to manage documents, increase efficiency, and improve communication. But many people are still confused about exactly what an Intranet is and how it differs from the Internet. In this article, I won’t bore you with a detailed comparison of both. We all already understand what the Internet is and what it does. Instead, I will concentrate on differences that will clarify what an Intranet is and why it is useful in workplaces.
All versions of the SharePoint user interface provide an option to change the title (or display name) of a list or library. Changing SharePoint library URL (or internal name), however, is not exactly very intuitive. We will discuss the process in this article.
This article discusses how to create a timer job for deleting orphaned users (SharePoint users that are deleted or disabled in AD) using Visual Studio. I have tested this solution on both SharePoint 2016 and SharePoint 2010. So, it would of course also work for SharePoint 2013.