CloudShare adds new releases and updates to our platform every other week. Sometimes they’re big updates, sometimes small. We want to keep your experience fresh and always improving, so they can be major upgrades, performance improvements, bug fixes or new functions.
Managing policies …and your usage …and your costs …and how it all adds up sounds super dull, right? And it is.
That is, until it isn’t. Have you ever had to experienced the feeling of going to your boss or any other financial controller in your company with an unexpected bill? And that bill happened to be larger than you could have imagined? It’s a long walk to their office isn’t it? Well, we don’t want you to experience that, ever!
Many of our users view their CloudShare environments as separate and different entities than their own organizational infrastructure and systems. On one side, there is your organizational environment and on the other there are your CloudShare environments. But why make this distinction when they can both be part of the same entity? More and more organizations are starting to understand the needs for Hybrid Cloud solutions and look for different ways to implement them.
If you’ve not been living on the moon, you’ve probably heard of the concept of “Nested Virtualization”.
This is a method of running a Virtual Machine inside a Virtual Machine.
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.
“Wow! That’s Cool!” was my first reaction.
“I wish I knew about this sooner.” was my second.
That’s a really auspicious start to my joining CloudShare.
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!
So, you have decided to Develop/Test or run Demos/Training in the Cloud. That’s Great! That is the right choice. While we are all aware of the benefits of the Cloud. You now have to put your trust and data somewhere else. So it’s important that you feel safe there.