SMARTERASP.NET MCP · BETA
BetaDeployment
MCP manages hosting-side deployment access. Your repository remains the source of truth, and GitHub Actions performs the actual deployment.
Windows: IIS WebDeploy
- Enable access with
deployment_enable_webdeploy. - Set a caller-generated password with
deployment_rotate_webdeploy_credential. - Read the sanitized destination values using
deployment_get_webdeploy_settings. - Store the username and password as GitHub repository secrets.
- Use a GitHub Actions workflow appropriate for your .NET or Windows application.
Linux: FTPS
Use the FTPS credentials and destination exposed by the Linux hosting plan’s supported control-panel functions. Store credentials as GitHub secrets and deploy only the built application output to the intended site root.
No hosted GitHub integration
The Beta does not connect to your GitHub account, create repositories, install GitHub Apps, or execute a proprietary deploy function. This keeps source access and deployment credentials under your control.
Safe credential rotation
Create the new deployment secret, update every consuming workflow, perform a test deployment, and only then retire the old value. Read operations never return stored passwords.