{"id":4444,"date":"2008-05-12T04:00:00","date_gmt":"2008-05-12T04:00:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/webdev\/2008\/05\/12\/visual-studio-2008-sp1-beta\/"},"modified":"2008-05-12T04:00:00","modified_gmt":"2008-05-12T04:00:00","slug":"visual-studio-2008-sp1-beta","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/dotnet\/visual-studio-2008-sp1-beta\/","title":{"rendered":"Visual Studio 2008 SP1 Beta"},"content":{"rendered":"

Visual Studio 2008 SP1 Beta is now available!  You can download it here<\/A> (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\u2019ll 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.<\/P>\n

Installation Note<\/STRONG>: If you previously installed a Visual Studio 2008 Hotfix (in particular, KB944899), you should run the Hotfix Cleanup Utility before <\/STRONG>installing Visual Studio 2008 SP1 Beta. For more information, see Remove KB944899 for Visual Studio 2008 SP1 Beta1<\/A>. <\/P>\n

New Features<\/B>:<\/B><\/H3>\n
Class Libraries and Web Application Projects in Express<\/H5>\n

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<\/A>.<\/P>\n

\"clip_image002[9]\"<\/A><\/P>\n

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.<\/P>\n

JScript Formatting<\/H5>\n

Your JScript code can now be formatted in both inline script blocks and .js pages. See linked blog post for additional details<\/A> on this new feature added for SP1.<\/P>\n

\"clip_image003\"<\/A><\/P>\n

More Support for External JScript Libraries<\/H5>\n

SP1 includes support for the intellisense engine to work with external libraries jQuery<\/A>, Ext<\/A>, and Prototype<\/A>. For more details on these fixes, please see our jQuery blog post<\/A> or our Ext JS bog post<\/A>. <\/P>\n

\"clip_image005\"<\/A><\/P>\n

Dynamic Data Templates<\/H5>\n

The .NET framework 3.5 SP1 now has support for Dynamic Data and the Entities framework. As a part of Visual Studio SP1, we\u2019ve added new templates for both web site and WAP to get you started working with these features. If you\u2019re interested in learning more about Dynamic Data, you can visit the MSDN code gallery site for Dynamic Data<\/A>. 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.<\/P>\n

\"clip_image007\"<\/A><\/P>\n

SQL Server 2008 Support<\/H5>\n

We have added support for SQL Server 2008 in Visual Studio 2008. Specifically here is what we\u2019ve added:<\/P>\n

\u00b7 Visual Web Developer Express now comes with the SQL Server 2008 Express Beta<\/P>\n

\u00b7 We now support drag-drop of SQL 2008-specific data types in the designer from the Server Explorer \u2013 examples include DateTime2, DateTimeOffset, Date, and Time.<\/P>\n

\u00b7 The control designers and wizards for SqlDataSource and ObjectDataSource also support the above SQL Server 2008 data types<\/P>\n

\u00b7 You can use the Database Publishing Wizard in Visual Studio (right-click a node in Server Explorer, and choose \u201cPublish to provider\u2026\u201d) to publish to and from a SQL Server 2008 database<\/P>\n

\"clip_image008[4]\"<\/A><\/P>\n

WCF Renaming Support<\/H5>\n

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.<\/B><\/P>\n

\"clip_image010[4]\"<\/A><\/B><\/B><\/P>\n

IIS Module and Handler Templates<\/H5>\n

We have added two new templates in WAP projects and class libraries\u2014one for an IIS module and one for an IIS handler. For more information on development using these, check out Mike Volodarsky\u2019s post on advanced Web server deployment and development with IIS 7.0 and ASP.NET<\/A>.<\/P>\n

\"image\"<\/A> <\/P>\n

Bug Fixes<\/B>:<\/B><\/H3>\n

We have many areas in which we fixed bugs: Performance, HTML Editor, Jscript, CSS, Designer, and the Project system. Below you\u2019ll find a more in-depth description of many of the improvements we\u2019ve made in each area:<\/P>\n

Performance<\/B>:<\/B><\/H5>\n

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<\/A> 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.<\/P>\n

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.<\/P>\n\n\n\n\n\n\n
Issue<\/B><\/TD>\nDesigner load is extremely slow when assemblies are missing.<\/TD><\/TR>\n
Description<\/B><\/TD>\nIn a web site or WAP that references assemblies that are not present in your GAC or bin, changing to design view is extremely slow, and can make the IDE appear to hang if there are many instances of controls on the page that rely on assemblies that are missing.<\/TD><\/TR>\n
Resolution<\/B><\/TD>\nThis should now be a quick operation<\/TD><\/TR>\n
Link<\/B><\/TD>\nNone<\/TD><\/TR><\/TBODY><\/TABLE>\n
CSS:<\/H5>\n

<\/STRONG><\/P>\n\n\n\n\n\n\n
Issue<\/B><\/TD>\nCSS Formatting includes extra spaces. <\/TD><\/TR>\n
Description<\/B><\/TD>\nWhen you format your CSS document and you have a URL in quotes, extra spaces were inserted prior to the URL. An example is: background: url(‘Images\/myBackground.jpg’ ); inserting would cause background: url(‘ Images\/myBackground.jpg’ ).<\/TD><\/TR>\n
Resolution<\/B><\/TD>\nThis should now be a quick operationNo spaces are inserted on document formatting<\/TD><\/TR>\n
Link<\/B><\/TD>\nhttp:\/\/connect.microsoft.com\/VisualStudio\/feedback\/ViewFeedback.aspx?FeedbackID=337653<\/A><\/TD><\/TR><\/TBODY><\/TABLE>\n
JScript:<\/H5>\n\n\n\n\n\n\n
Issue<\/B><\/TD>\nAdd support for remote jscript files in intellisense<\/TD><\/TR>\n
Description<\/B><\/TD>\nYou were unable to load js from absolute URLs – Example: <script src=”http:\/\/mydomain.com\/file.js”><\/TD><\/TR>\n
Resolution<\/B><\/TD>\nYou can now load Jscript files from absolute URLs, so you can refer to remote .js files on web servers and get intellisense on those files.<\/TD><\/TR>\n
Link<\/B><\/TD>\nNone<\/A><\/TD><\/TR><\/TBODY><\/TABLE>\n\n\n\n\n\n\n
Issue<\/B><\/TD>\nJavaScript IntelliSence missing RegExp object members. <\/TD><\/TR>\n
Description<\/B><\/TD>\nIf you declared a RegExp variable, such as \u201cvar reg = new RegExp(“e”);\u201d, and typed reg., you would get no intellisense dropdown.<\/TD><\/TR>\n
Resolution<\/B><\/TD>\nYou now get intellisense on the RegEx class.<\/TD><\/TR>\n
Link<\/B><\/TD>\nhttp:\/\/connect.microsoft.com\/VisualStudio\/feedback\/ViewFeedback.aspx?FeedbackID=331534<\/A><\/A><\/TD><\/TR><\/TBODY><\/TABLE>\n\n\n\n\n\n\n
Issue<\/B><\/TD>\nTypo in JavaScript IntelliSense<\/TD><\/TR>\n
Description<\/B><\/TD>\nUnder the string properties, you will see \u201cfontSize()\u201d and \u201cfontColor()\u201d.<\/TD><\/TR>\n
Resolution<\/B><\/TD>\nThey are now fontsize() and fontcolor().<\/TD><\/TR>\n
Link<\/B><\/TD>\nhttp:\/\/connect.microsoft.com\/VisualStudio\/feedback\/ViewFeedback.aspx?FeedbackID=331523<\/A><\/A><\/TD><\/TR><\/TBODY><\/TABLE>\n
Editor:<\/H5>\n\n\n\n\n\n\n
Issue<\/B><\/TD>\nVB Snippets in inline web services do not properly insert import statements. <\/TD><\/TR>\n
Description<\/B><\/TD>\nIn an inline web service (not in a code behind page), if you choose to insert a snippet that requires an import, we used to add \u201c<%@… %> statements<\/TD><\/TR>\n
Resolution<\/B><\/TD>\nProper code import statements are now added.<\/TD><\/TR>\n
Link<\/B><\/TD>\nNone<\/A><\/TD><\/TR><\/TBODY><\/TABLE>\n\n\n\n\n\n\n
Issue<\/B><\/TD>\nVisual Studio does not have support for VBScript<\/TD><\/TR>\n
Description<\/B><\/TD>\nIn Visual Studio 2008 support for VBScript was removed, so text colorization and intellisense no longer functioned.<\/TD><\/TR>\n
Resolution<\/B><\/TD>\nWe have returned support here so it should work similarly to past versions<\/TD><\/TR>\n
Link<\/B><\/TD>\nhttps:\/\/connect.microsoft.com\/VisualStudio\/feedback\/ViewFeedback.aspx?FeedbackID=292379<\/A><\/A><\/TD><\/TR><\/TBODY><\/TABLE>\n\n\n\n\n\n\n
Issue<\/B><\/TD>\nDebugging classic ASP pages<\/TD><\/TR>\n
Description<\/B><\/TD>\nBreakpoints were not properly hit in classic ASP pages<\/TD><\/TR>\n
Resolution<\/B><\/TD>\nThey are now working properly<\/TD><\/TR>\n
Link<\/B><\/TD>\nhttp:\/\/connect.microsoft.com\/VisualStudio\/feedback\/ViewFeedback.aspx?FeedbackID=322633<\/A><\/A><\/TD><\/TR><\/TBODY><\/TABLE>\n\n\n\n\n\n\n
Issue<\/B><\/TD>\nQuotes not inserted after Class or CssClass attribute even when the option is enabled<\/TD><\/TR>\n
Description<\/B><\/TD>\nIf you type the \u201cclass\u201d or \u201cCssClass\u201d property with the option to \u201cInsert Attribute Value Quotes when Typing\u201d, you used to get no quotes.<\/TD><\/TR>\n
Resolution<\/B><\/TD>\nThis option now works properly<\/TD><\/TR>\n
Link<\/B><\/TD>\nNone<\/A><\/TD><\/TR><\/TBODY><\/TABLE>\n\n\n\n\n\n\n
Issue<\/B><\/TD>\nHTML editor in Split view resize problem<\/TD><\/TR>\n
Description<\/B><\/TD>\nIn split view in a dual monitor setup, when \u201cvertical split mode\u201d is enabled, you were unable to drag the splitter around.<\/TD><\/TR>\n
Resolution<\/B><\/TD>\nNow you are able to drag the splitter around<\/TD><\/TR>\n
Link<\/B><\/TD>\nhttp:\/\/connect.microsoft.com\/VisualStudio\/feedback\/ViewFeedback.aspx?FeedbackID=317032<\/A><\/A><\/TD><\/TR><\/TBODY><\/TABLE>\n\n\n\n\n\n\n
Issue<\/B><\/TD>\nImages disappear in design view when opening 2nd or more aspx pages<\/TD><\/TR>\n
Description<\/B><\/TD>\nIf your ImageUrl on a server control points to an image location that is not app relative, the image would not always display correctly in the designer.<\/TD><\/TR>\n
Resolution<\/B><\/TD>\nThe image should now display correctly<\/TD><\/TR>\n
Link<\/B><\/TD>\nhttp:\/\/connect.microsoft.com\/VisualStudio\/feedback\/ViewFeedback.aspx?FeedbackID=308786<\/A><\/A><\/TD><\/TR><\/TBODY><\/TABLE>\n
Project System \/ Templates \/ Compilation \/ Debugging<\/H5>\n\n\n\n\n\n\n
Issue<\/B><\/TD>\nCOMException when you open a WAP that uses IIS without permissions to IIS<\/TD><\/TR>\n
Description<\/B><\/TD>\nIf you try to open a WAP that uses IIS without admin privileges, you will get an a cryptic error message talking of a \u201cSystem.Runtime.InteropServices.COMException\u201d. This can also happen when you upgrade your existing VS2005 WAPs.<\/TD><\/TR>\n
Resolution<\/B><\/TD>\nNow you get an actionable error message<\/TD><\/TR>\n
Link<\/B><\/TD>\nhttp:\/\/connect.microsoft.com\/VisualStudio\/feedback\/ViewFeedback.aspx?FeedbackID=317124<\/A><\/A><\/TD><\/TR><\/TBODY><\/TABLE>\n\n\n\n\n\n\n
Issue<\/B><\/TD>\nUsing configSource for <system.web><compilation> section breaks debugging in VS2008<\/TD><\/TR>\n
Description<\/B><\/TD>\nIn 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.<\/TD><\/TR>\n
Resolution<\/B><\/TD>\nNow if Visual Studio detects a configSource, we ignore the debug option and you must set this manually.<\/TD><\/TR>\n
Link<\/B><\/TD>\n\n

http:\/\/connect.microsoft.com\/VisualStudio\/feedback\/ViewFeedback.aspx?FeedbackID=312199<\/A><\/P><\/TD><\/TR><\/TBODY><\/TABLE>\n\n\n\n\n\n\n
Issue<\/B><\/TD>\n\n

Files marked \u201cCopy Always\u201d to the output directory in WAP do not get copied when you build to a location different than the default<\/P><\/TD><\/TR>\n

Description<\/B><\/TD>\nIn a WAP project, if you add a file and change it to \u201cCopy Always\u201d in the property grid, it will not get copied if you try to output to some other folder, such as by the following command line \u201cmsbuild \/p:OutDir=c:\\MyOutDir WebApplication1.csproj\u201d. Note that this is how Team Build operates so files of this type in Team Build cases will be copied properly.<\/TD><\/TR>\n
Resolution<\/B><\/TD>\nNow files marked as this type will be copied<\/TD><\/TR>\n
Link<\/B><\/TD>\nNone<\/A><\/TD><\/TR><\/TBODY><\/TABLE>\n\n\n\n\n\n\n
Issue<\/B><\/TD>\nVS will hang with IE8 when Ctrl-F5, View in Browser, or F5<\/TD><\/TR>\n
Description<\/B><\/TD>\nIn the IE8 Beta, Visual Studio would hang for long periods of time when starting the web browser with or without the debugger<\/TD><\/TR>\n
Resolution<\/B><\/TD>\nThis should now behave like other versions of IE.<\/TD><\/TR>\n
Link<\/B><\/TD>\nNone<\/A><\/TD><\/TR><\/TBODY><\/TABLE>\n\n\n\n\n\n\n
Issue<\/B><\/TD>\nMultiple debug actions without closing IE may deadlock VS with IE.<\/TD><\/TR>\n
Description<\/B><\/TD>\nWith script debugging enabled, occasionally on certain configurations VS might hang when starting without debugging.<\/TD><\/TR>\n
Resolution<\/B><\/TD>\nVS should no longer hang<\/TD><\/TR>\n
Link<\/B><\/TD>\nNone<\/A><\/TD><\/TR><\/TBODY><\/TABLE>\n\n\n\n\n\n\n
Issue<\/B><\/TD>\n\n

AutoEventWireup=”false” by default in sub-master page.<\/P><\/TD><\/TR>\n

Description<\/B><\/TD>\nWhen you create a master page that inherits another master page, the template will set AutoEventWireup=\u201dfalse\u201d<\/TD><\/TR>\n
Resolution<\/B><\/TD>\nIt is now set to \u201ctrue\u201d in this case<\/TD><\/TR>\n
Link<\/B><\/TD>\nhttp:\/\/connect.microsoft.com\/VisualStudio\/feedback\/ViewFeedback.aspx?FeedbackID=299418<\/A><\/A><\/TD><\/TR><\/TBODY><\/TABLE>\n\n\n\n\n\n\n
Issue<\/B><\/TD>\nWeb config validation does not recognize ‘traceOutputOptions’ attribute<\/TD><\/TR>\n
Description<\/B><\/TD>\nThe web.config would squiggle the ‘traceOutputOptions’ attribute and indicate that it is not a recognized attribute. It would give the error: \u201cThe ‘traceOutputOptions’ attribute is invalid – The value ‘Callstack, DateTime’ is invalid according to its datatype ‘NmToken’ – The ‘,’ character, hexadecimal value 0x2C, cannot be included in a name.\u201d<\/TD><\/TR>\n
Resolution<\/B><\/TD>\nIt now validates this correctly<\/TD><\/TR>\n
Link<\/B><\/TD>\nhttp:\/\/connect.microsoft.com\/VisualStudio\/feedback\/ViewFeedback.aspx?FeedbackID=304108<\/A><\/TD><\/TR><\/TBODY><\/TABLE>\n\n\n\n\n\n\n
Issue<\/B><\/TD>\nWeb Debugging fails if compilation element is defined inside of <location> element.<\/TD><\/TR>\n
Description<\/B><\/TD>\nIf you had a <location> tag in your web config, in which you had set debug=true, Visual Studio did not properly parse the file and tried to set debug=true anyway, which could break your web.config.<\/TD><\/TR>\n
Resolution<\/B><\/TD>\nNow we only set compilation debug to true if either we have root System.Web section which contains a <compilation> tag, or if you have neither a root System.web compilation section nor a <location> tag.<\/TD><\/TR>\n
Link<\/B><\/TD>\nhttp:\/\/connect.microsoft.com\/VisualStudio\/feedback\/ViewFeedback.aspx?FeedbackID=293526<\/A><\/A><\/TD><\/TR><\/TBODY><\/TABLE>\n\n\n\n\n\n\n
Issue<\/B><\/TD>\nAutomatically updating webreference in client, while debugging webservice on the same machine.<\/TD><\/TR>\n
Description<\/B><\/TD>\nThere are cases when Visual Studio may update a web reference while you are debugging.<\/TD><\/TR>\n
Resolution<\/B><\/TD>\nWe now explicitly prohibit Visual Studio from updating a web reference while in debug mode.<\/TD><\/TR>\n
Link<\/B><\/TD>\nhttp:\/\/connect.microsoft.com\/VisualStudio\/feedback\/ViewFeedback.aspx?FeedbackID=303796<\/A><\/A><\/TD><\/TR><\/TBODY><\/TABLE>\n\n\n\n\n\n\n
Issue<\/B><\/TD>\nVS2005 Publishes bin\\vssver2.scc<\/TD><\/TR>\n
Description<\/B><\/TD>\nIn a Web Application Project under source control, if you build and Publish Project we would publish the vssver2.scc file, and subsequent publishes would fail with the error \u201cUnable to add \u2018bin\/vssver2.scc\u2019 to the Web. The file \u2018bin\\vssver2.scc\u2019 already exists in the Web.<\/TD><\/TR>\n
Resolution<\/B><\/TD>\nVisual Studio no longer publishes this file, so publishing should no longer fail<\/TD><\/TR>\n
Link<\/B><\/TD>\nhttp:\/\/connect.microsoft.com\/VisualStudio\/feedback\/ViewFeedback.aspx?FeedbackID=310296<\/A><\/A><\/TD><\/TR><\/TBODY><\/TABLE>\n\n\n\n\n\n\n
Issue<\/B><\/TD>\n.sln file for Web Site solution doesn’t update PhysicalPath property when the .sln file is Saved As…<\/TD><\/TR>\n
Description<\/B><\/TD>\nWhen you do a \u201cSave As\u2026\u201d on your solution and you save it to a different location, the AspNetCompiler.PhysicalPath property of your solution would not change to reflect the new relative path of your web sites against that solution. This would cause MSBuild to fail with an error 1003: The directory \u2018<dirname>\u2019 doesn\u2019t exist.\u201d<\/TD><\/TR>\n
Resolution<\/B><\/TD>\nNow when you save your solution somewhere, the solution is dirtied with the new correct path to your web sites.<\/TD><\/TR>\n
Link<\/B><\/TD>\nNone<\/A><\/TD><\/TR><\/TBODY><\/TABLE>\n\n\n\n\n\n\n
Issue<\/B><\/TD>\nCannot Use IIS Web Server option and set project URL<\/TD><\/TR>\n
Description<\/B><\/TD>\nIn a WAP project where the files are on a remote location, if you specified a remote server to debug against in the Web property pages under \u201cUse Local IIS Web Server\u201d, we would not allow you to proceed without configuring the virtual directory, which was not possible for remote servers. This made it very difficult to debug against a remote IIS location for remote WAPs.<\/TD><\/TR>\n
Resolution<\/B><\/TD>\n\n

We now have the \u201cUse Custom Web Server\u201d option where you can specify a remote server to debug against. Screen shot below: <\/P>\n

\"image\"<\/A> <\/P><\/TD><\/TR>\n

Link<\/B><\/TD>\nhttp:\/\/connect.microsoft.com\/VisualStudio\/feedback\/ViewFeedback.aspx?FeedbackID=324664<\/A><\/A><\/TD><\/TR><\/TBODY><\/TABLE>\n
Designer<\/H5>\n\n\n\n\n\n\n
Issue<\/B><\/TD>\nHTML designer does not accept keyboard shortcuts<\/TD><\/TR>\n
Description<\/B><\/TD>\n\n

The following shortcut keys did not work in the designer:<\/P>\n

Ctrl+I, Ctrl+U, Ctrl+L, Ctrl+B<\/P><\/TD><\/TR>\n

Resolution<\/B><\/TD>\nThey now do the following: I = italic, U = underline, L = hyperlink, and B = bold<\/TD><\/TR>\n
Link<\/B><\/TD>\nhttp:\/\/connect.microsoft.com\/VisualStudio\/feedback\/ViewFeedback.aspx?FeedbackID=321928<\/A><\/A><\/TD><\/TR><\/TBODY><\/TABLE>\n\n\n\n\n\n\n
Issue<\/B><\/TD>\n“Format->Position” is disabled for all <span> based controls (Label, Hyperlink, SiteMapPath), absolute position on drop also does not work.<\/TD><\/TR>\n
Description<\/B><\/TD>\n\n

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.<\/P><\/TD><\/TR>\n

Resolution<\/B><\/TD>\nThis has been enabled for span selections.<\/TD><\/TR>\n
Link<\/B><\/TD>\nNone<\/A><\/TD><\/TR><\/TBODY><\/TABLE>\n\n\n\n\n\n\n
Issue<\/B><\/TD>\n<div> inside a table renders poorly when a width syle in percentage is applied<\/TD><\/TR>\n
Description<\/B><\/TD>\nIf inside a table cell you put text that wraps inside of a div tag that has a width applied, an example looking something like: \u201c<div style=\u201dwidth:50%\u201d>Long Text Here<\/div>\u201d, the div will render improperly with a very small width<\/TD><\/TR>\n
Resolution<\/B><\/TD>\nIt now matches IE<\/TD><\/TR>\n
Link<\/B><\/TD>\nNone<\/A><\/TD><\/TR><\/TBODY><\/TABLE>\n\n\n\n\n\n\n
Issue<\/B><\/TD>\nUnable to resize vertically certain html elements that have a height specified in percentage.<\/TD><\/TR>\n
Description<\/B><\/TD>\n\n

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:<\/P>\n

<textarea id=”TextArea1″ cols=”20″ rows=”2″ style=’width: 50%; height: 50%’><\/textarea><br \/><\/P>\n

<input id=”Button1″ type=”button” value=”button” style=’width: 50%; height: 50%’\/><\/P><\/TD><\/TR>\n

Resolution<\/B><\/TD>\nThe elements are now able to be resized in the designer<\/TD><\/TR>\n
Link<\/B><\/TD>\n<\/A><\/TD><\/TR><\/TBODY><\/TABLE>\n\n\n\n\n\n\n
Issue<\/B><\/TD>\n\n

ASP.NET StylesheetTheme can’t be use with Master Page in VS2008 RTM<\/P><\/TD><\/TR>\n

Description<\/B><\/TD>\nIf you\u2019re using master\/content pages, in your content page if you apply a theme as a StyleSheetTheme, but the theme contains a CSS page (as opposed to just Skin files), you will get an error rendering your page in design view for the content page.<\/TD><\/TR>\n
Resolution<\/B><\/TD>\nThe theme now displays correctly.<\/TD><\/TR>\n
Link<\/B><\/TD>\nhttp:\/\/connect.microsoft.com\/VisualStudio\/feedback\/ViewFeedback.aspx?FeedbackID=314745<\/A><\/A><\/TD><\/TR><\/TBODY><\/TABLE>\n\n\n\n\n\n\n
Issue<\/B><\/TD>\nProblem with NavigateURL of Hyperlink Control – URL resolution<\/TD><\/TR>\n
Description<\/B><\/TD>\n\n

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
\u201cname of the directory\/page.aspx\u201d as opposed to \u201c~\/name of the directory\/page.aspx\u201d<\/P><\/TD><\/TR>\n

Resolution<\/B><\/TD>\nWe now give the proper app-relative URL<\/TD><\/TR>\n
Link<\/B><\/TD>\n\n

http:\/\/connect.microsoft.com\/VisualStudio\/feedback\/ViewFeedback.aspx?FeedbackID=330792<\/A><\/P><\/TD><\/TR><\/TBODY><\/TABLE>\n\n\n\n\n\n\n
Issue<\/B><\/TD>\n\n

BulletedList control rendered incorrectly on the designer within a DIV with Overflow set to  Auto<\/P><\/TD><\/TR>\n

Description<\/B><\/TD>\nFrom within a container such as a div, bulleted items, such as <li>, might overflow outside of the container control with the overflow value set to hidden<\/TD><\/TR>\n
Resolution<\/B><\/TD>\nIt now properly clips the bulleted items when the overflow is set to hidden<\/TD><\/TR>\n
Link<\/B><\/TD>\nNone<\/A><\/TD><\/TR><\/TBODY><\/TABLE>\n\n\n\n\n\n\n
Issue<\/B><\/TD>\nComponent One Menu and Toolbar render a weird “x” in DV<\/TD><\/TR>\n
Description<\/B><\/TD>\nRendering a zero width div would render it as no width<\/TD><\/TR>\n
Resolution<\/B><\/TD>\nIt is now rendered as zero width<\/TD><\/TR>\n
Link<\/B><\/TD>\nNone<\/A><\/TD><\/TR><\/TBODY><\/TABLE>\n\n\n\n\n\n\n
Issue<\/B><\/TD>\nCannot insert a Hyperlink with an Image selection<\/TD><\/TR>\n
Description<\/B><\/TD>\nWith an image selected, you could not convert it to a hyperlink by going to the \u201cFormat > Convert to Hyperlink\u201d command, as it was disabled.<\/TD><\/TR>\n
Resolution<\/B><\/TD>\nThis command is now enabled for images<\/TD><\/TR>\n
Link<\/B><\/TD>\nNone<\/A><\/TD><\/TR><\/TBODY><\/TABLE>\n\n\n\n\n\n\n
Issue<\/B><\/TD>\nUnable to drop two controls w\/ same namespace, but from different assemblies on the design surface.<\/TD><\/TR>\n
Description<\/B><\/TD>\nIf you have two assemblies with two different custom controls that have the same namespace, when you drag the custom control, Visual Studio will incorrectly change the tag prefix of the first control to that of the second control, so you will get errors rendering these.<\/TD><\/TR>\n
Resolution<\/B><\/TD>\nIt now correctly respects the tagprefixes and namespaces.<\/TD><\/TR>\n
Link<\/B><\/TD>\nNone<\/A><\/TD><\/TR><\/TBODY><\/TABLE>\n\n\n\n\n\n\n
Issue<\/B><\/TD>\nCSS files in folders nested under App_Themes are not picked up at design time in VS 2008 RTM<\/TD><\/TR>\n
Description<\/B><\/TD>\nWhen using themes, if you create a style in a nested folder inside of your theme (e.g. App_Themes\\Theme1\\MyStyleSheets\\MyStyles.css), these would not be picked up by the designer.<\/TD><\/TR>\n
Resolution<\/B><\/TD>\nThey now display properly.<\/TD><\/TR>\n
Link<\/B><\/TD>\nhttp:\/\/connect.microsoft.com\/VisualStudio\/feedback\/ViewFeedback.aspx?FeedbackID=312146<\/A><\/A><\/TD><\/TR><\/TBODY><\/TABLE>\n\n\n\n\n\n\n
Issue<\/B><\/TD>\nMany NBSPs added and tag name corruption when editing a page that uses Telerik controls (popular custom controls)<\/TD><\/TR>\n
Description<\/B><\/TD>\nWhen there are multiple register directives for the same namespace in different assemblies, multiple NBSPs may be generated in your page and your markup could possibly be changed incorrect. This can be seen when using some Telerik controls.<\/TD><\/TR>\n
Resolution<\/B><\/TD>\nVS no longer changes your code incorrectly<\/TD><\/TR>\n
Link<\/B><\/TD>\nhttp:\/\/forums.asp.net\/t\/1185266.aspx<\/A><\/A><\/TD><\/TR><\/TBODY><\/TABLE>\n\n\n\n\n\n\n
Issue<\/B><\/TD>\nStyle was not preserved during style editing<\/TD><\/TR>\n
Description<\/B><\/TD>\nIn an inline style, there were cases when after using the style builder, your single quotes would be turned into \u201c&quot\u201d.<\/TD><\/TR>\n
Resolution<\/B><\/TD>\nWe now always use single quotes in inline styles<\/TD><\/TR>\n
Link<\/B><\/TD>\nNone<\/A><\/TD><\/TR><\/TBODY><\/TABLE>\n\n\n\n\n\n\n
Issue<\/B><\/TD>\n\n

~\/ is not supported in <link> element<\/P><\/TD><\/TR>\n

Description<\/B><\/TD>\nIf you put a \u201c~\/\u201d in a link tags that were runat=server to refer to a location of a style sheet, Visual Studio wouldn\u2019t be able to interpret this. E.g. \u201c<link href=”~\/Styles\/StyleSheet.css” rel=”stylesheet” type=”text\/css” runat=”server” \/>\u201d<\/TD><\/TR>\n
Resolution<\/B><\/TD>\nThis is now allowed at design-time.<\/TD><\/TR>\n
Link<\/B><\/TD>\nNone<\/A><\/TD><\/TR><\/TBODY><\/TABLE>\n\n\n\n\n\n\n
Issue<\/B><\/TD>\nTelerik Controls Not Working in Visual Studio 2008<\/TD><\/TR>\n
Description<\/B><\/TD>\nSome telerik control configuration aren\u2019t working properly in all cases in VS2008. Specifically, if you click on the RadAjaxManager and click Configure Ajax Manager, you will get an empty collection when you inherit from a master page.<\/TD><\/TR>\n
Resolution<\/B><\/TD>\nYou now get the appropriate collection when using this configuration utility.<\/TD><\/TR>\n
Link<\/B><\/TD>\nhttp:\/\/www.telerik.com\/community\/forums\/thread\/b311D-bbgthd.aspx<\/A><\/A><\/TD><\/TR><\/TBODY><\/TABLE>\n

The following are some additional bug fixes in the designer space:<\/P>\n

http:\/\/connect.microsoft.com\/VisualStudio\/feedback\/ViewFeedback.aspx?FeedbackID=315930<\/A><\/P>\n

http:\/\/connect.microsoft.com\/VisualStudio\/feedback\/ViewFeedback.aspx?FeedbackID=317251<\/A><\/P>\n

http:\/\/connect.microsoft.com\/VisualStudio\/feedback\/ViewFeedback.aspx?FeedbackID=321902<\/A><\/P>\n

http:\/\/connect.microsoft.com\/VisualStudio\/feedback\/ViewFeedback.aspx?FeedbackID=337534<\/A><\/P>\n

http:\/\/connect.microsoft.com\/feedback\/ViewFeedback.aspx?SiteID=477&FeedbackID=310198<\/A><\/P>\n

http:\/\/connect.microsoft.com\/VisualStudio\/feedback\/ViewFeedback.aspx?FeedbackID=311717<\/A><\/P>\n

http:\/\/connect.microsoft.com\/VisualStudio\/feedback\/ViewFeedback.aspx?FeedbackID=322465<\/A><\/P>\n

http:\/\/connect.microsoft.com\/VisualStudio\/feedback\/ViewFeedback.aspx?FeedbackID=327262<\/A><\/P><\/p>\n","protected":false},"excerpt":{"rendered":"

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\u2019ll attempt to give an overview of the features as well as some of the key issues the […]<\/p>\n","protected":false},"author":404,"featured_media":58792,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[197],"tags":[7265,31,7271,7304,7303,147,7302,7292,7267,7268],"class_list":["post-4444","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-aspnet","tag-announcements","tag-asp-net","tag-css","tag-ie8beta","tag-sp1","tag-visual-studio","tag-visual-studio-2008","tag-vs2008","tag-vwd","tag-web"],"acf":[],"blog_post_summary":"

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\u2019ll attempt to give an overview of the features as well as some of the key issues the […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts\/4444","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/users\/404"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/comments?post=4444"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts\/4444\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/media\/58792"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/media?parent=4444"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/categories?post=4444"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/tags?post=4444"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}