I purchased MonoTouch Professional but while debugging with the iPhone it gives an error: “No
Valid iPhone code signing keys found in keychain”.
The store page of Xamarin https://store.xamarin.com/ for the Professional version shows two important things however:
Deploy to your devices
Publish to app stores
I connected my device but I don’t know how to actually get my app running on the iPhone. Basically I have two questions:
How to configure the iPhone to debug with?
How to deploy app to the iPhone with MonoTouch (Professional License) version?
A third, seperate question is if it is necessary to enroll in the iOS Developer program from
Apple. If so, which is suitable for us because I don’t want to put my app on to the App
Store.
My app is only available to our clients for their internal use.
In fact, you should start from their iPhone tutorial,
http://docs.xamarin.com/ios/getting_started/Hello_iPhone#Deploying_to_the_Device
where deploying to device is mentioned. Also you need to learn from Apple resources, such as
http://www.intertech.com/Blog/post/Xcode-4-Deploying-Your-App-to-Your-Own-iPhone-iPad-iPod-touch.aspx
You have to enroll you to the iOS Developer Programm otherwise you cant deploy to devices. If you dont like to Publish to the App Store you also can deploy Apps with the TestFlight SDK. It´s a free SDK which allows you to Deploy Apps without the App Store.
Actually this is the tutorial you need to follow. There are lots of hidden buttons you wown't find by yourself
http://docs.xamarin.com/guides/ios/getting_started/device_provisioning/
Related
I wrote a UWP program and I used Restricted capability
broadFileSystemAccess
When I published this application I obtained permission from Microsoft, and its now in the Microsoft Store.
But when I tried to install it, it got an error:
My computer: Windows 10 1809
I have tried googling this, and writing to Microsoft, both without finding a positive result.
First, make sure the problem is actually only with your app by trying to install some other app if that will work.
If this happens only with your app, you should definitely contact Windows developer support for this issue. Select Contact us tab, then Windows 10 UWP app development and submit your incident. They should be able to help. You can also post the problem on the publishing Forum for greater visibility.
I'm trying to make a UWP App where users have to log in to my website (a hypothetical one as of now). I want the user to be able to run the App while logged into the website without having to download the App to their own computer. I want this website deployment to work in web browsers beyond IE. Is this even possible?
You'll be surprised to learn about UNO which is a platform promising UWP everywhere. You can run your UWP app inside a browser (using WebAssembly), Android, iOS, and of course natively as UWP on Windows 10 devices.
https://platform.uno/
Please be aware that as far as i know this is not production ready so you should expect issues, bugs, and weird behavior. Their gitter chat room is somewhat active and the team behind is responsive. But be warned.
I am looking to write a simple app which accepts input from an Xbox 360 controller. I am developing in C# and my current dev environment is a windows 10 machine.
I've attempted to install XNA studio 4.0, and got a system notification saying that it isn't supported. When I clicked on the notification for more info, I was redirected to a webpage which started a Windows Live Gaming installer download.
This seems to rule out XInput.
I thought my alternative was to use the Windows.Gaming.Input namespace, but it seems to be limited to metro apps.
I don't know what are my other alternatives.
What is the correct library for me to be using, and where do I download it from?
XINPUT will read the Xbox One controller with the drivers currently on Windows Update, but you will be unable to access the 'impulse trigger motors' using that API. For C# usage, look at SharpDX or SlimDX.
You can use Windows Runtime APIs from desktop apps including Windows.Gaming.Input. They key is you have to initialize WinRT with Windows::Foundation::Initialize.
See DirectX Tool Kit: Now with GamePads. If you were writing in C++, I'd also recommend looking at the DirectX Tool Kit GamePad class.
I have developed a Windows phone 8.1 app. Now I want to distribute it to others.
I have done Create App Packages in Visual Studio, and it passed all the certification tests. So I have the .appx file, but I am not able to install it in other Windows phones.
Its showing this error:
Can't install this company app: There is a problem with this company app. Contact your company's support person for help.
I have googled and found out that there is two ways of distributing the app:
1) Mobile Device Management Tool,
2) Side-Loading
and without having an enterprise-signing certificate from Symantec it is not possible to distribute the app.
Another option is to upload the app to the store, but I don't want to do it at this moment.
So is there any way to install the app in other windows phone?
In a simple way? I don't want any certificates. I just simply want to install the app in my friends phone. Like we can create and install .exe files easily.
There are a few ways to achieve this without getting the certificate required for sideloading.
Beta
First of all - you ask for the simplest way to distribute an app.
I assume that there might be updates in the future (and if only to fix this annoying little bug that might find or whatever). Then submitting it to the store as Beta app is really something you should consider; it won't be visible - it won't be accessible to anyone whom you haven't authorised to use the app. The certification process in Beta is quite fast, as it is merely a sanity check.
Regarding the cost of the dev account: it is quite cheap (https://msdn.microsoft.com/en-us/library/windows/apps/jj863494.aspx) and can even be free, for students and startups through the respective programs (DreamSpark, BizSpark). Also: no recurring fees, even if you're not a student anymore.
But the true benefit is that all you need to do is give the authorised testers the link to your app once it is published and then all the updates are handled through the store. No messy package distribution to the individual people, no notifications - testers will get the updates like for every other app. Long term, that would save you a lot of time and the testers a lot of hassle in preparing their device for being able to play your app, they do not need to developer unlock their phones.
Without Beta submission
If you want to just send them the app package,
they must (also) have a Microsoft account. If I recall correctly, they can have one developer unlocked device even without the dev registration (http://dev.windows.com/en-us/join)
they need the Windows Phone SDK, which comes as part of Visual Studio, which installs the required tools
connect their phone to the computer
to developer unlock their device, they have to run a tool called "Windows Phone Developer Registration" and sign in with their Microsoft account
to deploy the app, use the tool called "Application Deployment".
Everytime an update is distributed, they simply need to use the "Application Deployment" tool.
or use the command line :D
Unless your friend's phone is developer unlocked, you have to submit it to the app store.
Apologies for the noobish question, and I did try to search but couldn't find the right answer (or didn't search properly).
Currently have an app developed in a windows desktop environment because it gives us access to deeper features of the PC such as serial port comms etc. that the normal metro environment wouldn't allow. We're currently developing the UI based on metroUI so we can run it on an 8.1 touchscreen (metroUI looks good, gives us a touch-screen experience with PC features) but we have no intention of putting it on the marketplace.
Just wanted to confirm if this is in fact doable, and we can have this desktop application with a metro UI? Or is my noobishness meaning I'm overlooking some technical feasibility that makes it impossible?
This is doable with the Windows 8.1 Update (from April 2014). It's not supported before that since Windows Store apps were blocked from communicating with desktop processes.
The Windows 8.1 Update adds a feature "Brokered Windows Runtime Components" designed to allow side-loaded Windows Store apps to communicate with a desktop back-end. This will allow your Windows Store app UI to call the desktop component to access API that aren't available in the limited app package environment.
See Brokered Windows Runtime Components for side-loaded Windows Store apps for details.
See Try It Out: Sideload Windows Store Apps on TechNet for how to enable side-loading on your systems. See Windows 8.1 Update: Sideloading Enhancements for updates on how to enable a system for sideloading (no license required when on a domain, and significantly easier to get a sideloading license for non-domain joined systems).
The developer license system is designed for development and test purposes only. You really don't want to use it for production. Use the proper enterprise side-loading system instead.
From my understanding, the whole point here is to make it look like a Windows Store app. If you're app is a WPF one, you can already use Mahapps.metro.
You can create a Windows Store app without going to the store by Sideloading it. You create an app package first. The user has to right click the .ps1 file in that package to see the option Run with PowerShell and install it in a very old fashioned DOS like manor. It will only run when the user has a Microsoft Developer License and renew it every month. However, it is not allowed to keep using a Developer License of the end user to run a Store app. In the end, the system has to be domain bound to be allowed to run these apps, or you have to buy a Enterprise Sideloading key. These come in packages of 100 for $ 3000,- or you can unlock all PC's for 1 client for $ 100-.
It would be nicer if the specific pros of a Store program were available in a desktop environment but with W10 coming up I do expect a bit more integration and less restrictions.
Hope this answers your question.