So, Windows Phone 7 requires Windows 7/Vista...
-
Try running 3ds Max, photoshop, OpenOffice, Visual Studio on a PC with Windows 7 and only 4GB of ram and you'll see.
funny that your saying that. i don't seem to have any issues with W7 and running all of those apps at once. As a matter of fact at one time i run: 3 instances of VS2010 Pro Outlook Word Excel Photoshop 64bit Lightwave 3D Deep Exploration 3DS Max Milkshape 3D Firefox (with no less than 8 tabs open at a time) Google Chrome Aptana Studio 2 IconFX Navicat Lite and with all these things running at once on a W7 Ultimate 64bit with 4gigs of ram. and i can safely tell you that i do not even notice the resource drain on my system. I can run VS (x3) each compiling large apps, run deep exploration doing a Full Res HDR 3d Render , and play the Newest Need For Speed Hot Pursuit all at once and W7 just performs like a champion. so i myself do not know where you are getting the run 'these apps all at once' and you will see from.
-
Try running 3ds Max, photoshop, OpenOffice, Visual Studio on a PC with Windows 7 and only 4GB of ram and you'll see.
I run Autocad Maya, Photoshop and visual Studio on Windows 7 with only 2GB of RAM. So far there are no problems because of memory. -Saurabh
-
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 think the point is that he wants to support Windows Phone 7. The OS of the development environment has nothing to do with it, and the official SDK should be available for multiple operating systems. I wouldn't buy an apple computer, let alone the most recent, to develop apps for the iphone.
I wanna be a eunuchs developer! Pass me a bread knife!
-
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.
First, the cost of having to support an EOL OS like XP. Make it only work on Vista and Windows 7, and you save money on support cost. Last I checked, Microsoft was a business, so wanting to say, "Hey, you want to make money from building Windows Phone 7 apps, have the decency to support us to by buying a latest version of our OS that we support". When did it become so one-sided that Microsoft should make it easier to develop on Windows 7 phones just because they screwed up big time on Windows Mobile 6? Otherwise, it would be just as fair an argument from those on DOS 3.3 demanding that if Microsoft is going to support an unsupported EOL OS like XP, why stop there? There are still plenty of large businesses and government agencies running on DOS machines (sad, but true - Don't believe me? Ask the New Zealand Health Board what they run the patient health records on.) Second, don't like that you have to get Vista or Windows 7, then I am sure Microsoft would happily suggest Android SDK. As for Microsoft's attempt to get people to upgrade, sounds like a smart move to tie it in with the development SDKs. I am not convinced that Windows Phone 7 is the right platform to put my development efforts at this stage, but requiring me to use a supported OS to use their SDK seems not only reasonable but appropriate.
James Wallis Martin JB Metrics Ltd, Director www.jbmetrics.com
-
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.
What? How can any serious developer still be on *only* XP? Get with the current century, man!
-
What? How can any serious developer still be on *only* XP? Get with the current century, man!
I know, do you think I develop on WinXP because I want to? Workplace and time restrictions make me stuck with it. But that doesn't mean I don't take new stuff serious. But I think this deviates from the original inquiry as how development OS version should play any role on the developmento to another OS (mobile).
-
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
It's not Windows 7 development, but Windows Phone 7 development, another OS entirely. We're just using another OS to do the development for mobile. So the development OS shouldn't play any part on that.
-
First, the cost of having to support an EOL OS like XP. Make it only work on Vista and Windows 7, and you save money on support cost. Last I checked, Microsoft was a business, so wanting to say, "Hey, you want to make money from building Windows Phone 7 apps, have the decency to support us to by buying a latest version of our OS that we support". When did it become so one-sided that Microsoft should make it easier to develop on Windows 7 phones just because they screwed up big time on Windows Mobile 6? Otherwise, it would be just as fair an argument from those on DOS 3.3 demanding that if Microsoft is going to support an unsupported EOL OS like XP, why stop there? There are still plenty of large businesses and government agencies running on DOS machines (sad, but true - Don't believe me? Ask the New Zealand Health Board what they run the patient health records on.) Second, don't like that you have to get Vista or Windows 7, then I am sure Microsoft would happily suggest Android SDK. As for Microsoft's attempt to get people to upgrade, sounds like a smart move to tie it in with the development SDKs. I am not convinced that Windows Phone 7 is the right platform to put my development efforts at this stage, but requiring me to use a supported OS to use their SDK seems not only reasonable but appropriate.
James Wallis Martin JB Metrics Ltd, Director www.jbmetrics.com
jbmetrics wrote:
First, the cost of having to support an EOL OS like XP
I'm aware of that. The point is the impact of not supporting an OS on free apps on the market. I think one of the main concearns of success of a mobile platform is the availability of mass free apps. See Android and IPhone.
jbmetrics wrote:
"Hey, you want to make money from building Windows Phone 7 apps, have the decency to support us to by buying a latest version of our OS that we support"
Actually its mostly the other way around. How many free applications are there in Android and IPhone market? The majority is free if compared to paid ones. Developers are mostly contributing, not making money, so why not: "How about you let us choose the OS to help YOU make money".
jbmetrics wrote:
When did it become so one-sided that Microsoft should make it easier to develop on Windows 7 phones just because they screwed up big time on Windows Mobile 6
Maybe to gain some market share? If you make things difficult, don't you agree that you attract less developers?
jbmetrics wrote:
Otherwise, it would be just as fair an argument from those on DOS 3.3 demanding that if Microsoft is going to support an unsupported EOL OS like XP, why stop there?
You're stretching too far. There's still a massive amount of XP users yet, and I don't beleive XP pose any technological constraint for development.
jbmetrics wrote:
Second, don't like that you have to get Vista or Windows 7, then I am sure Microsoft would happily suggest Android SDK
If they wanted that why would they enter the fight at all? This is simply nonsense. It's not that I don't want to use Vista or 7, but as others I currently don't have too much access to it. And it's not about me, it's about developers stuck on XP.
jbmetrics wrote:
As for Microsoft's attempt to get people to upgrade, sounds like a smart move to tie it in with the development SDKs
I think that won't bring big bucks to MS, the majority of Windows users are not developers, developers are just tiny bit of the pie. And it's more likely to developers not use an SDK than upgrade because of it. It's like live mesh. I'll simply use Dropbox instead, because even havi
-
I run Autocad Maya, Photoshop and visual Studio on Windows 7 with only 2GB of RAM. So far there are no problems because of memory. -Saurabh
-
I think the point is that he wants to support Windows Phone 7. The OS of the development environment has nothing to do with it, and the official SDK should be available for multiple operating systems. I wouldn't buy an apple computer, let alone the most recent, to develop apps for the iphone.
I wanna be a eunuchs developer! Pass me a bread knife!
EXACTLY!
-
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.
Christian Graus wrote:
I can't imagine that there's more than 20 people in the world, developer or otherwise, who care about a windows phone.
:laugh: That's exactly my point. How do they plan to get 10 developers in the world to care about it if they keep making it about the desktop OS.
-
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.
When Microsoft announced last year that they were discontinuing support for XP, I guess they meant it. I have friends who are clinging desperately to XP like a guy who refuses to replace his beat up Gremlin with a newer car. What it's about is evolution...like biology, tech and software evolve as well. It would require a massive amount of overhead to maintain support for XP as well as Vista and Windows 7. Every piece of software would have to be customized for 3 OS's. However lame that may seem to XP users, it makes good business sense in the long run.
-
When Microsoft announced last year that they were discontinuing support for XP, I guess they meant it. I have friends who are clinging desperately to XP like a guy who refuses to replace his beat up Gremlin with a newer car. What it's about is evolution...like biology, tech and software evolve as well. It would require a massive amount of overhead to maintain support for XP as well as Vista and Windows 7. Every piece of software would have to be customized for 3 OS's. However lame that may seem to XP users, it makes good business sense in the long run.
This was one of the better arguments against supporting XP I've seen so far. And yes, this might make sense on the long run but in the short term as MS struggle to get relevance on mobile market, I'd say let the Desktop OS team worry about that, not the mobile one, I think that after many failed attempts to build up its market share on the mobile market, that doesn't really sound too smart. However, I don't have numbers to support my opinion, so I don't really know the impact of excluding XP as dev environment in WP7 app availability. I also don't know the amount of impact the app availabilty plays on the market.
-
Well XP is an 8 year old OS and is certainly not suited for writing code targeted at a modern day mobile device. I wouldn't blame them for not supporting XP.
Regards, Nish
My technology blog: voidnish.wordpress.com
Nishant Sivakumar wrote:
XP is an 8 year old OS and is certainly not suited for writing code targeted at a modern day mobile device.
How so? You can write code for anything on any operating system, because the OS has got absolutely bugger all to do with writing code. I work in Windows (XP or Weven) with C and Java code that will be run on Solaris and Linux machines. Going by some of the comments in this thread, code for Weven Phone should be written exclusively on the phones themselves! If MS can't provide an SDK that can be used by developers without the expense of buying new hardware or operating systems, then they don't deserve the effort those developers would put into writing the apps that will sell their phones for them. It's like games consoles: If devs don't write stuff to run on them, they won't sell.
I wanna be a eunuchs developer! Pass me a bread knife!
-
When Microsoft announced last year that they were discontinuing support for XP, I guess they meant it. I have friends who are clinging desperately to XP like a guy who refuses to replace his beat up Gremlin with a newer car. What it's about is evolution...like biology, tech and software evolve as well. It would require a massive amount of overhead to maintain support for XP as well as Vista and Windows 7. Every piece of software would have to be customized for 3 OS's. However lame that may seem to XP users, it makes good business sense in the long run.
brainflex wrote:
it makes good business sense in the long run
Sure, but in the short run, developers who could have been writing apps for the weven phone will instead be writing them for Android or the iphone.
I wanna be a eunuchs developer! Pass me a bread knife!
-
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.
The main reason is that the Development tools need Vista/7. VS2010 needs these newer OSes. They are not trying to force Windows 7 on users, the tools take advantage of parts of the OS that XP simply does not have.
-
The main reason is that the Development tools need Vista/7. VS2010 needs these newer OSes. They are not trying to force Windows 7 on users, the tools take advantage of parts of the OS that XP simply does not have.
Adam Benoit wrote:
The main reason is that the Development tools need Vista/7. VS2010 needs these newer OSes
You're wrong, I have VS 2010 on XP and use it with no problems at al.
-
Adam Benoit wrote:
The main reason is that the Development tools need Vista/7. VS2010 needs these newer OSes
You're wrong, I have VS 2010 on XP and use it with no problems at al.
But can you create Windows Phone 7 Apps? I'm guessing not because the Windows Phone Emulator requires Vista or 7 as per http://msdn.microsoft.com/en-us/library/ff626524%28v=VS.92%29.aspx[^] Operating system Windows 7 32-bit, Windows 7 64-bit, Windows Vista 32-bit, Windows Vista 64-bit. Note: Windows XP, Windows Server, Virtual PC, and Hyper-V are not supported. I Probably should have been more specific.
-
But can you create Windows Phone 7 Apps? I'm guessing not because the Windows Phone Emulator requires Vista or 7 as per http://msdn.microsoft.com/en-us/library/ff626524%28v=VS.92%29.aspx[^] Operating system Windows 7 32-bit, Windows 7 64-bit, Windows Vista 32-bit, Windows Vista 64-bit. Note: Windows XP, Windows Server, Virtual PC, and Hyper-V are not supported. I Probably should have been more specific.
Exatly, but I beleive it's not because of OS limitation as VS 2010 runs on XP (and the emulator on VS2010). It's just they aren't supporting the emulator on XP. That's exactly the problem
-
EXACTLY!
Go take a look at this link: How to install the Windows Phone Developer Tools on Windows Server 2008. You should be able to figure out how to install the SDK on WinXP from it.
Phil