SDK feedback - some choices for the next SDK in January (ish)
Hey guys!
Internally we are doing the planning process for the next couple of months and I am figuring out how and when we should release the SDK. We know that we want to release it in Jan - you guys have been waiting quite a while, and there is lots of good code stuff in the last almost-half-year that we have done.
Some questions, though:
1) We've been working on an API update to fix what we call the 'two-level' api. this describes how in the IR namespace (phx.ir.instruction, etc.) properties that only make sense for one particular operand or instruction type are pushed up to the parent class. is this API fix important to you? is it important enough to slip releasing the SDK by a month?
2) Do you think that you may want to use Visual Studio 2008 (ie, Orcas) in the future? is support for this important, or is it more important that we continue to support Whidby
3) If we do the API work and it turns out we may slip our SDK release by more then a month, are you guys okay with us dropping samples that we didnt have time to fix in the new SDK release?
Any other thoughts? We'd like to make our planning process more transparent so you guys can impact what and how we ship in the SDK - after all, we do it for you guys : )
Thanks,
Lin
すべての返信
Hi,
I for one think that support for VS2008 is important - since its the edition me and my colleagues are using on a daily basis. Ive tried to upgrade Phoenix projects made in VS2005 to VS2008 but unfortunately it does not seem to work, so official VS2008 would be fantastic :-)
Regards
Per
Technical University of Denmark
Lin Xu (MSFT) wrote: 1) We've been working on an API update to fix what we call the 'two-level' api. this describes how in the IR namespace (phx.ir.instruction, etc.) properties that only make sense for one particular operand or instruction type are pushed up to the parent class. is this API fix important to you? is it important enough to slip releasing the SDK by a month?
I would say that the API needs to start getting frozen, so if you think this is something that will need to be done eventually, do it now and slip the release.
Is there a scenario that's realistic that doesn't involve VS 2008? I think it's crucial to support 2008 and 2005.Lin Xu (MSFT) wrote: 2) Do you think that you may want to use Visual Studio 2008 (ie, Orcas) in the future? is support for this important, or is it more important that we continue to support Whidby
Lin Xu (MSFT) wrote: 3) If we do the API work and it turns out we may slip our SDK release by more then a month, are you guys okay with us dropping samples that we didnt have time to fix in the new SDK release?
So long as said samples are released back to the community in pieces, perhaps through CodePlex or some other channel, sure. Phoenix is a large enough piece of software that it needs as many samples as can be handed out, but let's not hold up the release just for that. :-)
Lin Xu (MSFT) wrote: Any other thoughts? We'd like to make our planning process more transparent so you guys can impact what and how we ship in the SDK - after all, we do it for you guys : )
How about a hard estimate? We're in to February now, and still no hard date for a new SDK drop.- I second the hard estimate part - if possible it would be nice to know when the new SDK will be coming.
- +1 for VS2008 and an updated release estimate.
The new SDK will require and work with VS2008. We just made the updates for VS2008 internally and are fixing a few install/build issues.
I realize it's taken longer than expected to get this SDK out, but we are closing in on it and should have it ready sometime later this month.
