<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>ASP Experts &#187; Visual Web Developer</title>
	<atom:link href="http://www.aspexperts.com/tag/visual-web-developer/feed" rel="self" type="application/rss+xml" />
	<link>http://www.aspexperts.com</link>
	<description>.net programming, mssql, c#, vb.net....</description>
	<lastBuildDate>Tue, 07 Feb 2012 13:06:59 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
		<item>
		<title>Visual Studio 2010 SP1 Beta IIS Express Integration</title>
		<link>http://www.aspexperts.com/visual-studio-2010-sp1-beta-iis-express-integration</link>
		<comments>http://www.aspexperts.com/visual-studio-2010-sp1-beta-iis-express-integration#comments</comments>
		<pubDate>Sat, 11 Dec 2010 23:05:48 +0000</pubDate>
		<dc:creator>Editor</dc:creator>
				<category><![CDATA[Articles]]></category>
		<category><![CDATA[IIS]]></category>
		<category><![CDATA[News]]></category>
		<category><![CDATA[Reference]]></category>
		<category><![CDATA[.NET]]></category>
		<category><![CDATA[asp]]></category>
		<category><![CDATA[c#]]></category>
		<category><![CDATA[host]]></category>
		<category><![CDATA[hosting]]></category>
		<category><![CDATA[IIS Express]]></category>
		<category><![CDATA[microsoft]]></category>
		<category><![CDATA[programming]]></category>
		<category><![CDATA[Sayed Ibrahim Hashimi]]></category>
		<category><![CDATA[sql]]></category>
		<category><![CDATA[vb.net]]></category>
		<category><![CDATA[Visual Studio 2010]]></category>
		<category><![CDATA[Visual Web Developer]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[A few days ago Jason Zander blogged about the availability of Visual Studio SP1 Beta (all links below in resources section). I am happy to let you guys know that with SP1 Beta we have enabled integration of IIS Express into Visual Studio. After you hav...]]></description>
			<content:encoded><![CDATA[<p>A few days ago Jason Zander blogged about the availability of Visual Studio SP1 Beta (all links below in resources section). I am happy to let you guys know that with SP1 Beta we have enabled integration of IIS Express into Visual Studio. After you have installed SP1 Beta you have to download IIS Express separately for the option to “light up”. After you’ve downloaded and installed IIS Express you can now create Web projects and Websites which use IIS Express instead of Cassini (the default web server used in Visual Studio). For more information regarding the difference between IIS Express and IIS/Cassini please see Scott’s blog linked below. Visual Studio 2010 has two types of web projects; Web Application Project (WAP) and Website projects&#8230;(<a href="http://blogs.msdn.com/b/webdevtools/archive/2010/12/11/visual-studio-2010-sp1-beta-iis-express-integration.aspx">read more</a>)<img src="http://weblogs.asp.net/aggbug.aspx?PostID=7661065" width="1" height="1"></p>
]]></content:encoded>
			<wfw:commentRss>http://www.aspexperts.com/visual-studio-2010-sp1-beta-iis-express-integration/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Request for Real-World Web Applications</title>
		<link>http://www.aspexperts.com/request-for-real-world-web-applications</link>
		<comments>http://www.aspexperts.com/request-for-real-world-web-applications#comments</comments>
		<pubDate>Mon, 12 Jul 2010 20:50:24 +0000</pubDate>
		<dc:creator>Editor</dc:creator>
				<category><![CDATA[Articles]]></category>
		<category><![CDATA[News]]></category>
		<category><![CDATA[Reference]]></category>
		<category><![CDATA[.NET]]></category>
		<category><![CDATA[asp]]></category>
		<category><![CDATA[c#]]></category>
		<category><![CDATA[host]]></category>
		<category><![CDATA[hosting]]></category>
		<category><![CDATA[microsoft]]></category>
		<category><![CDATA[perf]]></category>
		<category><![CDATA[performance]]></category>
		<category><![CDATA[programming]]></category>
		<category><![CDATA[sql]]></category>
		<category><![CDATA[VanK]]></category>
		<category><![CDATA[vb.net]]></category>
		<category><![CDATA[Visual Studio 2010]]></category>
		<category><![CDATA[Visual Web Developer]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[In preparation for enhancing Visual Studio design-time experience testing, we’d like to collect a catalog of real world applications to use for performance, stress, and ad hoc testing by the Web Platform and Tools team. We’re looking for small, medium, and large applications covering a range of architectures, languages, frameworks, and features. Your contributions will help us to ensure stability and performance in the areas of greatest interest to you. These additional testing opportunities will also help us ensure that we will have more real world samples to verify every release of Visual Studio whether it is Beta, RC or RTM. If you are interested in helping us, please provide the following information: Please send an email to WptApps@live...(<a href="http://blogs.msdn.com/b/webdevtools/archive/2010/07/12/request-for-real-world-web-applications.aspx">read more</a>)<img src="http://weblogs.asp.net/aggbug.aspx?PostID=7566989" width="1" height="1">]]></description>
			<content:encoded><![CDATA[<p>In preparation for enhancing Visual Studio design-time experience testing, we’d like to collect a catalog of real world applications to use for performance, stress, and ad hoc testing by the Web Platform and Tools team. We’re looking for small, medium, and large applications covering a range of architectures, languages, frameworks, and features. Your contributions will help us to ensure stability and performance in the areas of greatest interest to you. These additional testing opportunities will also help us ensure that we will have more real world samples to verify every release of Visual Studio whether it is Beta, RC or RTM. If you are interested in helping us, please provide the following information: Please send an email to WptApps@live&#8230;(<a href="http://blogs.msdn.com/b/webdevtools/archive/2010/07/12/request-for-real-world-web-applications.aspx">read more</a>)<img src="http://weblogs.asp.net/aggbug.aspx?PostID=7566989" width="1" height="1"></p>
]]></content:encoded>
			<wfw:commentRss>http://www.aspexperts.com/request-for-real-world-web-applications/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Web Custom Control Behavior and Authoring</title>
		<link>http://www.aspexperts.com/web-custom-control-behavior-and-authoring</link>
		<comments>http://www.aspexperts.com/web-custom-control-behavior-and-authoring#comments</comments>
		<pubDate>Thu, 10 Jun 2010 17:13:00 +0000</pubDate>
		<dc:creator>Editor</dc:creator>
				<category><![CDATA[Articles]]></category>
		<category><![CDATA[News]]></category>
		<category><![CDATA[Reference]]></category>
		<category><![CDATA[.NET]]></category>
		<category><![CDATA[asp]]></category>
		<category><![CDATA[c#]]></category>
		<category><![CDATA[Custom Controls]]></category>
		<category><![CDATA[host]]></category>
		<category><![CDATA[hosting]]></category>
		<category><![CDATA[microsoft]]></category>
		<category><![CDATA[Multitargeting]]></category>
		<category><![CDATA[programming]]></category>
		<category><![CDATA[References]]></category>
		<category><![CDATA[sql]]></category>
		<category><![CDATA[Toolbox]]></category>
		<category><![CDATA[vb.net]]></category>
		<category><![CDATA[Visual Studio 2008]]></category>
		<category><![CDATA[Visual Studio 2010]]></category>
		<category><![CDATA[Visual Web Developer]]></category>
		<category><![CDATA[VS2008]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[Some Best Practices and Guidance for Web Control Vendors Targeting Visual Studio The goal of this post is to provide guidance for control vendors on best practices for writing custom controls with regard to their behavior in Visual Studio. It is designed to give vendors insight into how Visual Studio behaves when performing common actions related to custom controls, as well as suggestions to optimize the experience for their consumers from within VS&#8212;largely concentrating on VS versions 2008 and 2010. This post does not cover runtime or control programming concepts such as usage of any control or design-time specific APIs. For more information on these other concepts, please see the &#8220;links and other resources&#8221; section at the...(<a href="http://blogs.msdn.com/b/webdevtools/archive/2010/06/10/web-custom-control-behavior-and-authoring.aspx">read more</a>)<img src="http://weblogs.asp.net/aggbug.aspx?PostID=7530624" width="1" height="1">]]></description>
			<content:encoded><![CDATA[<p>Some Best Practices and Guidance for Web Control Vendors Targeting Visual Studio The goal of this post is to provide guidance for control vendors on best practices for writing custom controls with regard to their behavior in Visual Studio. It is designed to give vendors insight into how Visual Studio behaves when performing common actions related to custom controls, as well as suggestions to optimize the experience for their consumers from within VS&mdash;largely concentrating on VS versions 2008 and 2010. This post does not cover runtime or control programming concepts such as usage of any control or design-time specific APIs. For more information on these other concepts, please see the &ldquo;links and other resources&rdquo; section at the&#8230;(<a href="http://blogs.msdn.com/b/webdevtools/archive/2010/06/10/web-custom-control-behavior-and-authoring.aspx">read more</a>)<img src="http://weblogs.asp.net/aggbug.aspx?PostID=7530624" width="1" height="1"></p>
]]></content:encoded>
			<wfw:commentRss>http://www.aspexperts.com/web-custom-control-behavior-and-authoring/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>General Performance Improvements in VS2010 since Beta2</title>
		<link>http://www.aspexperts.com/general-performance-improvements-in-vs2010-since-beta2</link>
		<comments>http://www.aspexperts.com/general-performance-improvements-in-vs2010-since-beta2#comments</comments>
		<pubDate>Fri, 30 Apr 2010 22:14:00 +0000</pubDate>
		<dc:creator>Editor</dc:creator>
				<category><![CDATA[Articles]]></category>
		<category><![CDATA[News]]></category>
		<category><![CDATA[Reference]]></category>
		<category><![CDATA[VS2010]]></category>
		<category><![CDATA[.NET]]></category>
		<category><![CDATA[asp]]></category>
		<category><![CDATA[c#]]></category>
		<category><![CDATA[host]]></category>
		<category><![CDATA[hosting]]></category>
		<category><![CDATA[microsoft]]></category>
		<category><![CDATA[perf]]></category>
		<category><![CDATA[performance]]></category>
		<category><![CDATA[programming]]></category>
		<category><![CDATA[Ranjini]]></category>
		<category><![CDATA[sql]]></category>
		<category><![CDATA[vb.net]]></category>
		<category><![CDATA[Visual Studio 2010]]></category>
		<category><![CDATA[Visual Web Developer]]></category>
		<category><![CDATA[VS10]]></category>
		<category><![CDATA[VWD]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[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...(<a href="http://blogs.msdn.com/webdevtools/archive/2010/04/30/general-performance-improvements-in-vs2010-since-beta2.aspx">read more</a>)<img src="http://weblogs.asp.net/aggbug.aspx?PostID=7466623" width="1" height="1">]]></description>
			<content:encoded><![CDATA[<p>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&#8230;(<a href="http://blogs.msdn.com/webdevtools/archive/2010/04/30/general-performance-improvements-in-vs2010-since-beta2.aspx">read more</a>)<img src="http://weblogs.asp.net/aggbug.aspx?PostID=7466623" width="1" height="1"></p>
]]></content:encoded>
			<wfw:commentRss>http://www.aspexperts.com/general-performance-improvements-in-vs2010-since-beta2/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>VWD Available on Web Platform Installer (Now in Four Languages)</title>
		<link>http://www.aspexperts.com/vwd-available-on-web-platform-installer-now-in-four-languages</link>
		<comments>http://www.aspexperts.com/vwd-available-on-web-platform-installer-now-in-four-languages#comments</comments>
		<pubDate>Thu, 29 Apr 2010 17:05:24 +0000</pubDate>
		<dc:creator>Editor</dc:creator>
				<category><![CDATA[Articles]]></category>
		<category><![CDATA[News]]></category>
		<category><![CDATA[Reference]]></category>
		<category><![CDATA[.NET]]></category>
		<category><![CDATA[Announcements]]></category>
		<category><![CDATA[asp]]></category>
		<category><![CDATA[c#]]></category>
		<category><![CDATA[host]]></category>
		<category><![CDATA[hosting]]></category>
		<category><![CDATA[Install]]></category>
		<category><![CDATA[Installation]]></category>
		<category><![CDATA[microsoft]]></category>
		<category><![CDATA[programming]]></category>
		<category><![CDATA[sql]]></category>
		<category><![CDATA[VanK]]></category>
		<category><![CDATA[vb.net]]></category>
		<category><![CDATA[Visual Web Developer]]></category>
		<category><![CDATA[VWD]]></category>
		<category><![CDATA[Web Platform Installer]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[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...(<a href="http://blogs.msdn.com/webdevtools/archive/2010/04/29/vwd-available-on-web-platform-installer-now-in-four-languages.aspx">read more</a>)<img src="http://weblogs.asp.net/aggbug.aspx?PostID=7465242" width="1" height="1">]]></description>
			<content:encoded><![CDATA[<p>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&#8230;(<a href="http://blogs.msdn.com/webdevtools/archive/2010/04/29/vwd-available-on-web-platform-installer-now-in-four-languages.aspx">read more</a>)<img src="http://weblogs.asp.net/aggbug.aspx?PostID=7465242" width="1" height="1"></p>
]]></content:encoded>
			<wfw:commentRss>http://www.aspexperts.com/vwd-available-on-web-platform-installer-now-in-four-languages/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Design View Performance Improvements</title>
		<link>http://www.aspexperts.com/design-view-performance-improvements</link>
		<comments>http://www.aspexperts.com/design-view-performance-improvements#comments</comments>
		<pubDate>Wed, 28 Apr 2010 20:30:00 +0000</pubDate>
		<dc:creator>Editor</dc:creator>
				<category><![CDATA[Articles]]></category>
		<category><![CDATA[News]]></category>
		<category><![CDATA[Reference]]></category>
		<category><![CDATA[.NET]]></category>
		<category><![CDATA[asp]]></category>
		<category><![CDATA[c#]]></category>
		<category><![CDATA[Designer]]></category>
		<category><![CDATA[host]]></category>
		<category><![CDATA[hosting]]></category>
		<category><![CDATA[microsoft]]></category>
		<category><![CDATA[programming]]></category>
		<category><![CDATA[sql]]></category>
		<category><![CDATA[vb.net]]></category>
		<category><![CDATA[Visual Studio 2010]]></category>
		<category><![CDATA[Visual Web Developer]]></category>
		<category><![CDATA[VWD]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[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...(<a href="http://blogs.msdn.com/webdevtools/archive/2010/04/28/design-view-performance-improvements.aspx">read more</a>)<img src="http://weblogs.asp.net/aggbug.aspx?PostID=7464162" width="1" height="1">]]></description>
			<content:encoded><![CDATA[<p>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&#8230;(<a href="http://blogs.msdn.com/webdevtools/archive/2010/04/28/design-view-performance-improvements.aspx">read more</a>)<img src="http://weblogs.asp.net/aggbug.aspx?PostID=7464162" width="1" height="1"></p>
]]></content:encoded>
			<wfw:commentRss>http://www.aspexperts.com/design-view-performance-improvements/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Web Deployment: Excluding Files and Folders via the Web Application’s Project File</title>
		<link>http://www.aspexperts.com/web-deployment-excluding-files-and-folders-via-the-web-application%e2%80%99s-project-file</link>
		<comments>http://www.aspexperts.com/web-deployment-excluding-files-and-folders-via-the-web-application%e2%80%99s-project-file#comments</comments>
		<pubDate>Thu, 22 Apr 2010 18:00:00 +0000</pubDate>
		<dc:creator>Editor</dc:creator>
				<category><![CDATA[Articles]]></category>
		<category><![CDATA[News]]></category>
		<category><![CDATA[Reference]]></category>
		<category><![CDATA[.NET]]></category>
		<category><![CDATA[asp]]></category>
		<category><![CDATA[c#]]></category>
		<category><![CDATA[host]]></category>
		<category><![CDATA[hosting]]></category>
		<category><![CDATA[microsoft]]></category>
		<category><![CDATA[programming]]></category>
		<category><![CDATA[publish]]></category>
		<category><![CDATA[sql]]></category>
		<category><![CDATA[vb.net]]></category>
		<category><![CDATA[Visual Studio 2010]]></category>
		<category><![CDATA[Visual Web Developer]]></category>
		<category><![CDATA[VS10]]></category>
		<category><![CDATA[VWD]]></category>
		<category><![CDATA[WAP]]></category>
		<category><![CDATA[Web Deployment]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[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...(<a href="http://blogs.msdn.com/webdevtools/archive/2010/04/22/web-deployment-excluding-files-and-folders-via-the-web-application-s-project-file.aspx">read more</a>)<img src="http://weblogs.asp.net/aggbug.aspx?PostID=7454748" width="1" height="1">]]></description>
			<content:encoded><![CDATA[<p>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&#8230;(<a href="http://blogs.msdn.com/webdevtools/archive/2010/04/22/web-deployment-excluding-files-and-folders-via-the-web-application-s-project-file.aspx">read more</a>)<img src="http://weblogs.asp.net/aggbug.aspx?PostID=7454748" width="1" height="1"></p>
]]></content:encoded>
			<wfw:commentRss>http://www.aspexperts.com/web-deployment-excluding-files-and-folders-via-the-web-application%e2%80%99s-project-file/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>One-Click Publish &#8211; What&#8217;s New Since Beta 2</title>
		<link>http://www.aspexperts.com/one-click-publish-whats-new-since-beta-2</link>
		<comments>http://www.aspexperts.com/one-click-publish-whats-new-since-beta-2#comments</comments>
		<pubDate>Tue, 20 Apr 2010 23:02:00 +0000</pubDate>
		<dc:creator>Editor</dc:creator>
				<category><![CDATA[Articles]]></category>
		<category><![CDATA[News]]></category>
		<category><![CDATA[Reference]]></category>
		<category><![CDATA[.NET]]></category>
		<category><![CDATA[asp]]></category>
		<category><![CDATA[c#]]></category>
		<category><![CDATA[Development]]></category>
		<category><![CDATA[host]]></category>
		<category><![CDATA[hosting]]></category>
		<category><![CDATA[microsoft]]></category>
		<category><![CDATA[MSDeploy]]></category>
		<category><![CDATA[programming]]></category>
		<category><![CDATA[publish]]></category>
		<category><![CDATA[sql]]></category>
		<category><![CDATA[vb.net]]></category>
		<category><![CDATA[Visual Studio 2010]]></category>
		<category><![CDATA[Visual Web Developer]]></category>
		<category><![CDATA[VS10]]></category>
		<category><![CDATA[Web Deployment]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[Publishing using MSDeploy In-Process Deployment or Remote Agent Through the Beta 2 release, VS 2010 had only supported publishing to servers using MSDeploy&#39;s IIS deployment handler technology integrated with the “Web Management Service”, a.k.a. WMSVC. As long as you had an account on a hosting server using WMSVC, you could use MSDeploy to update your web content. This is the msdeploy technology most people will use when publishing to a hosted site and, therefore, was released first. (In case you are interested in how the server should be configured, check out the link: http://technet.microsoft.com/en-us/library/dd722796(WS.10).aspx ) In the RC release of VS 2010, We added support for two more msdeploy technologies that target specific deployment...(<a href="http://blogs.msdn.com/webdevtools/archive/2010/04/20/one-click-publish-what-s-new-since-beta-2.aspx">read more</a>)<img src="http://weblogs.asp.net/aggbug.aspx?PostID=7451726" width="1" height="1">]]></description>
			<content:encoded><![CDATA[<p>Publishing using MSDeploy In-Process Deployment or Remote Agent Through the Beta 2 release, VS 2010 had only supported publishing to servers using MSDeploy&#39;s IIS deployment handler technology integrated with the “Web Management Service”, a.k.a. WMSVC. As long as you had an account on a hosting server using WMSVC, you could use MSDeploy to update your web content. This is the msdeploy technology most people will use when publishing to a hosted site and, therefore, was released first. (In case you are interested in how the server should be configured, check out the link: http://technet.microsoft.com/en-us/library/dd722796(WS.10).aspx ) In the RC release of VS 2010, We added support for two more msdeploy technologies that target specific deployment&#8230;(<a href="http://blogs.msdn.com/webdevtools/archive/2010/04/20/one-click-publish-what-s-new-since-beta-2.aspx">read more</a>)<img src="http://weblogs.asp.net/aggbug.aspx?PostID=7451726" width="1" height="1"></p>
]]></content:encoded>
			<wfw:commentRss>http://www.aspexperts.com/one-click-publish-whats-new-since-beta-2/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Upgrade or Uninstall of Office 2007 might cause VS 2008 Web designer to hang</title>
		<link>http://www.aspexperts.com/upgrade-or-uninstall-of-office-2007-might-cause-vs-2008-web-designer-to-hang</link>
		<comments>http://www.aspexperts.com/upgrade-or-uninstall-of-office-2007-might-cause-vs-2008-web-designer-to-hang#comments</comments>
		<pubDate>Mon, 19 Apr 2010 17:16:00 +0000</pubDate>
		<dc:creator>Editor</dc:creator>
				<category><![CDATA[Articles]]></category>
		<category><![CDATA[News]]></category>
		<category><![CDATA[Reference]]></category>
		<category><![CDATA[Visual Studio]]></category>
		<category><![CDATA[.NET]]></category>
		<category><![CDATA[asp]]></category>
		<category><![CDATA[c#]]></category>
		<category><![CDATA[Designer]]></category>
		<category><![CDATA[host]]></category>
		<category><![CDATA[hosting]]></category>
		<category><![CDATA[microsoft]]></category>
		<category><![CDATA[Office 2010]]></category>
		<category><![CDATA[programming]]></category>
		<category><![CDATA[sql]]></category>
		<category><![CDATA[vb.net]]></category>
		<category><![CDATA[Visual Studio 2008]]></category>
		<category><![CDATA[visual Studio 2008 sp1]]></category>
		<category><![CDATA[Visual Web Developer]]></category>
		<category><![CDATA[VS2008]]></category>
		<category><![CDATA[VWD]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[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&#39;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...(<a href="http://blogs.msdn.com/webdevtools/archive/2010/04/19/upgrade-or-uninstall-of-office-2007-might-cause-vs-2008-web-designer-to-hang.aspx">read more</a>)<img src="http://weblogs.asp.net/aggbug.aspx?PostID=7449895" width="1" height="1">]]></description>
			<content:encoded><![CDATA[<p>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&#39;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&#8230;(<a href="http://blogs.msdn.com/webdevtools/archive/2010/04/19/upgrade-or-uninstall-of-office-2007-might-cause-vs-2008-web-designer-to-hang.aspx">read more</a>)<img src="http://weblogs.asp.net/aggbug.aspx?PostID=7449895" width="1" height="1"></p>
]]></content:encoded>
			<wfw:commentRss>http://www.aspexperts.com/upgrade-or-uninstall-of-office-2007-might-cause-vs-2008-web-designer-to-hang/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Rendering Issue in Visual Studio 2010 when Accessing the Session State in the OnInit() Method</title>
		<link>http://www.aspexperts.com/rendering-issue-in-visual-studio-2010-when-accessing-the-session-state-in-the-oninit-method</link>
		<comments>http://www.aspexperts.com/rendering-issue-in-visual-studio-2010-when-accessing-the-session-state-in-the-oninit-method#comments</comments>
		<pubDate>Thu, 15 Apr 2010 22:56:00 +0000</pubDate>
		<dc:creator>Editor</dc:creator>
				<category><![CDATA[Articles]]></category>
		<category><![CDATA[News]]></category>
		<category><![CDATA[Reference]]></category>
		<category><![CDATA[.NET]]></category>
		<category><![CDATA[asp]]></category>
		<category><![CDATA[c#]]></category>
		<category><![CDATA[Designer]]></category>
		<category><![CDATA[host]]></category>
		<category><![CDATA[hosting]]></category>
		<category><![CDATA[microsoft]]></category>
		<category><![CDATA[programming]]></category>
		<category><![CDATA[sql]]></category>
		<category><![CDATA[vb.net]]></category>
		<category><![CDATA[Visual Studio 2010]]></category>
		<category><![CDATA[Visual Web Developer]]></category>
		<category><![CDATA[VS10]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[In VS 2010, if you are accessing the Session state in the OnInit(…) method of your page, similar to the following code snippet: then you will encounter an “Error Creating Control” for ASP.NET controls when viewing the Design view of the page. For example, if you have an ASP.NET button control on the page, the designer will display the error: “ Error Creating Control – Button1 Session state can only be used when enableSessionState is set to true, either in a configuration file or in the Page directive. Please also make sure that System. Web.SessionStateModule or a custom session state module is included in the &#60;configuration&#62;\&#60;system.web&#62;\&#60;httpModules&#62; section in the application configuration.”. Screen shot of the error: However...(<a href="http://blogs.msdn.com/webdevtools/archive/2010/04/15/rendering-issue-in-visual-studio-2010-when-accessing-the-session-state-in-the-oninit-method.aspx">read more</a>)<img src="http://weblogs.asp.net/aggbug.aspx?PostID=7446033" width="1" height="1">]]></description>
			<content:encoded><![CDATA[<p>In VS 2010, if you are accessing the Session state in the OnInit(…) method of your page, similar to the following code snippet: then you will encounter an “Error Creating Control” for ASP.NET controls when viewing the Design view of the page. For example, if you have an ASP.NET button control on the page, the designer will display the error: “ Error Creating Control – Button1 Session state can only be used when enableSessionState is set to true, either in a configuration file or in the Page directive. Please also make sure that System. Web.SessionStateModule or a custom session state module is included in the &lt;configuration&gt;\&lt;system.web&gt;\&lt;httpModules&gt; section in the application configuration.”. Screen shot of the error: However&#8230;(<a href="http://blogs.msdn.com/webdevtools/archive/2010/04/15/rendering-issue-in-visual-studio-2010-when-accessing-the-session-state-in-the-oninit-method.aspx">read more</a>)<img src="http://weblogs.asp.net/aggbug.aspx?PostID=7446033" width="1" height="1"></p>
]]></content:encoded>
			<wfw:commentRss>http://www.aspexperts.com/rendering-issue-in-visual-studio-2010-when-accessing-the-session-state-in-the-oninit-method/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

