<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:blog="http://dnn-connect.org/blog/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:media="http://search.yahoo.com/mrss/">
  <channel>
    <title>ASP.NET</title>
    <link>https://www.revindex.com/Resources/Blogs/blog/8/locale/en-US/ASP-NET</link>
    <description>ASP.NET Web Programming</description>
    <managingEditor>slim@revindex.com</managingEditor>
    <pubDate>Sun, 08 Mar 2026 10:46:41 GMT</pubDate>
    <lastBuildDate>Sun, 08 Mar 2026 10:46:41 GMT</lastBuildDate>
    <generator>DotNetNuke Blog RSS Generator Version 6.4.2.0</generator>
    <ttl>30</ttl>
    <atom:link href="https://www.revindex.com/DesktopModules/Blog/API/RSS/Get?tabid=65&amp;moduleid=394&amp;blog=8" rel="self" type="application/rss+xml" />
    <item>
      <title>How to Find Application Pool by Process ID in IIS 7.0</title>
      <link>https://www.revindex.com/Resources/Blogs/Post/581/How-to-Find-Application-Pool-by-Process-ID-in-IIS-7-0</link>
      <description>Starting IIS7, you can find the name of the application pool by process id using the following appcmd. (IIS, Windows)</description>
      <author>slim@revindex.com (Revindex Solution)</author>
      <blog:author>Revindex Solution</blog:author>
      <guid isPermaLink="true">https://www.revindex.com/Resources/Blogs/Post/581/How-to-Find-Application-Pool-by-Process-ID-in-IIS-7-0</guid>
      <pubDate>Mon, 12 Jan 2009 18:08:00 GMT</pubDate>
      <blog:publishedon>2009-01-12 18:08:00Z</blog:publishedon>
    </item>
    <item>
      <title>Migrating IIS7 Site Settings</title>
      <link>https://www.revindex.com/Resources/Blogs/Post/577/Migrating-IIS7-Site-Settings</link>
      <description>This article shows you how to migrate IIS 7 settings to a new machine using the new appcmd provided by IIS. (Web Server, ASP.NET, Windows)</description>
      <author>slim@revindex.com (Revindex Solution)</author>
      <blog:author>Revindex Solution</blog:author>
      <guid isPermaLink="true">https://www.revindex.com/Resources/Blogs/Post/577/Migrating-IIS7-Site-Settings</guid>
      <pubDate>Sun, 28 Sep 2008 09:05:00 GMT</pubDate>
      <blog:publishedon>2008-09-28 09:05:00Z</blog:publishedon>
    </item>
    <item>
      <title>Microsoft Fiddler Web Debugging Proxy</title>
      <link>https://www.revindex.com/Resources/Blogs/Post/654/Microsoft-Fiddler-Web-Debugging-Proxy</link>
      <description>Here's a great Microsoft tool that deserves more attention than it gets. Fiddler is a free debugger software that hooks onto your Internet Explorer or Firefox browser. It allows a programmer to see the HTTP packets passing through the machine in a nicely arranged way. (asp.net, programming, perl, php)
</description>
      <author>slim@revindex.com (Revindex Solution)</author>
      <blog:author>Revindex Solution</blog:author>
      <guid isPermaLink="true">https://www.revindex.com/Resources/Blogs/Post/654/Microsoft-Fiddler-Web-Debugging-Proxy</guid>
      <pubDate>Thu, 18 Oct 2007 00:33:00 GMT</pubDate>
      <blog:publishedon>2007-10-18 00:33:00Z</blog:publishedon>
    </item>
    <item>
      <title>Never Leave Source Code on the Server</title>
      <link>https://www.revindex.com/Resources/Blogs/Post/653/Never-Leave-Source-Code-on-the-Server</link>
      <description>I'm not a big fan when it comes to deploying source code on the Web server especially with the new Web Site projects that comes with VS.NET 2005. If your server got hacked before, you'll understand why source code on the server is a very bad idea. (c#, asp.net, php, perl, security, dotnetnuke)</description>
      <author>slim@revindex.com (Revindex Solution)</author>
      <blog:author>Revindex Solution</blog:author>
      <guid isPermaLink="true">https://www.revindex.com/Resources/Blogs/Post/653/Never-Leave-Source-Code-on-the-Server</guid>
      <pubDate>Sun, 09 Sep 2007 17:07:00 GMT</pubDate>
      <blog:publishedon>2007-09-09 17:07:00Z</blog:publishedon>
    </item>
    <item>
      <title>Nested Form in ASP.NET Page</title>
      <link>https://www.revindex.com/Resources/Blogs/Post/569/Nested-Form-in-ASP-NET-Page</link>
      <description>It's common practice on the web to copy and paste a third party HTML code to add functionality to a page. To embed this kind of code is normally a breeze for even non-programmers. What appears to be easy is actually quite complicated to do on ASP.NET pages. The reason is because every ASP.NET page is wrapped in one big HTML Form.</description>
      <author>slim@revindex.com (Revindex Solution)</author>
      <blog:author>Revindex Solution</blog:author>
      <guid isPermaLink="true">https://www.revindex.com/Resources/Blogs/Post/569/Nested-Form-in-ASP-NET-Page</guid>
      <pubDate>Tue, 24 Jul 2007 20:09:00 GMT</pubDate>
      <blog:publishedon>2007-07-24 20:09:00Z</blog:publishedon>
    </item>
    <item>
      <title>How to Create a Self-Signed SSL Certificate</title>
      <link>https://www.revindex.com/Resources/Blogs/Post/564/How-to-Create-a-Self-Signed-SSL-Certificate</link>
      <description>When you're testing a web site on IIS either on your own development PC or on staging, you need a way to generate a self-signing certificate if you don't want to put out a few hundred dollars. In the past, Microsoft made available a tool called SelfSSL inside the IIS 6.0 Resource Kit. The tool works but there is a bug when you try to create more than one certificate on the same machine. You keep losing the first certificate you created. The better way is to use the new Microsoft SSL Diagnostics tool ... (ASP.NET, IIS)
</description>
      <author>slim@revindex.com (Revindex Solution)</author>
      <blog:author>Revindex Solution</blog:author>
      <guid isPermaLink="true">https://www.revindex.com/Resources/Blogs/Post/564/How-to-Create-a-Self-Signed-SSL-Certificate</guid>
      <pubDate>Wed, 11 Jul 2007 01:44:00 GMT</pubDate>
      <blog:publishedon>2007-07-11 01:44:00Z</blog:publishedon>
    </item>
  </channel>
</rss>