Building application firewall for SharePoint site will never been so easy. With Azure App Service we can quickly create public facing application firewall using IIS Application Request Routing and protect SharePoint web site in internal network. In this scenario, you will :
Create Azure App Service to serve as Reverse Proxy Register custom domain in Azure App Service Forward request from public URL to SharePoint internal URL The steps:
Using CI/CD pipeline in Visual Studio Online or Team Foundation Server, we can build and release our code easily to target server. However there is requirement that the target server must be prepared for remote deployment from the Agent server or we must install Agent inside the server. For many organizations, this requirement can be configured easily - however there are some organization that does not allow remote deployment or installation of agent.
Last month, I had to reinstall my laptop because of disk failure. Today, when I try to compile my SPFx (SharePoint Framework) project, I encounter “phyton2” not found exception. In fact, when I read the exception it was thrown by gyp npm component. This component apparently requires phyton to be installed . I can not find anywhere in SPFx documentation, the instruction to install phyton - although this will be triggered by the tooling.
Cross site forgery is also known as one-click attack or session riding and abbreviated as CSRF or XSRF (see Wikipedia - https://en.wikipedia.org/wiki/Cross-site_request_forgery). It is outlined in one of OWASP Top 10 security high vulnerability checklist - hence every developer must be aware of how to prevent this attack from their code. If you browse to SharePoint application page inside hive folder, you will see following line: this particular control will actually provide form digest which is set of token strings that has been generated by server for the requested page.
I will close this year activity by moving my wordpress hosting from JustHost to Azure. I am using JustHost introductory offer USD 3.95 / months for the past 4 years, but unfortunately I can not get that price anymore. They renewed my plan a month before ends, with new price USD 9.49 / months. The monthly subscription seems just a cup of coffee, but JustHost will charge 4 years in advance totalling USD 455.
One day I have a requirement to provide list item purging from SharePoint. Deleting small list item may not be a problem, however deleting huge items from a list will impact the whole SharePoint farm performance during the operation. The issue is caused by the locking mechanism that occurs during the delete operation. Additionally the deleted list item will be stored to recycle-bin of the site, hence it will contribute to another performance impact.
This is 5 part blog series, on how to “Cost Optimization for On-demand Private Build Server for SharePoint”. Although I specifically write this for SharePoint’s build server, however the concept and ideas is also applicable for anyone looking for optimizing their cost running private CI/CD (Continuous Integration/Continuous Delivery) in Visual Studio online. The series in these articles are:
Part 1, Introduction to Visual Studio Online Build and Release Agent Part 2, Cost Analysis and Optimizing Cost Part 3, Step-by-Step Creation Private Build Server for SharePoint Part 4, Azure Automation Service Part 5, Integrates Azure Automation Service in Build Pipeline In Part 2 In Part 2, we know that the cost will be much cheaper if we choose Azure VM RI (Reserved Instance) compared to Pay As You Go.
I have met many SharePoint developers and administrator that can not provide detail information of the error. Most of them do not know, how to enable SharePoint’s debug mode. There are lot of guidance in internet, but I will just write here as this is very basic information that every developer or SharePoint administrator must know! In order to enable SharePoint’s debug mode, 3 places that you need to modify in web.
This is 5 part blog series, on how to “Cost Optimization for On-demand Private Build Server for SharePoint”. Although I specifically write this for SharePoint’s build server, however the concept and ideas is also applicable for anyone looking for optimizing their cost running private CI/CD (Continuous Integration/Continuous Delivery) in Visual Studio online. The series in these articles are:
Part 1, Introduction to Visual Studio Online Build and Release Agent Part 2, Cost Analysis and Optimizing Cost Part 3, Step-by-Step Creation Private Build Server for SharePoint Part 4, Azure Automation Service Part 5, Integrates Azure Automation Service in Build Pipeline In Part 1 In Part 1, I have written about Visual Studio Team Services, build agent and private build server.
This is 5 part blog series, on how to “Cost Optimization for On-demand Private Build Server for SharePoint”. Although I specifically write this for SharePoint’s build server, however the concept and ideas is also applicable for anyone looking for optimizing their cost running private CI/CD (Continuous Integration/Continuous Delivery) in Visual Studio Online. The series in these articles are:
Part 1, Introduction to Visual Studio Online Build and Release Agent Part 2, Cost Analysis and Optimizing Cost Part 3, Step-by-Step Creation Private Build Server for SharePoint Part 4, Azure Automation Service Part 5, Integrates Azure Automation Service in Build Pipeline Introduction to Visual Studio Build and Release Agent Many of you might already know about Team Foundation Server (TFS) the on-premise source code management, work item management, reporting, and developer’s collaboration tools.