Hi Rick, have an issue on a Win 7 Prof machine where the install just won't play.
Initially the Install-IIS-Features.ps1 would not run saying "not a recognised command..." on all lines even after I changed script rights. Closer inspection on manually turning on IS & features there where some differences to your Docs. I checked to see that IIS is V7.5 and .NET installed in 4.8.
When I try to test I just get a blank screen - no interpetation of code I think as it thinks about it for a sec. When I click on an .aspx page the code simply comes up in a edit window? Have use IIS to change all permissions to full. I also should have Administrator rights.
Since there no indications or other error where can I start to look. As this is a standalone APP I do not wish to head done IIS Express as you recommend manual starting from CONSOLE?
EDIT: See below there is no ASP.NET 4.8
EDIT2: See below the errors received using ps1 script
PS C:\webconnectionprojects\ppg> ./Install-IIS-Features.ps1
The term 'Enable-WindowsOptionalFeature' is not recognized as the name of a cmdlet, function, script file, or operable
program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At C:\webconnectionprojects\ppg\Install-IIS-Features.ps1:14 char:30
+ Enable-WindowsOptionalFeature <<<< -Online -FeatureName IIS-WebServerRole
+ CategoryInfo : ObjectNotFound: (Enable-WindowsOptionalFeature:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
EDIT3: Only hint I can find is this error?
Can you help, thanks Paul.
Don't know based on the information you're providing. The script won't work because - well, it's Windows 7 which is 15+ years old and those features weren't available then.
I'm not sure what's wrong - go through the troubleshooting bit in the documentation and then report what you find there.
The other thing is - you don't need to run with IIS on your dev machine. You can use IIS Express or if you're on the latest version of Web Connection (v7+) you can use the Web Connection Web Server locally. Both of those don't require explicit configuration and will just work by pointing at the folder.
And you might want to make sure you have all the steps in here if you do stick to IIS:
+++ Rick ---