Microsoft's Big Day -- Visual Studio Magazine

Desmond File

Microsoft's Big Day

On Feb. 27, Microsoft is kicking off a three-headed launch event for Visual Studio 2008, SQL Server 2008 and Windows Server 2008. As ever, with these formal launch events, the actual date of the shindig has little bearing on the state of the software itself. Visual Studio 2008 went final back in November, while SQL Server 2008 won't ship until the second quarter of this year.

What we want to know is: What are your thoughts on the new versions of these landmark Microsoft products? Have you been working with the 2008 versions of Visual Studio, SQL Server or Windows Server? If so, we want to hear from you.

Write me at mdesmond@reddevnews.com, and your input could appear in an upcoming issue of Redmond Developer News magazine.

Posted by Michael Desmond on 01/24/2008

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.