title: How can I fix a VS_NEEDSNEWMETADATA error in Integration Services Catalog?
body: <p>I've recently switched from using Visual Studio 2010 to Visual Studio 2012, and from executing an SSIS package directly from the files on the server to using an Integration Services Catalog.  </p>
  
  <p>I am now the Integration Services Catalog execution is now failing because a new deployment of the package errors out with a VS_NEEDSNEWMETADATA error.  In my previous environment I would fix such errors by opening the offending data flow component and resaving the file.</p>
  
  <p>In the new environment I would have assumed that opening the component in Visual Studio, verifying that it is correct, saving the file, and re-deploying the package to Integration Services Catalog would fix the problem.  But now, the error persists.  </p>
  
  <p>I can manually execute the package from Visual Studio, which is what we've been doing for the last few days, but that's, er, not really a good long term solution.  ;)</p>
  
  <p>I'm willing to entertain the possibility that the deployment wizard isn't actually deploying the new package.  (I'm quite new with Integration Services Catalog), but I can't even seem to figure out how to determine the most recent deployment date from ISC.  </p>
  
  <p>Can anyone guess what is going on here?</p>
  
  <p>Thanks,  --sw</p>