* original image from http://chocolatey.org/ Time to time we need to build up/rebuild development environment from scratch. There are a dozen reasons to do so, from recreating a dev VM, working at client site or getting a new client while working as a consultant and so on. Every time you need to install some of the end user software, such as Skype, Chrome, Firefox, Adobe Reader and the rest. Next, dev software is req
Some of the useful SharePoint related link just stumbled this week. RT @mikkokoskinen: One of the best examples for apps so far. Self-Service Site Provisioning using #Apps for #SharePoint 2013 http://t.co/pW… #Chocolatey rules, no doubts! I’d recommend to take a look at #SharePoint packages by @maxmelcher – they are good – http://t.co/RCq7WgPg15 SPChat: Matthias Einig about SharePoint Solution Deplo
SharePoint 2010 introduced CSOM as a new way to create client side application. It was a quite nice step forward which allows creating “light” client side applications and minimize farm downtime. With the latest SharePoint 2013 trends – html/js apps – it is worth to utilize CSOM even more intensively for your “old” SharePoint 2010 projects. However, some common routines to deploy a
SharePoint 2010 introduced CSOM as a new way to create client side application. It was a quite nice step forward which allows creating “light” client side applications and minimize farm downtime. With the latest SharePoint 2013 trends – html/js apps – it is worth to utilize CSOM even more intensively for your “old” SharePoint 2010 projects. However, some common routines to deploy a
Some of the useful SharePoint related link just stumbled this week. Nice, but needs to be simplified – Build #SharePoint 2013 Lab in the Cloud with Windows #Azure http://t.co/cfDZn78484 #sharepoint #sp2013 RT @spietrek: “@SP365uk: SharePoint Online / SharePoint 2013 Balsamiq Mock Up Template http://t.co/193MwMn9WH #sp365 #SharePoint #office365” Training | Apps for Office and SharePoint | 2013, apps, cloud servi
It seems that most of the intranet portals have a lot in common. It could be news feed, last documents, last tasks, “who is new web part” and the rest “catchy” things you may have already seen in your intranet projects. Finally, sort of “about”, “company structure”, “help” or “get started” pages could be one of the “must have” feature
Some of the useful SharePoint related link just stumbled this week. RT @cfiessinger: Jeff Teper says: “We think of Exchange, SharePoint and Yammer now as one product” http://t.co/nXK7BDF2Ch #Office365 #SharePoint RT @pl_sharepoint: My New Book Professional #SharePoint 2013 admin is out! by Todd Klindt http://t.co/Fp128m5Ec6 SharePoint/TFS Continuous Integration Starter Pack – https://t.co/oyWWDqja0n
* original comics by Rob DenBleyker at http://www.explosm.net/comics/1896/ SharePoint solution deployment is not an “on-click-job” and never will be. Depending on the target project, scope and size, there could be a lot of preliminary routines and “better to have” steps. Next, different deployment strategy could be required – from deployment to upgrade and retract. In turns, those strate
Some of the useful SharePoint related link just stumbled this week. SharePoint Code Analysis Framework (SPCAF) BETA – http://t.co/owzRes1c2F #sharepoint #SPCAF #ALM RT @SharePointNinja: Check out Exam Ref 70-332: Advanced Solutions of Microsoft® SharePoint® Server 2013 http://t.co/XOSIVndxe4 RT @xelikk: Databases that support #SharePoint 2013 http://t.co/wrDSIeqwgZ The future is here! – Deployment Conside
SharePoint solution development is not a sweet thing to work with. High complexity of SharePoint itself combined with poor support by Visual Studio produce a lot of challenges on all stages of the project. Mostly, it is not time and cost effective to develop without such a great addins like CKSDev, SPDisposeCheck or ReSharper. SPCAF is one more really valuable asset in tooling set for SharePoint projects. It checks t