ps1 cannot be loaded because running scripts is disabled on this system

This issue happened when the user having an undefined ExecutionPolicy.

Apply below command on the terminal it should solve the issue:

Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy Unrestricted

Sign-out in SharePoint

The Sign-Out feature is disabled in SharePoint, and it's very important specially when you are using windows authentication to log-in the site, you can use the below link to clear the current user session:

YourSite/_layouts/closeConnection.aspx?loginasanotheruser=true

Install and Configure the Workflow Manager

 

Copyright for:

https://potifar5000.wordpress.com/2015/08/19/install-and-configure-the-workflow-manager-for-sharepoint/

SharePoint Server 2013 brings a major advancement to workflow: enterprise features such as fully declarative authoring, REST and Service Bus messaging, elastic scalability, and managed service reliability.

SharePoint Server 2013 can use a new workflow service built on the Windows Workflow Foundation components of the .NET Framework 4.5. This new service is called Workflow Manager and it is designed to play a central role in the enterprise. Processes are central to any organization and workflow is the orchestrator of processes.

The SharePoint 2010 Workflow platform has been carried forward to SharePoint Server 2013. All of your workflows that were built by using SharePoint Server 2010 will continue to work in SharePoint Server 2013.

In SharePoint Server 2010 the workflow engine installed automatically with the product. This continues to be the case with the SharePoint 2010 Workflow platform in SharePoint Server 2013. If you simply install SharePoint Server 2013 and do not install and configure Workflow Manager then you will have a nearly identical experience with building workflows as you did in SharePoint Server 2010.

The SharePoint 2013 Workflow platform only becomes available to you, and your tools, after you download and install the new Workflow Manager service and configure it to communicate with your SharePoint Server 2013 farm.

SharePoint Designer 2013 includes new functionality designed specifically for Workflow Manager. In SharePoint Designer 2013 this new platform is known as the SharePoint 2013 Workflow platform. These new features include:

• A visual workflow development experience that uses a Visio 2013 add-in
• A new action that enables no-code web service calls from within a workflow
• New actions for creating a task and starting a task process
• New coordination actions that let you start a workflow built on the SharePoint 2010 Workflow platform from a workflow built on the SharePoint 2013 Workflow platform
• A new Dictionary type
• New workflow building blocks such as Stage, Loop, and App Step

Workflow Manager brings a new class of workflow to SharePoint Server 2013. Workflows built by using Workflow Manager can take advantage of several new capabilities. These include enterprise features such as:

• High Density and Multi-Tenancy
• Elastic Scale
• Activity / Workflow Artifact Management
• Tracking and Monitoring
• Instance Management
• Fully Declarative Authoring
• REST and Service Bus Messaging
• Managed Service Reliability
  [Source]

*This configuration is for HTTP only. The HTTPS configuration will be covered in later posts.

Preparation
Before you install the Workflow Manager, make sure that the corresponding SharePoint farm is up and running. Use the same setup user as you did for the SharePoint installation.

*Note that the below result is also applicable to Project Server.
Download WorkflowManager.exe here. Click on the WorkflowManager.exe to setup by a Web Platform Installer 4.5

*This is the latest version at the time of writing. The below steps will be identical when a new version is released.

Workflow Manager

Prerequisites for installing Workflow Manager

Installing the Workflow Manager

Choose Configure Workflow Manager with Default Settings (Recommended)

Complete fields to indicate SQL server and generate a Certificate Key

Created and Configured Service Bus farm, Service Bus gateway and farm management database

Workflow Manager, Service Bus 1.0, Execute ASP.NET iis Registration tool and Workflow Client were successfully installed

Service Bus and Workflow database were created

WorkflowMgmtPool and Workflow Management Site

Install Windows Azure SDK, PowerShell, Cross-platform Command Line Tools

Items Installed.

Register Workflow:

Open Sharepoint management shell as administrator:

Register-SPWorkflowService –SPSite “http://YourSQLServer” –WorkflowHostUri “http://YourSQLServer:12291” –AllowOAuthHttp

Installation done.

To test, open SharePoint designer and connect to the SharePoint Site:

To verify, create a new site workflow. If the SharePoint 2013 workflow option is listed, then the installation was a success:

And DONE!

Microsoft Edge built by "Chromium"

First Of All, what is Chromium?

Chromium is an open-source browser project that forms the basis for the Chrome web browser. But let’s take a little deeper look at what that means.

When Google first introduced Chrome back in 2008, they also released the Chromium source code on which Chrome was based as an open-source project. That open-source code is maintained by the Chromium Project, while Chrome itself is maintained by Google.

The biggest difference between two browsers is that, while Chrome is based on Chromium, Google also adds a number of proprietary features to Chrome like automatic updates and support for additional video formats. Google also took a similar approach with the Chromium OS, which is an open-source project that forms the basis for their own Chrome OS—the operating system that runs on Chromebooks.

Now, why Microsoft built the new edge using Chromium?

At first, the new name of Edge is "Edge Insider", and as Microsoft announcements that every things changed, and when we return to Edge Insider website we will know why Microsoft go with Chromium.

Microsoft tries to replace IE with Edge but it seems that this didn't meet them ambition, Microsoft has therefore launched a new product "Edge Insider".

