Skip to main content

Visual Studio 2008 Service Pack 1 Released

The first of the series of service packs for VS2008 has just been released . With Service Pack 1, Visual Studio 2008 introduces a large assortment of new features for targeting Windows, Office, and the Web. Developers building .NET-basedapplications will enjoy improved performance in the WPF designer, new components for Visual Basic and Visual C++, as well as an MFC-based Office 2007 Ribbon. Web developers will see continued improvement in the client-side script tooling including JavaScript IntelliSense. Additionally, full support for SQL Server 2008, the ADO.NET Entity Framework and performance improvements for the IDE make Service Pack 1 a great release across the board.

The .NET Framework 3.5 Service Pack 1 delivers more controls, a streamlined setup, improved start-up performance, and powerful new graphics features for client development and rich data scaffolding, improved AJAX support, and other improvements for Web development. Additionally it introduces the ADO.NET Entity Framework and ADO.NET Data Services, which simplify data access code in applications by providing an extensible, conceptual model for data from any data source and enabling this model to closely reflect business requirements.

Some of the new features includes :

Visual Studio 2008 Service Pack 1 includes:

* Improved designers for building WPF applications
* Full support for SQL Server 2008
* The introduction of the ADO.NET Entity Designer
* Visual Basic and Visual C++ components and tools (including an MFC-based Office 2007 style 'Ribbon')
* Improvements to Team Foundation Server to respond to customer feedback on version control usability and performance, improved e-mail integration with work item tracking and full support for hosting on SQL Server 2008
* Improvements for Web development including richer JavaScript support, enhanced AJAX and data tools, and Web site deployment

The .NET Framework 3.5 Service Pack 1 includes:

* Performance increases between 20-45% for WPF-based applications - without having to change any code
* WCF improvements that give developers more control over the way they access data and services
* Streamlined installation experience for client applications
* Improvements in the area of data platform, such as the ADO.NET Entity Framework, ADO.NET Data Services and support for SQL Server 2008's new features.


Read More About this Release from Microsoft

Comments

Popular posts from this blog

Hiding Unwanted Python Folders and Files in Visual Studio Code

Visual Studio Code is a universal editor and pretty good at it. However, the explorer view maybe cluttered with the automatically generated folders and files confusing developers. Python is no different. Below are example files and folders generated by Python.

The __pycache__ folder and *.pyc files  are totally unnecessary to the developer. To hide these files from the explorer view, we need to edit the settings.json for VSCode. Add the folder and the files as shown below:
Copy and paste the lines below :

"**/*.pyc":{"when":"$(basename).py"},"**/__pycache__":true

Getting Started with Stateless : A Lightweight Workflow Library Alternative for .NET

A year ago, I was looking for a simple workflow manager for a project I was working. Its a medium sized application that involves tracking the state of assets in the system. Back in 2008, Microsoft (MS) introduced new technologies along with the release of Visual Studio 2008: Windows Presentation Foundation (WPF), Windows Communication Foundation (WCF), and Windows Workflow Foundation(WF). Having worked in a company utilizing mostly MS products for development, my first option was to go with WF. After doing some time reading and studying the library, I paused and decided it was too complex for my requirement. Using WF would be an overkill and the fact that it has, a rather, steep learning curve, there has to be another option. My mind toyed with the idea of developing a simple workflow library myself. It would be a learning experience but it might end up consuming a lot of time.

Why reinvent the wheel? So I started querying the internet for a better solution. I stumbled upon Stateless

Get Started with MongoDB Stitch : The New Backend As Service Offering from MongoDB

Halfway of this year, the guys from MongoDB launch their new backend as service product called MongoDB Stitch. While the launch is just for the beta, the promise of the service is quite interesting. MongoDB has been around for long now and some development stacks have been based on its database product, the MongoDB-ExpressJS-Angular-NodeJS (MEAN) and the MongoDB-ExpressJS-React-NodeJS (MERN) stacks to name a few. These stacks, however, relies on backend technology such as ExpressJS and NodeJS. The idea of provisioning servers and developing the backend solution makes it daunting for small to medium scale applications. MongoDB Atlas, at least made life much easier by providing on cloud database solution, but there must be a simpler solution, right? A solution the would stitch the backend and frontend together ( see what I did there ?).
MongoDB Stitch lets developers focus on building applications rather than on managing data manipulation code, service integration, or backend infrastruct…