How I can share my windows phone 7 app for internal sharing. Like I created on app and I want to share with company stakeholders. Or second case is I made my app for some private company and they don't want to share or publish on marketplace. They just want to use this app for within the company and organization.
Any Idea how we can share this app.
I think you can do it with the use of Sharepoint.
Check this out: http://msdn.microsoft.com/en-us/sharepointandwindowsphone7trainingcourse_creatingprivateapplicationslab.aspx
I've did some more research, there should be something called a 'enterprise marketplace'.
You still publish you app to the normal marketplace, but only people with the direct (Zune) link can download the app. It is not to be found in the public marketplace.
With the introduction of Windows Phone 8 there will be a possibility to create an 'Company hub'
IIRC when you beta test your application (provided you have a AppHub membership) you can specify a number of private testers for your application, although I think this is limited to around 10. I don't think you can publish a private application.
Source
Related
I work at a company in which we need to restrict administrative access but allow the install of select programs with an easy way to update the list of programs. We want to develop a sort of appstore for everyone's PC where they can access the list of allowed apps and install what they need. We want to write this in C#.
To do this i have initially developed a windows service that starts as a localhost and runs at boot time giving it admin powers. I than use an application which talks to the windows service via a service hosted by the windows service. Long story short its told what app the user wants from the list and the list provides the file path for the application stored on a private repository.
This is a sort of very very early attempt at this and security is in mind and will be added once the concept functions.
Now onto the problem were having.... when we launch the installer using our service the installer window never launches in the desktop for the user to configure the options that could be in an installer. This of course poses a problem for a lot of our installers. After some quick research i understand why this happens due to what level the services run in the operating system and their inability to access the desktop.
My question is..... is there a way to solve this problem? a way to have a service launch at bootime and launch installers as an administrator on the users desktop? or is this too messy and creates too many issues? is there a way to do this with a console app or WPF?
Thanks in advance!
Indeed like what you found about windows services, I don't think this whole flow can work as a service. There seems to have some workarounds though, according to this thread: How can I run an EXE program from a Windows Service using C#?
If it's an app-store where users can choose what to install, maybe an application is all that's needed. Like you said:
I than use an application which talks to the windows service via a service hosted by the windows service. Long story short its told what app the user wants from the list and the list provides the file path for the application stored on a private repository.
Seems like an application can handle all the works here already.
I have created an Windows 8 store application for a small business using visual studios 2012, C# and xaml. The problem I am having is when I side load the application it requires a developer license every 30 days which the company is not happy with. The company do not want the application made available to the public hence my hesitation to put the application on windows store. So as side loading does not seem acceptable are there any suggestions on how to make an application private (only downloadable by people I choose) in windows store?
You can perform sideloading without developer licence, but Enterprise or Professional version of Windows is required.
System Center allows you to deploy private app to the company managed devices. Windows Intune allows you to create private Company App Hub
There is promise to create Windows Store for businesses, where apps will be available only for company employess, or contractors. Azure Active Directory accounts will be required. http://www.techradar.com/news/software/business-software/microsoft-will-launch-windows-store-for-business-with-windows-10-1292471
Go for Windows store. On the process of creating your app in the store you can select several availability of your app.
1. Make app available publicly
2. Restrict to certain countries
3. Only the people you allow can download the app (people you chose must have a live account)
4. Make the app visible via a URL. (People who had the URL can access the app)
5. Use promotional code. (People who have the code can access the app)
Only drawback is some of these options will only work if the end users are using Windows 10.
Let me know if you require more info. I've done this before.
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.
I want to start another App or Program from my Windows Store App. For example my App is showing emails, so if someone clicks on such an email Outlook should open. Is this possible in an "App-Sandbox"?
It is not possible to just launch an arbitrary application, but with custom protocol activation you can launch an app that handles that protocol and if it is not installed - the OS will ask the user to install it. It means that if you can define a custom protocol in your app - you can launch it from another app with this protocol assuming no other app registers to handle it. An example of that is any XBOX Live app - if you check their manifest files - they all handle custom protocols.
If your specific question is about launching a specific app by name or location then no, this is not possible, but if you know a protocol handled by the app you want to launch - you can try using that - just bear in mind that there might be other apps that handle that protocol.
Short answer: no, it's not possible.
You can open files with their associated application but not spawn any arbitrary external process.
As #mitch-wheat pointed out, that's why it's called a sandbox.
Check out this sample
The sample is for Windows 8.1 but I think will work for Windows 8 as well.