I want to run the app with classic mode, but in Azure how should I do that?
The only idea I can figure is startup script? Is that correct?
You have to deploy your website in a WebRole, and not WebSite. Doing so, you have the ability to run a startup task in elevated mode.
Put the following line in your startup task script:
appcmd.exe set config -section:system.applicationHost/applicationPools /applicationPoolDefaults.managedPipelineMode:"Classic" /commit:apphost
And this will do the trick.
Related
Can anyone tell me how to use w3wp to start SharePoint applications from the command line?
And provide me with a small example.
You could try to run the command below in the command prompt to start the site that is hosted on the IIS.
%windir%\system32\inetsrv\appcmd start sites "Default Web Site"
If you want to start the App pool then you could use the command below.
%windir%\system32\inetsrv\appcmd start apppool "DefaultAppPool"
Output:
To stop the site you could use the command below.
%windir%\system32\inetsrv\appcmd stop sites "Default Web Site"
Notes:
make sure you run the command prompt as an administrator.
Actual i have installed a self hosted agent on my local machine
now my issue is when i am running a release pipeline for a client machine i have a powershell task in which i have a command that runs an exe file located in client machine which displays a message box .
but when I am checking at client machine i am able to see the exe is running in task Manger during the execution of my release pipeline but show how i am not able to see the interface of the application .
You can try adding -Wait to your powershell command. For below example.
Start-Process -FilePath "path to programm.exe" -Wait
You also need to make sure the deployment agent(the agent installed on client machine) is running in interactive mode.
To configure the agent in deployment group to run in interative mode. You need to change the Registration script you copied in azure devops. Remove --runasservice when you run the registration script on the client machine
Then you will be asked to set the agent to run as service or not as below screenshot(Please enter or type N to select interative mode) during the setup.
Check Interactive vs. service for more information.
I'm trying to get Kentico Continuous Integration running as a step in my CI process. However, I'm encountering the following error when my deployment script runs:
Running Kentico Continuous Integration...
Continuous Integration Console
Kentico Software
System.Exception: Login failed for user 'MACHINE-NAME\ci-runner-user'.
at CMS.DataEngine.CMSApplication.ReportApplicationError(String message)
at CMS.DataEngine.CMSApplication.Init()
at CMS.ContinuousIntegration.ConsoleApp.Program.InitKenticoApplication(String webAppPhysicalPath)
at CMS.ContinuousIntegration.ConsoleApp.Program.Deserialize(String webAppPhysicalPath)
at CMS.ContinuousIntegration.ConsoleApp.Program.Main(String[] args)
How do I enable the local user my deployment script runs as to successfully execute ~\CMS\bin\ContintinuousIntegration.exe -r?
My initial thought is that you’re using integrated security in the web.config - make sure that the user you mention has SQL access for your Kentico DB
You need to allow PowerShell ISE to run unrestricted. To do so follow these instructions:
Install or make sure PowerShell ISE is installed
Run PS as Administrator
First time only - run this command in PS ISE, "Set-ExecutionPolicy Unrestricted". It should show LocalMachine as Unrestricted. This will allow you to execute the script for CI Restore
I am unable to install the VSTS Agent Azure VM extension on an Azure VM. I tried both the Install extension blade in the Azure portal and the Powershell option. When I try from the portal it just gets stuck at transitioning. If I run the Powershell script it gets stuck trying to connect to server.
I was able to install it on another server without any issues. The 2 servers are part of a web farm so they are exact images.
I am following the steps detailed at this url https://learn.microsoft.com/en-us/vsts/build-release/concepts/definitions/release/deployment-groups/howto-provision-deployment-group-agents?view=vsts .
I am trying to deploy from VSTS to an Azure VM.
This is the screen when I try to run the powershell script.
Run the config file directly (from C:/vstsagent folder) in cmdline and try again with dev.azure.com/{organisation name} url.
I need to get the deployment slot in runtime.
For example I think of something like :
process.env.ENVIRONMENT
Is there a way to get that?
Thanks
You can set the NODE_ENV to development variable under the Website App settings configuration on the portal.
Additionally, if you are using the Azure CLI (which you can install via npm install azure-cli -g), you can run the following azure site config add NODE_ENV=development assuming your CLI is configured.