Microsoft released the developer preview for SharePoint Framework.
It’s all in Github now – https://github.com/SharePoint/sp-dev-docs/wiki
If you are new to this, watch the official Microsoft statement to get some heads up – https://blogs.office.com/2016/05/04/the-sharepoint-framework-an-open-and-connected-platform/
Also note that SharePoint Framework web parts are not supported for production use yet.
So just be ready guys !!!
Microsoft has introduced an exciting automation procedure called Microsoft Flow – https://flow.microsoft.com/en-us/
You can relate this to IFTTT where you can connect all of your best apps to achieve amazing things. Who wouldn’t like to light up their house during sunset 🙂
Microsoft Flow allows you to connect your Office 365 accounts with services like Dropbox, Trello, Slack or Google Drive.
There are plenty of free templates which can get you started or you can create automation from blank.
Create your own recipes and enjoy 🙂
This is totally awesome.
An environment for testing or developing code that leverage Office 365 APIs – http://apisandbox.msdn.microsoft.com/
Play around with the sample codes that the site has or change and add code on the fly to test yours.
While installing the SharePoint Server 2013 prerequisites, you see the following error in the event log and the setup log:
Product: AppFabric 1.1 for Windows Server — Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action Env_PSModulePath_powershell_i, location: c:\Program Files\AppFabric 1.1 for Windows Server\Microsoft.ApplicationServer.InstallHelper.exe, command: powershell.exe “-command \”$str = [System.Environment]::GetEnvironmentVariable( \\\”PSModulePath\\\ “, [System.EnvironmentVariableTarget]::Machine); $str = $str+\\\”;c:\Program Files\AppFabric 1.1 for Windows Server\PowershellModules\\\”; c:\Windows\system32\setx.exe /M PSModulePath \\\”$str\\\”\ “” “C:\Users\Administrator\AppData\Local\Temp\AppServerSetup1_1_CustomActions(2014-5-15 11-08-45).log”
The PSModulePath environment variable is corrupted. There is a quotation mark at the end.
C:\Windows\system32\WindowsPowerShell\v1.0\Modules\;C:\Program Files (x86)\Microsoft SQL Server\110\Tools\PowerShell\Modules;c:\Program Files\AppFabric 1.1 for Windows Server\PowershellModules”
Delete the ending quotation mark and re-run the setup.
Original Official post here.
Microsoft has changed the plans for bi-monthly CUs. The CUs will be released on a monthly basis from now on. This means for all products that is being supported. Cool, eh!!
That means faster patches and updates to your products.
And so, the July 2014 CU for SharePoint 2013 has been released.
Visit the official blog for details.
The Release Candidate for Visual Studio 2013 Update 3, is now available for download
Some cool new features:
- Application Insights. Application Insights, Microsoft’s service for monitoring production web sites and Windows Store and Phone apps, is now included in this update. Key enhancements in this release include polish to the account setup experience to create accounts directly in Azure without requiring a Visual Studio Online account as well as other enhancements from the Preview we published to the Visual Studio Gallery.
- Visual Studio Graphics Analyzer. Diagnosing DirectX rendering and performance issues is tricky and the Visual Studio Graphics Diagnostics features help. In Update 3, we have enhanced the Graphics Analyzer to analyze graphics frames and to view the impact of shader code changes without re-running the app. You can easily configure capture options in Tools Options under Graphics Diagnostics.
- Managed memory dump analysis. When analyzing managed memory dump files, you can now Go to Definition and Find All References of the selected type. To learn more, check out the blog post on .NET Memory Analysis.
- CPU and Memory Usage tool. The CPU Usage tool in the Performance and Diagnostics hub now enables you to navigate from a function name in the Call Tree to the definition of that function in the editor so that you can easily see the code that is using CPU in your application. We have also made improvements to the Memory Usage tool such as support for Win32 and WPF applications (.NET 4.0 and up on Windows 8.1) and the ability to force garbage collections in managed apps.
- Multi-Monitor configuration with Windows Store App. When debugging a Windows Store app with a multi-monitor configuration, Visual Studio now remembers which monitor your app was last run on. Here are some images to describe this experience.
- CodeLens. CodeLens, an editor productivity feature available in Visual Studio Ultimate, is now available to show authors and changes to files in Git repositories. If you use Git for source control and TFS for work item tracking, CodeLens work item indicators now provide information about work items associated with a method, or class.
- ALL CAPS. The change in our menus to use all capital letters was one of the areas about which we received a lot of feedback, so a while ago we added a registry key that disabled the ALL CAPS menus in Visual Studio 2012. To make the setting more discoverable and to enable it to remain set as you upgrade across Visual Studio versions, we have now added a Tools Options setting under the general Environment settings that lets you set your preferred menu bar styling. We also roam this setting so it’s available on all your devices.
Find the entire msdn blog with more details here.
“No item exists at… It may have been deleted or renamed by another user”. – This might be an irritating error when you enable Anonymous access to a SharePoint Survey.
This normally happens when you have multiple pages with a page separator in a Survey and when you try to respond using “Anonymous” access.
SharePoint Survey initially uses the NewForm.aspx to create the survey. It gets the incremented ID value and goes to EditForm.aspx with the same ID in querystring. Everything goes as planned until now. Once the user goes into the next set of questions in the second page of the survey, the same ID is passed as a query string again and it throws this wierd error. Now, this happens only when you are not logged in.
What could be the reason?
If you check the advanced settings in the same Survey, you can find a setting similar to the image below.
Reading between the lines, you can see that it is set to “Create responses and edit responses that were created only by the current user” which kind of creates a confusion for anonymous users. Change this option to “Create and edit all responses” and the issue will be resolved. This in effect allows Anonymous users to edit the response it just created. Everything should be fine from now.