2 more detail
source | link

I have migrated a slighly larger solution with more than one feature and some assets deployed to the layouts folder from 2007 to 2010 and. I was happy with the out of the box experience in Visual Studio 2010 after I got used to it. The migration was a bit more manual than I expected at first, but overall, not overly complex. I recommend starting the migration with the Out of the Box tools to help build familiarity with them. That could reduce your future dependence on third-party tools that may not upgrade well or be maintained as well as full MS supported tools.

I have migrated a slighly larger solution from 2007 to 2010 and was happy with the out of the box experience in Visual Studio 2010 after I got used to it. The migration was a bit more manual than I expected at first, but overall, not overly complex. I recommend starting the migration with the Out of the Box tools to help build familiarity with them. That could reduce your future dependence on third-party tools that may not upgrade well or be maintained as well as full MS supported tools.

I have migrated a solution with more than one feature and some assets deployed to the layouts folder from 2007 to 2010. I was happy with the out of the box experience in Visual Studio 2010 after I got used to it. The migration was a bit more manual than I expected at first, but overall, not overly complex. I recommend starting the migration with the Out of the Box tools to help build familiarity with them. That could reduce your future dependence on third-party tools that may not upgrade well or be maintained as well as full MS supported tools.

1
source | link

I have migrated a slighly larger solution from 2007 to 2010 and was happy with the out of the box experience in Visual Studio 2010 after I got used to it. The migration was a bit more manual than I expected at first, but overall, not overly complex. I recommend starting the migration with the Out of the Box tools to help build familiarity with them. That could reduce your future dependence on third-party tools that may not upgrade well or be maintained as well as full MS supported tools.