Posts

Showing posts from February, 2012

Managing Legacy Classic ASP Websites

In the 10 years since ASP.NET 1.0 was first released, all Classic ASP websites will have been converted to ASP.NET, right? 


Well...


Like it or not, legacy systems are still with us and they are likely to be with us for some time yet. As developers, it's a fairly reasonable assumption that we want all systems to utilize the latest technology, and converting Classic ASP websites to either ASP.NET 4.0 or ASP.NET MVC3 Web Applications will be a logical step. There's just one problem; return on investment.


Many if not most businesses will be feeling the pinch right now, and the return on investment in time and resources to convert Classic ASP websites may well be difficult to see for financial managers. The improved manageability, stability, testing, etc, that comes from using the latest technologies will be negated by managers watching the bottom line very carefully. If the investment on conversion doesn't make an improvement to the bottom line, or someone else isn't willing …

Creating CSR Requests for FTPS in IIS 7.5

Image
IIS 7.5 took a great step forward with the inclusion of an FTPS module that can be installed during set-up. There are a wealth of great sources of information on how to setup an FTPS site, however one issue I ran into was how to generate a CSR to purchase an SSL certificate for my FTPS site. All the examples I saw used self-signed certificates; presumably so the examples could be followed without any costs involved in purchasing an SSL certificate.
 To create a CSR for an FTPS site, you need to open IIS 7.5 manager, click on the server name in the left hand pane, then double click on "Server Certificates" in the main window


From here, click on "Generate Certificate Request" in the right hand actions menu to launch the Request Certificate wizard. On the first screen of the wizard, you will need to enter the distinguished name properties for your site, remembering to use ftp.yourdomain.co.uk as the Common Name (obviously replace yourdomain.co.uk!).


Clicking next bri…