February 25, 2011
Blog ArchivesHow to compress CSS/JavaScript before publish/package
Today I saw a post on stackoverflow.com asking Using Microsoft AJAX Minifier with Visual Studio 2010 1-click publish . This is a response to that question. The Web Publishing Pipeline is pretty extensive so it is easy for us to hook in to it in order t…
0
Working with different versions of AjaxControlToolkit in Visual Studio 2010
When working with different versions of AjaxControlToolkit , Visual Studio 2010 contains some interesting improvements compared to previous versions of Visual Studio. When adding a particular version of AjaxControlToolkit controls (or other similar third-party controls) to the toolbox using the Choose Toolbox Items dialog, we now show the version number of the control that is being added. Figure 1 Once various versions of these AjaxControlToolkit (ACT) controls such as ACT 3.0 and ACT 4.0 are added to the toolbox in separate tabs (one tab per version), o nly the latest applicable version of the ACT controls will display as visible in the toolbox. This reduces confusion when different versions of ACT are present. The version number of the control…(read more)
General Performance Improvements in VS2010 since Beta2
When we released Beta2 in Oct 2009, there was a lot of customer excitement about the super cool features in VS 2010. However, one recurring complaint from customers was that the performance of VS 2010 was not on par with Orcas. Customers were experiencing general slowness in a lot of features that was hindering them with daily operations. We heard you all loud and clear. Since then our team has put in a lot of hard work to deliver a first class experience in Web Developement and have fixed a lot of performance issues seen in Beta2. The most notable ones are 1. Switching to Desiger from Editor 2. General Designer performance 3. Loading Toolbox 4. Command line msbuild 5. Build and Rebuild within IDE 6. Adding events by double-clicking controls…(read more)
VWD Available on Web Platform Installer (Now in Four Languages)
Visual Web Developer 2010 Express is available for installation via the Web Platform Installer at http://micorosoft.com/express/web . The English SKU was published on April 12 th , French, German and Japanese went live on April 27 th and Spanish, Italian, Russian, Simplified Chinese, Traditional Chinese, and Korean will be released soon. Running the Web Platform Installer on an operating system of one of the available languages automatically selects that language of Visual Web Developer 2010 Express (VWD) to be installed. You can select a different language by using the Options link at the lower-left corner of the main WebPI window. In the “Change Options” dialog, select the language you’d like to have installed. If it’s available, you’ll see…(read more)
Design View Performance Improvements
Hi, I’m Dan Chartier, I work on the Web Tools designer and helped improve its performance in Visual Studio 2010. For some background, Visual Studio 2008 completely replaced the original trident (Internet Explorer) designer with the FrontPage designer (which is also used by Expression Web). While we gained many improvements with this change, we received customer complaints about various performance problems that we wanted to address in 2010. In general, the designer is quite fast. This is especially true when editing pure HTML documents, which is what it was originally designed to do well. However, the designer edits more than HTML. It also has the rather sophisticated ability to edit ASP.Net pages containing various interesting web controls…(read more)
Tip #104: Did you know … How to view text for the ‘hint’ buttons on the Publish Web Dialog?
After the Beta 2 release of Visual Studio 2010, the Publish Web Dialog was modified to include two information buttons associated with the Service URL and Site/application text boxes. (See Figure 1) Figure 1 – New information (‘hint’) buttons (see circled…(read more)
Tip #103 revisited
In Tip #103 I showed a way of customizing the start page in order to add the New Website and Open Website controls. It turns out that using a loose XAML file as I did in that post is not the recommended practice; in fact, it’s recommended that you…(read more)
Framework .NET 3.5 Sp1 required for targeting frameworks 2.0, 3.0 or 3.5 (multi-targeting) using Visual Studio 2010
We have had some customers ask why they are unable to target earlier frameworks .NET 2.0, 3.0 or 3.5 using Visual Studio 2010. Targeting earlier frameworks (also known as Multi-targeting) is in-fact fully supported in VS 2010, but there is a pre-requisite that .NET Framework 3.5 Sp1 must be installed on the machine for VS 2010 to be able to target any of the earlier frameworks 2.0, 3.0 or 3.5. During VS 2010 installation, only the latest 4.0 version of the .NET framework will be installed on your machine as part of the Visual Studio installation. So if 3.5 Sp1 was not already present on your machine, you will see only the .NET Framework 4 in the target framework dropdown of the New Website / New Project dialogs (In these dialogs, framework dropdown…(read more)
Web Deployment: Excluding Files and Folders via the Web Application’s Project File
Web Deployment (see this posting for an overview) offers a set of pre-determined options to allow users to include the most common sets of files for deployment. These options are as follows and can be found under the “Items to deploy” section on the Package / Publish Web property page. Only files needed to run this application: This will include only the files required to run the application. Specifically, files to be included will be those found in the bin folder and those files whose Build Action property = Content (such as .aspx, .ascx, and .master). All files in this project: This will include all files within the project file. All files in this project folder: This will include all files in the source project folder, including those not…(read more)
Upgrade or Uninstall of Office 2007 might cause VS 2008 Web designer to hang
With Office 2010 releasing, some of you might be upgrading to Office 2010 from Office 2007. A plain uninstall of Office 2007 might also run into the issue described below. If this is something you have done (or plan to do) and are running a 64-bit OS, please keep on reading. On machines with a 64-bit OS, uninstall of Office 2007 will break the VS 2008 web designer. You will find that the VS designer won't be able to load, and any attempts to switch to Design View will hang the product. Note that 32-bit machines are not affected and neither are other VS releases. The root cause of this problem is that Office 2007 and the VS 2008 web designer both share a component, 32-bit MSXML5. When Office 2007 uninstalls or gets upgraded, MSXML5 is removed…(read more)
