You've probably considered this, but, why not keep everything in VFP and just call a VFP COM mtdll from a .asp file...
>I have a situation that I would like to solve. In most places where I have a new content to offer to the user, I usually have an ASP page. So, that page contains some includes references which also contains some ASP code. So, for example, index.asp is including icon.html. In icon.html, I have some ASP code. As icon.html will be interpreted within index.asp, everything works.
>
>Now, for that specific content, wherever I go in VFP to generate some template using WWC, I am facing a situation where I have to maintain icon2.html, which is included in the template, which contains the same behavior but written in VFP. I have to maintain it in parallel as since this code in generated in VFP, I can't have some ASP code in it. Some, in several places, I have to maintain several files in double. One which contains a logic in ASP and another version which contains the logic in VFP. How can I avoid that?