Your official information source from the .NET Web Development and Tools group at Microsoft.
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.
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”
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:
What has happened to the ReportViewer control in VWD 2008?
I have a 2005 project that uses the 2005 ReportViewer control. This project is now located on a new machine that has VWD 2008 on it (not VWD 2005).
I have installed the ReportViewer 2008 redistributable but the ReportViewer control does not appear in the VWD 2008 toolbox and is not available to add. The ReportViewer 2005 installer won't run without VWD 2005 so my project can't be modified / built in 2008.
Any idea why this is or when a fix will be available?
Oh my deepest and deepest thank you! Support for Class Libraries and Web Application Projects in Express. That makes it U*S*E*F*U*L for other things than as a toy! I bow of respect!
Cause it's not about being cheap and not wanting to pay for the PRO version, as I say in my blog post at http://blogs.aspcode.net/archive/2008/05/20/288.aspx I have paid for VS since Visual Studio 97, sometimes with MSDN Enterprise subscriptions. It's just about something small and slick, quick to load etc and I cant tell you how good the timing is I foudn out about this update.
On XP Pro PC with all windows updates on prior to all original Express versions of VWD 2008, VC# 2008 and SQL 2005 (plus Management Studio). The PC is relatively new and has never had anything other than these express tools on it. The only other MS product of note is MS Virtual PC 2007. Checked windows updates prior to installing SP1 Beta for VC# and then for VWD. No web application projects are available from any menu. Uninstalled VWD 2008 SP1 Beta, rebooted and installed it from scratch using same install exe. Still the same issue. Does RTFM apply here or is there really a problem?
I haven't had any issues with the ReportViewer control. The ReportViewer should show up under the Reporting tab. I even double checked to make sure it shows regardless of what framework version you are targetting (2.0, 3.0 or 3.5). It will be above the Crystal Reports controls. If it is not there, you might try adding it manually by browsing to the assembly in the assembly cache.
If you cannot find the Microsoft.ReportViewer.Design and the Microsoft.ReportViewer.WebDesign assemblies in your assembly cache, then you have an installation problem, and you need to try to reinstall the product.
Tools > Import and Export Settings > Reset all settings.
MPoole: What do you see as your version number if you go to Help > About in VWD Express SP1? Are you seeing the other SP1 features in your express build? For instance, if you go to tools > options, do you see the JScript node under text editor? If you go to %program files%\Microsoft Visual Studio 9.0\Common7\IDE\VWDExpress\ProjectTemplates\CSharp\Web\1033, do you see project templates there?
Feel free to email me at johndund at microsoft dot com so we can help investigate.
This SP1 Beta doesn't solve my issue.
After installing SP1 Beta, I still having the below issue.
"Using configSource for <system.web><compilation> section breaks debugging in VS2008
Description In a WAP project, if you had a configSource in your web.config that pointed to a section that enabled debugging, Visual Studio would not detect this and prompt you to enable debugging anyway, thus breaking your web.config.
Resolution Now if Visual Studio detects a configSource, we ignore the debug option and you must set this manually. "
How do solve this?
tammy, We fixed it in sp1. This is what we did:
If we see compilation configSource in web.config, we'll assume the user put debug=true in the config source config file and simply ignore putting debug=true.
Could you confirm this please? thanks
1. Create a compilation.config under root
2. move web.config's compilation node to compilation.config, and make it debug=true
3. In web.config's original place, put <compilation configSource='compilation.config' />
4. F5. Verify debugging started successfully.
<add assembly="System.Core, Version=184.108.40.206, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
<add assembly="System.Web.Extensions, Version=220.127.116.11, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
<add assembly="System.Data.DataSetExtensions, Version=18.104.22.168, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
<add assembly="System.Xml.Linq, Version=22.214.171.124, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
tammy, if you still have the problem, could you post your web.config and brief repro steps? Thanks.
Will this service pack allow remote debugging of classic ASP (VS 2008 Pro) through the Remote Debugger? we have a number of sites on our development box and having to setup our local IIS to work on one can be a pain..
Yes you can remote debug classic ASP on VS2008 SP1. However you will need to manually attached the debugger to the remote process. Auto-attach via F5 will not work for classic ASP.
If you plan to setup a remote development box, I would also warn that it is *not* recommended for team development as any developer debugging the remote machine will block all other developers from using that server.
Is there any way of having multiple developers remotely debugging? I have both VS 2005 Standard and Visual Studio 2008 Standard at home and I know it does not support the remote debugging (I just have it installed on my dev box at home).
but at work we currently are running VS 2005 Professional and have multiple developers all developing on there local machines on a dot net project with subversion. and we also have a large number of classic sites running on our development box that we still maintain. It would be nice if we didn't have to pull down a copy of the site each time we wanted to work on it.
Is there any way for us to have multiple developers debugging remotely? (there would never be 2 developers debugging the same site, at the same time)
Also out of curiosity does the intellisense for classic ASP have any way of recognizing class files and giving you intelsense for the class functions?
Earlier today we shipped a public beta of our upcoming .NET 3.5 SP1 and VS 2008 SP1 releases. These servicing
Unfortunately there isn't a way to have multiple developers debug the same server remotely. I think the best recommendation is either only having 1 developer debug the remote server, or to create a local copy of the application on the developer's machine.
Visual Web Developer