Visual Studio 2010 deployment script creates objects in wrong order - trigger after stored procedure
You may have run into a known issue with Visual Studio 2010:


Connect request
SO Question
MSDN forum thread


That said, Microsoft recommends you help Visual Studio detect the object dependencies it seems to be ignoring in its deployment script by:


  schema-qualify[ing] the names of objects that are involved in dependent relationships.


So if everything you are developing sits in the dbo schema, make sure to prepend the proc and view names giving you trouble with their schema name.  For example: dbo.MyView instead of just MyView. Visual Studio has a "Fully Qualify Name" feature under the Refactor menu when you right-click on an object that'll help you do that very quickly.

If that doesn't help, give Google a spin and take a look at some of the workarounds suggested on the pages linked above. Let us know what ended up working for you.