So, I've been wanting to move out of VS2003 for the longest time, and I finally have. I moved from Visual Source Safe to TFS 2010, VS2003 to VS2010, windows XP to Win 7 ... and I'm relatively impressed so far. Besides one glitch with crystal reports (its still in beta, even though VS is not), I've been happy with the changes.
It's been a few weeks, and I need to make some changes to a WM6 SmartDevice application. I open up VS2010, and get my project from TFS, it converts the projects and i get an error - something like "This project type is not supported" - WTF?! After doing some research, in what might be the _dumbest_ move for VS2010, MS decided to not support ANY Smart Device development with VS2010 except for WM7+.
Yes, So any Smart Device Project you must use VS2008 or earlier. This is ridiculous. It can multitarget the real framework, but not the compact framework? I know its not a big deal, but now I have to have VS2008 installed side by side for ONE project. And I know they say they run fine side by side but I've experienced many weird things with them installed side by side, especially when updates are applied, or, in my case, VS2010 was installed BEFORE vs 2008.
I'm just so frustrated. I think it was a _very_ bad move on Microsoft's behalf.
</rant>
It's been a few weeks, and I need to make some changes to a WM6 SmartDevice application. I open up VS2010, and get my project from TFS, it converts the projects and i get an error - something like "This project type is not supported" - WTF?! After doing some research, in what might be the _dumbest_ move for VS2010, MS decided to not support ANY Smart Device development with VS2010 except for WM7+.
Yes, So any Smart Device Project you must use VS2008 or earlier. This is ridiculous. It can multitarget the real framework, but not the compact framework? I know its not a big deal, but now I have to have VS2008 installed side by side for ONE project. And I know they say they run fine side by side but I've experienced many weird things with them installed side by side, especially when updates are applied, or, in my case, VS2010 was installed BEFORE vs 2008.
I'm just so frustrated. I think it was a _very_ bad move on Microsoft's behalf.
</rant>
Facebook
Twitter