VSLive! FL 2007: Reporting Innovations in SQL Server and Visual Studio 2005 -- Visual Studio Magazine

VSLive! FL 2007: Reporting Innovations in SQL Server and Visual Studio 2005

Check out the new reporting tools in SQL Server 2005 and Visual Studio 2005.

By Bill Wolff
05/01/2006

This video is no longer available on this site.

About the Author

Bill Wolff is an independent consultant, trainer, and architect specializing in Microsoft development technologies. His company, Agility Systems, is based in the Philadelphia area. Bill is founder and president of the philly.net user group, a board member for INETA (Vice President, Speaker Bureau), and a VSLive! speaker. Bill was a contributing author to several books and articles. His certifications include trainer, systems engineer, developer, and Microsoft MVP for VB.NET.

Printable Format

comments powered by Disqus

Featured

Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.
Diving Deep into .NET MAUI

Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.
Copilot AI Boosts Abound in New VS Code v1.96

Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.
AdaBoost Regression Using C#

Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.
Versioning and Documenting ASP.NET Core Services

Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.