|
Thanks!! But this:
"The Windows Phone Developer Tools are not officially supported on operating systems other than Windows Vista or Windows 7. In between the CTP and the CTP Refresh, a block was added to setup to prevent installing on Windows Server 2008 to help enforce this support limitation."
is what I'm talking about. It boggles my mind. Yeah, I know they are not supporting it, therefore not allowing to install. But they don't need this. Add a few lines on License Agreement and MS is off the hook.
|
|
|
|
|
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.
|
|
|
|
|
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
|
|
|
|
|
Try running 3ds Max, photoshop, OpenOffice, Visual Studio on a PC with Windows 7 and only 4GB of ram and you'll see.
|
|
|
|
|
ed welch wrote: 3ds Max, photoshop, OpenOffice, Visual Studio
ed your a bloody masochist, you have just named 4 of the most resource hungry apps invented and you want to starve the memory as well.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
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.
|
|
|
|
|
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
|
|
|
|
|
Yes, just opening the apps is no problem - the problems happens when you start using the apps (i.e. editing reasonable size scenes and images)
|
|
|
|
|
you want me to believe that running these on xp is better?
You cant outrun the world, but there is no harm in getting a head start
|
|
|
|
|
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.
|
|
|
|
|
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.
|
|
|
|
|
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.
|
|
|
|
|
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.
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.
|
|
|
|
|
Just the ones who write the really important apps like...um...iFart.
Apple has what a gazillion apps available, 15 of which are useful?
|
|
|
|
|
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.
|
|
|
|
|
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 
|
|
|
|
|
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!
|
|
|
|
|
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.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
