Video: How Do I: Develop a Document-Level Deployment for Office 2003? (Part 1)

Presenter:Steve Hansen

In this video, Steve Hansen helps you to understand how to develop a local Visual Studio Tools for Office 2003 document-level deployment.


The following text is a software generated transcript of the video. Click on a minute link to jump to a location within the video

Minute 0
By my name is Steve Hanson with office zealot com this video is how do I deploy it is still document level solution locally and this is the first of a multipart series since weird looking at document level deployments this uses office 2003 since the current version of the store does not support office 2007 document level solutions at design time look for that functionality in the upcoming release of Visual Studio took out a sample project here just a little hello world type thing a run at it in debug mode sickens you it does simply displays a little MessageBox on startup and this video doesn t really get into how to do the deployment is what s as how to understand how a planet works so the next version watch it builds on a project that does all the stuff but the first and
Minute 1
To an understanding of what makes this solution worked out as Visual Studio do it if I misinformation very helpful as you start building your own deployments so they are going to be debug folder so this is a project where when you build the project in Visual Studio dumps the assembly and the document out into this folder insurgency if I go out there directly open the document my assembly runs correctly so if you open up this document with the application manifest editor is a few more clues about how this solution is working so use the application manifest editor and open up the
Minute 2
So there s no deployment manifest with us with this document that thing you can see is the assembly path since there is no path here we ve only got the assembly name that means that the Visual Studio of the Mr runtime will look in the same directory as the document for the assembly so you might wonder while Canada s copy the document in the assembly into a different folder and have it work and when you try that you ll bump into the other social thing to know about this of appointments which is the cast policy or the security policies that allow the solutions to run saw this copy them into a different folder
Minute 3
Turn open up the document in LA open up these document customization is not available if the click details can see that failed to grant permission to execute so no to look at the cast policy that allowed the solution to run in the first place open up the net framework 2 0 configuration and go into the under the user node and you notice in the code groups as of this dough projects item this is where when you create a new project Visual Studio automatically traces cast policy for your and if he s make the window bigger you can see the path so you can find a solution without knowing what the Gwyneth
Minute 4
Sunday way if I go to the hello world VB dll item I can see that Visual Studio crater URL condition specifying the URL to the assembly and then granting that assembly full trust God to see that this cast policy is really gone to the specific location which is why can move it to a different folder and expect us item to run it also see that there is a policy on the debug folder itself so as an example to show how you could get that to run and just to test the security policy that that is why the solution is a running in a trade
Minute 5
Another code group and just go do this for testing would not recommend never doing this fact on name of a such as the seed is a lot better ways to do this but as you think about how to deploy locally and you want to allow the user to move the document around anywhere in the computer never run some people may think while one alleges create this type of cast policy where Jos trust anything unless you drive in and as you can see here this doesn t affect work but there s a much better way to much better way to do this is much more secure
Minute 6
So that because a little bit social so wide open when I go in and delete that cast policy then you would want to do this because it opens up it would allow any assembly to run an issue drive similar delete that I wasn t a delete the DLL because you really won t want to have users have to copy around the DLL anyway you want the mode to probably move that filed the hello world VB that XLS file anywhere in their computer and run but they shouldn t have to move the deal all around so the key to doing this is to use the application manifest editor and go in and update the assembly path of the embedded application manifest so that it points to a specific location
Minute 7
Salicylates since I m going to point it to where the assembly is residing in my debug folder and then they ll say that now I can move this document anywhere on my local drive here and open up and have it work so in this case on the piggybacking off of the cast policy that Visual Studio created which is allowing the assembly in the debut of folder to run with full permission and wherever I copy or save this document is always can refer to that assembly in that location and betray
Minute 8
At the permissions it needs to execute so I saved a copy of the document to DC drive if I navigate to that document and open it and it also runs correctly from that location solicitor really demonstrate the two things really need to be concerned about when doing document level deployments to a local computer that is Kat Kruk has policies that allow the family to run an embedded application manifest that specify where to find the assembly and in other video I ll show how to create a setup program that world take care of these two issues automatically so that you can deploy a document level solution to other computers without manually setting is a thanks for watching a great day

Click here to go to original video page