<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Workaround for the &amp;quot;CMS&amp;quot; virtual directory problem with VS.NET 2005 (Update: 02.06.2006)</title><link>http://blogs.technet.com/stefan_gossner/archive/2006/01/31/418436.aspx</link><description>With VS.NET 2005 the VS.NET product team decided to change the behaviour of VS.NET for web applications. Up to VS.NET 2003 only virtual directories and files explicitly added to the projects were taken into consideration for the compilation. With VS.NET</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Workaround for the "CMS" virtual directory problem with VS.NET 2005</title><link>http://blogs.technet.com/stefan_gossner/archive/2006/01/31/418436.aspx#418507</link><pubDate>Wed, 01 Feb 2006 10:03:30 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:418507</guid><dc:creator>Alvis</dc:creator><description>Its look like when other products made swift trasaction towards VS 2005 the CMS 2002 is just one painfull product to do much in this regard. Why not Microsoft simply let SPS v3 do the cleanup for this un sucessfull product</description></item><item><title>re: Workaround for the "CMS" virtual directory problem with VS.NET 2005</title><link>http://blogs.technet.com/stefan_gossner/archive/2006/01/31/418436.aspx#418515</link><pubDate>Wed, 01 Feb 2006 11:01:41 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:418515</guid><dc:creator>Stefan_Gossner</dc:creator><description>The problem here is VS.NET - not MCMS.&lt;br/&gt;The behaviour of VS.NET changed in a way that it is no longer possible to exclude specific virtual directories easily.&lt;br/&gt;As you can see in Spencers article the VS.NET team recognized the limitations of the current implementation of VS.NET 2005 and are working on a solution for this.</description></item><item><title>re: Workaround for the "CMS" virtual directory problem with VS.NET 2005</title><link>http://blogs.technet.com/stefan_gossner/archive/2006/01/31/418436.aspx#419021</link><pubDate>Wed, 08 Feb 2006 15:42:37 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:419021</guid><dc:creator>Stefan_Gossner</dc:creator><description>That is not correct!&lt;br /&gt;Changing the CMS virtual directory into a web application will cause serious problems during authoring!&lt;br /&gt;&lt;br /&gt;See here for details:&lt;br /&gt;&lt;a rel="nofollow" target="_new" href="http://download.microsoft.com/download/4/2/5/4250f79a-c3a1-4003-9272-2404e92bb76a/MCMS+2002+-+"&gt;http://download.microsoft.com/download/4/2/5/4250f79a-c3a1-4003-9272-2404e92bb76a/MCMS+2002+-+&lt;/a&gt;(complete)+FAQ.htm#A68A7EBB-3DD3-42EC-96DC-0D6BBEB271D9&lt;br /&gt;&lt;br /&gt;Cheers,&lt;br /&gt;Stefan</description></item><item><title>re: Workaround for the "CMS" virtual directory problem with VS.NET 2005</title><link>http://blogs.technet.com/stefan_gossner/archive/2006/01/31/418436.aspx#419040</link><pubDate>Wed, 08 Feb 2006 23:00:21 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:419040</guid><dc:creator>Mark Zak</dc:creator><description>Just wanted to add a note that you must not cascade the hidden attribute down the directory tree as this causes 404 errors when MCMS tries to access the files contained within.</description></item><item><title>Microsoft Content Management Server 2002 Service Pack 2 Resources</title><link>http://blogs.technet.com/stefan_gossner/archive/2006/01/31/418436.aspx#419327</link><pubDate>Sun, 12 Feb 2006 22:00:54 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:419327</guid><dc:creator>Andrew Connell [MVP MCMS]</dc:creator><description /></item><item><title>Microsoft Content Management Server 2002 Service Pack 2 Resources</title><link>http://blogs.technet.com/stefan_gossner/archive/2006/01/31/418436.aspx#419344</link><pubDate>Sun, 12 Feb 2006 22:09:31 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:419344</guid><dc:creator>Andrew Connell [MVP MCMS]</dc:creator><description /></item><item><title>Tech Talk PT  &amp;raquo; Blog Archive   &amp;raquo; Microsoft Content Management SP2</title><link>http://blogs.technet.com/stefan_gossner/archive/2006/01/31/418436.aspx#422762</link><pubDate>Wed, 22 Mar 2006 13:22:13 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:422762</guid><dc:creator>Tech Talk PT  » Blog Archive   » Microsoft Content Management SP2</dc:creator><description>PingBack from &lt;a rel="nofollow" target="_new" href="https://techtalkpt.wordpress.com/2006/03/22/microsoft-content-management-sp2/"&gt;https://techtalkpt.wordpress.com/2006/03/22/microsoft-content-management-sp2/&lt;/a&gt;</description></item><item><title>re: Workaround for the "CMS" virtual directory problem with VS.NET 2005</title><link>http://blogs.technet.com/stefan_gossner/archive/2006/01/31/418436.aspx#424015</link><pubDate>Mon, 03 Apr 2006 17:22:09 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:424015</guid><dc:creator>Alastair</dc:creator><description>This 'workaround' appears to break the Publish Website facility. Great.</description></item><item><title>re: Workaround for the "CMS" virtual directory problem with VS.NET 2005</title><link>http://blogs.technet.com/stefan_gossner/archive/2006/01/31/418436.aspx#424031</link><pubDate>Mon, 03 Apr 2006 18:32:43 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:424031</guid><dc:creator>Stefan_Gossner</dc:creator><description>Hi Alastair, seems you did not only apply this to the directories but also to all content inside these directories.&lt;br&gt;You should NOT apply this to the subdirectories.</description></item><item><title>ASP.NET 2.0 and MCMS article series</title><link>http://blogs.technet.com/stefan_gossner/archive/2006/01/31/418436.aspx#434728</link><pubDate>Sat, 10 Jun 2006 10:51:23 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:434728</guid><dc:creator>Stefan Goßner</dc:creator><description>Now after MCMS 2002 SP2 has been released I would like to point you again to an article series I have...</description></item><item><title>re: Workaround for the "CMS" virtual directory problem with VS.NET 2005 (Update: 02.06.2006)</title><link>http://blogs.technet.com/stefan_gossner/archive/2006/01/31/418436.aspx#443847</link><pubDate>Sat, 29 Jul 2006 01:08:18 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:443847</guid><dc:creator>G</dc:creator><description>Works great for our current project w/o switching back and forth on IIS. Thanks!</description></item><item><title>re: Workaround for the "CMS" virtual directory problem with VS.NET 2005 (Update: 02.06.2006)</title><link>http://blogs.technet.com/stefan_gossner/archive/2006/01/31/418436.aspx#516304</link><pubDate>Tue, 14 Nov 2006 22:41:38 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:516304</guid><dc:creator>Philip</dc:creator><description>&lt;p&gt;This does NOT work for me. I have set IIS_CMS to hidden but still the project builds with errors from the CMS folder. Here is the error:&lt;/p&gt;
&lt;p&gt; Error 'Microsoft.ContentManagement.SharePoint.Dialogs.DialogBase' does not contain a definition for 'IDS_CSS_BACKGROUND1'	c:\Program Files\Microsoft Content Management Server\Server\IIS_CMS\WssIntegration\Controls\DialogTitle.ascx	5	&lt;/p&gt;</description></item><item><title>re: Workaround for the "CMS" virtual directory problem with VS.NET 2005 (Update: 02.06.2006)</title><link>http://blogs.technet.com/stefan_gossner/archive/2006/01/31/418436.aspx#516320</link><pubDate>Tue, 14 Nov 2006 23:17:14 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:516320</guid><dc:creator>PhilipS</dc:creator><description>&lt;p&gt;I have to also set sub directory WssIntegration to hidden.&lt;/p&gt;</description></item><item><title>re: Workaround for the "CMS" virtual directory problem with VS.NET 2005 (Update: 02.06.2006)</title><link>http://blogs.technet.com/stefan_gossner/archive/2006/01/31/418436.aspx#516908</link><pubDate>Wed, 15 Nov 2006 11:24:23 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:516908</guid><dc:creator>Stefan_Gossner</dc:creator><description>&lt;p&gt;Hi Philip, this is as expected.&lt;/p&gt;
&lt;p&gt;You need to set the CONTENT of IIS_CMS to hidden - not IIS_CMS itself.&lt;/p&gt;
</description></item><item><title>re: Workaround for the "CMS" virtual directory problem with VS.NET 2005 (Update: 02.06.2006)</title><link>http://blogs.technet.com/stefan_gossner/archive/2006/01/31/418436.aspx#517116</link><pubDate>Wed, 15 Nov 2006 17:17:38 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:517116</guid><dc:creator>Phil</dc:creator><description>&lt;p&gt;Thanks Stefan, &amp;nbsp; I misread your post.&lt;/p&gt;</description></item></channel></rss>