On Sun, May 5, 2013 at 7:36 AM, Richard Stuart <span dir="ltr"><<a href="mailto:rl.stuart@verizon.net" target="_blank">rl.stuart@verizon.net</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>Do any of you have any ideas on how to convert asp to html</div></blockquote><div><br></div><div>As Michael originally pointed out, you don't convert to HTML. HTML pages are [largely] static content. Active Server Pages (ASP) are dynamic. Dynamic pages use functions and libraries that can be Server-side (Application Server) and/or Client-side (Browser) specific.</div>
<div><br></div><div>Also, as others pointed out, there are great differences between old, legacy ASP (VB-centric) and newer <a href="http://ASP.NET">ASP.NET</a> (.NET-centric, which is C# aka Java object-like). The biggest issue with the former is that the functions and libraries are older Windows IIS and IE-specific, not even supported in some cases by newer IIS and IE, server and client. The latter is at least Java-based, especially when it comes to system and other methods, although there are Win32-only specifics too. </div>
<div><br></div><div>In both cases, your "best bet" is to investigate the great number of ASP/<a href="http://ASP.NET">ASP.NET</a> to JavaServer Pages (JSP) converts and solutions. They won't work flawlessly, but they will often handle much of the burden for you. Again, the biggest issue will functions and libraries, especially old, legacy ASP that will not even be supported on newer Windows platforms, much less Linux. As always, Microsoft solutions are designed for Win32-only, and do not even support some of their non-desktop/server platform well.</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div> and cgi/perl scripts.<br></div></blockquote><div><br></div><div>Again, CGI is a dynamic, server-side solution. You don't convert it to HTML.</div>
<div><br></div><div>Here's an analogy ...</div><div> - Thinking a dynamic server/language page can be converted into a static HTML page is like thinking one can convert a Macro-laden Office document into a static, flat text file.</div>
<div><br></div><div>The biggest issue with enterprises is the sheer amount of investment they make into periodically _abandoned_ Microsoft solutions.</div><div><br></div><div>I had one major, household name company that evaluated, but failed (for political reasons) to go with standard HTML and Java applets in 2001, and made heavy investments in IIS, IE and ASP. By 2008, they were going nuts since both their on-line and internal presence -- 90% of their operations -- were MS IE 6-only, and wish they had gone with an open set of standards. Unfortunately, by then, they had 400 developers who felt threatened with either training or replacement if they moved to a open standard platform, so that "inertia" was hard to defeat, even if it saved the company $100M/year.</div>
<div><br></div><div>The problem is never cost, but inertia. Total Cost of Ownership (TCO) almost always favors open standards, beyond initial cost, which is minor in comparison.</div><div><br></div><div>-- bjs</div><div>
<br></div><div>[1] <a href="http://en.wikipedia.org/wiki/Active_Server_Pages">http://en.wikipedia.org/wiki/Active_Server_Pages</a></div><div>[2] <a href="http://en.wikipedia.org/wiki/JavaServer_Pages">http://en.wikipedia.org/wiki/JavaServer_Pages</a></div>
<div><br></div><div><br></div><div>--</div></div>Bryan J Smith - Professional, Technical Annoyance<br>b.j.smith at <a href="http://ieee.org" target="_blank">ieee.org</a> - <a href="http://www.linkedin.com/in/bjsmith" target="_blank">http://www.linkedin.com/in/bjsmith</a><br>
<br>