Getting publish files windows azure - azure

The steps I have taken:
1) Get-AzurePublishSettingsFile
I then download the file.
2) Import-AzurePublishSettingsFile
now the problem is here, I have put the first file in the C drive, but it cant seem to find it.
I do the following
Import-AzurePublishSettingsFile C:\-credentials.publishsettings
powershell returns the following error
CategoryInfo : InvalidArgument: (:) [Import-AzurePublishSettingsFile], ParameterBindingException
FullyQualifiedErrorId : PositionalParameterNotFound,Microsoft.WindowsAzure.Management.Cmdlets.ImportAzurePublish
SettingsCommand
any idea how to resolve this.
thanks

You are passing the the incorrect publishsettings file location in your command as below and that's why you are getting the exception:
PS> import-AzurePublishSettingsFile C:\-credentials.publishsettings
Nobody knows where you are storing the publishsettings in your machine so what you really need is to download publishsettings file again using Get-AzurePublishSettingsFile PS command and this time remember where you are saving it in your local machine.
Once you know the publishsettings file path pass it correctly with import-AzurePublishSettingsFile PS command and it will work.
PS> import-AzurePublishSettingsFile CORRECT_PATH_TO_PUBLISHSETTINGS_FILE
I have created a sample PS script menu to use Windows Azure so you can take a look here.

From what I understand, there are 2 ways to publish to Azure using VS 2012: the first one is 1) via "publish" and 2) the second one is "publish via azure".
1) If you are selecting "publish" which is just to Azure websites the while it gives up an option to select the downloaded publish settings these settings do not actually import and the only way I get the website deployed is by setting up the profile manually.
2) to use your downloaded publish settings, you must select "publish to azure", which then imports the certificate and allows you proceed to the next steps within the VS 2012 deployment to a cloud service.
It took me a while to understand that publishing via VS 2012 is a completely separate process from using Azure Powershell to manage Azure VMs (or blobs) which also requires you to work with the downloaded publishsettings which I left in my "downloads" folder per below:
PS C:> Import-AzurePublishSettingsFile 'C:\Users[me]\Downloads[Pay-As-You-Go-credentials.publishsettings]'
Note: the single quotes seem to be required.

Related

Continuous deployment to Azure of ASP.NET Core app

I'm trying to set up continuous deployment (.NET Core 1.1 Web Application) with the build mechanism of VSTS.
To do so I'm following the steps displayed on the official doc of Microsoft :
Use VSTS to Build and Publish to an Azure Web App with Continuous Deployment.
The first 3 steps (restore/publish/zip) work without any issue. But the fourth step is failing. I'm not able to publish the app to my Azure App Service.
Here is the error (from the log) :
2016-12-22T14:12:13.1175907Z Got connection details for azureRM WebApp:'devoteamlogin-staging'
2016-12-22T14:12:13.5419583Z Running command: "C:\Program Files\IIS\Microsoft Web Deploy V3\msdeploy.exe" -verb:getParameters -source:package="C:\a\1\a\DevoteamLogin.zip" > "C:\a\1\s\parameter.xml"
2016-12-22T14:12:14.8449274Z Error Code: ERROR_EXCEPTION_WHILE_CREATING_OBJECT
2016-12-22T14:12:14.8449274Z More Information: Object of type 'package' and path 'C:\a\1\a\DevoteamLogin.zip' cannot be created. Learn more at:
2016-12-22T14:12:14.8449274Z Error: The Zip package 'C:\a\1\a\DevoteamLogin.zip' could not be loaded.
2016-12-22T14:12:14.8449274Z Error: Package file 'C:\a\1\a\DevoteamLogin.zip' is not in a supported .zip format and therefore cannot be read.
2016-12-22T14:12:14.8449274Z Error count: 1.
2016-12-22T14:12:14.8509276Z ##[error]TypeError: Cannot read property 'output' of null
2016-12-22T14:12:14.8589281Z ##[section]Finishing: Deploy AzureRM App Service: devoteamlogin-staging
Step details
Am I missing something somewhere ? I did exactly what the documentation says (same variables, same steps, same configuration).
Update: After making some new tests, I see that the 'dotnet restore' command does not restore anything because it does not find the project.json. But there is no project.json file anymore in the new ASP.NET Core 1.1 Web application (everything is in the .csproj file).
warn : The folder 'C:\a\1\s' does not contain a project to restore.
Here is a solution https://twitter.com/DonovanBrown/status/816380372028002304. This shows the requirements to build csproj projects with Team Services. It is a full working solution.
I think the format of your zip archive is wrong, I used the native archive file task instead and unchecked "Prefix root folder name to archive paths".
Also I followed the documentation from the Visual Studio Team instead of the one from the dotnetcore team. It works better I found.

Unabled to deploy service fabric application to azure remote cluster from VSTS continuous inrgration

