While I was searching for my next SharePoint event I get surprised with the number of available events all around the world. Because of that I decided to create a chronological list with all upcoming SharePoint events and basic info about each of the available events.
Let’s see which events finished in my list:
In my previous post you saw how the default SharePoint Online public-facing site looks like. You can see it below on the left side.
Also, on the right side you can see customized version of the very same site. As you can see it looks completely different, but what’s more important, all customizations were performed using built-in tools only. Another fact clear from the images below is the fact I have no talent for design, but do me a favor and ignore that fact.
Now let’s see the list of customizations we performed in order to create a new version of the public website.
Office 365 plans comes with support for public facing websites. No matter if you are using Small Business Plan (P Plan) or one of the Enterprise Plans (E Plans), you can create exactly one public facing website. The difference between plans is the fact that for P plan public website is created automatically at the root level immediately after you establish your account, and for the E plans it have to be created manually.
In this blog post I’ll show you how easy is to create and customize a public facing website hosted inside your SharePoint Online services.
I guess you all already noticed that Microsoft and all other major players are moving towards cloud computing and offering various online services. SharePoint wasn’t skipped in that movement, so now Microsoft also offers SharePoint Online services as the part of the Microsoft Office 365 service.
Please note that SharePoint Online services are not available as the separate service, but only as part of one of available Office 365 plans. There are few available Office 365 plans that contain SharePoint Online services. From the SharePoint point of view, let’s see what’s inside those plans.
As you already know, SharePoint PowerShell command set can be extended by using Visual Studio 2010. In this blog post I’ll show you how easy is to write a solution that contains all required components that defines one PowerShell command (cmdlet).
To make it better, I’ll share my solution with you, just to give you jump start while creating your own cmdlet solutions.
In order to create a new SharePoint PowerShell command, we’ll have to create and deploy three components:
- Assembly that contains cmdlet definition (deployed to GAC).
- Cmdlet registration xml file that defines our command (deployed to the 14’s hive CONFIG\POWERSHELL\REGISTRATION folder).
- Cmdlet help file (deployed to the 14’s hive CONFIG\POWERSHELL\HELP folder).