Investing in third party ASP.NET toolsets is well worth it, but only if you find the best toolset for your project. But what characteristics should you be looking for, and how do you make a thorough—but fast—evaluation?
To help, we created a checklist of factors to consider on your quest for productivity. You can save even more time by using the handy spreadsheet provided at the end. It enables you to quickly rate different solutions on a range of predefined factors.
October 2013 brought a new release of Microsoft Visual Studio, ushering in some of the most dramatic changes to ASP.NET since the introduction of the framework in .NET 1.0. This whitepaper will review 10 of the most important changes, and explain what makes them so valuable for ASP.NET developers. You will learn why Visual Studio 2013 is the version of the IDE to upgrade to, no matter if you are currently running in version 2012, 2010, 2008, or 2005.
Do you stick to the default ASP.NET controls because you doubt the productivity gains of third-party controls? Telerik Developer Evangelist, Jeff Fritz, gave himself a challenge: build the same application by allocating 30 minutes to working with the default Visual Studio toolset and 30 minutes to Telerik UI for ASP.NET AJAX. He then compared the results based on how much functionality he implemented and the amount of code he had to write. The productivity gap may surprise you.
Copyright © 2016, Progress Software Corporation and/or its subsidiaries or affiliates. All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks or appropriate markings.