Just wondering about the white picture after deploying my app to itunesconnect.
After renaming the .ipa file to .zip and browsing through it it noticed that .net has not include an itunesartwork... file. Only the appicon and my icons for the tabbar included.
I created the .ipa with the terminal command:
dotnet publish -f:net7.0-ios -c:Release /p:ArchiveOnBuild=true
Did i miss something? Is there an optional parameter to force Visual Studio 2022 to create that 1024x1024 graphic?
If i look in the iossimulator folder for that app it includes all the graphics, and i think the file appiconItunesArtwork.png is the important one?
Related
Application upgraded using Microsoft's auto upgrade command line tool.
Some code fixes, and the code builds successfully.
Visual Studio however does not show me any way to debug my app.
When trying to click on Debug anyway, a random Android Emulator from my list(which is not showing currently)
Will open, but deployment will fail without specifying the reason.
Has anyone managed to upgrade an existing Xamarin.Forms project to Maui?
I managed to make VS recognize the Android project in my converted solution.
I added the <SingleProject>true</SingleProject> property into my Android project's .csproj file under the first/main property group, closed VS, deleted Bin, Obj, .vs folders.
After starting VS again , I rebuilt and VS allowed me to debug on selected .net targets like a single project Maui solution.
This is very strange that it works, since this solution is made of 3 project like in a Xamarin.Forms solution, so it doesn't make since that adding this property solves the issue, but there you go.
Delete .bin and .obj folders. Delete solution's hidden .vs folder. Build. Does it show debug option now?
Try restarting VS (after the successful build). Now work?
If not, Create a new project using Maui template.
Use solution / manage all nugets to add nugets used by your project.
Copy all your source files into that new project.
Project / "Add existing items": all those source files.
I'm trying to configure automatic build of a Xamarin Forms application, for Android and iOS, using Visual Studio App Center, but after choosing the branch in Build App\Project select box I cannot see my projects (.csproj files). Or better, I'm not able to see the .csproj files of projects I have to build (customers' customizations), but I can see the .csproj of my core projects.
Configuring iOS build I was able to select the .sln file, and it worked, but on Android I cannot see neither the .csproj nor the .sln.
My repository structure:
root folder
src
main solution file
Core projects
customers' customizations folder
customer A folder
customer A .sln
customer A iOS, Android and Forms folders, each one with a .csproj file
...
After hours of blasphemies I've found the reason here: https://learn.microsoft.com/en-us/appcenter/build/xamarin/android/
For best performance, the analysis is currently limited to four
directory levels including the root of your repository.
My repository was too deep and .csproj files weren't reachable. I contacted Microsoft to ask if I had to change my repository structure and they said that yes, the only solution to quick solve was to remove a "layer", so I deleted the src folder moving all the content at the top level.
I am trying to follow the tutorial from the command line. I have generated the project and deployed the blank website then added a vs2012 project to the source folder maintaining the original heirarchy. I have edited the docfx.json file to include "src/.csproj" "src/.cs*" which i assume are searched recursively. The project was previously commented for use with SandCastle so there should be plenty to extract or generate metadata from. I currently have vs2012 msdn installed. My issue is that the metadata never builds and even when I'm using the sample seed project all the md files show up on the webhost but not the documentation from the source files.
There is no requirement to have the complete VS2017 installed, instead you can just install the build tools of VS2017. Download
Just start a developer prompt for VS2017 environment and do docfx from there, it should then be able to extract metadata. I had problems with VB.NET projects with docfx and older Visual Studio tooling for some reason.
I'm trying to release an iOS app built using Visual Studio 2015 Cordova Tools. I can deploy to the simulator and to my device just fine. But I can't find where the .ipa file is being created? My bin/iOS/release folder is empty even after cleaning solution, restarting, and rebuilding.
I have not tried with the latest versions, but I never found that I could build a release version from VS for iOS. I always went and opened the project on the Mac with XCode, using the project in the remote-build folder, tweaked the project settings (VS project never seems to allow multiple device orientations, I need to check on the others, choose the correct developer profile, and usually correct the bundle identifier). Then build and submit to app store from XCode as a normal iOS app.
Perhaps the latest versions are better on this, but I doubt you will find the app bundle in your VS solution folders, it would have to be on the Mac.
I have installed VS 2015 preview. I am trying to use the Hybrid App javascript template to create a new project. But I do not see any cordova.js in the project. Trying to learn following the sample given here [ http://msdn.microsoft.com/en-us/library/dn832630.aspx ] it refers to referencing the cordova.js file from root of the project. But there is no such file visible. Nor are there any instructions to explicitly import it. What am I missing?
The application does build and show up in Ripple OK. But i am trying to figure out where does cordova.js file reside.
Thanks.
Cordova.js is added at the build time, after you build the project, you can find the cordova.js at \bld\Ripple\Android\Debug or \bld\Debug\platforms\android\assets\www (in case of Android similarly for different platform).
Therefore when you add reference to cordova.js in index.html, it is picked at run time. That's the reason your app is running fine even though Cordova.js is not present in Visual Studio project directory.