Are You a .NET Survivor? Tell Us About It -- Visual Studio Magazine

Data Driverby David Ramel

Are You a .NET Survivor? Tell Us About It

The editors of Redmond Developer News are pulling together a .NET Survivors Guide. For those developing database driven apps, please share whatever tips you may have. What new skills are a must? (ADO.NET, LINQ to SQL, etc.?) What lessons can you share? Anyone starting to delve into the new reporting services features of SQL Server 2008? How about Beta 2 of Visual Stodio 2008 , which among other thing shows significant improvements in LINQ to SQL, which allows developers to use Microsoft’s new Language Integrated Query against a relational database to query, update and insert data.

Don’t miss RDN senior editor Kathleen Richards' complete report.

Posted by Jeffrey Schwartz on 08/08/2007

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.