WPSDK 7.1.1

1,788 views

Published on

An introduction to Windows Phone SDK 7.1.1 at WPUG (London - Feb 28)

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,788
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Codename not acknowledged by Microsoft
  • Other devices coming – particularly in new markets
  • NOT a go live license – DO NOT PUT ON PRODUCTION MACHINES. Can’t submit apps built against it - apparently
  • Must have 7.1 already installed
  • Can launch both at the same time.Must pass a parameter if starting from the command line
  • Not guaranteed to be future comptible
  • Create a property on something in global scope to make accessing this if need be
  • Yes, 2 emulators
  • Background audio is unaffected
  • Running under lock is still considered bad though
  • Same rules as per normal for saving memory – but must be more thorough
  • Won’t show up in marketplace for such devices
  • Hopefully future versions (beta & RTW) mean we won’t need to worry about this
  • Must remove the emulator first – apparently
  • WPSDK 7.1.1

    1. 1. WP SDK v 7.1.1 Allegedly AKA “Tango”
    2. 2. For lower spec devices Like the Lumia 610
    3. 3. 2 big differences All about resources 256MB
    4. 4. Get the SDKhttp://go.microsoft.com/fwlink/?LinkId=242824
    5. 5. Install the SDKRemember it’s a CTP
    6. 6. What’s installed Not a lot...
    7. 7. NOT a new OS
    8. 8. a new emulator
    9. 9. Detect low memory devicespublic bool Is256MbDevice(){ // Place call in a try block in case the user is not // running the most recent version of the Windows Phone OS // and this method call is not supported. try { var result = (long)DeviceExtendedProperties .GetValue("ApplicationWorkingSetLimit"); return result < 94371840L; } catch (ArgumentOutOfRangeException) { // The device has not received the OS update, // which means the device is a 512-MB device. return false; }}
    10. 10. Detect low memory devicesif (Environment.OSVersion.Version.Build >= 8731){ var result = (long)DeviceExtendedProperties .GetValue("ApplicationWorkingSetLimit"); return result < 94371840L; } else { return false; }
    11. 11. Only detect available memory once Save the results (IsolatedStorageSettings)
    12. 12. TestIn emulatorS, for now
    13. 13. No generic background agentsResource-intensive or periodic
    14. 14. Resource-intensive agent alternative Do it when the app is running
    15. 15. Periodic task agent alternative Push Notifications
    16. 16. Save memory Do less
    17. 17. Save memoryFewer, smaller resources
    18. 18. Save memoryApps, not controls
    19. 19. bewareLong lists, complex templates and animations, orientation changes
    20. 20. Opting outThey won’t even know you exist
    21. 21. Opting out<?xml version="1.0" encoding="utf-8"?><Deployment xmlns="http://schemas.microsoft.com/windowsphone/2009/d... <App xmlns="" ProductID="{b0cd6a33-0fde-43f0-ace3-86df62da <IconPath IsRelative="true" IsResource="false">ApplicationIcon.png</IconPath> <Capabilities> <Capability Name="ID_CAP_NETWORKING"/> ... </Capabilities> <Requirements> <Requirement Name="ID_REQ_MEMORY_90" /> </Requirements> ...
    22. 22. Uninstall the SDKemulator, then assemblies
    23. 23. Worth doing? Bahrain, Bulgaria, China, CostaRica, Croatia, Estonia, Iceland, Iraq, Israel, Kazakhstan, Latvia, Lithuania, Qatar, Romania, SaudiArabia, Slovakia, Slovenia, Thailand, Turkey, UAE, Ukraine, Venezuela and Vietnam

    ×