This is the fifth and final part of blog series that walk you through each of Telerik's Cloud Controls and show you how easy you can use them to create an app. This post demonstrates the usage of RadCloudNotificationControl and RadCloudFeedbackControl.
In the last post I showed you how from time to time it is necessary to change our code to enhance readability, make maintenance easier or to optimize the codes performance. This practice is called “Refactoring.” Normally making these kinds of changes can be a nerve-wracking experience for developers as they can’t be certain that their changes aren’t breaking something else. However, having a suite of unit tests the exercise your business code enables you to refactor your code without worry; as long as your tests pass you know that your code still satisfies your business needs. In addition to our code, sometimes our unit tests themselves need some refactoring. This post explains how to refactor your unit tests and demonstrates a few NUnit features that will help us with this endeavor.
As time goes on in any software development project you’ll no doubt find inefficiencies in your code that you would like to remove. Other times you’ll receive new requirements that are going to necessitate large scale changes in your existing code. And you will still occasionally find code that you’ve written in the past that will make you ask “What was I thinking when I did that?!” When these situations arrive, it’s time to look at refactoring your code.
The Q2 2013 release of Kendo UI saw the introduction of the new Scheduler widget - a highly requested, highly customizable widget that allows you to schedule things in a calendar view.
Along with a new widget, of course, there is a lot of new documentation and new resources for getting started and using it. The schedular, with it’s already powerful and flexible feature set (in spite of still being a ‘beta’) is no exception, of course. And one of the best resources I’ve seen for getting started with it, is the Kendo UI Scheduler screencast course at Udemy.com.
JustCode works very hard in the background to make you as productive as possible without getting in your way. In order to do this there is some startup work that must be done, and this can affect the start up time for Visual Studio. Read here to see what's going on behind the scenes.
I’ve previously discussed a bit of the TDD workflow; start with a requirement, derive a test from the requirement, write just enough code to make that test pass, repeat. This is sometimes referred to as “Red, Green, Refactor” which I’ll be coming back to several times over the course of this series. In this post I’ll show you how this approach can be extended to dealing with software defects.
When iteratively planning an Agile project where the team partitions work into timeboxed iterations, understanding capacity is very important. Planning an iteration is very much like using a bucket to scoop water out of a pool, where the pool represents the complete set of backlog items on your project and the bucket represents the amount of work that can be accomplished in a single iteration. Understanding how much water a bucket holds will give you an idea of how many buckets are required to empty the pool. Similarly, understanding how much work your team can deliver in an iteration will ...
As a Kendo UI customer, you have access to the best support in the industry. Here are a few tips to help you get the most out of your Kendo UI support and get faster resolution for your issues.