How to pre compile a website using aspnet_compiler?

Just use the below command to precompile your website

 

aspnet_compiler -p physicalOrRelativePath -v / targetPath

 

More information regarding the same can be found here

https://msdn.microsoft.com/library/ms229863(v=vs.100).aspx

https://msdn.microsoft.com/en-in/library/ms227976(v=vs.90).aspx

How to generate self-signed Secure Sockets Layer (SSL) certificate for Internet Information Services (IIS) 6.0?

SelfSSL version 1.0 is a command-line executable tool that you can use to generate and install a self-signed Secure Sockets Layer (SSL) certificate for Internet Information Services (IIS) 6.0. Because SelfSSL generates a self-signed certificate that does not originate from a commonly trusted source, the tool's usefulness is limited to two specific scenarios:

Download IIS 6.0 Resource Kit Tools from link

http://www.microsoft.com/downloads/details.aspx?FamilyID=56FC92EE-A71A-4C73-B628-ADE629C89499&displaylang=en

And use

SelfSSL version 1.0

SelfSSL (SelfSSL.exe) can help you generate and install a self-signed SSL certificate. Because the SelfSSL tool generates a self-signed certificate that does not originate from a trusted source, use the SelfSSL tool only in the following scenarios:
• When you have to create a security-enhanced private channel between your server and a limited, known group of users
• When you have to troubleshoot third-party certificate problem

You can find this exe in start->All Programs -> IIS Resources-> SelfSSL-> SelfSSL.exe

More information regarding "IIS 6.0 Resource Kit Tools " can be found at the below link
http://support.microsoft.com/kb/840671

Page cannot be found" when browsing aspx pages in Windows Server 2003 with IIS 6.0

You may get a Page cannot be found message when you browse aspx pages in a Windows Server 2003 environment.

That is because in Windows 2003, all the webservice extensions are "Prohibited" by default to ensure security.

To resolve this, do the following steps:-

1. From your Run command, type inetmgr and press enter.
2. Expand the appropriate nodes in the IIS to locate the "Webservice Extensions" Node
3. Click on the same.
4. You will find a list of "prohibited" extensions in the right.
5. Click on ASP.NET and Active Server Pages and "allow" it

That should resolve this issue.

This article applies for Windows Server 2003, IIS 6.0 environment

Happy Supporting

Rajesh Kamalakshan