<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://forums.asp.net/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>Visual Studio 2005</title><link>http://forums.asp.net/138.aspx</link><description>General discussions of Visual Studio 2005.  &lt;a href="http://aspadvice.com/SignUp/list.aspx?l=162&amp;c=30" target="_blank"&gt;Email List&lt;/a&gt;</description><dc:language>en</dc:language><generator>CommunityServer 2007 SP1 (Build: 20510.895)</generator><item><title>Re: running classic asp pages in VS 2005 IDE</title><link>http://forums.asp.net/thread/2381659.aspx</link><pubDate>Tue, 27 May 2008 02:26:04 GMT</pubDate><guid isPermaLink="false">4c671506-2930-414c-a40b-8bf57ded5924:2381659</guid><dc:creator>cjsteury</dc:creator><slash:comments>0</slash:comments><comments>http://forums.asp.net/thread/2381659.aspx</comments><wfw:commentRss>http://forums.asp.net/commentrss.aspx?SectionID=138&amp;PostID=2381659</wfw:commentRss><description>&lt;p&gt;thanks for this !&amp;nbsp;&lt;/p&gt;</description></item><item><title>Re: running classic asp pages in VS 2005 IDE</title><link>http://forums.asp.net/thread/1990813.aspx</link><pubDate>Mon, 05 Nov 2007 20:07:26 GMT</pubDate><guid isPermaLink="false">4c671506-2930-414c-a40b-8bf57ded5924:1990813</guid><dc:creator>Mikhail Arkhipov (MSFT)</dc:creator><slash:comments>0</slash:comments><comments>http://forums.asp.net/thread/1990813.aspx</comments><wfw:commentRss>http://forums.asp.net/commentrss.aspx?SectionID=138&amp;PostID=1990813</wfw:commentRss><description>&lt;p&gt;I guess it depends on the amount of server side code. Technically compiled VB.NET or C# always wins over interpreted VBScript. However, if bottleneck is elsewhere, changing server language may not make much difference.&lt;/p&gt;</description></item><item><title>Re: running classic asp pages in VS 2005 IDE</title><link>http://forums.asp.net/thread/1990760.aspx</link><pubDate>Mon, 05 Nov 2007 19:39:10 GMT</pubDate><guid isPermaLink="false">4c671506-2930-414c-a40b-8bf57ded5924:1990760</guid><dc:creator>TheITGuyFromNY</dc:creator><slash:comments>0</slash:comments><comments>http://forums.asp.net/thread/1990760.aspx</comments><wfw:commentRss>http://forums.asp.net/commentrss.aspx?SectionID=138&amp;PostID=1990760</wfw:commentRss><description>&lt;p&gt;As a classic ASP developer for several years (but not a million), this is a funny post and proves one thing for sure...DOT NET Web &amp;quot;developers&amp;quot; are indeed different than web &amp;quot;programmers&amp;quot; for sure&amp;nbsp;or, said differently, if you can&amp;#39;t open up notepad and write both server-side and client-side code, then you&amp;#39;re missing all the really great underlying architecture that makes this world tick.&lt;/p&gt;
&lt;p&gt;This also provdes the point of why I continue to write in Classic ASP versus this new stuff...that is, there is SO MUCH OVERHEAD built into&amp;nbsp;asp.net that hinders performance...so much that web developers don&amp;#39;t even know how to debug their apps without using the proprietary .NET Visual Studio environment...this is amazing to me.&lt;/p&gt;
&lt;p&gt;BTW, I&amp;#39;ve yet to find a proven situation where ASP.NET is faster than Classic ASP...either to code or in runtime. I&amp;#39;m not saying there&amp;#39;s no such thing, just that in the gobs and gobs of work I&amp;#39;ve done through they last 10 years, I&amp;#39;ve yet to come across a situation where I think it&amp;#39;s worth it for my customer to make the update to their existing application.&lt;/p&gt;</description></item><item><title>Re: running classic asp pages in VS 2005 IDE</title><link>http://forums.asp.net/thread/1840864.aspx</link><pubDate>Fri, 03 Aug 2007 22:08:08 GMT</pubDate><guid isPermaLink="false">4c671506-2930-414c-a40b-8bf57ded5924:1840864</guid><dc:creator>Mikhail Arkhipov (MSFT)</dc:creator><slash:comments>0</slash:comments><comments>http://forums.asp.net/thread/1840864.aspx</comments><wfw:commentRss>http://forums.asp.net/commentrss.aspx?SectionID=138&amp;PostID=1840864</wfw:commentRss><description>&lt;p&gt;Is there are several dllhost.exe running? Perhaps you are not picking the right one...&lt;/p&gt;</description></item><item><title>Re: running classic asp pages in VS 2005 IDE</title><link>http://forums.asp.net/thread/1840861.aspx</link><pubDate>Fri, 03 Aug 2007 22:06:49 GMT</pubDate><guid isPermaLink="false">4c671506-2930-414c-a40b-8bf57ded5924:1840861</guid><dc:creator>Mikhail Arkhipov (MSFT)</dc:creator><slash:comments>0</slash:comments><comments>http://forums.asp.net/thread/1840861.aspx</comments><wfw:commentRss>http://forums.asp.net/commentrss.aspx?SectionID=138&amp;PostID=1840861</wfw:commentRss><description>&lt;p&gt;VS Development server does not support classic ASP, it only supports ASP.NET. You have to use IIS for the classic ASP work.&lt;/p&gt;</description></item><item><title>Re: running classic asp pages in VS 2005 IDE</title><link>http://forums.asp.net/thread/1840300.aspx</link><pubDate>Fri, 03 Aug 2007 16:28:23 GMT</pubDate><guid isPermaLink="false">4c671506-2930-414c-a40b-8bf57ded5924:1840300</guid><dc:creator>webber123456</dc:creator><slash:comments>0</slash:comments><comments>http://forums.asp.net/thread/1840300.aspx</comments><wfw:commentRss>http://forums.asp.net/commentrss.aspx?SectionID=138&amp;PostID=1840300</wfw:commentRss><description>&lt;p&gt;they do need a classic asp forum here...&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;try this ASP studio product here : http://en.ewebxp.com/&amp;nbsp;&lt;/p&gt;</description></item><item><title>Re: running classic asp pages in VS 2005 IDE</title><link>http://forums.asp.net/thread/1410124.aspx</link><pubDate>Tue, 26 Sep 2006 08:58:50 GMT</pubDate><guid isPermaLink="false">4c671506-2930-414c-a40b-8bf57ded5924:1410124</guid><dc:creator>Gawan</dc:creator><slash:comments>0</slash:comments><comments>http://forums.asp.net/thread/1410124.aspx</comments><wfw:commentRss>http://forums.asp.net/commentrss.aspx?SectionID=138&amp;PostID=1410124</wfw:commentRss><description>&lt;p&gt;Hi Mikhail !&lt;/p&gt;&lt;p&gt;It&amp;#39;s very important for me to debug some classic ASP-Pages.&lt;/p&gt;&lt;p&gt;I tried everything mentioned in these two blogs:&lt;br /&gt;&lt;/p&gt;&lt;p&gt;http://blogs.msdn.com/mikhailarkhipov/archive/2005/06/24/432308.aspx&lt;/p&gt;&lt;p&gt;http://blogs.msdn.com/mikhailarkhipov/archive/2006/02/07/527293.aspx&amp;nbsp;&lt;/p&gt;&lt;p&gt;I&amp;#39;m running Win Pro XP SP2 and Visual Studio 2005 and installed IIS 5.1 afterwards. Now I put my ASP-Files in the default-folder for web publishing (c:\inetpub\wwwrroot). In the next step i opened my ASP-page using VS2005 and in my web browser. Then I set a few breakpoints (to make sure at least one of them is hit) and attached the page to the process:&lt;/p&gt;&lt;p&gt;Debug / Attach to Process&amp;nbsp; --&amp;gt;&amp;nbsp;&amp;nbsp; Attach to:&amp;nbsp; Script code&amp;nbsp; --&amp;gt;&amp;nbsp; dllhost.exe&amp;nbsp; (....IWAM....,got the right one with listdlls).&lt;/p&gt;&lt;p&gt;Then I tried to reload the page in the browser - hoping to hit a breakpoint - but NOTHING happened. I can reload the page as often as I want and set my breakpoints whereever I want - they are not hit. &lt;/p&gt;&lt;p&gt;Do you have any idea what I did wrong ?&lt;/p&gt;&lt;p&gt;TIA&lt;/p&gt;&lt;p&gt;Gawan&lt;br /&gt;&lt;br /&gt;&amp;nbsp;&lt;/p&gt;</description></item><item><title>Re: running classic asp pages in VS 2005 IDE</title><link>http://forums.asp.net/thread/1409598.aspx</link><pubDate>Mon, 25 Sep 2006 20:00:10 GMT</pubDate><guid isPermaLink="false">4c671506-2930-414c-a40b-8bf57ded5924:1409598</guid><dc:creator>bsodano</dc:creator><slash:comments>0</slash:comments><comments>http://forums.asp.net/thread/1409598.aspx</comments><wfw:commentRss>http://forums.asp.net/commentrss.aspx?SectionID=138&amp;PostID=1409598</wfw:commentRss><description>&lt;p&gt;I figured that is that case, just wanted to know how creative some folks have gotten since Cassini&amp;#39;s release.&amp;nbsp; I&amp;#39;m now on to attempt Remote Classic ASP debugging via VS 2005.&amp;nbsp; The first step is to get Info Security to approve the install of the VS Remote Debugger on our IIS server.&amp;nbsp; We&amp;#39;ll see how that goes in a few weeks...&lt;/p&gt;&lt;p&gt;Brian&lt;/p&gt;</description></item><item><title>Re: running classic asp pages in VS 2005 IDE</title><link>http://forums.asp.net/thread/1409596.aspx</link><pubDate>Mon, 25 Sep 2006 19:58:19 GMT</pubDate><guid isPermaLink="false">4c671506-2930-414c-a40b-8bf57ded5924:1409596</guid><dc:creator>bsodano</dc:creator><slash:comments>0</slash:comments><comments>http://forums.asp.net/thread/1409596.aspx</comments><wfw:commentRss>http://forums.asp.net/commentrss.aspx?SectionID=138&amp;PostID=1409596</wfw:commentRss><description>&lt;p&gt;Yes indeed, asp.tlb is installed at - C:\Program Files\Microsoft Visual Studio 8\Common7\Packages\schemas\xml&lt;/p&gt;&lt;p&gt;It installed when VS installed itself, however the Intellisense is not active.&amp;nbsp; On my home machine, which had IIS installed before I installed VS 2005 (at work I use 2003 and 2005 both), Intellisense worked like a charm.&amp;nbsp; However, without IIS installed it appears asp.tlb isn&amp;#39;t the only thing needed for ASP Intellisense to function correctly.&lt;/p&gt;&lt;p&gt;Brian&lt;/p&gt;</description></item><item><title>Re: running classic asp pages in VS 2005 IDE</title><link>http://forums.asp.net/thread/1409369.aspx</link><pubDate>Mon, 25 Sep 2006 16:31:10 GMT</pubDate><guid isPermaLink="false">4c671506-2930-414c-a40b-8bf57ded5924:1409369</guid><dc:creator>Mikhail Arkhipov (MSFT)</dc:creator><slash:comments>0</slash:comments><comments>http://forums.asp.net/thread/1409369.aspx</comments><wfw:commentRss>http://forums.asp.net/commentrss.aspx?SectionID=138&amp;PostID=1409369</wfw:commentRss><description>Classic ASP intellisense is not coming from IIS, but it does need asp.tlb copy of which, I believe, ships with VS. If asp.tlb is missing from VS installation,&amp;nbsp;try&amp;nbsp;copying it from machine that does have IIS installed.&amp;nbsp;It typically sits in Common7\Packages\schemas\xml\ASP.tlb. Maybe it is not installed since Web editing components are not installed as they require IIS in VS 2003.</description></item><item><title>Re: running classic asp pages in VS 2005 IDE</title><link>http://forums.asp.net/thread/1409364.aspx</link><pubDate>Mon, 25 Sep 2006 16:27:19 GMT</pubDate><guid isPermaLink="false">4c671506-2930-414c-a40b-8bf57ded5924:1409364</guid><dc:creator>Mikhail Arkhipov (MSFT)</dc:creator><slash:comments>0</slash:comments><comments>http://forums.asp.net/thread/1409364.aspx</comments><wfw:commentRss>http://forums.asp.net/commentrss.aspx?SectionID=138&amp;PostID=1409364</wfw:commentRss><description>&lt;p&gt;It is techincally not possible, at least not in a reasonable time. asp.dll is a native extension to IIS, Cassini is unable to load or process IIS extension modules, it just does not have right architecture. Cassini is a simple ASP.NET host. In IIS there is a different host written as IIS extension.&lt;/p&gt;</description></item><item><title>Re: running classic asp pages in VS 2005 IDE</title><link>http://forums.asp.net/thread/1409347.aspx</link><pubDate>Mon, 25 Sep 2006 16:11:21 GMT</pubDate><guid isPermaLink="false">4c671506-2930-414c-a40b-8bf57ded5924:1409347</guid><dc:creator>bsodano</dc:creator><slash:comments>0</slash:comments><comments>http://forums.asp.net/thread/1409347.aspx</comments><wfw:commentRss>http://forums.asp.net/commentrss.aspx?SectionID=138&amp;PostID=1409347</wfw:commentRss><description>&lt;p&gt;Mikhail,&lt;/p&gt;&lt;p&gt;On a slightly tangent topic, do you know of anyone who has tried to hack Cassini to be able to dish out classic ASP pages and/or debug?&amp;nbsp; I ask this because as a policy, we are not allowed to install IIS locally at the place I am contracting at.&amp;nbsp; Additionally, we are only allowed to use their approved hardware/computers to develop on.&amp;nbsp; I am working on mixed applications running ASP 3.0, as well as .NET 1.1 and 2.0.&amp;nbsp; As a result I have VS 2003 and 2005 installed to handle both, however working with the classic ASP is painful.&amp;nbsp; Everything is hand-edited, may as well be in notepad as there is no Intellisense available (my guess is because IIS is not installed) or debugging.&amp;nbsp; Any thoughts?&lt;/p&gt;&lt;p&gt;&lt;br /&gt;Brian&lt;/p&gt;</description></item><item><title>Re: running classic asp pages in VS 2005 IDE</title><link>http://forums.asp.net/thread/1334126.aspx</link><pubDate>Thu, 06 Jul 2006 16:12:53 GMT</pubDate><guid isPermaLink="false">4c671506-2930-414c-a40b-8bf57ded5924:1334126</guid><dc:creator>Mikhail Arkhipov (MSFT)</dc:creator><slash:comments>0</slash:comments><comments>http://forums.asp.net/thread/1334126.aspx</comments><wfw:commentRss>http://forums.asp.net/commentrss.aspx?SectionID=138&amp;PostID=1334126</wfw:commentRss><description>&lt;p&gt;Since you installed IIS after you installed VS 2005 and .NET 2.0, IIS now runs ASP.NET 1.1 as it is default install on XP. Open command prompt, go to \windows\microsoft.net\framework\v2.0.xxxx and run &lt;/p&gt;
&lt;p&gt;aspnet_regiis -i&lt;/p&gt;</description></item><item><title>Re: running classic asp pages in VS 2005 IDE</title><link>http://forums.asp.net/thread/1333864.aspx</link><pubDate>Thu, 06 Jul 2006 13:20:02 GMT</pubDate><guid isPermaLink="false">4c671506-2930-414c-a40b-8bf57ded5924:1333864</guid><dc:creator>fkopan</dc:creator><slash:comments>0</slash:comments><comments>http://forums.asp.net/thread/1333864.aspx</comments><wfw:commentRss>http://forums.asp.net/commentrss.aspx?SectionID=138&amp;PostID=1333864</wfw:commentRss><description>&lt;p&gt;I did figure out the XP install part.&lt;/p&gt;
&lt;p&gt;If I run with debugging it gives me a "server unavailable" message in an XML format.&amp;nbsp; If I run without debugging, I get.....&lt;/p&gt;
&lt;h1&gt;&lt;span&gt;Server Application Unavailable &lt;/span&gt;&lt;/h1&gt;
&lt;p&gt;&lt;span&gt;The web application you are attempting to access on this web server is currently unavailable.&amp;nbsp; Please hit the "Refresh" button in your web browser to retry your request. &lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;Administrator Note: &lt;/b&gt;An error message detailing the cause of this specific request failure can be found in the application event log of the web server. Please review this log entry to discover what caused this error to occur. &lt;/p&gt;
&lt;p&gt;I looked in the application event logs, &lt;/p&gt;
&lt;p&gt;Warning....&lt;/p&gt;&lt;font size=1&gt;
&lt;p&gt;Failed to initialize the AppDomain:/LM/W3SVC/1/Root/TPN v1 with Classic&lt;/p&gt;
&lt;p&gt;Exception: System.IO.FileLoadException&lt;/p&gt;
&lt;p&gt;Message: Could not load file or assembly 'System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Access is denied.&lt;/p&gt;
&lt;p&gt;StackTrace: at System.Reflection.Assembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark&amp;amp; stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection)&lt;/p&gt;
&lt;p&gt;at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark&amp;amp; stackMark, Boolean forIntrospection)&lt;/p&gt;
&lt;p&gt;at System.Reflection.Assembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark&amp;amp; stackMark, Boolean forIntrospection)&lt;/p&gt;
&lt;p&gt;at System.Activator.CreateInstance(String assemblyName, String typeName, Boolean ignoreCase, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, Evidence securityInfo, StackCrawlMark&amp;amp; stackMark)&lt;/p&gt;
&lt;p&gt;at System.Activator.CreateInstance(String assemblyName, String typeName)&lt;/p&gt;
&lt;p&gt;at System.AppDomain.CreateInstance(String assemblyName, String typeName)&lt;/p&gt;
&lt;p&gt;at System.AppDomain.CreateInstance(String assemblyName, String typeName)&lt;/p&gt;
&lt;p&gt;at System.Web.Hosting.ApplicationManager.CreateAppDomainWithHostingEnvironment(String appId, IApplicationHost appHost, HostingEnvironmentParameters hostingParameters)&lt;/p&gt;
&lt;p&gt;at System.Web.Hosting.ApplicationManager.CreateAppDomainWithHostingEnvironmentAndReportErrors(String appId, IApplicationHost appHost, HostingEnvironmentParameters hostingParameters)&lt;/p&gt;
&lt;p&gt;Error....&lt;/p&gt;&lt;font size=1&gt;
&lt;p&gt;Failed to execute request because the App-Domain could not be created. Error: 0x80070005 Access is denied. &lt;/p&gt;&lt;/font&gt;&lt;/font&gt;</description></item><item><title>Re: running classic asp pages in VS 2005 IDE</title><link>http://forums.asp.net/thread/1333336.aspx</link><pubDate>Wed, 05 Jul 2006 21:27:14 GMT</pubDate><guid isPermaLink="false">4c671506-2930-414c-a40b-8bf57ded5924:1333336</guid><dc:creator>Mikhail Arkhipov (MSFT)</dc:creator><slash:comments>0</slash:comments><comments>http://forums.asp.net/thread/1333336.aspx</comments><wfw:commentRss>http://forums.asp.net/commentrss.aspx?SectionID=138&amp;PostID=1333336</wfw:commentRss><description>XP Professional comes with IIS 5.1. You can install it in Control Panel | Add Remove Programs | Windows Components.</description></item></channel></rss>