3.94 score from hupso.pl for:
tomverhoeff.nl



HTML Content


Titletom verhoeff - windows (phone/8) development and more....

Length: 57, Words: 8
Description my blog as a windows phone development mvp | partner @eveohnl | speaker | blogger | #wp7nl | #wpdev | #win8dev | gadgets | student #tudelft

Length: 139, Words: 20
Keywords tom, verhoeff, microsoft, student, partner, computer, science, student, delft, eveoh, blackboard, mvp, most valuable professional
Robots
Charset UTF-8
Og Meta - Title pusty
Og Meta - Description pusty
Og Meta - Site name pusty
Tytuł powinien zawierać pomiędzy 10 a 70 znaków (ze spacjami), a mniej niż 12 słów w długości.
Meta opis powinien zawierać pomiędzy 50 a 160 znaków (łącznie ze spacjami), a mniej niż 24 słów w długości.
Kodowanie znaków powinny być określone , UTF-8 jest chyba najlepszy zestaw znaków, aby przejść z powodu UTF-8 jest bardziej międzynarodowy kodowaniem.
Otwarte obiekty wykresu powinny być obecne w stronie internetowej (więcej informacji na temat protokołu OpenGraph: http://ogp.me/)

SEO Content

Words/Characters 3459
Text/HTML 39.44 %
Headings H1 18
H2 2
H3 4
H4 0
H5 0
H6 0
H1
windows 8.1 semanticzoom object crashes app with a win32 exception when setting the visibility to collapsed
windows phone week is coming!
windows phone app studio – now’s the time to build your first app!
so what is app studio?
what do i need to get started?
next steps?
breaking down the google maps – windows phone issue
google maps on windows phone with an android useragent
playing around with google chrome
another experiment
 so what does this mean?
do we care?
work in progress
wp7 review reader now supports 54 marketplaces
wp7 app analytics using mtiks in just 5 minutes
making money with windows phone applications at techdays 2012
forcing capability detection in a windows phone application
marketplace fails to detect capabilities, causes crash
H2
cause
solution
H3
detection process
detection rules
forcing detection
conclusion
H4
H5
H6
strong
update: after the whole uproar caused by this and other posts around the web google decided to revert back to the old situation. i hope it also showed google that a lot of windows phone users do like google’s services and that they should see if improving the whole experience is possible. turns out they’re not that evil in this case after all. head over to the verge for more details.
i got redirected away.
reply
retweet
favorite
microphone
camera
photocamera
videocamera
update
if it’s referencing:
then add:
1
b
i
em update: after the whole uproar caused by this and other posts around the web google decided to revert back to the old situation. i hope it also showed google that a lot of windows phone users do like google’s services and that they should see if improving the whole experience is possible. turns out they’re not that evil in this case after all. head over to the verge for more details.
i got redirected away.
reply
retweet
favorite
microphone
camera
photocamera
videocamera
update
if it’s referencing:
then add:
1
Bolds strong 13
b 0
i 0
em 13
Zawartość strony internetowej powinno zawierać więcej niż 250 słów, z stopa tekst / kod jest wyższy niż 20%.
Pozycji używać znaczników (h1, h2, h3, ...), aby określić temat sekcji lub ustępów na stronie, ale zwykle, użyj mniej niż 6 dla każdego tagu pozycje zachować swoją stronę zwięzły.
Styl używać silnych i kursywy znaczniki podkreślić swoje słowa kluczowe swojej stronie, ale nie nadużywać (mniej niż 16 silnych tagi i 16 znaczników kursywy)

Statystyki strony

twitter:title pusty
twitter:description pusty
google+ itemprop=name pusty
Pliki zewnętrzne 35
Pliki CSS 21
Pliki javascript 14
Plik należy zmniejszyć całkowite odwołanie plików (CSS + JavaScript) do 7-8 maksymalnie.

Linki wewnętrzne i zewnętrzne

Linki 121
Linki wewnętrzne 1
Linki zewnętrzne 120
Linki bez atrybutu Title 81
Linki z atrybutem NOFOLLOW 0
Linki - Użyj atrybutu tytuł dla każdego łącza. Nofollow link jest link, który nie pozwala wyszukiwarkom boty zrealizują są odnośniki no follow. Należy zwracać uwagę na ich użytkowania

Linki wewnętrzne

#page

Linki zewnętrzne

tom verhoeff http://blog.tomverhoeff.nl
home http://blog.tomverhoeff.nl
eveoh http://blog.tomverhoeff.nl/category/eveoh/
windows 8 http://blog.tomverhoeff.nl/category/win8/
windows phone http://blog.tomverhoeff.nl/category/wpdev-2/
about http://blog.tomverhoeff.nl/about/
contact http://blog.tomverhoeff.nl/contact/
windows 8.1 semanticzoom object crashes app with a win32 exception when setting the visibility to collapsed http://blog.tomverhoeff.nl/2013/10/21/windows-8-1-app-crashes-with-a-win32-exception-when-setting-the-visibility-to-collapsed/
tom verhoeff http://blog.tomverhoeff.nl/author/tomverhoeff/
windows 8 http://blog.tomverhoeff.nl/category/win8/
windows sizes and scaling options http://msdn.microsoft.com/en-us/library/windows/apps/hh465349.aspx#support_different_screen_sizes
this msdn page http://msdn.microsoft.com/en-us/library/windows/apps/dn297195.aspx
continue reading http://blog.tomverhoeff.nl/2013/10/21/windows-8-1-app-crashes-with-a-win32-exception-when-setting-the-visibility-to-collapsed/
27 comments http://blog.tomverhoeff.nl/2013/10/21/windows-8-1-app-crashes-with-a-win32-exception-when-setting-the-visibility-to-collapsed/#comments
windows phone week is coming! http://blog.tomverhoeff.nl/2013/09/28/windows-phone-week-is-coming/
tom verhoeff http://blog.tomverhoeff.nl/author/tomverhoeff/
windows phone http://blog.tomverhoeff.nl/category/wpdev-2/
joost http://twitter.com/localjoost
matteo http://twitter.com/qmatteoq
rodolpho https://twitter.com/rodocarmo
windows phone developer blog http://blogs.windows.com/windows_phone/b/wpdev/archive/2013/09/27/join-local-community-driven-events-windows-phone-developer-week.aspx
windows phone week website https://wpcommunityweek.eventday.com/
twitter http://twitter.com/winphoneweek
facebook https://www.facebook.com/winphoneweek
- http://blog.tomverhoeff.nl/wp-content/uploads/2013/09/1146493_607943152591764_1569401329_n.png
continue reading http://blog.tomverhoeff.nl/2013/09/28/windows-phone-week-is-coming/
4 comments http://blog.tomverhoeff.nl/2013/09/28/windows-phone-week-is-coming/#comments
windows phone app studio – now’s the time to build your first app! http://blog.tomverhoeff.nl/2013/08/06/windows-phone-app-studio-nows-the-time-to-build-your-first-app/
tom verhoeff http://blog.tomverhoeff.nl/author/tomverhoeff/
windows phone http://blog.tomverhoeff.nl/category/wpdev-2/
windows phone app studio http://apps.windowsstore.com/
http://apps.windowsstore.com http://apps.windowsstore.com/
recent blogposts on the official windows phone developer blog http://blogs.windows.com/windows_phone/b/wpdev/
windows phone app studio forums http://social.msdn.microsoft.com/forums/wpapps/en-us/home?forum=wpappstudio
windows phone app studio uservoice http://wpdev.uservoice.com/forums/216486
continue reading http://blog.tomverhoeff.nl/2013/08/06/windows-phone-app-studio-nows-the-time-to-build-your-first-app/
10 comments http://blog.tomverhoeff.nl/2013/08/06/windows-phone-app-studio-nows-the-time-to-build-your-first-app/#comments
breaking down the google maps – windows phone issue http://blog.tomverhoeff.nl/2013/01/05/breaking-down-the-google-maps-windows-phone-issue/
tom verhoeff http://blog.tomverhoeff.nl/author/tomverhoeff/
windows phone http://blog.tomverhoeff.nl/category/wpdev-2/
the verge for more details. http://www.theverge.com/2013/1/5/3840620/google-bringing-maps-back-to-windows-phone
reports started showing http://www.theverge.com/2013/1/4/3836510/windows-phone-8-users-unable-to-access-google-maps
fiddler http://www.fiddler2.com/fiddler2/
removing activesync support for gmail http://www.theverge.com/2012/12/14/3768274/google-gmail-activesync-windows-phone
still blocking a fully featured youtube app for windows phone http://www.theverge.com/2013/1/2/3828274/microsoft-claims-google-blocking-windows-phone-youtube-app
thenextweb also realized http://www.theverge.com/2012/12/14/3768274/google-gmail-activesync-windows-phone
gmaps http://www.windowsphone.com/s?appid=7b8bedd5-4368-e011-81d2-78e7d1fa76f8
continue reading http://blog.tomverhoeff.nl/2013/01/05/breaking-down-the-google-maps-windows-phone-issue/
98 comments http://blog.tomverhoeff.nl/2013/01/05/breaking-down-the-google-maps-windows-phone-issue/#comments
work in progress http://blog.tomverhoeff.nl/2012/10/21/work-in-progress/
tom verhoeff http://blog.tomverhoeff.nl/author/tomverhoeff/
wp7 http://blog.tomverhoeff.nl/category/wpdev-2/wp7/
follow me on twitter http://www.twitter.com/tomverhoeff
continue reading http://blog.tomverhoeff.nl/2012/10/21/work-in-progress/
2 comments http://blog.tomverhoeff.nl/2012/10/21/work-in-progress/#comments
wp7 review reader now supports 54 marketplaces http://blog.tomverhoeff.nl/2012/03/29/wp7-review-reader-now-supports-54-marketplaces/
tom verhoeff http://blog.tomverhoeff.nl/author/tomverhoeff/
msp http://blog.tomverhoeff.nl/category/msp/
wp7 http://blog.tomverhoeff.nl/category/wpdev-2/wp7/
announced http://windowsteamblog.com/windows_phone/b/windowsphone/archive/2012/03/28/marketplace-arrives-in-13-new-countries.aspx
wp7 review reader http://wp7reviews.tomverhoeff.com/
previous posts on this subject http://blog.tomverhoeff.nl/tag/wp7rr/
twitter http://www.twitter.com/tomverhoeff
continue reading http://blog.tomverhoeff.nl/2012/03/29/wp7-review-reader-now-supports-54-marketplaces/
2 comments http://blog.tomverhoeff.nl/2012/03/29/wp7-review-reader-now-supports-54-marketplaces/#comments
wp7 app analytics using mtiks in just 5 minutes http://blog.tomverhoeff.nl/2012/03/02/wp7-app-analytics-using-mtiks-in-just-5-minutes/
tom verhoeff http://blog.tomverhoeff.nl/author/tomverhoeff/
msp http://blog.tomverhoeff.nl/category/msp/
wp7 http://blog.tomverhoeff.nl/category/wpdev-2/wp7/
this post http://blog.tomverhoeff.nl/?p=732
- http://blog.tomverhoeff.nl/wp-content/uploads/2012/03/mtiks1.png
google analytics (using msaf) http://msaf.codeplex.com/
flurry http://www.flurry.com/
preemptive runtime intelligence https://runtimeintelligence.com
mtiks http://mtiks.com/
continue reading http://blog.tomverhoeff.nl/2012/03/02/wp7-app-analytics-using-mtiks-in-just-5-minutes/
6 comments http://blog.tomverhoeff.nl/2012/03/02/wp7-app-analytics-using-mtiks-in-just-5-minutes/#comments
making money with windows phone applications at techdays 2012 http://blog.tomverhoeff.nl/2012/02/24/making-money-with-windows-phone-applications-at-techdays-2012/
tom verhoeff http://blog.tomverhoeff.nl/author/tomverhoeff/
msp http://blog.tomverhoeff.nl/category/msp/
wp7 http://blog.tomverhoeff.nl/category/wpdev-2/wp7/
choosing the right name/logo/description http://blog.tomverhoeff.nl/2011/05/20/things-to-consider-before-submitting-your-wp7-app/
trial api http://blog.tomverhoeff.nl/2010/12/07/implementing-and-debugging-trial-mode-in-a-wp7-app/
analytics (using mtiks) http://blog.tomverhoeff.nl/2012/03/02/wp7-app-analytics-using-mtiks-in-just-5-minutes/
channel9 http://channel9.msdn.com/events/techdays/techdays-2012-the-netherlands/2263
contact form http://blog.tomverhoeff.nl/contact/
twitter http://www.twitter.com/tomverhoeff
continue reading http://blog.tomverhoeff.nl/2012/02/24/making-money-with-windows-phone-applications-at-techdays-2012/
4 comments http://blog.tomverhoeff.nl/2012/02/24/making-money-with-windows-phone-applications-at-techdays-2012/#comments
forcing capability detection in a windows phone application http://blog.tomverhoeff.nl/2011/12/30/forcing-capability-detection-in-a-windows-phone-application/
tom verhoeff http://blog.tomverhoeff.nl/author/tomverhoeff/
msp http://blog.tomverhoeff.nl/category/msp/
wp7 http://blog.tomverhoeff.nl/category/wpdev-2/wp7/
#wp7dev http://twitter.com/search?q=%23wp7dev
http://t.co/pu3psv62 http://t.co/pu3psv62
#wpdev http://twitter.com/search?q=%23wpdev
30/12/2011 18:08 http://twitter.com/#!/lancewmccarthy/status/152798255904858112
tweetdeck http://www.tweetdeck.com
reply https://twitter.com/intent/tweet?in_reply_to=152798255904858112
retweet https://twitter.com/intent/retweet?tweet_id=152798255904858112
favorite https://twitter.com/intent/favorite?tweet_id=152798255904858112
- http://twitter.com/intent/user?screen_name=lancewmccarthy
@lancewmccarthy http://twitter.com/intent/user?screen_name=lancewmccarthy
@lancewmccarthy https://twitter.com/#!/lancewmccarthy/status/152806302890987520
- http://blog.tomverhoeff.nl/wp-content/uploads/2011/12/capabilities.png
tweet http://www.twitter.com/tomverhoeff
continue reading http://blog.tomverhoeff.nl/2011/12/30/forcing-capability-detection-in-a-windows-phone-application/
4 comments http://blog.tomverhoeff.nl/2011/12/30/forcing-capability-detection-in-a-windows-phone-application/#comments
marketplace fails to detect capabilities, causes crash http://blog.tomverhoeff.nl/2011/12/23/marketplace-fails-to-detect-capabilities/
tom verhoeff http://blog.tomverhoeff.nl/author/tomverhoeff/
msp http://blog.tomverhoeff.nl/category/msp/
wp7 http://blog.tomverhoeff.nl/category/wpdev-2/wp7/
continue reading http://blog.tomverhoeff.nl/2011/12/23/marketplace-fails-to-detect-capabilities/
3 comments http://blog.tomverhoeff.nl/2011/12/23/marketplace-fails-to-detect-capabilities/#comments
2 http://blog.tomverhoeff.nl/page/2/
3 http://blog.tomverhoeff.nl/page/3/
4 http://blog.tomverhoeff.nl/page/4/
» http://blog.tomverhoeff.nl/page/2/
last http://blog.tomverhoeff.nl/page/5/
warp theme framework http://www.yootheme.com

Zdjęcia

Zdjęcia 5
Zdjęcia bez atrybutu ALT 2
Zdjęcia bez atrybutu TITLE 3
Korzystanie Obraz ALT i TITLE atrybutu dla każdego obrazu.

Zdjęcia bez atrybutu TITLE

http://blog.tomverhoeff.nl/wp-content/uploads/2013/09/1146493_607943152591764_1569401329_n.png
http://blog.tomverhoeff.nl/wp-content/plugins/twitter-blackbird-pie//images/bird.png
http://a2.twimg.com/profile_images/1593647845/twitterpic_normal.jpg

Zdjęcia bez atrybutu ALT

http://blog.tomverhoeff.nl/wp-content/plugins/twitter-blackbird-pie//images/bird.png
http://a2.twimg.com/profile_images/1593647845/twitterpic_normal.jpg

Ranking:


Alexa Traffic
Daily Global Rank Trend
Daily Reach (Percent)









Majestic SEO











Text on page:

tom verhoeff homeeveohwindows 8windows phoneaboutcontact 21 oct 2013 windows 8.1 semanticzoom object crashes app with a win32 exception when setting the visibility to collapsed written by tom verhoeff. posted in windows 8 while working on retargeting one of our existing windows 8 apps to windows 8.1 i ran into an issue with the semanticzoom object. because of the new windows sizes and scaling options in windows 8.1 it’s recommend to handle the page’s sizechanged event to switch to your various viewstates. please see this msdn page for instructions on how to implement this. this is the piece of code that handles visualstatetransitions: void groupeditemspage_sizechanged(object sender, sizechangedeventargs e) { if (e.newsize.width < 500) { visualstatemanager.gotostate(this, "minimallayout", true); } else if (e.newsize.width < e.newsize.height) { visualstatemanager.gotostate(this, "portraitlayout", true); } else { visualstatemanager.gotostate(this, "defaultlayout", true); } } unfortunately there appears to a bug in the semanticzoom object that causes a win32-exception and crash when one of those state transitions involves collapsing a semanticzoom object. this only happens when executing the transition within the sizechanged event-handler. after messing around with this issue for a bit i figured out a simple workaround. scheduling the visualstate transition through the ui-thread’s dispatcher performs the transition without raising any exceptions. if your “minimallayout” state contains said transition this code would work: async void groupeditemspage_sizechanged(object sender, sizechangedeventargs e) { if (e.newsize.width < 500) { var dispatcher = windows.ui.core.corewindow.getforcurrentthread().dispatcher; await dispatcher.runasync(windows.ui.core.coredispatcherpriority.normal, () => visualstatemanager.gotostate(this, "minimallayout", true)); } else if (e.newsize.width < e.newsize.height) { visualstatemanager.gotostate(this, "portraitlayout", true); } else { visualstatemanager.gotostate(this, "defaultlayout", true); } } continue reading 27 comments 28 sep 2013 windows phone week is coming! written by tom verhoeff. posted in windows phone just a quick note on the windows phone week event that’s kicking off in two days. a while back my windows phone dev mvp friends joost, matteo and rodolpho had the crazy idea of organizing some wpdev events around the world together. the event started growing and with the first event kicking of this monday we have a total of 19 events scheduled around the world. read the full story on the windows phone developer blog and check out all the events on the windows phone week website. i’m helping out the team with social media channels on twitter and facebook. tweeting about one of the events? be sure to use the hashtag #wpdevweek continue reading 4 comments 06 aug 2013 windows phone app studio – now’s the time to build your first app! written by tom verhoeff. posted in windows phone microsoft has just released windows phone app studio, a great tool that will help you build your first windows phone app in virtually no time. after taking it for a short testdrive i’m sure it will help everyone (even without programming knowledge) to build an app. ever had that feeling you wanted to build something? but you didn’t have enough time? or you don’t think you have the required skills? be sure to give app studio a try! it will help you produce your first app and you’ll learn a lot while you are at it. are you a developer? app studio could still save you loads of time, time that you can invest in building the awesome features that’ll make your app stand out. so what is app studio? app studio is a tool that will help you build a windows phone app in 4 simple steps: have an idea add content choose style use it! as a developer that loves to write some code you can add in step 5: “take it to the next level” app studio is a great way to get started building your own apps. if you don’t have to knowledge or time to develop a full app it will help you put it together. by grabbing the source of your newly built app you’ll be able to extend the functionality by adding your own features. this will help you understand what it takes to develop a full app and will make your app stand out in the marketplace. what do i need to get started? app studio is a fully web based tool, all you need to get started is a microsoft account. it would also make sense to have a windows phone to actually test your apps, but it isn’t strictly required. that’s basically all you need, now head over to http://apps.windowsstore.com to get started. there’s some resources to help you get started: recent blogposts on the official windows phone developer blog windows phone app studio forums windows phone app studio uservoice (if you have feedback) next steps? this post marks the start of a series of blogposts that will help you make the most out of your app studio experience. give it a try yourself and come back over the course of the next days for more tutorials. continue reading 10 comments 05 jan 2013 breaking down the google maps – windows phone issue written by tom verhoeff. posted in windows phone update: after the whole uproar caused by this and other posts around the web google decided to revert back to the old situation. i hope it also showed google that a lot of windows phone users do like google’s services and that they should see if improving the whole experience is possible. turns out they’re not that evil in this case after all. head over to the verge for more details. the original article was posted when google maps was inaccessible to windows phone users. yesterday reports started showing up that google is redirecting all windows phone users away from the mobile google maps website. there’s been quite some discussion on why google is doing this. are they doing it to mock windows phone users? or is ie10 mobile just not capable of rendering google maps the right way? here’s google’s official statement: the mobile web version of google maps is optimized for webkit browsers such as chrome and safari. however, since internet explorer is not a webkit browser, windows phone devices are not able to access google maps for the mobile web. i used google maps before occasionally (nokia maps for windows phone does it’s job, so you won’t need google anyway) and although the experience wasn’t perfect it definitely worked. microsoft responded to google’s statement with a very simple and clear statement: internet explorer in windows phone 8 and windows 8 use the same rendering engine i ran a few experiments to see what is really going on here. google maps on windows phone with an android useragent google is detecting windows phones by their user agent. by running my connection through a proxy and using a script to present a different useragent i tried to open google maps. not surprisingly it just worked. i used this useragent: mozilla/5.0 (linux; u; android 2.3.4; fr-fr; htc desire build/grj22) applewebkit/533.1 (khtml, like gecko) version/4.0 mobile safari/533.1 want to try this yourself? use fiddler! through rules -> customize rules you get to a textfile specifying scripts dat fiddler runs when processing network calls. adding osession.orequest[“user-agent”]=”mozilla/5.0 (linux; u; android 2.3.4; fr-fr; htc desire build/grj22) applewebkit/533.1 (khtml, like gecko) version/4.0 mobile safari/533.1″; to the onbeforerequest part changes the useragent on all webrequests. playing around with google chrome on twitter some users reported that google is just detecting the string “windows phone” disregarding any other information. this was obviously worth a try, so i moved to my desktop browser (chrome). this is the useragent of google chrome on my desktop: mozilla/5.0 (windows nt 6.2; wow64) applewebkit/537.11 (khtml, like gecko) chrome/23.0.1271.97 safari/537.11 to give it a shot i added “windows phone” to this string: mozilla/5.0 (windows nt 6.2; wow64) applewebkit/537.11 (khtml, like gecko) chrome/23.0.1271.97 safari/537.11 windows phone now navigating to google maps again i got redirected away. another experiment matthias shapiro uploaded a video to youtube where he proves the same point. using a webview within a windows phone app you can manually specify a useragent. here’s what happened:  so what does this mean? google’s own statement suggests that not supporting webkit is the problem here, however the experiments mentioned show that there doesn’t appear to be any real problems. combine this fact with some other recent development like google removing activesync support for gmail users and google still blocking a fully featured youtube app for windows phone. it just shows that google is just mocking windows phone and its users, something thenextweb also realized. it’s just another chapter in the ecosystem war. it’s also worth noting that 3rd party google maps apps for windows phone like gmaps still work. do we care? the real victims here are the regular windows phone users. if they happen to use gmail they want to get it on their phones, if they happen to need google maps they just want to access it. fortunately gmail still works for current users and i’m counting on microsoft to provide a decent solution in the future. for the google maps part i actually really don’t care. nokia maps for windows phone is native, it has a great experience and offers practically all the features that i would use with google maps (maps, traffic info, local search, etc.). but for a company like google that says: google’s mission is to organize the world’s information and make it universally accessible and useful. all those moves appear to be a bit sad. google was always praised for it’s openness, but they’re acting more and more like microsoft was back in the 90s (and that’s not a good thing) continue reading 98 comments 21 oct 2012 work in progress written by tom verhoeff. posted in wp7 some of you might have noticed that i’ve gone a little silent on this blog. no worries, i’ll be back writing on windows phone and windows 8 soon, but for now have to focus on founding my new company methylium. in the meantime you can follow me on twitter to stay up to date. continue reading 2 comments 29 mar 2012 wp7 review reader now supports 54 marketplaces written by tom verhoeff. posted in msp, wp7 yesterday microsoft announced that marketplaces in 13 new countries were opening up. today i am happy to announce that support for those new marketplaces has been added to the wp7 review reader tool. the tool keeps helping out developers to get easy access to their reviews by simply entering the appid and bookmarking the url. for more information on the review reader, please see the previous posts on this subject. some of you might have also noticed that i’ve gone a little silent on my blog and twitter recently. i’m trying to catch up, but there are some important wp7 projects that require my full attention at the moment. i will be releasing some brand new windows phone apps targeted at the dutch market in the coming weeks. stay tuned for more news on that part. continue reading 2 comments 02 mar 2012 wp7 app analytics using mtiks in just 5 minutes written by tom verhoeff. posted in msp, wp7 this post is part of a follow up series on my techdays session on “making money with windows phone applications”. see this post for more info and an index. why build in analytics into your mobile application? this subject has been covered in many blog posts an their conclusion is usually the same. first of all you just want to know how many people use your app and how often they do it. but knowing (at least to some extent) what part of your app is used the most and what epic feature is never found by users is also valuable. as a developer there’s plenty of frameworks to choose from: google analytics (using msaf) flurry preemptive runtime intelligence (less interesting since their deal with ms ended) mtiks in this post i will cover mtiks, since it’s just too easy to get started. you’ll be able to instrument your app in literally just a few minutes. continue reading 6 comments 24 feb 2012 making money with windows phone applications at techdays 2012 written by tom verhoeff. posted in msp, wp7 last week the yearly event for dutch developers on the microsoft platform took place in the hague. just like last year i did a session on “making money with windows phone applications”. the session is targeted at an audience that is new to the platform. it covers all the subjects that are relevant for earning some money except the building of the app itself (there’s other sessions for that). although the content is pretty basic it does give interesting insights in opportunities to make the most out of your apps. since people keep asking me about the different subjects i decided to cover everything in some blogposts over the coming week. some subjects have been covered in the past. this post will server as an index to those posts, feel free to suggest additions if there’s anything you would like to know. the session covered these subjects, i will update them with links when i published the relevant blogposts: marketplace submissions/choosing the right name/logo/description trial api marketplace and social media “tasks” advertising app promotion/marketing reporting (app hub, distimo, etc.) analytics (using mtiks) the session itself was presented in dutch and is available on channel9. the slides are in english and are available through slideshare. if you would like to contact me feel free to do so in the comments, the contact form or twitter. and do share your wp7 succes stories! continue reading 4 comments 30 dec 2011 forcing capability detection in a windows phone application written by tom verhoeff. posted in msp, wp7 last week i blogged about a problem i came across when beta testing a new wp7 application. my problem was related to the id_cap_medialib capability. today i noticed somebody on twitter having similar issues. problem! #wp7dev 's: when submitting an app that uses the video recorder <"id_cap_microphone"> is removed http://t.co/pu3psv62 #wpdev30/12/2011 18:08 via tweetdeckreplyretweetfavorite@lancewmccarthylance w. mccarthy fortunately there is a way to force detection of every capability. the key is knowing what reference to use to force the detection. in this post i will show how to implement a simple workaround to ensure detection. please note that all of this is just temporary. microsoft’s engineering teams are working on fixing these detection issues, so these tricks should not be required anymore in the future. detection process first of all it is important to realize that the ingestion tool does not scan the actual c# and xaml (that’s not included in the xap package anyway). the actual scanning happens on the intermediate language (il) that is generated by the compiler. this is important to keep in mind when implementing this workaround. detection rules essentially both the marketplace test kit and the app hub itself use the same set of rules to determine what capabilities are required. fortunately those rules are supplied with the test kit in understandable xml format. to find out what class you need to reference to force detection it is sufficient to check this list of rules. the rules.xml can be found in “c:\program files (x86)\microsoft sdks\windows phone\v7.1\tools\marketplace” for example here’s the part on the id_cap_microphone capability. forcing detection the rules.xml file basically tells you what classes to reference to force the detection (i highlighted them). in any case you can just add a dummy file (either xaml or just cs) and make a reference to just one of these classes. in case of the microphone @lancewmccarthy suggests this line: microphone microphone = microphone.default; this is a microphone-specific solution. another option is to just add this line: microsoft.xna.framework.audio.microphone temp = null; this is where you need to remember the code gets compiled before scanning. the compiler implements a lot of optimization which in this case would lead to discarding a variable that is never accessed. adding another line that references the variable solves this. this can be pretty much anything, for example: messagebox.show(temp.tostring()); if you would actually run this code it will always throw a nullreferenceexception, but since this is a dummy file that will never happen. although the code is unreachable the ingestion tool notices it. you can use the marketplace test kit to verify this. conclusion by combining the information in the rules.xml with a simple dummy file you should be able to force detection of any capability. the other way around rules.xml can also help you identify why a certain capability gets detected. do you come across any problems when using this method? feel free to leave a comment or send me a tweet. continue reading 4 comments 23 dec 2011 marketplace fails to detect capabilities, causes crash written by tom verhoeff. posted in msp, wp7 those of you following me on twitter might have noticed some complaints about the beta version of one of my new applications not working the way it should. the app implements a backgroundaudioagent to play an audio stream. when directly deploying the xap to a device this works like a charm. for a last round of testing i submitted the app for private beta testing through the app hub. to my big surprise the version downloaded through private beta instantly crashes when trying to start the backgroundagent. apart from analyzing, signing, encrypting and repackaging the xap nothing should be changed by the private beta process, so this should not be possible. cause we investigated the problem together with the microsoft marketplace dev support team. we figured out the crash was related to the specified capabilities. to play background audio the agent relies on the id_cap_medialib capability. this was specified in our manifest-file, but during the submission process the required capabilities are analyzed and overwritten. apparently the app hub contains a bug causing the medialib capability to remain undetected in certain situations. when using the marketplace test kit the same problem shows, it does not detect the medialib capability. when the application tries to execute any action related to this capability it simply throws an exception and crashes. solution obviously this is a bug in the marketplace ingestion tool that microsoft needs to fix. the support team states: “i can tell you that it’s a known problem at our side that engineering team is already investigating”. fortunately there’s a pretty obvious and easy workaround to solve this problem. just add a “dummy” page to your application. add elements to this page the ensure detection of the missing capability. in my case we forced detection of the medialib capability by inserting a mediaelement and making sure at least the x:name is specified( ). now both the marketplace test kit and the app hub’s ingestion tool will detect the capability therefore solving the problem. update: the support team also provided me with some other workarounds that are easier and cleaner, but still force detection of the missing medialib capability. if your app is referencing any of these libraries just add the one line of code to your app. if it’s referencing: then add: microsoft.phone.dll microsoft.devices.mediahistory history = null; microsoft.xna.framework.dll microsoft.xna.framework.media.medialibrary lib = null; none of the above ones, so very likely it’s at least referencing system.windows.dll system.windows.controls.mediaelement me = null; i don’t know if anybody experienced problems with apps crashing after going to the marketplace submissions process, but the first place to search for errors appears to be the detected capabilities. the marketplace test kit performs the same analysis the marketplace does, so it’s easy to check. the engineering team is working on fixing the issues, but for the time being forcing detection by adding dummy elements is easiest workaround. continue reading 3 comments 1234»last powered by warp theme framework


Here you find all texts from your page as Google (googlebot) and others search engines seen it.

Words density analysis:

Numbers of all words: 3294

One word

Two words phrases

Three words phrases

the - 6.74% (222)
you - 2.28% (75)
app - 2.25% (74)
one - 2.22% (73)
for - 1.85% (61)
windows - 1.79% (59)
phone - 1.73% (57)
and - 1.67% (55)
this - 1.67% (55)
that - 1.34% (44)
use - 1.18% (39)
google - 1.03% (34)
all - 0.94% (31)
our - 0.88% (29)
out - 0.82% (27)
not - 0.79% (26)
work - 0.76% (25)
post - 0.76% (25)
with - 0.73% (24)
mar - 0.7% (23)
your - 0.7% (23)
detect - 0.7% (23)
state - 0.67% (22)
dev - 0.64% (21)
just - 0.64% (21)
microsoft - 0.61% (20)
some - 0.61% (20)
market - 0.58% (19)
here - 0.58% (19)
user - 0.58% (19)
place - 0.58% (19)
are - 0.58% (19)
get - 0.55% (18)
any - 0.55% (18)
maps - 0.55% (18)
read - 0.52% (17)
marketplace - 0.52% (17)
web - 0.49% (16)
capability - 0.49% (16)
new - 0.49% (16)
round - 0.49% (16)
will - 0.49% (16)
media - 0.49% (16)
detection - 0.46% (15)
add - 0.46% (15)
now - 0.43% (14)
when - 0.43% (14)
like - 0.43% (14)
how - 0.39% (13)
kit - 0.39% (13)
can - 0.39% (13)
wp7 - 0.39% (13)
tom - 0.36% (12)
problem - 0.36% (12)
able - 0.36% (12)
too - 0.36% (12)
event - 0.36% (12)
what - 0.36% (12)
have - 0.36% (12)
but - 0.36% (12)
comment - 0.36% (12)
around - 0.36% (12)
test - 0.33% (11)
comments - 0.33% (11)
over - 0.33% (11)
way - 0.33% (11)
help - 0.33% (11)
build - 0.33% (11)
studio - 0.33% (11)
verhoeff - 0.33% (11)
posted - 0.33% (11)
agent - 0.33% (11)
written - 0.33% (11)
there - 0.33% (11)
was - 0.3% (10)
form - 0.3% (10)
it’s - 0.3% (10)
ever - 0.3% (10)
reading - 0.3% (10)
continue - 0.3% (10)
rules - 0.3% (10)
start - 0.3% (10)
blog - 0.3% (10)
verhoeff. - 0.3% (10)
microphone - 0.3% (10)
other - 0.3% (10)
tool - 0.3% (10)
users - 0.3% (10)
develop - 0.3% (10)
they - 0.27% (9)
ran - 0.27% (9)
lib - 0.27% (9)
application - 0.27% (9)
time - 0.27% (9)
back - 0.27% (9)
here’s - 0.27% (9)
using - 0.24% (8)
more - 0.24% (8)
part - 0.24% (8)
need - 0.24% (8)
apps - 0.24% (8)
week - 0.24% (8)
started - 0.24% (8)
visualstate - 0.24% (8)
posts - 0.24% (8)
capability. - 0.24% (8)
also - 0.24% (8)
know - 0.24% (8)
medialib - 0.21% (7)
changed - 0.21% (7)
mobile - 0.21% (7)
version - 0.21% (7)
session - 0.21% (7)
file - 0.21% (7)
webkit - 0.21% (7)
got - 0.21% (7)
class - 0.21% (7)
make - 0.21% (7)
force - 0.21% (7)
show - 0.21% (7)
support - 0.21% (7)
news - 0.21% (7)
does - 0.21% (7)
framework - 0.21% (7)
code - 0.21% (7)
twitter - 0.21% (7)
would - 0.21% (7)
team - 0.21% (7)
first - 0.21% (7)
crash - 0.21% (7)
developer - 0.21% (7)
sure - 0.18% (6)
dummy - 0.18% (6)
try - 0.18% (6)
own - 0.18% (6)
useragent - 0.18% (6)
same - 0.18% (6)
access - 0.18% (6)
transition - 0.18% (6)
chrome - 0.18% (6)
those - 0.18% (6)
cover - 0.18% (6)
info - 0.18% (6)
subject - 0.18% (6)
should - 0.18% (6)
except - 0.18% (6)
there’s - 0.18% (6)
through - 0.18% (6)
require - 0.18% (6)
object - 0.18% (6)
real - 0.18% (6)
sizechanged - 0.18% (6)
issue - 0.18% (6)
reference - 0.18% (6)
full - 0.18% (6)
happen - 0.18% (6)
workaround - 0.18% (6)
dec - 0.18% (6)
page - 0.18% (6)
visualstatemanager.gotostate(this, - 0.18% (6)
simple - 0.15% (5)
2012 - 0.15% (5)
google’s - 0.15% (5)
dispatcher - 0.15% (5)
about - 0.15% (5)
audio - 0.15% (5)
beta - 0.15% (5)
see - 0.15% (5)
experience - 0.15% (5)
after - 0.15% (5)
case - 0.15% (5)
run - 0.15% (5)
fortunately - 0.15% (5)
actual - 0.15% (5)
work. - 0.15% (5)
phone” - 0.15% (5)
exception - 0.15% (5)
true); - 0.15% (5)
msp, - 0.15% (5)
very - 0.15% (5)
their - 0.15% (5)
implement - 0.15% (5)
rules. - 0.15% (5)
xml - 0.15% (5)
hub - 0.15% (5)
these - 0.15% (5)
process - 0.15% (5)
want - 0.15% (5)
dat - 0.15% (5)
capabilities - 0.15% (5)
since - 0.15% (5)
still - 0.15% (5)
required - 0.15% (5)
cause - 0.15% (5)
last - 0.15% (5)
feature - 0.15% (5)
has - 0.15% (5)
mtiks - 0.12% (4)
engine - 0.12% (4)
give - 0.12% (4)
statement - 0.12% (4)
semanticzoom - 0.12% (4)
appear - 0.12% (4)
don’t - 0.12% (4)
used - 0.12% (4)
adding - 0.12% (4)
its - 0.12% (4)
analytics - 0.12% (4)
subjects - 0.12% (4)
else - 0.12% (4)
another - 0.12% (4)
feel - 0.12% (4)
rules.xml - 0.12% (4)
it. - 0.12% (4)
mozilla/5.0 - 0.12% (4)
working - 0.12% (4)
next - 0.12% (4)
easy - 0.12% (4)
events - 0.12% (4)
(khtml, - 0.12% (4)
gecko) - 0.12% (4)
ingestion - 0.12% (4)
off - 0.12% (4)
phone. - 0.12% (4)
this. - 0.12% (4)
that’s - 0.12% (4)
days - 0.12% (4)
review - 0.12% (4)
noticed - 0.12% (4)
blogposts - 0.12% (4)
(e.newsize.width - 0.12% (4)
information - 0.12% (4)
var - 0.12% (4)
mission - 0.12% (4)
came - 0.12% (4)
applications - 0.12% (4)
2013 - 0.12% (4)
line - 0.12% (4)
stand - 0.12% (4)
null; - 0.12% (4)
i’m - 0.12% (4)
been - 0.12% (4)
making - 0.12% (4)
money - 0.12% (4)
reader - 0.09% (3)
marketplaces - 0.09% (3)
might - 0.09% (3)
(windows - 0.09% (3)
browser - 0.09% (3)
testing - 0.09% (3)
2011 - 0.09% (3)
engineering - 0.09% (3)
detected - 0.09% (3)
invest - 0.09% (3)
them - 0.09% (3)
building - 0.09% (3)
check - 0.09% (3)
forcing - 0.09% (3)
great - 0.09% (3)
please - 0.09% (3)
solution - 0.09% (3)
lot - 0.09% (3)
key - 0.09% (3)
every - 0.09% (3)
string - 0.09% (3)
experiment - 0.09% (3)
video - 0.09% (3)
story - 0.09% (3)
mccarthy - 0.09% (3)
uses - 0.09% (3)
gmail - 0.09% (3)
handle - 0.09% (3)
works - 0.09% (3)
related - 0.09% (3)
you’ll - 0.09% (3)
step - 0.09% (3)
scan - 0.09% (3)
covered - 0.09% (3)
obvious - 0.09% (3)
contact - 0.09% (3)
tell - 0.09% (3)
keep - 0.09% (3)
temp - 0.09% (3)
basic - 0.09% (3)
why - 0.09% (3)
from - 0.09% (3)
actually - 0.09% (3)
submission - 0.09% (3)
8.1 - 0.09% (3)
pretty - 0.09% (3)
features - 0.09% (3)
background - 0.09% (3)
problems - 0.09% (3)
specified - 0.09% (3)
itself - 0.09% (3)
recent - 0.09% (3)
send - 0.09% (3)
workaround. - 0.09% (3)
crashes - 0.09% (3)
play - 0.09% (3)
together - 0.09% (3)
device - 0.09% (3)
most - 0.09% (3)
free - 0.09% (3)
least - 0.09% (3)
before - 0.09% (3)
while - 0.09% (3)
update - 0.09% (3)
world - 0.09% (3)
xap - 0.09% (3)
important - 0.09% (3)
referencing - 0.09% (3)
dutch - 0.09% (3)
private - 0.09% (3)
open - 0.09% (3)
wpdev - 0.09% (3)
script - 0.09% (3)
bug - 0.09% (3)
agent. - 0.09% (3)
apps. - 0.09% (3)
id_cap_microphone - 0.09% (3)
although - 0.09% (3)
never - 0.09% (3)
found - 0.09% (3)
suggest - 0.09% (3)
coming - 0.09% (3)
android - 0.09% (3)
mediaelement - 0.09% (3)
follow - 0.09% (3)
api - 0.06% (2)
available - 0.06% (2)
index - 0.06% (2)
did - 0.06% (2)
etc.) - 0.06% (2)
relevant - 0.06% (2)
anything - 0.06% (2)
example - 0.06% (2)
slides - 0.06% (2)
solve - 0.06% (2)
compiler - 0.06% (2)
implements - 0.06% (2)
variable - 0.06% (2)
throw - 0.06% (2)
certain - 0.06% (2)
win32 - 0.06% (2)
process, - 0.06% (2)
capabilities. - 0.06% (2)
tries - 0.06% (2)
problem. - 0.06% (2)
option - 0.06% (2)
elements - 0.06% (2)
missing - 0.06% (2)
x:name - 0.06% (2)
then - 0.06% (2)
history - 0.06% (2)
oct - 0.06% (2)
ones, - 0.06% (2)
submissions - 0.06% (2)
search - 0.06% (2)
gets - 0.06% (2)
line: - 0.06% (2)
share - 0.06% (2)
xaml - 0.06% (2)
across - 0.06% (2)
application. - 0.06% (2)
id_cap_medialib - 0.06% (2)
object. - 0.06% (2)
detection. - 0.06% (2)
ensure - 0.06% (2)
fixing - 0.06% (2)
issues, - 0.06% (2)
realize - 0.06% (2)
scanning - 0.06% (2)
@lancewmccarthy - 0.06% (2)
both - 0.06% (2)
into - 0.06% (2)
set - 0.06% (2)
culture=neutral, - 0.06% (2)
- 0.06% (2)
- 0.06% (2)
classes - 0.06% (2)
year - 0.06% (2)
future. - 0.06% (2)
platform - 0.06% (2)
happens - 0.06% (2)
decided - 0.06% (2)
figured - 0.06% (2)
bit - 0.06% (2)
possible. - 0.06% (2)
they’re - 0.06% (2)
within - 0.06% (2)
users. - 0.06% (2)
yesterday - 0.06% (2)
away - 0.06% (2)
doing - 0.06% (2)
mock - 0.06% (2)
rendering - 0.06% (2)
right - 0.06% (2)
statement: - 0.06% (2)
update: - 0.06% (2)
transitions - 0.06% (2)
internet - 0.06% (2)
explorer - 0.06% (2)
devices - 0.06% (2)
anyway) - 0.06% (2)
worked. - 0.06% (2)
few - 0.06% (2)
experiments - 0.06% (2)
really - 0.06% (2)
going - 0.06% (2)
detecting - 0.06% (2)
phones - 0.06% (2)
causes - 0.06% (2)
whole - 0.06% (2)
performs - 0.06% (2)
different - 0.06% (2)
extend - 0.06% (2)
– - 0.06% (2)
social - 0.06% (2)
helping - 0.06% (2)
website. - 0.06% (2)
app. - 0.06% (2)
together. - 0.06% (2)
content - 0.06% (2)
choose - 0.06% (2)
idea - 0.06% (2)
knowledge - 0.06% (2)
had - 0.06% (2)
source - 0.06% (2)
two - 0.06% (2)
understand - 0.06% (2)
down - 0.06% (2)
fully - 0.06% (2)
kicking - 0.06% (2)
note - 0.06% (2)
required. - 0.06% (2)
basically - 0.06% (2)
head - 0.06% (2)
async - 0.06% (2)
started. - 0.06% (2)
official - 0.06% (2)
contains - 0.06% (2)
series - 0.06% (2)
yourself - 0.06% (2)
come - 0.06% (2)
without - 0.06% (2)
appears - 0.06% (2)
(linux; - 0.06% (2)
interesting - 0.06% (2)
developers - 0.06% (2)
company - 0.06% (2)
accessible - 0.06% (2)
always - 0.06% (2)
500) - 0.06% (2)
i’ve - 0.06% (2)
gone - 0.06% (2)
little - 0.06% (2)
silent - 0.06% (2)
stay - 0.06% (2)
sizechangedeventargs - 0.06% (2)
were - 0.06% (2)
today - 0.06% (2)
announce - 0.06% (2)
simply - 0.06% (2)
provide - 0.06% (2)
trying - 0.06% (2)
targeted - 0.06% (2)
sender, - 0.06% (2)
groupeditemspage_sizechanged(object - 0.06% (2)
minutes - 0.06% (2)
techdays - 0.06% (2)
void - 0.06% (2)
“making - 0.06% (2)
applications”. - 0.06% (2)
many - 0.06% (2)
conclusion - 0.06% (2)
people - 0.06% (2)
knowing - 0.06% (2)
(using - 0.06% (2)
nokia - 0.06% (2)
current - 0.06% (2)
2.3.4; - 0.06% (2)
moved - 0.06% (2)
fr-fr; - 0.06% (2)
htc - 0.06% (2)
desire - 0.06% (2)
build/grj22) - 0.06% (2)
applewebkit/533.1 - 0.06% (2)
version/4.0 - 0.06% (2)
safari/533.1 - 0.06% (2)
"defaultlayout", - 0.06% (2)
fiddler - 0.06% (2)
"portraitlayout", - 0.06% (2)
“windows - 0.06% (2)
obviously - 0.06% (2)
worth - 0.06% (2)
desktop - 0.06% (2)
something - 0.06% (2)
6.2; - 0.06% (2)
wow64) - 0.06% (2)
applewebkit/537.11 - 0.06% (2)
chrome/23.0.1271.97 - 0.06% (2)
safari/537.11 - 0.06% (2)
added - 0.06% (2)
e.newsize.height) - 0.06% (2)
youtube - 0.06% (2)
where - 0.06% (2)
specify - 0.06% (2)
suggests - 0.06% (2)
however - 0.06% (2)
"minimallayout", - 0.06% (2)
shows - 0.06% (2)
present - 0.06% (2)
windows phone - 1.31% (43)
in the - 0.46% (15)
google maps - 0.43% (14)
phone app - 0.36% (12)
tom verhoeff - 0.33% (11)
on the - 0.33% (11)
your app - 0.33% (11)
of the - 0.33% (11)
app studio - 0.33% (11)
by tom - 0.3% (10)
continue reading - 0.3% (10)
posted in - 0.3% (10)
tom verhoeff. - 0.3% (10)
written by - 0.3% (10)
verhoeff. posted - 0.3% (10)
to the - 0.3% (10)
this is - 0.27% (9)
the marketplace - 0.27% (9)
the app - 0.27% (9)
windows 8 - 0.24% (8)
help you - 0.24% (8)
to get - 0.21% (7)
of you - 0.21% (7)
will help - 0.21% (7)
in windows - 0.18% (6)
you can - 0.18% (6)
this post - 0.18% (6)
get started - 0.18% (6)
if you - 0.18% (6)
test kit - 0.18% (6)
one of - 0.18% (6)
marketplace test - 0.15% (5)
google is - 0.15% (5)
to force - 0.15% (5)
on twitter - 0.15% (5)
detection of - 0.15% (5)
phone users - 0.15% (5)
in msp, - 0.15% (5)
for more - 0.15% (5)
out the - 0.15% (5)
true); } - 0.15% (5)
with a - 0.15% (5)
app hub - 0.15% (5)
msp, wp7 - 0.15% (5)
of your - 0.12% (4)
phone dev - 0.12% (4)
(e.newsize.width < - 0.12% (4)
medialib capability. - 0.12% (4)
a full - 0.12% (4)
need to - 0.12% (4)
is the - 0.12% (4)
able to - 0.12% (4)
you need - 0.12% (4)
a windows - 0.12% (4)
like gecko) - 0.12% (4)
to your - 0.12% (4)
use the - 0.12% (4)
for windows - 0.12% (4)
semanticzoom object - 0.12% (4)
(khtml, like - 0.12% (4)
i will - 0.12% (4)
= null; - 0.12% (4)
with the - 0.12% (4)
in this - 0.12% (4)
force detection - 0.12% (4)
that will - 0.12% (4)
just add - 0.12% (4)
ingestion tool - 0.12% (4)
the problem - 0.09% (3)
post i - 0.09% (3)
free to - 0.09% (3)
to this - 0.09% (3)
engineering team - 0.09% (3)
the rules.xml - 0.09% (3)
working on - 0.09% (3)
dummy file - 0.09% (3)
it’s a - 0.09% (3)
for the - 0.09% (3)
at least - 0.09% (3)
but the - 0.09% (3)
the mobile - 0.09% (3)
that google - 0.09% (3)
windows 8.1 - 0.09% (3)
but for - 0.09% (3)
maps for - 0.09% (3)
the xap - 0.09% (3)
with windows - 0.09% (3)
making money - 0.09% (3)
that is - 0.09% (3)
by the - 0.09% (3)
related to - 0.09% (3)
to know - 0.09% (3)
all you - 0.09% (3)
money with - 0.09% (3)
on this - 0.09% (3)
phone applications - 0.09% (3)
private beta - 0.09% (3)
the medialib - 0.09% (3)
although the - 0.09% (3)
feel free - 0.09% (3)
reading 2 - 0.09% (3)
4 comments - 0.09% (3)
might have - 0.09% (3)
support team - 0.09% (3)
you would - 0.09% (3)
like google - 0.09% (3)
all the - 0.09% (3)
studio is - 0.09% (3)
a great - 0.09% (3)
to use - 0.09% (3)
be able - 0.09% (3)
app in - 0.09% (3)
reading 4 - 0.09% (3)
the most - 0.09% (3)
the windows - 0.09% (3)
phone week - 0.09% (3)
to build - 0.09% (3)
the world - 0.09% (3)
app and - 0.09% (3)
your first - 0.09% (3)
around the - 0.09% (3)
what class - 0.06% (2)
blog and - 0.06% (2)
of rules - 0.06% (2)
to reference - 0.06% (2)
to check - 0.06% (2)
kit and - 0.06% (2)
phone developer - 0.06% (2)
both the - 0.06% (2)
the actual - 0.06% (2)
the ingestion - 0.06% (2)
important to - 0.06% (2)
of all - 0.06% (2)
not be - 0.06% (2)
can be - 0.06% (2)
over to - 0.06% (2)
an app - 0.06% (2)
simple workaround - 0.06% (2)
when i - 0.06% (2)
build your - 0.06% (2)
it does - 0.06% (2)
make the - 0.06% (2)
most out - 0.06% (2)
about the - 0.06% (2)
the time - 0.06% (2)
like to - 0.06% (2)
the right - 0.06% (2)
helping out - 0.06% (2)
analytics (using - 0.06% (2)
week i - 0.06% (2)
beta testing - 0.06% (2)
was related - 0.06% (2)
id_cap_medialib capability. - 0.06% (2)
today i - 0.06% (2)
/> be sure - 0.06% (2)
/> - 0.06% (2)
kicking of - 0.06% (2)
forcing detection - 0.06% (2)
the missing - 0.06% (2)
detect the - 0.06% (2)
sizechangedeventargs e) - 0.06% (2)
exception and - 0.06% (2)
groupeditemspage_sizechanged(object sender, - 0.06% (2)
of code - 0.06% (2)
how to - 0.06% (2)
please see - 0.06% (2)
there’s a - 0.06% (2)
workaround to - 0.06% (2)
sizechanged event - 0.06% (2)
using the - 0.06% (2)
the support - 0.06% (2)
with some - 0.06% (2)
that are - 0.06% (2)
if your - 0.06% (2)
app is - 0.06% (2)
of these - 0.06% (2)
new windows - 0.06% (2)
appears to - 0.06% (2)
the semanticzoom - 0.06% (2)
does not - 0.06% (2)
500) { - 0.06% (2)
the detection - 0.06% (2)
capability. the - 0.06% (2)
the microsoft - 0.06% (2)
a dummy - 0.06% (2)
to just - 0.06% (2)
this line: - 0.06% (2)
this case - 0.06% (2)
this. this - 0.06% (2)
this code - 0.06% (2)
should be - 0.06% (2)
performs the - 0.06% (2)
through the - 0.06% (2)
visualstatemanager.gotostate(this, "minimallayout", - 0.06% (2)
semanticzoom object. - 0.06% (2)
have noticed - 0.06% (2)
implements a - 0.06% (2)
bug in - 0.06% (2)
trying to - 0.06% (2)
visualstatemanager.gotostate(this, "defaultlayout", - 0.06% (2)
else { - 0.06% (2)
visualstatemanager.gotostate(this, "portraitlayout", - 0.06% (2)
e.newsize.height) { - 0.06% (2)
else if - 0.06% (2)
place in - 0.06% (2)
sure to - 0.06% (2)
wp7 last - 0.06% (2)
what do - 0.06% (2)
this was - 0.06% (2)
my desktop - 0.06% (2)
chrome on - 0.06% (2)
mozilla/5.0 (windows - 0.06% (2)
nt 6.2; - 0.06% (2)
wow64) applewebkit/537.11 - 0.06% (2)
a fully - 0.06% (2)
gecko) chrome/23.0.1271.97 - 0.06% (2)
(windows nt - 0.06% (2)
google chrome - 0.06% (2)
6.2; wow64) - 0.06% (2)
applewebkit/537.11 (khtml, - 0.06% (2)
chrome/23.0.1271.97 safari/537.11 - 0.06% (2)
to google - 0.06% (2)
app stand - 0.06% (2)
appear to - 0.06% (2)
some other - 0.06% (2)
make your - 0.06% (2)
support for - 0.06% (2)
“windows phone” - 0.06% (2)
around with - 0.06% (2)
are the - 0.06% (2)
what is - 0.06% (2)
google that - 0.06% (2)
the whole - 0.06% (2)
over the - 0.06% (2)
maps the - 0.06% (2)
of google - 0.06% (2)
to access - 0.06% (2)
give it - 0.06% (2)
i used - 0.06% (2)
out of - 0.06% (2)
on windows - 0.06% (2)
the useragent - 0.06% (2)
using a - 0.06% (2)
it just - 0.06% (2)
(linux; u; - 0.06% (2)
android 2.3.4; - 0.06% (2)
fr-fr; htc - 0.06% (2)
desire build/grj22) - 0.06% (2)
applewebkit/533.1 (khtml, - 0.06% (2)
get started. - 0.06% (2)
version/4.0 mobile - 0.06% (2)
app for - 0.06% (2)
phone users. - 0.06% (2)
you have - 0.06% (2)
this subject - 0.06% (2)
little silent - 0.06% (2)
the next - 0.06% (2)
targeted at - 0.06% (2)
the coming - 0.06% (2)
wp7 app - 0.06% (2)
mtiks in - 0.06% (2)
part of - 0.06% (2)
on “making - 0.06% (2)
build a - 0.06% (2)
has been - 0.06% (2)
that i’ve - 0.06% (2)
covered in - 0.06% (2)
first of - 0.06% (2)
so what - 0.06% (2)
and what - 0.06% (2)
is never - 0.06% (2)
easy to - 0.06% (2)
you’ll be - 0.06% (2)
and that - 0.06% (2)
the required - 0.06% (2)
gone a - 0.06% (2)
way to - 0.06% (2)
if they - 0.06% (2)
21 oct - 0.06% (2)
happen to - 0.06% (2)
need google - 0.06% (2)
just want - 0.06% (2)
full app - 0.06% (2)
the google - 0.06% (2)
develop a - 0.06% (2)
features that - 0.06% (2)
your own - 0.06% (2)
and make - 0.06% (2)
by adding - 0.06% (2)
to develop - 0.06% (2)
noticed that - 0.06% (2)
i’ve gone - 0.06% (2)
a little - 0.06% (2)
silent on - 0.06% (2)
phone and - 0.06% (2)
have to - 0.06% (2)
app it - 0.06% (2)
mar 2012 - 0.06% (2)
wp7 review - 0.06% (2)
on fixing - 0.06% (2)
written by tom - 0.3% (10)
tom verhoeff. posted - 0.3% (10)
by tom verhoeff. - 0.3% (10)
verhoeff. posted in - 0.3% (10)
will help you - 0.18% (6)
the marketplace test - 0.15% (5)
posted in msp, - 0.15% (5)
marketplace test kit - 0.15% (5)
in msp, wp7 - 0.15% (5)
phone app studio - 0.12% (4)
a windows phone - 0.12% (4)
for windows phone - 0.12% (4)
in windows phone - 0.12% (4)
posted in windows - 0.12% (4)
windows phone application - 0.12% (4)
if (e.newsize.width < - 0.12% (4)
to force detection - 0.09% (3)
of your app - 0.09% (3)
feel free to - 0.09% (3)
with windows phone - 0.09% (3)
this post i - 0.09% (3)
be able to - 0.09% (3)
windows phone week - 0.09% (3)
force detection of - 0.09% (3)
you need to - 0.09% (3)
studio is a - 0.09% (3)
money with windows - 0.09% (3)
that will help - 0.09% (3)
continue reading 2 - 0.09% (3)
that google is - 0.09% (3)
continue reading 4 - 0.09% (3)
true); } else - 0.09% (3)
just want to - 0.06% (2)
mar 2012 wp7 - 0.06% (2)
some of you - 0.06% (2)
been covered in - 0.06% (2)
gone a little - 0.06% (2)
would like to - 0.06% (2)
session on “making - 0.06% (2)
if you would - 0.06% (2)
is important to - 0.06% (2)
msp, wp7 last - 0.06% (2)
/> - 0.06% (2)
of the missing - 0.06% (2)
test kit and - 0.06% (2)
both the marketplace - 0.06% (2)
the support team - 0.06% (2)
should not be - 0.06% (2)
the ingestion tool - 0.06% (2)
a dummy file - 0.06% (2)
reference to force - 0.06% (2)
was related to - 0.06% (2)
kit and the - 0.06% (2)
you might have - 0.06% (2)
in the future. - 0.06% (2)
a simple workaround - 0.06% (2)
how to implement - 0.06% (2)
in this post - 0.06% (2)
the id_cap_medialib capability. - 0.06% (2)
noticed that i’ve - 0.06% (2)
nt 6.2; wow64) - 0.06% (2)
appear to be - 0.06% (2)
windows phone developer - 0.06% (2)
your app stand - 0.06% (2)
a full app - 0.06% (2)
develop a full - 0.06% (2)
help you build - 0.06% (2)
tool that will - 0.06% (2)
your first app - 0.06% (2)
2013 windows phone - 0.06% (2)
sizechangedeventargs e) { - 0.06% (2)
the most out - 0.06% (2)
void groupeditemspage_sizechanged(object sender, - 0.06% (2)
bug in the - 0.06% (2)
"defaultlayout", true); } - 0.06% (2)
else { visualstatemanager.gotostate(this, - 0.06% (2)
"portraitlayout", true); } - 0.06% (2)
e.newsize.height) { visualstatemanager.gotostate(this, - 0.06% (2)
(e.newsize.width < 500) - 0.06% (2)
groupeditemspage_sizechanged(object sender, sizechangedeventargs - 0.06% (2)
need to get - 0.06% (2)
in this case - 0.06% (2)
windows phone is - 0.06% (2)
(windows nt 6.2; - 0.06% (2)
nokia maps for - 0.06% (2)
the google maps - 0.06% (2)
they happen to - 0.06% (2)
if they happen - 0.06% (2)
gecko) chrome/23.0.1271.97 safari/537.11 - 0.06% (2)
applewebkit/537.11 (khtml, like - 0.06% (2)
like gecko) chrome/23.0.1271.97 - 0.06% (2)
wow64) applewebkit/537.11 (khtml, - 0.06% (2)
google chrome on - 0.06% (2)
windows phone users. - 0.06% (2)
like gecko) version/4.0 - 0.06% (2)
build/grj22) applewebkit/533.1 (khtml, - 0.06% (2)
fr-fr; htc desire - 0.06% (2)
u; android 2.3.4; - 0.06% (2)
use the same - 0.06% (2)
and windows 8 - 0.06% (2)
the mobile web - 0.06% (2)
google maps the - 0.06% (2)
your app is - 0.06% (2)

Here you can find chart of all your popular one, two and three word phrases. Google and others search engines means your page is about words you use frequently.

Copyright © 2015-2016 hupso.pl. All rights reserved. FB | +G | Twitter

Hupso.pl jest serwisem internetowym, w którym jednym kliknieciem możesz szybko i łatwo sprawdź stronę www pod kątem SEO. Oferujemy darmowe pozycjonowanie stron internetowych oraz wycena domen i stron internetowych. Prowadzimy ranking polskich stron internetowych oraz ranking stron alexa.