i bumped into issue when I wanted to use EventHandlerList in Windows Phone application. Errro occured telling me it was not found even though msdn claims it is supposed to exist on WP platform. http://msdn.microsoft.com/pl-pl/library/system.componentmodel.eventhandlerlist%28v=vs.110%29.aspx Do you happen to know what I;m doing wrong?
The link you provided does not mention support of Windows Phone anywhere in the documentation.
Please be aware that Windows Phone 8 uses a subset of the .NET 4.5 framework, so not everything is present.
Related
Since submitting a Windows Phone 8.1 app alongside our Windows Phone 8 I've noticed some strange behaviour in the store regarding app version numbers. In my AppManifest and when I'm building packages for the store I set a version number say, 2.0.2.1.
The package uploads fine but when visible in the store and on the upload page the version number has changed to when I built the package, for example v2015.918.xxxxx = 18/9/2015. I guess this is fine as it will keep getting larger but I still rather show the actual version number.
Thanks to an automated Twitter account I've noticed it happening to other apps too: https://twitter.com/NewsCuriosityWP/status/646956803079700480
I'd love to know why this happening, a bug with the store maybe?
Here are some examples:
I had this problem too, I posted about it in the forums: https://social.msdn.microsoft.com/Forums/en-US/d2913ad6-6130-45b6-8a7f-086ff7f04cff/problem-with-version-number?forum=wpsubmit
Apparently it is working as intended ... but when I ported an app to Win10 UWP, it really messed up the version numbers and now I have to specify a version starting with 2015.... :-(
If you want to avoid this for new applications, you can prevent it from creating an app bundle, and then it should use the version number you specified.
Unfortunately, for already published app you cannot go back from app bundling
Hope this helps...
As stated in the doc, this method is not supported on WP8. But I tried it anyway and it works in the emulator. I dont have a test device right now, has anybody tried it already?
Expression.Compile was not supported in WP7, since it depended on Reflection.Emit which was not included in WP7. WP8 however now supports Expression.Compile. The Simple Injector IoC framework for instance, makes use of this internally and supports WP8 and Windows Store Apps.
I understood Silverlight was drop by MS.
I create my first app permitting to read RSS in WindowsPhone and I need to add a reference to System.ServiceModel.Syndication.dll. In the doc http://msdn.microsoft.com/en-us/library/windowsphone/develop/hh487167(v=vs.105).aspx, I need to find this lib in Microsoft SDKs/Silverlight/v4.0/Libraries/Client/.Why should I do it? Why I can't add directly a lib from the standard .net4?
Can you help me to understand.
[UPDATE]
When I add the lib from C:\Program Files (x86)\Microsoft SDKs\Silverlight\v4.0\Libraries\Client\
Visual Studio shows a windows "Adding reference to Windows Phone XNA assembly is safe. However adding reference to a silverlight assembly may lead to unexpexted application behavior. Do you want to continue.
So my assumption is this lib shoudn't be use but I don't find another way.
Maybe by add a ref from .Net 4 or 4.5.
Best regards,
Alexandre
The Windows Phone 7 SDK was built on top of Silverlight. For Windows Phone 8 this was changed so that there isn't a direct history with Silverlight but it was based on WinRT instead. Lots of functionality was made available to Silverlight controls to support backwards compatibility with apps written for 7.
Because WinRT is not compatible with classes written for the full version of the framework you cannot use these in your Windows Phone apps.
The warning you are getting is just a warning. It's telling you that your doing something that isn't an ideal and so you may have issues. Unfortunately there are no other versions of the SyndicationFeed object available to Windows Phone apps so you'll need to use this library if you want the functionality of SyndicationFeed without recreating it yourself. The good news is that there are no issue with using this class in your app. Just be sure to test carefully, on real devices, if you start to use other functionality from that assembly because, as the warning says: "there may be unexpected behaviour".
Using Microsoft Windows 7 and either Visual studio 2010 or 2012, how should I program for Windows Phone 8?
Assuming it is not possible, when does Microsoft plan to fix that?
Asked a different but related question, and got this answer, which if correct gives me the answer I was looking for.
You can't - you'll need Windows 8 64-bit to develop for Windows Phone 8, and additionally you'll want the Professional version of Windows 8 to leverage the emulator.
See http://www.microsoft.com/en-us/download/details.aspx?id=35471 for details.
I don't think the following is a recommended approach but I don't see any compelling reason for why that is so feel free to read on.
According to this answer it seems that you can make programs that are runnable on Windows Phone 8 (WP8) although it won't have all the features but probably most, and maybe the developer experience will not be the same. Also it does not seem to be an officially supported way ( I am not sure about that point ).
So it seems like you could use SDK 7.1 for example and update it to SDK 7.8. According to the System Requirements it runs on Windows 7. Keep in mind that I don't know if it is officially supported.
I am porting a Windows 8 Metro application to a Windows 8 Phone app.
While the Win 8 phone app compiles, there are many API's which throw the API not implemented exception at runtime.
Is there a way to identify all the API's that are not implemented in an existing source?
The only way I can think of doing is to identify all API's being used in my app and then check if that API is supported or not.
Thanks,
Avinash
MSDN will specify if a given API is not implemented.
It will have a section like this: (for example see this page which is a common example).
Remarks
Windows Phone 8
This API is not implemented and will throw an exception if called.
It's quite confusing as lower down the page says...
Minimum supported phone Windows Phone 8
... but that's misleading as you have found already.
I think tooltips from Intellisense may help you as well from within Visual Studio.