Only because it’s been a while and I need to get back in the habit of posting… But, since I had to look this up recently I thought I would add it to my little mind dump here. Recently we were playing around with securing some lists, and it’s really intuitive in SPD 2010 on how to hide a list from the browser, but a little tricky to remember how to unhide the list once you’ve hidden it…
How to hide a list in Designer:
- Open the site in SharePoint designer 2010.
- Open the page used to view and manage the settings for the list by selecting the list from the Lists and Libraries page, which you can get to from the Site Objects toolbar.
- Uncheck option “Display this list on quick launch”.
- Check the “Hide from browser”.
Open the SharePoint site in the browser and confirm that you list is now hidden.
How to open a hidden list and unhide it in Designer:
- Open the site in SharePoint designer 2010.
- Click the “All Files” folder at the bottom of the Site Objects toolbar.
- Expand the “Lists” folder
- Find the list you want to unhide and right-click on it and choose “Properties…”
- Now you have your hidden list’s property page open in SPD.
- Uncheck the “Hide from browser” and save.
Hey SoCal Devs
Last time this conference came around, you said we didn’t give you enough notice to get the cost approved by your company. Well, now you have plenty of time. For those of us in SoCal, if you go to one paid conference a year, this should be it.
Dev Intersection – Nov 10-13 2014 Las Vegas
Everyone you want to see will be speaking here :
- Scott Guthrie
- Steve Guggenhimer
- Scott Hanselman
- John Papa
- Michele Bustamante
- Richard Campbell
- Dan Wahlin
- Paul Sheriff
- Mark Minasi
- Billy Hollis
- Juval Lowy
And Many more. If you are a .Net Developer in the west, this is really an event you don’t want to miss.
You can find out more and register here : http://devintersection.com/
If you use the code “SoCal” at registration, you will get an additional $50 off of your registration.
And Remember.. this is not just DEV, it’s also :
SharePoint, Office 365, ASP.net, Visual Studio, Azure, SQL too.
Microsoft has just released a good set of examples of Apps on CodePlex. Most will work on Office 365 as well as on-Prem Sharepoint Server 2013.
Currently this project is very focused on the SharePoint scenarios but they say they are also keeping an eye on including the all-up Office Developer moving forward. These volunteers are working with the MSDN Content Publishing team to take the most impactful and useful samples that complete common customer scenarios and publishing them as "Solution Packs" of content as well as "Sample Packs" of sample code.
Extremely useful for those of us “SharePoint Chefs” who take various code recipes and add our own flavor to them.
You can get additional details from the introduction presentation.
Quick list of included scenarios
- Cloud based site collection provisioning
- Creating site collections remotely using SP Apps in on-premises
- Provision and integrate Yammer group into site provisioning
- Manage and update theme settings in host web
- Changing host web rendering with custom CSS
- Site policy management with CSOM
- Wiki page manipulation using CSOM
- Site collection enumeration
- Setting up Apps to Windows Azure with specific roles
- People picker implementation for provider hosted app
- Taxonomy picker implementation for provider hosted app
- Uploading of large files to SharePoint
- Deploy branding to personal SkyDrive Pro sites automatically
- Connect to and manipulate Office365 sites using console application
- Provide custom template pattern for sub site creation
- Manipulation of user profile properties remotely
- Build sync of user profile properties in cloud
- Mass deployment of branding elements from console app
- Hybrid self-service site collection provisioning – one UI for cloud and on-prem
- Synchronization of user profile pictures from on-prem to SharePoint Online
- Dynamic permission handling
- Remote event receivers from host web
Check the new SharePoint Online Solution Pack for branding and provisioning. This package contains some examples, which originate from the AMS reference implementations. Here are the direct links for the Solution Pack
You can find an introduction to the SharePoint Online Solution Pack for branding and provisioning by following the blog post – Introduction to SharePoint Online Solution Pack for branding and provisioning released.
Microsoft is rebranding their SkyDrive service as “OneDrive”.
Not just a rebranding though, several new capabilities, including automatic camera backup for Android and the ability to share and view videos just as easily as photos. In addition, customers who refer friends can now receive up to 5 GB (in 500 MB increments) for each friend who accepts an invitation to OneDrive, plus 3 GB just for using the camera backup feature.
According to the site:
We’ve built OneDrive into the latest versions of Windows, Windows Phone, Office, and Xbox. You can even make OneDrive your default storage option, so you never have to worry about whether you are saving files to the cloud: They are just there. If you happen to carry an iPhone or Android phone, or use an iPad, Android tablet, Windows device, or a Mac—OneDrive is available there, too.
So, here’s the invite link: https://onedrive.live.com?invref=c3cc3a0c7234880d&invsrc=90
I really like the idea, hopefully they can pull it off.
Sometimes working on a DEV server runs into some unexpected features. Like bad performance. Sometimes the bad performance leads to bonus features in the error logs.
This one started popping up in the ULS viewer:
Unexpected error occurred in method ‘GetObject’ , usage ‘SPViewStateCache’ – Exception ‘Microsoft.ApplicationServer.Caching.DataCacheException: ErrorCode<ERRCA0018>:SubStatus<ES0001>:The request timed out..
However, it’s a simple enough fix, just increase the timeout for the cache. Not something you want to do in a production environment, but when you’re running on a DEV machine and you just need the SharePoint 2013 platform to run without errors so it’s not masking any actual issues, this seems to work pretty well.
$LogonTokenCache = Get-SPDistributedCacheClientSetting -ContainerType DistributedLogonTokenCache
$LogonTokenCache.RequestTimeout = 300
Set-SPDistributedCacheClientSetting -ContainerType DistributedLogonTokenCache -DistributedCacheClientSettings $LogonTokenCache
$ViewStateCache = Get-SPDistributedCacheClientSetting -ContainerType DistributedViewStateCache
$ViewStateCache.RequestTimeout = 300
Set-SPDistributedCacheClientSetting -ContainerType DistributedViewStateCache -DistributedCacheClientSettings $ViewStateCache
This will usually get rid of the error from popping up in the ULS logs.