Help to understand what happens when you update the application with a background agent...
I have application for WP8 with background agent. User install
app from store, run app and run background agent.
In new version of app I'm modify code of background agent, publish
new version to store.
User upgrade app from store, but not run main application.
What happens in this case?
On the device, there is a new version of the application, but not until the background agent was restarted from the new version of the main application, in remembrance remains running and running an old copy of the background agent?
That is, the application renewed, but still works a background agent from the old version of the application?
Found in testing.
After the application is updated the next time the agent starts a new instance of the agent of the background of the new version of the application.
Related
I have an application I'm working on. It has a DCOM component. When accessing it from another server the application starts and responds fine.
However, it starts in the background. This is not the behavor I want. I want it to start normally.
I'm porting the application from XP to Windows 10. In XP, it does not have this behavour.
How can I force the application to start in the foreground?
Is there any way to detect previous version of the application after update?
Problematic scenario:
User installs an application but never launch it. After some time application is updated automatically or via Store application. Now user launch the application and how to check if update happend and what version was previously installed?
There is no problem if user launch the application before update. I could write something to Isloated Storage which survive update. But what about scenrio described above?
Is there a way to get current foreground application, by some background process or application running in background?
I would like to make a history of user's activity. In Android we can use package manager and get running applications. Is there a similar approach in Windows Phone 8?
No. there is no any API or any other technique available to do that as of now in Windows Phone.
I am in the finishing staging of creating my first Window Phone 8 application. I am using MVVMCross as the MVVM framework for the application. The application is running great in debug mode on both the simulator and my connected phone. The issue I am having is the application will not run on my phone unless it's attached via debugging. When I click on the application on the phone it simply flashes but never launches the application.
Some additional information after using Crittercism to catch the exception:
0 at Cirrious.CrossCore.Mvx.ResolveTService
1 at Mobile.Contacts.Phone.App.b__0()
After further review I realized that I had the following setup code inside
if (System.Diagnostics.Debugger.IsAttached)
var setup = new Setup(RootFrame);
setup.Initialize();
I started working on windows-8 this morning and I am surprised that installed app not displayed in the emulator which I installed in the morning. To be clear.
1. I created the new project called Test1 using visual studio Express 2012.
2. I installed on the emulator.
3. I close the emulator completely.
4. After an hour I created Test2 using visual studio Express 2012.
But i am not able to find the Test1 project in windows-8 phone emulator.
But when i work on iPhone and android the apps will be available if i recreate the emulator.
What could be wrong?. Do I need to change any settings?
the emulator does not persist app installs to the base image. (this was true with WP7x emulators). I don't remember seeing anything that tells me it has changed.
Emulator shutdown + start == fresh new emulator. Only time it persists your app etc is when you change settings like display language etc and emulator initiates a restart.