Where to Begin, How to Begin?
When developers need to start playing with new technologies, or testing against requirements, they can’t just begin. Setting up in preparation for a new deployment requires both time and effort: Machines, OS versions, frameworks… It all needs to be arranged, provisioned and/or reserved. This can take much longer than the actual test, and often yields a much higher error rate.
Cloud computing providers should help the community. With ability to create, replicate and share a fully functional environment CloudShare does just that. It provides complete support for creating, replicating and managing SharePoint environments. This and a few other things make CloudShare the leader in the SharePoint market.
We are happy to announce a significant service enhancement to all CloudShare customers. Our goal is to provide developers, testers and managers with a cloud platform that is easy to operate, transparently priced and cost effective.
In this article I will show you how to re-start al the instances of the SharePoint Timer Service in a SharePoint farm by means of PowerShell and the Server Side Object Model. Both approaches are quite similar as you will see in the code. Let’s start :-).
As software continues to “eat the world”, everything in the development and deployment process is scrutinized and subjected to automation. Whether you find this revolutionary or business as usual, it’s worth considering: What can be automated?
Last week we began comparing CloudShare’s virtual labs to general purpose systems like Azure IaaS, pointing out the key features of a virtual lab: automated provisioning, saving, clone, suspension and sharing of full IT environments. This enables full system tests on-demand and automates many tedious IT and configuration tasks. This week we discuss how this automation also makes the lab much more cost-effective than a patchwork solution built from IaaS like Azure.
As you know, SharePoint Property Bags are a powerful mechanism we have available in SharePoint to create and define configuration properties at the different logical levels in the platform architecture: Farm, Web Application, Site Collection, Site, List / Document Library and Folder). SharePoint Property bags are very useful to store configuration properties such as Database connection strings, specific data for the solutions we are building, etc. Finally, It’s a best practice to use Property Bags to store and retrieve such configuration properties required by our SharePoint solutions. In this article I will so you how to create and update SharePoint Property Bags from a CSV file using PowerShell so you can automate the process of maintaining your Property Bags in your SharePoint deployment.
Over the next few weeks, we will discuss CloudShare’s place in the cloud. Our goal is to sharpen the contradictions among these platforms, explain the benefits of virtual labs and highlight CloudShare’s unique features. First, let’s compare Azure dev/test VMs to virtual lab management in CloudShare.
This time I would like to share a quick tip with you that allows you to solve typical problems you can find when working with dates in your SharePoint code: how to convert a date in ISO 8061 format to a .NET DateTime format. For instance, this situation happens when you have to update a list item field inside the code of a SharePoint event receiver and the field type to process is just a SharePoint DateTime field.
BIG DATA AND IN-MEMORY DATABASE
Nowadays when you are looking for Big Data techniques you get in touch with Hadoop. If you are googling for an In-Memory Database you will find SAP HANA. These are two actual topics which are on top of the Gartner Hype Cycle of Emerging Technologies (Gartner, 2014).
That’s one of the reason why we from IT-Logix wanted to create a test environment which all of our consultants can access easily. But technologies like SAP HANA needs lots of HDD space, let alone of memory. The minimum memory requirement even just for testing SAP HANA is 24 GB (SAP, 2014). As we don’t need a production system which is always up and running we were looking for a cheaper solution compared to buying new hardware and host the new test system on premise.
REQUIREMENTS LED US TO CLOUDSHARE TEAM LABS