I wrote some apps in C#, Windows Phone 7 (2010 Express Edition). I use Win7. The build is ok, it succeeds. When I start debugging session, the WP emulator appears and disappears a couple of time and then the program ends with the error: "Object invoked has disconnected from its client". I googled the net, search in stackoverflow, but found nothing specific (I mean C# and WP 7).
Have anyone any idea ?
Thanks
The problem is that, your memory is too low, the minimum requirements for the Emulator to run is at least 1.5 GB but 2 GB is recommended. Try upgrading your RAM and it should work. :)
fro here:http://social.msdn.microsoft.com/Forums/en-US/wpdevelop/thread/d7dee3ab-cae9-4a5e-827d-3c86ffd6afd5/
Try Building your Solution, if solution is getting build successfully (As you said),
Then Press Ctrl + F5 And let allowed Windows Phone Emulator to get fully load,
Now just try to navigate you app, and the close Emulator, and then try with F5 (Debug). It work for me
(As It may be the problem with low memory.)
Related
I am having severe problems getting an app working in Retail Mode on the Xbox One.
The app works fine in Dev Mode, I have uploaded to the store and it passes certification fine but when the app is then installed via the store onto a Retail Xbox One it refuses to run.
Firstly it was crashing whilst on the splash screen, no error message just returning back to the Xbox homes screen, Due to now being in Retail mode I cannot connect a debugger to the app. I've setup my own exception handler to send errors to my backend server and it was crashing with the exception:
Cannot create instance of type 'Microsoft.Advertising.WinRT.UI.AdControl'
It's using the latest Microsoft.Services.Store.SDK and therefore Microsoft.Advertising SDK for XAML. I've took out the AdControl from MainPage.xaml and now we have a UI come up on screen! Not ideal as the ads are needed for monetization.
Unfortunately that's not the end of the problems, during the app initialisation it copies files from the Data folder of the solution to localstorage, for some reason it's now hanging on the following:
StorageFile anjFile = await localCacheFolder.GetFileAsync(App.AbilitiesFileName);
What's so different running apps on the Xbox in Retail Mode compared to Dev Mode? The app also functions fine on mobile and desktop so I know there shouldn't be any problems. The only way to try and find out what's causing problems is to comment out lines, or put placeholders in the app to change a debug textbox on screen to see what part of code is running and rebuild and submit to the store again, wait for certification and then redownload from the store to the Xbox, a very slow and time consuming task and I'm now up to Submission 12 of an app I'm getting very frustrated with!
Update: Seems like the AdControl issue started around 9th Feb and is affecting several apps on Xbox One and is possibly due to a framework update to the libraries involved. Not sure why it isn't affecting Dev Mode as well.
Thanks a lot for reporting this issue out on the forum and helping us with investigations. The root cause of the issue has been identified and fix has been rolled out. The framework update will take a couple of days to reach most devices as and when any new app or updated ad-enabled app gets updated on the Xbox device.
Dev Mode only: The issue doesn't affect Dev mode and only Retail mode since Retail mode actually is the most secure and most strict environment and requires that all binaries involved are signed and certified. If anything is missing, Retail mode is the only one which will surface the issue in this fashion - not loading the libraries.
Fix and roll out process: You could reach out to the users who reported problems for your app and ask them to re-install your app. The other option that you (as a developer) have is to push an update to your app (only version change) and push it to your users. This will get the framework updated on the end user devices and speed up the fix roll out. Those developers who had taken off the ad control, please put it back and push the update for your apps.
Please feel free to reach out to us (msft-aia-help#microsoft.com) in case of any issues or queries regarding this topic. Thanks for the patience and sorry for the inconvenience caused during this period.
-Vivek.
Seems like the AdControl issue started around 9th Feb and is affecting several apps on Xbox One and is possibly due to a framework update to the libraries involved. Not sure why it isn't affecting Dev Mode as well.
I have got a update from our engineering team, this issue has been fixed. But you may need to uninstall and reinstall any of the affected apps in your XBOX, after that it should work fine.
Please let me the result after you reinstall all the affected apps in your XBOX.
Thank you.
I developed a UWP music app in C# which use BackgroundMediaPlayer in Windows API.
Since I associated the app to the store, it doesn't play sound after the first app launch.
1st launch -> Everything is fine.
x launch after until computer restart => No sound (still playback
position tracking/play/pause works).
Does somebody have an explanation or a fix?
This is the answer from a Microsoft employee:
We have confirmed the root cause and we are getting this fixed. Sorry about that. The workaround is to change your "Package name" to be greater than 20 characters. Please let us know if that works for you.
When I associated my app with the store, my package name got under 20 character; wich was causing the bug.
I changed it to be more than 20 char and my app worked well again.
The problem is that any store association or app upload will set back the package name.
Microsoft told me the bug will be fixed. It was on October 1th 2015.
Check https://github.com/Microsoft/Windows-universal-samples/issues/141 for more info.
As far as I have seen, this is some bug introduced in Windows 10 RTM. At this point I would advise you to use alternative APIs (like MediaElement).
So using the following diagram:
You can see that the only time when anything breaks is when I use ClickOnce in Windows 10, however the notifications work perfectly fine if I run it directly from the exe. When I run it using ClickOnce using the console I can see the same methods get hit in the console but the notifications don't show up. I have tried to get this fixed for a very long time now with no avail.
The click once is deployed to a network share. The ClickOnce notifications work fine on Windows 8. I have absolutely no idea what could be causing this.
So got into discussion with someone I know at Microsoft and it looks like in the latest version (that he said should be released somewhere in November 2015) should contain the fix for this issue.
Waiting it out and hopefully the fix comes, if not I will contact him again and see how things are going as I would say this is a really bad problem.
In my home and work pc's and in one friend of mine's it runs just ok, but when i sent it to someone else it 'loads' for 10 seconds responseless, then there is an error:
alt text http://dl.dropbox.com/u/3045472/Sem%20t%C3%ADtulo-1.png
Since it works on at least four computers, i assume the program itself is just ok (same exact EXE).
What could be happening ?
info:
C#
.net 3.5
worked on Windows 7 32/64 bits,
windows XP and vista.
does some threading simple stuff, but
it doesn't even open the form, and it
doesn't open up running either, so
the functionality is irrelevant.
There are infinitely many possible answers. So I will give you the way to figure it out instead.
Add a handler for the event: AppDomain.CurrentDomain.UnhandledException of type UnhandledExceptionEventHandler.
You will be able to see the reason for the crash. It's probably best to write it out to a file somewhere anyway.
The first check is to make sure the .NET framework is already installed on the target machine, then make use of Brian's suggestion (which will not even work if the framework is not installed!).
I am developing a WPF application and have recently started testing it on a machine with Windows XP Tablet edition. The application runs Full screen. When the computer goes into standby while my application is still running, returning from standby causes the igxprd32 display driver to stop working. When this happens I get a "Windows - Display Driver Stopped Responding" message, the resolution drops, and the colors get all messed up.
Instead of waiting for the computer to go into standby on it's own I've also test manually putting it into standby via the start menu. Bring the computer out of standby after this usually results in Windows crashing with a blue screen.
This only seems to happen on Windows XP Tablet edition.
What is causing this and how can I fix it?
EDIT: Apparently what I was told was wrong. The machine actually is running XP Professional,
using the Mobile Intel 945 Chipset Family. I installed the latest drivers from the Intel website, this didn't fix the problem. I did find that if you google "igxprd32" you find there are many people who have problems with this driver.
This might be too obvious but, have you checked for a more up-to-date driver? I've seen this as the answer to similar problems on the MSDN WPF forum.