Can't say. Never tried it on an upgrade. Experiment.

For the module install I just did the url request with credentials.

My Powershell script

# Administrator level Account in the site
$User = "redacted"
$Password = "password"
#The second command uses the ConvertTo-SecureString cmdlet to create a secure string from a plain text password. The command uses the *AsPlainText* parameter to indicate that the string is plain text and the *Force* parameter to confirm that you understand the risks of using plain text.
$PWord = ConvertTo-SecureString -String $Password -AsPlainText -Force

#The third command uses the New-Object cmdlet to create a **PSCredential** object from the values in the $User and $PWord variables.
$Credential = New-Object -TypeName "System.Management.Automation.PSCredential" -ArgumentList $User, $PWord

(Invoke-WebRequest "https:/Redacted" -Credential $Credential -UseBasicParsing).Content

---

Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
www.dynamisys.co.uk

I have the source already and have found the Upgrade.cs class. Had had an interesting idea of perhaps importing this project into our own solution and just calling the UpgradeApplication method from it. That way we can upgrade DNN from our own application at a click of a button.

Just an idea at the moment which I'm going to play with this afternoon. Hopefully Michael will be able to say if this is the way he envisaged it working and if not if it's a viable solution.

Scott

Morning Michael, 

What is your take on the approaches discussed in here? Is this different to the approach you alluded to?

Thanks, 

Scott