i'm just starting to play around with azure, I'm going through the tutorial for XamarinIOS. When I get to the step to publish, I cant even get the publish option available when I right click its just not there. Im using Visual Studio Ultimate 2013.
Heres the link to the tutorial.
http://azure.microsoft.com/en-us/documentation/articles/mobile-services-dotnet-backend-xamarin-ios-get-started/
I get all the way to Publish your mobile service step.
I do get a warning when I build, look below.
Warning 1 Found conflicts between different versions of the same dependent assembly. Please set the "AutoGenerateBindingRedirects" property to true in the project file. For more information, see http://go.microsoft.com/fwlink/?LinkId=294190.
You need to make sure you have downloaded the PublishSettings file first before you can deploy. This is shown in Step 2 of the "Publish your mobile service" on the page you linked to. If you don't have this file the publishing framework won't know where to deploy your mobile services code to.
Related
I am trying to publish a Xamarin.Forms app to Google Play but the Microsoft docs don't accurately reflect the current UI for Visual Studio. According to these docs, in order to publish to Google Play, you must first change the Channel from "Ad Hoc" to "Google Play". The docs say you do this by clicking the "back" button in the Distribute dialog.
Here's the problem: That button does not exist, at least not in the latest version of Visual Studio. I took a screenshot to illustrate:
As you can see, this does not match the screenshot in the Microsoft docs, which show a "Back" button that you're instructed to click on in order to navigate to the "Select Channel" dialog, which is where I need to go in order to make it a Google Play app. Simply clicking on "Select Channel" does absolutely nothing at all. Right-clicking anywhere only gives the option to delete and start over. I tried that and got the same result.
My app is a fairly simple Xamarin.Android C# app with package format set to "bundle" and Dex compiler set to "d8". Whether AOT/LLVM is enabled has no impact on this issue. Screenshots of full Android Options below:
What am I missing?? How do I get Visual Studio to play nice and let me select the correct channel?
Firstly even in the past to publish your App, you had to do it via Google Play Store website initally first anyway. You were able to push updates and new version after that. However, as far as I know (since I literally just published my first app 3 weeks ago), Visual Studio API that was responible for publishing the app is deprectated. You should get that error when you try to push it to Google Play. You can use the addhock option to sign the APK and push that APK directly via Google Play Console. Visual Studio doesnt support it anymore.
I am developing a bot in Azure using the Bot Framework (C#). After spinning it up on Azure I downloaded the source code and tried to open the provided Visual Studio solution file but got an error
Creation of virtual directory http://localhost:3894/ failed with the error: Filename: redirection.config Error cannot read configuration file
Google points towards an issue with IIS or IISExpress but the recommended solutions (forcing IIS to recreate config files by renaming them) didn't work. I don't know if the issue is with Visual Studio, my system, or something else entirely but anything that could shine light on the situation would be appreciated.
EDIT: Deleted and Re-downloaded both VS and IISExpress, did not fix the problem
Try to right click your project in solution explorer and select properties. The select web on the left side. click the create virtual directory button. see if that works for you.
This was working fine yesterday.
I made several changes to my system (updates from VS Community 15) and the Azure SDK updates, etc., - as was recommended by the software.
Today, when I right click on the web app and select Publish (using the same or manually entered public information) I see the following error on my Azure App Service Activity tab:
Can't find existing loaded project:http://localhost:55809
I have since tried other publish profiles, none seem to work.
I can successfully build and run the web app on localhost.
In Visual Studio, go to View -> Other Windows -> Web Publish Activity and you will see the Azure App Service Activity window.
Click on the Publish web icon that you will find there. It should work.
Publishing via FTP to azure instead of WebDeploy worked for me.
Change the deploy method to Ftp then change it right back to "Web Deploy". This keeps working for me
In the project folder in the website.publishproj file change the SourceWebProject tag to contain your client name instead of the localhost.
At least this worked for me :)
Update 13 Dec 2015:
Having the same problem again. The previously mentioned fix does not work. However publishing via FTP to azure works.
When you get the azure publish profile you get both Web Deploy and FTP. Try using FTP.
An update of Visual Studio Community 2015 to version 14.0.24720.00 Update 1 seems to have corrected the problem.
Update or install from here. Visual Studio Community Download from Microsoft
When I open a sample Blinky application in Visual Studio, compile and run it, it gets automatically deployed to the target configured WindowsIoT device. After that, on Windows 10 machine where I compile it, the application binaries are located in the bin sub-folder of the project folder as one would expect.
I would like to automate the deployment, so that I could run deployment code
without Visual Studio, specify target device and the binaries location and it would deploy it. I cannot find any API that allows
to deploy apps to Windows IoT, how do I do that?
This shiny Windows IoT stuff is a new area, and there is not a lot of info available apart from the samples and the getting started page. Any pointers are appreciated.
Update: As noted in comments, once one start thinking of mass production, they will probably need to conciser ICD. This, is not, however the problem I'm trying to solve currently. I would like to figure out how I can provide Over-the-Air updates to my UWP application running on Raspberry Pi and Windows IoT. I also would you like to know how I can automate build / deployment in general, but that may be automatically solved if I have a proper OTA solution.
There is a set of instructions on how to do it, which can be found in the same github repo you are linking in your question, but in a different folder. Note, that you need an appx for these instructions to work, and it's not created by the solution build by default.
This page provide (non IoT specific) instructions on using VS to build the appx. And this blog post talks about the command line tool that can be used for making appx.
Note, that the last two links are also talking about publishing an application to app store, so you'll need to make some mental adjustments around that.
I have a website in C# Visual Studio 2013, which was developed by another developer and is hosted on Azure cloud service. Whenever I make any changes and try to publish, Visual Studio hangs and I can't publish it. It is not showing any error message. Besides that I can successfully deploy it by building it, but as it's taking too much time and also costs money to client (as VS Team Services only provides monthly 60 minutes of free build, after that clients get charged for extra minutes). I am using following steps for publishing and it's works fine but after publishing starts Visual Studio hangs and is unresponsive.
The steps to publish the website are as follows:
1) Open the solution in visual studio.
2) Right click on the azure project in the solution explorer, and select publish.
3) The first step in the wizard is to sign in, make sure to select your credentials.
4) The next step is settings, make sure environment is set to production and build configuration is set to release, then click next.
5) The final step is a summary, simply click the publish button.
I am very new to Azure so let me know if I need to make any setting during set up my project.
I hit the same problem after installing the 2.8 SDK and tools. After checking out these answers I still had the problem, but found a solution.
Right click the Azure project in the VS2013 solution explorer, open project properties. Go to the application tab, and there's an "Upgrade" button to upgrade the project to the latest SDK. That did the trick for me.
It sounds like you are doing the right steps to deploy using the wizard. However I don't have enough information to know what would cause this to hang. There are some documentation details about the wizard that might help? https://msdn.microsoft.com/en-us/library/azure/hh535756.aspx
There are other ways to deploy to Azure, which may solve the issue. You can for example download a publish settings profile, and use this to deploy instead of the wizard. Details here: http://blogs.msdn.com/b/avkashchauhan/archive/2012/05/10/downloading-windows-azure-publish-settings-subscription-configuration-file.aspx
Or you can deploy continuously from Git - https://azure.microsoft.com/en-us/documentation/articles/web-sites-publish-source-control/#Step75
Both solutions will require some tinkering in the Azure portal or getting in with PowerShell but there's a lot of ways to deploy.
Doing these two things fixed it for me, not sure which:
Clean build
Server Explorer > (Had to re-enter Azure credentials)
VS2013 update 5.
A related post found here..
https://social.technet.microsoft.com/Forums/virtualization/en-US/4e51b1f0-91c3-4ce9-9a15-a8d10f912c5b/publish-cloud-service-causes-visual-studio-2013-to-hang-crash?forum=windowsazuredevelopment
One user was able to get past the publish freezing by doing the following..
So I did a line-by-line comparison between all of the files in that
new project and everything in my existing one and found only two
possible things wrong:
1) The version stamps (dates, really) in my
files were not upgraded to reflect the latest version of the Azure
tools. I manually changed those in my existing project to match the
garbage test project's date stamps.
2) My XML files had some empty
sections that did not exist in the new project's files, so I simply
removed those empty sections.
3) Beyond that, I also deleted my *.user
file.
Specifically, I was able to remove schemaVersion="2014-06.2.4" from my ServiceConfiguration and ServiceDefinition files and it fixed the issue.
My guess is that your installed sdk version is different than the specified schemaversion.
I tried all above methods none worked for me. So this is for people who already tried above and still couldn't make it work.
=> Publish in Release mode :-)
Yes I was trying to publish in Debug mode which was causing it to hang till death ;-)