So, Windows Phone 7 requires Windows 7/Vista...
-
We're not righting code for the OS, we are using the OS to write code for another OS. It should have nothing to do with Windows XP or whatever. And I think blaming is not the point, but look at Android, any Windows XP can develop for a modern Adroid based device. What am I continue to develop on? Android, and not WP7. That's the question. I wonder if that was a good decision to make.
Fabio Franco wrote:
We're not righting code for the OS, we are using the OS to write code for another OS. It should have nothing to do with Windows XP or whatever.
Well it costs them time and resources to get the emulator to work on XP, and the same goes for their custom Visual Studio editions. I reckon they decided against officially supporting XP due to those reasons.
Regards, Nish
My technology blog: voidnish.wordpress.com
-
In what way would XP be unsuitable as a text editor for source code, even though that code is targeted at WP7?
harold aptroot wrote:
In what way would XP be unsuitable as a text editor for source code, even though that code is targeted at WP7?
It's the emulator that won't run on XP. Theoretically you can copy the compiler and assemblies over and edit and compile the code. You just won't be able to run/debug it since the emulator is officially supported only on Vista and later OSes.
Regards, Nish
My technology blog: voidnish.wordpress.com
-
Well anyone writing code today should surely test it on all OSes they intend to support, and I am sure you do support Vista and Windows 7. Although it's possible that you have others in your dev team who develop on W7 while some of you are left to use older OSes. If so, well not much you can do about that I guess.
Regards, Nish
My technology blog: voidnish.wordpress.com
I agree that testing should be done to all OSes (when they are targeted), however, the .Net Framework makes it easy for us not to worry about that, unless in some specific situations. And no, the whole company is Windows XP.
-
I agree that testing should be done to all OSes (when they are targeted), however, the .Net Framework makes it easy for us not to worry about that, unless in some specific situations. And no, the whole company is Windows XP.
Fabio Franco wrote:
And no, the whole company is Windows XP.
Interesting, so you write in-house software I guess.
Regards, Nish
My technology blog: voidnish.wordpress.com
-
Fabio Franco wrote:
We're not righting code for the OS, we are using the OS to write code for another OS. It should have nothing to do with Windows XP or whatever.
Well it costs them time and resources to get the emulator to work on XP, and the same goes for their custom Visual Studio editions. I reckon they decided against officially supporting XP due to those reasons.
Regards, Nish
My technology blog: voidnish.wordpress.com
Nishant Sivakumar wrote:
Well it costs them time and resources to get the emulator to work on XP
I agree with that, but how that will pay off to them? I wonder if the investiment to support XP (or build it to XP and that most stuff is likely to work in W7) wouldn't pay off by having a much wider developer base. I have no idea about the cost impact, I just wonder how much to build an emulator for W7, I mean, every other mobile company (except Apple) did just that. The fact is, that many will not contribute to their market store, I can't say in numbers (humm good poll idea) but I do beleive that there is a reasonable bunch.
-
Yeah, I received a code project offer today about WP7 development. I thought to myself: "Yaayyy!! Let's get cracking" :rolleyes: Then I went to download the SDK just to realize it supports only Windows 7 and Vista. :omg: It completely turned me down. Now I ask you folks, while most other major competitors (except IPhone) allow Windows XP or even older OSes, don't you guys think that this is a shot on the foot? Given that MS have been strugling to get in the mobile market with relevance, I think the worse thing to do would be constraining stuff like this. :doh: Are they trying to sell Windows 7? I would like to beleive they are not. The fact is that MS just lost a contributor.
Fabio Franco wrote:
Yeah, I received a code project offer today about WP7 development
From your current employer ? if yes, then you should ask them for an upgrade to Win7. If not, then you should have read the fine prints.
Watched code never compiles.
-
Fabio Franco wrote:
And no, the whole company is Windows XP.
Interesting, so you write in-house software I guess.
Regards, Nish
My technology blog: voidnish.wordpress.com
What do you mean? It's a consulting company, that develop solution to banks. Yes, we do it all from the company, we're not a resourcing company.
-
Fabio Franco wrote:
Yeah, I received a code project offer today about WP7 development
From your current employer ? if yes, then you should ask them for an upgrade to Win7. If not, then you should have read the fine prints.
Watched code never compiles.
Maximilien wrote:
From your current employer ?
No, unless I worked for microsoft
Maximilien wrote:
If not, then you should have read the fine prints.
What's that supposed to mean? All I'm questioning is the decision to support Vista/7 only.
-
harold aptroot wrote:
In what way would XP be unsuitable as a text editor for source code, even though that code is targeted at WP7?
It's the emulator that won't run on XP. Theoretically you can copy the compiler and assemblies over and edit and compile the code. You just won't be able to run/debug it since the emulator is officially supported only on Vista and later OSes.
Regards, Nish
My technology blog: voidnish.wordpress.com
-
Nishant Sivakumar wrote:
Well it costs them time and resources to get the emulator to work on XP
I agree with that, but how that will pay off to them? I wonder if the investiment to support XP (or build it to XP and that most stuff is likely to work in W7) wouldn't pay off by having a much wider developer base. I have no idea about the cost impact, I just wonder how much to build an emulator for W7, I mean, every other mobile company (except Apple) did just that. The fact is, that many will not contribute to their market store, I can't say in numbers (humm good poll idea) but I do beleive that there is a reasonable bunch.
I reckon they did a market analysis and decided that they won't lose out on too many devs if they excluded XP.
Regards, Nish
My technology blog: voidnish.wordpress.com
-
What do you mean? It's a consulting company, that develop solution to banks. Yes, we do it all from the company, we're not a resourcing company.
Interesting that you only test and develop on XP then, because it's possible that your end users may be on Vista or Windows 7. Even with .NET you still run into OS compatibility issues sometimes.
Regards, Nish
My technology blog: voidnish.wordpress.com
-
And that emulator is apparently using DirectX 10 or some other post-XP-only technology..
harold aptroot wrote:
And that emulator is apparently using DirectX 10 or some other post-XP-only technology..
I guess so. The devs who wrote it probably decided to do it the fastest way possible :-)
Regards, Nish
My technology blog: voidnish.wordpress.com
-
Interesting that you only test and develop on XP then, because it's possible that your end users may be on Vista or Windows 7. Even with .NET you still run into OS compatibility issues sometimes.
Regards, Nish
My technology blog: voidnish.wordpress.com
Actually, the good thing is that the client is on XP too. And the systems don't really rely on windows, only a few front-ends and most of them are web based.
-
I would say that the majority of developers at least have access to a Windows 7 machine, because as a developer you need to test that your software works at least on the latest platform. I wouldn't expect a developer to work on XP as it's pretty much end of life.
Wout
No. If your a developer for a *mobile* platform, then it doesn't matter what OS version your PC is running - except a developer is more likely to be using a lot of apps that consume a lot of resources. Windows 7 is a lot more resource hungry than Windows XP, so you can have more stuff running on XP. And besides that there is absolutly nothing wrong with XP. It works just fine.
-
No. If your a developer for a *mobile* platform, then it doesn't matter what OS version your PC is running - except a developer is more likely to be using a lot of apps that consume a lot of resources. Windows 7 is a lot more resource hungry than Windows XP, so you can have more stuff running on XP. And besides that there is absolutly nothing wrong with XP. It works just fine.
funny I can remember people saying exactly that about windows NT and windows 7 seems to be able to run on any platform that can run xp, i have a aspire one on which 7 runs better than the xp i had on it before
You cant outrun the world, but there is no harm in getting a head start
-
I reckon they did a market analysis and decided that they won't lose out on too many devs if they excluded XP.
Regards, Nish
My technology blog: voidnish.wordpress.com
They might only lose 2-3 people that way, but that's 40% of what they're likely to get as a whole. I can't imagine that there's more than 20 people in the world, developer or otherwise, who care about a windows phone.
Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
-
funny I can remember people saying exactly that about windows NT and windows 7 seems to be able to run on any platform that can run xp, i have a aspire one on which 7 runs better than the xp i had on it before
You cant outrun the world, but there is no harm in getting a head start
-
I reckon they did a market analysis and decided that they won't lose out on too many devs if they excluded XP.
Regards, Nish
My technology blog: voidnish.wordpress.com
-
Maximilien wrote:
From your current employer ?
No, unless I worked for microsoft
Maximilien wrote:
If not, then you should have read the fine prints.
What's that supposed to mean? All I'm questioning is the decision to support Vista/7 only.
-
I work at major multi-national company that develop critical systems for big bank networks. All PCs are windows XP. So you're saying my job represents the end of life? You would say the majority of developers have access to W7 machine, but I dare you find any evidence of that. Anyways, I do have some limited access to W7 machine, but it is as it is, limited and therfore, not very fit to dedicate my work to develop stuff with that.
I work for a big bank (well medium anyway) network and am slaved to XP, and yes I consider this platform EOL, thank god they have at least made the decision to go to W7, getting it done on such a massive scale will take some doing. I don't see a problem with W7 development needing W7 as a minimum dev platform. If you want to build for the latest I feel it is reasonable to have the latest platform. Think of it as more justification to move to a W7 platform.
Never underestimate the power of human stupidity RAH