Visual Studio 2008 SP1 Beta is now available! You can download it here (though before you do, read the note below). In SP1, we have added some new features as well as many bug fixes. In this blog post I’ll attempt to give an overview of the features as well as some of the key issues the Visual Web Developer team has addressed so far in the service pack.
Installation Note: If you previously installed a Visual Studio 2008 Hotfix (in particular, KB944899), you should run the Hotfix Cleanup Utility before installing Visual Studio 2008 SP1 Beta. For more information, see Remove KB944899 for Visual Studio 2008 SP1 Beta1.
Visual Web Developer 2008 Express Edition now has support for Class Libraries and Web Application Projects. This enables you to leverage features only available in Visual Studio Standard and above before, including project-to-project references and the web application project build system. To create one of these projects, you can simply go to File > New Project. For more information on Web Application Projects (WAP), you can read this introduction to WAP on MSDN.
Note that Express SP1 is a standalone product that does not require Express RTM to be already installed, so you can install it on a clean machine. However if you choose to install Express SP1 on a machine that currently has RTM, your RTM version will automatically be uninstalled and replaced with the SP1 version. Also note that there are a couple installation behavioral limitations for SP1 Beta: Express SP1 Beta cannot be installed on top of a higher level SKU of Visual Studio (e.g. if you have Visual Studio Standard RTM on your machine, you will not be able to install VWD Express SP1 Beta); in addition, if you have a machine with both Express and Visual Studio installed, if you install the SP1 patch for Visual Studio, your Express SKU will not function properly.
Your JScript code can now be formatted in both inline script blocks and .js pages. See linked blog post for additional details on this new feature added for SP1.
SP1 includes support for the intellisense engine to work with external libraries jQuery, Ext, and Prototype. For more details on these fixes, please see our jQuery blog post or our Ext JS bog post.
The .NET framework 3.5 SP1 now has support for Dynamic Data and the Entities framework. As a part of Visual Studio SP1, we’ve added new templates for both web site and WAP to get you started working with these features. If you’re interested in learning more about Dynamic Data, you can visit the MSDN code gallery site for Dynamic Data. You can also use that site to download the latest releases and give feedback on the feature. Note that the templates that come with SP1 do not include the Dynamic Data wizard, which is available for download on the site.
We have added support for SQL Server 2008 in Visual Studio 2008. Specifically here is what we’ve added:
· Visual Web Developer Express now comes with the SQL Server 2008 Express Beta
· We now support drag-drop of SQL 2008-specific data types in the designer from the Server Explorer – examples include DateTime2, DateTimeOffset, Date, and Time.
· The control designers and wizards for SqlDataSource and ObjectDataSource also support the above SQL Server 2008 data types
· You can use the Database Publishing Wizard in Visual Studio (right-click a node in Server Explorer, and choose “Publish to provider…”) to publish to and from a SQL Server 2008 database
We now have proper renaming support for WCF classes inside of your Web Sites and Web Application Projects. If you rename your class, interface, or namespace of your WCF service, we now automatically fix up the web.config and SVC file so your web sites will build and work at run-time.
We have added two new templates in WAP projects and class libraries—one for an IIS module and one for an IIS handler. For more information on development using these, check out Mike Volodarsky’s post on advanced Web server deployment and development with IIS 7.0 and ASP.NET.
We have many areas in which we fixed bugs: Performance, HTML Editor, Jscript, CSS, Designer, and the Project system. Below you’ll find a more in-depth description of many of the improvements we’ve made in each area:
All performance hot fix changes are automatically a part of SP1. See http://blogs.msdn.com/webdevtools/archive/2008/02/09/downloadable-hotfix-performance-and-editor-fixes-for-microsoft-visual-studio-2008-and-visual-web-developer-express-2008.aspx for more information on the fixes here. In addition to the performance fixes in the hot fix changes, we have added the following fix seen below.
Note that you may still experience poor performance when typing in design view or during design/source view switch, as these have not been addressed fully in Beta.
http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=312199
Files marked “Copy Always” to the output directory in WAP do not get copied when you build to a location different than the default
AutoEventWireup="false" by default in sub-master page.
We now have the “Use Custom Web Server” option where you can specify a remote server to debug against. Screen shot below:
The following shortcut keys did not work in the designer:
Ctrl+I, Ctrl+U, Ctrl+L, Ctrl+B
Span tag selections, such as hyperlink controls, did not support the Positioning tool in the format menu. If you select these in design view and go to the format menu, the Position item will appear disabled. Some examples of these tags include: HyperLink, LinkButton, Label, CheckBox, RadioButton, SiteMapPath.
For certain elements (e.g. div, table, input), if you specify a percentage height specified and try to resize the element vertically, it is not resized. This happens when there is no outer positioned/sized container with height specified, Example:
<textarea id="TextArea1" cols="20" rows="2" style='width: 50%; height: 50%'></textarea><br />
<input id="Button1" type="button" value="button" style='width: 50%; height: 50%'/>
ASP.NET StylesheetTheme can't be use with Master Page in VS2008 RTM
In some cases the URL Picker dialog would give the wrong location for pages. For instance, if you had two pages in a folder, and in one page you had a server control that you wanted to link to another page by using the URL picker, you would get the “name of the directory/page.aspx” as opposed to “~/name of the directory/page.aspx”
http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=330792
BulletedList control rendered incorrectly on the designer within a DIV with Overflow set to Auto
~/ is not supported in <link> element
The following are some additional bug fixes in the designer space:
http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=315930
http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=317251
http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=321902
http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=337534
http://connect.microsoft.com/feedback/ViewFeedback.aspx?SiteID=477&FeedbackID=310198
http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=311717
http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=322465
http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=327262
Earlier today we shipped a public beta of our upcoming .NET 3.5 SP1 and VS 2008 SP1 releases.  These
Wow, this SP is really great 8)
{Copy paste uiteraard....} Earlier today we shipped a public beta of our upcoming .NET 3.5 SP1 and VS
In case you haven't heard, Microsoft has formally announced plans to provide a service pack (SP1
Good job guys. Does it show intellisense and comments for the standard jQuery distribution, or do you need one with special XML comments?
Thanks!
@Mike: You'll get a basic level of IntelliSense for standard jQuery, but we still recommend using a version that has the special XML comments. In SP1, you no longer get errors, but providing full IntelliSense for non-commented code isn't something that can be gained from a bug fix. =)
Hi.
I have two more points which are not really bugs, but gotchas which often cause time on development.
1. I often copy some code and paste it directly after it, or in other words I replicate code. Especially in the HTML editor with tables, because I don't want to type the raw table code again and again for each row, but paste and modify it. With VS 2005 SP1 it worked fine: Ctrl+C, 2, 3 or 4 times Ctrl+V. Now in VS 2008 Ctrl+V does not work if any text is selected, I first have to move the cursor to the end of the selection, press Ctrl+V, move to the new end etc... It would be nice to have Ctrl+V working again also if some text/code is currently selected.
2. I use generic lists etc. very often and since I use VS 2088 intellisense creates a ListBox<int> for me instead of a List<int>. This is because the C# class template in ASP.NET projects by default contains using statements for System.Web.UI and sub-namespaces but not System.Collections.Generic. These ASP.NET related namespaces are not needed most times in "normal" classes I guess, esp. comraped to other more common namespaces. If I use Add -> New Item -> Web Server Control it's ok, but not if I use Add -> Class.
Visual Studio 2008 Service Pack 1 Beta is now available!
Visual Studio 2008 Express Edition Service Pack 1 Beta is now available!
.NET Framework 3.5 Service Pack 1 Beta is now available!
Microsoft .NET framework 3.5 Service Pack 1 and Visual Studio 2008 Service Pack 1 now have public BETAs
.NET Visual Studio 2008 SP1 Beta VS2008 SP1 and .NET FX Beta Performance Improvements Introducing JScript
.NETVisualStudio2008SP1BetaVS2008SP1and.NETFXBetaPerformanceImprovementsIntroducing...