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:
From ScottGu's Blog: "Earlier today we shipped a public beta of our upcoming .NET 3.5 SP1 and VS 2008
A partir de hoy (Lunes 12 de Mayo) está disponible para la descarga la versión beta de lo que será el
Passi per ASP.NET Dynamic Data Controls , molto interessante per tirare su un sistema di gestione di
When are you going to add multiselect? i.e.-The ability to select multiple textboxes and change their property at one time?
"providing full IntelliSense for non-commented code"
I see that as a bug (of course MS doesn't, they never let standards bother them) so that's why I hoped this SP1 would solve what I deem to be a bug or at least a shortcoming.
Each new release must have a special VS version written for it, for every js library that you'd want to use. It's one thing that developers need to write docs (nobody likes that) but now there's the task of translating docs from format A to format B.
I hope now you understand why you need to fix this in the next SP or version of VS. Just a matter of understanding jsdoc is all. I know it's not xml, but it reasonably structured, so you can translate it real time to XML comments and then parse those for intellisense.
Never going to happen is my guess, am I right?
Hi Marco von Frieling--regarding your generic list issue, this should be addressed in the SP1 Beta, as we've revamped our using statements a bit. If you create a new C# class and type List, the "List<>" is what comes up in intellisense.
@Mike: I can't promise features, but I'd like you to know that we are well aware of the JSDoc compat issue. Standards are something we care very much about nowadays. We're part of OpenAJAX and there is a committee that works on rationalizing the documentation comment factions. At some point, we will either support both or at least there will be a translation mechanism. Unfortunately at the time of building our current IntelliSense engine (in late 2006), the JS libraries hadn't quite reached maturity and adoption was quite different than it is now. Our current format, although seemly one-off, is in natural alignment with C#/VB doc comments which many .NET developers are accustomed to. I hope this gives some insight into our rationale. Thanks for your feedback!
Eerder deze week brachten we een publieke betaversie uit van de komende .NET 3.5 SP1 en VS 2008 SP1.
This says that debugging classic ASP pages is fixed, but I have the SP1 beta installed and it is still not working. Does this work for anyone?
Also, the link for the bug goes to a report on the intellisense not being present. Intellisense is working for VBScript, but debugging is not.
What a shame that this STILL haven't been addressed:
Okay, debugging does work after all. I had thought that debugging support would include connecting to the process, but this is not the case. You have to manually connect just as you do in VS 2005.
【原文地址】 Visual Studio 2008 and .NET Framework 3.5 Service Pack 1 Beta 【原文发表日期】 Monday, May 12, 2008 9
Still no plans to fix the designer when the physical path to the project contains a "#" character?