I started using the new Explorer, and I hope it's a quantum leap already!

Visual Studio Code Shortcut

Ctrl + P	Quick Open, Go to File…
Ctrl + Shift + P	Show Command Palette
Ctrl+Shift+N	New window/instance
Ctrl+Shift+W	Close window/instance
Ctrl+,	User Settings
Ctrl+K Ctrl+S	Keyboard Shortcuts
Ctrl+X	Cut line (empty selection)
Ctrl+C	Copy line (empty selection)
Ctrl+Shift+K	Delete line
Ctrl+Enter	Insert line below
Ctrl+Shift+Enter	Insert line above
Ctrl+Home	Go to beginning of file
Ctrl+End	Go to end of
Ctrl+G	Go to Line
Ctrl+Shift+Tab	Navigate editor group history
Alt+Click	Insert cursor
Ctrl+`	Show integrated terminal
Ctrl+Shift+`	Create new terminal

For more commands, check the official document from Microsoft: keyboard-shortcuts-windows.pdf

TypeScript

To be a professional Angular developer, you must master the TypeScript language.

It's JavaScript language founded by Microsoft and it's open source language.

We should use it for Angular and to know more about it visit the below link:

https://www.typescriptlang.org/

creating a restful api tutorial with nodejs and mongodb

https://adrianmejia.com/creating-a-restful-api-tutorial-with-nodejs-and-mongodb/

Graphql - Best Resources

https://www.youtube.com/watch?v=xBAJ5nQkeiM

https://www.youtube.com/watch?v=S7ybWS7XLfs


https://www.youtube.com/watch?v=DUiIw7LJj1g

https://www.youtube.com/watch?v=dFKof6858nE&list=PL49CJpQOMjgw3DRvhiLvqGBAdubVQP3ux&index=5

https://www.youtube.com/watch?v=DNdMYeFWYcM&list=PL49CJpQOMjgw3DRvhiLvqGBAdubVQP3ux&index=8

The list is too large to save as a template. The size of a template cannot exceed 52428800 bytes.

By default, you can't save the SharePoint list when it's exceed 52428800 bytes, but you can increase the size by power shell as below:

stsadm -o setproperty -propertyname max-template-document-size -propertyvalue 100000000

Microsoft SharePoint Remote Code Execution Vulnerability

A remote code execution vulnerability exists in Microsoft SharePoint when the software fails to check the source markup of an application package. An attacker who successfully exploited the vulnerability could run arbitrary code in the context of the SharePoint application pool and the SharePoint server farm account.

Remediation:

The security update addresses the vulnerability by correcting how SharePoint checks the source markup of application packages.

Security Updates

Product	Article	Download	Impact	Severity	Supersedence
Microsoft SharePoint Enterprise Server 2016	4462211	Security Update	Remote Code Execution	Critical	4462155
Microsoft SharePoint Foundation 2010 Service Pack 2	4461630	Security Update	Remote Code Execution	Critical	4461580
Microsoft SharePoint Foundation 2013 Service Pack 1	4462143	Security Update	Remote Code Execution	Critical	4461596
Microsoft SharePoint Server 2010 Service Pack 2	4462184	Security Update	Remote Code Execution	Critical
	4461630	Security Update
Microsoft SharePoint Server 2013 Service Pack 1	4462202	Security Update	Remote Code Execution	Critical	4462139
	4462143	Security Update
Microsoft SharePoint Server 2019	4462199	Security Update	Remote Code Execution	Critical	4462171

Internal Server Error 500

When create a new web site, Internal Server Error 500  message appear, the solution is:

1. Open Front-End server.
2. open IIS
3. Select Application Pools
4. From the right side, select SecurityTokenServiceApplicationPool
5. Right-Click, Choose Advanced Settings.
6. Go to Identity, and set the Farm Admin user.
7. Recycle the Application Pool.

 

Live State

You can check the data volume for most sites as twitter and facebook http://www.internetlivestats.com/

Create a Web site with ease - Wix.com

Want to make your site even more beautiful? Find out how to do it with 10 stunning design features you can add quickly and easily.

When Use !important In CSS

The best reference explain the !important in CSS 

http://www.smashingmagazine.com/2010/11/02/the-important-css-declaration-how-and-when-to-use-it/

Direct Link To Workflow Manager 1.0

 

http://go.microsoft.com/fwlink/?LinkID=252092

Differences between Event Receivers and SharePoint Workflows

 

Event Receivers	Workflows
Can be Executed Synchronously or Asynchronously.	Can be Executed only Asynchronously which means when an action is completed.
Since it is executing in both modes we can cancel the action which is going to be occurred.	Once an action is started you cannot stop the operation.
Can't be initiated manually	Can be initiated automatically or manually.
Logs are not possible	Log can be written in workflows
Can be used in actions that needs to be completed immediately based on logic (Immediate execution)	Can be used in actions that will take even months or years to complete.( Long running)
no state is maintained	Workflow maintains state.
Triggered on Synchronous or Asynchronous events.	Triggered only on Creation/Change/deletion events.

 

The Reference: http://sharepoint-kings.blogspot.com/2013/08/differences-between-event-receivers-and.html