I wish I could say I found out about the Heartbleed bug very quickly and from some super deep technical source. But I didn’t. I found it on my favorite Tmblr blog, filled with animated gifs about DevOps that gets me through the day. And once I realized what this particular Gif was telling me, I too was in a small state of shock.
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.
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 post I will explain how you can do web performance tests in SharePoint 2013. In the same way you can detect/prevent any issue or problem on your SharePoint Solutions doing an exhaustive analysis using tools like MSOCAF (Microsoft SharePoint Online Code Analysis Framework), you can verify performance and stress abilities on your SharePoint applications by creating web performance and load tests. In this first post I will show you how to create a Web Performance Test for SharePoint 2013 using Visual Studio 2013 (VS 2013) Update 1 in a SharePoint 2013 CloudShare environment.
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.
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…
The time of the year for predictions has come, and as in previous years, CloudShare is throwing theirs in the pile. But these are not just any old predictions. I’m going to tell you how the life of the developer is going to change in 2014.
In the CloudShare dev group, we occasionally work with an outside consultant or contractor.
One of the most annoying pains when hiring a developer contractor is the need to provide him with a development environment. The consultant usually wants to work on his laptop in his office / home and needs a development environment immediately. Besides, as opposed to an in-house developer, there is no real value in letting him install and configure his own developer station.
If we have to audit a SharePoint environment in terms of the artifacts deployed or we are working for a customer demanding high quality in our development process, it is a good practice to do an exhaustive analysis of the artifacts already deployed or planned to be deployed in order to detect/prevent any issue or problem caused by those artifacts. One of the possibilities for doing that analysis is to use Microsoft SharePoint Online Code Analysis Framework (MSOCAF) provided by Microsoft and available through the following link: https://caf.sharepoint.microsoftonline.com/. You can freely use MSOCAF for analyzing SharePoint solutions and detect any problems introduced by them in a SharePoint farm. In this blog post I will do a first approach about how to use MSOCAF for analyzing SharePoint Solutions.
As developers, last week we had a great surprise coming from Microsoft: Visual Studio 2013 Release Candidate (VS 2013 RC) was publicly released together with Team Foundation Server 2013 RC, .NET Framework 4.5.1 RC, and related developer tools technologies. All the details about what’s new in the VS 2013 RC can be found in this great Soma Segar’s blog entry where you can find detailed information about what’s new in RC and the improvements and additions between VS 2013 Preview and RC release.