I have configured a CI build for a Service Fabric application, in Visual Studio Team Services, according to this documentation: https://azure.microsoft.com/en-us/documentation/articles/service-fabric-set-up-continuous-integration.
However I've changed the deployment portion specified on the document above. As I want to deploy on my previously created remote azure cluster so I call the
Deploy-FabricApplication.ps1 with the required parameters using power shell. But unfortunately this is not working. I'm getting the below error:
[void](Connect-ServiceFabricCluster #ClusterConnectionParameters)
InvalidOperation: (:) [Connect-ServiceFabricCluster], FabricException
FullyQualifiedErrorId : CreateClusterConnectionErrorId,Microsoft.ServiceFabric.Powershell.ConnectCluster
WARNING: Unable to Verify connection to Service Fabric cluster.
[error]Test-ServiceFabricClusterConnection : Cluster connection instance is null
[error]At C:\Program Files\Microsoft SDKs\Service
[error]Fabric\Tools\PSModule\ServiceFabricSDK\Publish-NewServiceFabricApplication.ps1:119 char:16
void
: ResourceUnavailable: (:) [Test-ServiceFabricClusterConnection], NullReferenceException
FullyQualifiedErrorId : GetClusterConnectionErrorId,Microsoft.ServiceFabric.Powershell.TestClusterConnection
I can deploy successfully using visual studio. Even if I run the Deploy-FabricApplication.ps1 from the build machine using power shell the application gets deployed without any error. But only if I run it using VSTS build step (part of CI), then the error mentioned above occurs.
Please note that as per the suggestion of Charisk on another stackoverflow thread I've modified the Deploy-FabricApplication.ps1 file to put the below line after line 169.
$global:clusterConnection = $clusterConnection
This doesn't help either. Thanks in advance for your kind help.
In your publish profile http://s30.postimg.org/bttleqitd/cloud.jpg you use StoreLocation="CurrentUser" but if you followed https://azure.microsoft.com/en-us/documentation/articles/service-fabric-set-up-continuous-integration and specifically the Import your automation certificate section under Set up your build machine then you probably have imported your certificate to the LocalMachine store location.
Simply change StoreLocation in your publish profile from CurrentUser to LocalMachine and you should be good to go.
dot source notation means call the script with . "xxx.ps1". Refer to this link for details: PowerShell – What is dot sourcing and why use it?

How to Create a VM and deploy an application in Azure Resource Group Template

I want to create a set of VMs using either the Resource Group Template in VS 2015 or utilise one of the azure-quickstart-templates as the basis for doing this.
My specific requirements are also to install a simple .exe application and modify its .ini file with a key that I want to pass from the template, i.e. seqno = copyindex() or similar.
Can anybody provide some guidance please?
For a simple Windows VM you can use either a DSC Extension or a Custom Script extension on the VM. Both of the samples in the azure-quickstart repo require you to figure out how to stage the artifacts needed for the extension (in this case the EXE and the script that installs the EXE).
If you go the VS 2015 route, you can start with a VM template, add the DSC or custom script extension and then the PowerShell script provided by Visual Studio will stage the artifacts for you if you make them part of the project.
You can also mix/match - grab a template from github, modify it in VS or take the VS PowerShell script and bring it into whatever workflow works best for you.
Note: one thing to keep in mind as well - you need to pass the location of that EXE into the script that does the install - that script/vm will need to know where to get it from. In the VS 2015 workflow you can use the parameter values of _artifactsLocation and just pass that value along to the installation script. If you start with a quickstart template, you have to manage that yourself.

manageprofiles.sh can't create DEPLOYMENT MANAGER

My goal is to create a Deployment Manager profile in my Websphere on Linux.
Reading tons of documentation pages gives just two methods:
1) using X GUI application WAS_root/bin/ProfileManagement/pmt.sh
In this case, according to manuals, i should choose Management option, click "Next" and choose Deployment Manager server type.
Actually when i run pmt.sh in my WAS installation there is no option to choose Deployment Manager in Management section and only one profile type that i'm able to create is AdminAgent.
2) using manageprofiles.sh script under WAS_root/bin directory.
The manuals say that i can use -serverType DEPLOYMENT_MANAGER option in order to create deployment manager profile.
Actually when i run the script:
./manageprofiles.sh -create -templatePath ../profileTemplates/management/ -ServerType DEPLOYMENT_MANAGER -isDefault -profileName dmgr -adminUserName websphere -adminPassword websphere1
I get the following message:
The following validation errors were present with the command line
arguments:
serverType: The value for this parameter must be within this set of values [ADMIN_AGENT]
That means that i don't have the ability to create Deployment Manager at all.
Please advise what steps i can perform to be able to install Deploy Manager except erase my WAS installation and install it from scratch once again.
Thanks a lot.
You have standalone aka base edition of WebSphere Application Server. To create Deployment Manager you need Network Deployment edition.
Unfortunately you will have to install it from scratch from different installation files (from ND, not base or developers edition).

PowerShell Script in TFS Build not uploading to Azure

After searching on Google, I've managed to put together a powershell script based on this site to upload my azure project. When I try to add it to TFS build process using the steps on the same site I get the following output:
My build says it's been running for 7 hours and if I login to windows azure there is no mention of the package. I have run it numerous other times since but not for as long, even after 10 minutes it still hasn't changed anything on the Azure dashboard.
If I run the same command from a command prompt on the build server then it runs and uploads the staging environment and it takes about 8-10 minutes to complete. Is there anything special I have to do to get it to run from TFS Build, or is there a way that I can get more meaningful output?
Finally found it. The default.publishsettings didn't have permission for the build service to read it. Added full permissions for the service and it now works.

Resources