Hi

I have a problem that I'm trying to find a decent solution to.

I have a classic asp + MS SQL server application which runs in the folder of the main site called /app

The front end pages of the site are currently just static html pages but I want to use wordpress to maintain it.

The current solutions I've come up with all have serious flaws.

1) install PHP and get wordpress running on the web server and run the asp application in a virtual folder. Problem: can't install wordpress on the same server for security reasons.

2) Use utility similar to wget on linux to schedule a download of the wordpress HTML output. This is my preferred option but wget for windows doesn't seem to work.

3) run the WP site on a second LAMP server and run some kind of proxy on the primary. Problem: slow, adds second point of failure + can't find such a script anyway.


I'm assuming the normal way to do this is to use separate domains for the front and back end but in I believe in this case having two domains would be seriously detrimental to my google rankings.

Have you looked into Active Server based blogging solutions?

1) install PHP and get wordpress running on the web server and run the asp application in a virtual folder. Problem: can't install wordpress on the same server for security reasons.



What security issue that you foresee here? it is possible now to host php solution in mix with asp.net hosting plans. if you could tell the security issue then we could check and let you know.



2) Use utility similar to wget on linux to schedule a download of the wordpress HTML output. This is my preferred option but wget for windows doesn't seem to work.



Not a advisable solution though if you have similar feature.



3) run the WP site on a second LAMP server and run some kind of proxy on the primary. Problem: slow, adds second point of failure + can't find such a script anyway.


I'm assuming the normal way to do this is to use separate domains for the front and back end but in I believe in this case having two domains would be seriously detrimental to my google rankings.



You're right - best to have is on single domain, you would need to revisit the first point#1 that you had raised and check what can be done to over come security problems. let us know what security issue that you foresee in this setup.

What this frontend and backend mean?

for security reasons
Can you expand on this vague statement?
I run PHP + ASP.NET sites just fine on a Windows IIS7 server.