CloudShare is a tool that many developers have made apart of their day-to-day work. And that platform has to be built just like any other application. Our awesome team of developers faces the same processes and challenges that the entire development world does, and they want to share their story with you.
Last week CloudShare joined the 2014 Build Conference in San Francisco. If you have never been to the conference, I recommend it. It is a great way for developers to find out what is new in the Microsoft Dev Tools world, meet with Peers to solve real world problems, and get up to speed on modern day trends. Like one of this years themes, DevOps.
As you know, Microsoft released the March Update of the Office Developer Tools for Visual Studio 2013 a few weeks ago in the SharePoint Conference hold in Las Vegas. In this article I will show you step by step how to create a SharePoint Cloud Business App using the update project template included in the tools.
Microsoft has recently released the Service Pack (SP) 1 for SharePoint 2013. In this article I will show you how easy is to install the first SP for SharePoint 2013 and also some of the new goodies coming with the platform. Let’s start.
In this article I will continue talking about how to create a Web Performance Test for SharePoint 2013 using Visual Studio 2013 (VS 2013) Update 1 in a SharePoint 2013 CloudShare environment. If you remember, in my last post about this topic I explained how easy is to define and create a Web Performance Test in VS 2013 Update 1. In this blog post, we will see how to execute an existing Web Test and also the performance information provided by the IDE.
At CloudShare we are working agile. Every 2 weeks we have a new version deployed to production. One of the advantages of such short iteration is the ability to get very early feedback from customers or from our customer facing colleagues.
However, we sometime want to get this feedback before the version is deployed. Our developers want to get validation from the product manager before QA start to run their tests. Or sometime we even want that of our customer facing persons will discuss a specific feature or UI with the customer itself, before the feature is done.
In this article I will continue talking about how to use the capabilities provided by MSOCAF (Microsoft SharePoint Online Code Analysis Framewor) for auditing a SharePoint environment in terms of .WSP solutions deployed. If you remember, in my last post about MSOCAF we simply reviewed how to install and use the tool in a CloudShare SharePoint development environment. In this blog post I will continue showing you how MSOCAF is a great tool for analyzing SharePoint solutions and detect any problems introduced by them in a SharePoint farm.
You may have seen in this previous post how CloudShare works great with TFS online, now Visual Studio Online. But it works great with your on-prem TFS as well!
Last week while I was doing a SharePoint 2013 training using my CloudShare environments as the training platform for my students I found several issues when trying to create and deploy workflows in Windows Azure Workflow (WAW). After some investigation I found that the problems were due to a change in the credentials of the user account used to run all the required WAW services. Basically, all services were stopped since the change in the credentials hadn’t been propagated to all services and therefore it was completely impossible to deploy any workflow to WAW. Below I will explain how I found the solution.
If you are a Developer on the Microsoft Stack, you have surely heard the news about the advancements, and renaming of TFS Services to Visual Studio On-Line. Visual Studio On-Line, announced on Nov 13th, comes with a lot of new technology advancements, like build services, Test Management, Load test etc. But it also changes in a big way the license paradigm for developers, where they subscribe to the IDE and the services they use, versus buying licenses. No big surprise given this has been the approach with Office for several years now. But with all that new stuff, there is a gaping problem left to be solved…