How To Host Wordpress Blog on IIS in a sub folder

wordpress.org has guides to do what you need.
See https://codex.wordpress.org/Installing_on_Microsoft_IIS


As to the choices, that is completely up to you in terms of level of comfort dealing with the systems to troubleshoot, resolve issues if they arise.

The way I handle this with my hosting clients is to never nest sites.

So for a setup like yours, I'd create a new host record, like blog.foo.com + then do a redirect from www.mysite.com/resources to this new host.

Many problems develop if you start nesting different types of installations.

As you're backups will have to become aware of how all this nesting translates to files + database(s).

Better to have standalone hosts for every type of install, so you know when you backup one host, you get all correct files.

And when you backup the main site, there's no requirement to recursively walk all directories discovering what else has to be backed up, in every nested install, to produce a full site backup.

David Favor - RE: So for a setup like yours, I'd create a new host record, like blog.foo.com + then do a redirect from www.mysite.com/resources to this new host.v

How would I do a redirect at www.mysite.com/resources to the new host?  Would this be an ASP page with code with the redirect?

The actual URL blog.foo.com must not be displayed in the browser.

You can either create a place holder html with a meta refresh, or setup a virtual directory that is a redirect... instead of home dir you would use the url as redirect.

Would using a redirect in the code have negative SEO consequences?

Please clarify your question. a redirect would direct the search engine to the new sub site to crawl.
the robots.txt.
IMHO, trying to concern oneself with something one can not control...

This is much simpler than what is being said.

All you need to do is to create your folder www.mysite.com/resources/.  Then install Wordpress in the resources folder.  It is that easy and I have done this in the past.  Avoid using sub domains because that gets treated as a separate domain for SEO reasons.

In Wodpress you can set up how your urls work. This makes a url like www.mysite.com/resourcescategory/categoryname/ not only feasible, but a great option.

Instructions for installing are in the docs https://codex.wordpress.org/Installing_WordPress and if your site happens to be using Plesk, you have a bonus because Plesk will not only install for you, but add security measures as well.

Scott,

The site is built using ASP and IIS on WIndows Server 2012.

How can I install Wordpress and Apache to www.mysite.com/resources/ without negatively affecting the rest of the site?

Why do you need Apache?  You only need PHP and your database.  I run php on windows iis 8 myself.

Install php https://technet.microsoft.com/en-us/library/hh994592(v=ws.11).aspx#WebPI

Are there any issues with having ASP using SQL Server with PHP using MySQL for the same domain hosted in IIS?

If you are on a shared hosting service, you may already have php installed. If you don't, it is possible that you will not be able to install php (or anything) on a shared server.   If that is the case, you can find .net blog http://www.dnnsoftware.com/, https://francis.bio/blogengine/ and probably many others.

What I have done in the past is to create my own. Creating your own can be easy if you keep your parameters simple. If the user is not technical and wants a lot of control, then WP or the others is a better choice.

I have my own server.  I must use ASP and Wordpress in IIS.

I appreciate your help Scott.  Thank you!