SharePoint Destination

Please use the below powershell script to get the list of sitecollections from a web application and store it in a text file. This will be run on Windows Powershell ISE   Microsoft.SharePoint.PowerShell" Get - SPWebApplication http: //yourwebapp.com | Get-SPSite | Select ID, Url | Out-File -FilePath "D:\spSites.txt"  

Please refer the link. I am yet to check this and so provided the referred link, https://blog.metrostarsystems.com/2013/06/13/sharepoint-solution-deployment-script-using-powershell/

PowerShell Remoting allows you to run individual PowerShell commands or access full PowerShell sessions on remote Windows systems.   PowerShell is locked-down by default, so you’ll have to enable PowerShell Remoting before using it. This setup process is a bit more complex if you’re using a workgroup – for example, on a home network — instead of a domain.   Enabling PowerShell Remoting On the computer you want to access remotely, open a PowerShell window as Administrator – right click the PowerShell shortcut and select Run as Administrator.   To enable PowerShell Remoting, run the following command (known as a cmdlet in PowerShell):  Enable-PSRemoting -Force This command starts the WinRM service, sets it to start automatically with your system, and creates a firewall rule that allows incoming connections. The -Force part of the command tells PowerShell to perform these actions without prompting you for each step     Workgroup ...

Very first question: What's the difference between SharePoint Management PowerShell and Windows PowerShell ISE SharePoint Management PowerShell: 1. Wrapper on top of Windows PowerShell with preloaded SharePoint objects 2. Comes with boring black command prompt 3. Comes with "SharePoint Snapin" Windows PowerShell ISE (Integrated Scripting Environment) 1. Simple default PowerShell with no SharePoint objects 2. comes with developer friendly and performs object based command line functions 3. We can add "SharePoint Snapin" Note: Windows PowerShell and Windows PowerShell ISE are different. Later is the better IDE and before one is typical black command prompt Script to add "SharePoint Snapin" if((Get-PSSnapin "Microsoft.SharePoint.PowerShell") -eq $null) {        Add-PSSnapin Microsoft.SharePoint.PowerShell } Post this, you can simply test it with simple commands: $web = Get-SPWeb "<<Siteurl>>" ...

To convert javascript event object to jQuery event object use the below code, var jQueryEvent = $.event.fix(javascriptevent); By converting to jQuery, then all the event properties will work across the browsers and even in older version (Like IE 8 and earlier). Reason behind is jQuery is cross browser script.  

jQuery is the wrapper on JavaScript. Meaning jQuery is the wrapper for the raw DOM objects returned by JavaScript. Since we get jQuery object bag, so we could use methods like css, etc., These methods are not available on the raw DOM object. document.getElementById('id') is faster than $('#id'). So use javascript, when there is simple work like using css or retrieving values. And use jQuery, if there is any complex functionality is involved and to use minimal coding. Also this is easy for the developers

When you develop web projects in Visual Studio, you need a web server to test or run them. Visual Studio lets you test with different web servers, including IIS Express , Internet Information Services (IIS), External Hosts, or Custom Web Servers By default, Visual Studio 2012 and Visual Studio 2013 use IIS Express. IIS Express is installed automatically when you install Visual Studio 2012 and Visual Studio 2013. If you want to install IIS Express in Visual Studio 2010 (SP1 is required), you can use the Microsoft Web Platform Installer. Reference: https://msdn.microsoft.com/en-us/library/58wxa9w5(v=vs.120).aspx