Little changes: Published assembly paths are relative to the deploy manifest
It's been crazy getting everything done to get Whidbey out the door. Some small changes have occurred in the past month or so that I'm going to blog about.
One change we made recently was that published assembly paths are now generated relative to the deploy manifest location rather than to the application manifest. So if you publish a VSTO application and the deploy manifest is at http://myserver/apps/deploy.manifest and you look at the app manifest in http://myserver/apps/deploy.manifest/1.0.0.0/app.manifest you will deep dependentAssembly paths that look like this "1.0.0.0/dll1.dll" rather than this "dll1.dll".
