Volume 2: Solutions and Publishing disclaimer


Deploy a Windows Forms solution that contains the Visio Viewer control



Download 0.72 Mb.
Page9/12
Date10.08.2017
Size0.72 Mb.
#31124
1   ...   4   5   6   7   8   9   10   11   12

Deploy a Windows Forms solution that contains the Visio Viewer control


The Visio Viewer can be used to view Visio drawings in native form (both .vsd and .vdx). The viewer is free and no license of Visio is required. Using the viewer the user can pan and zoom in the drawing and can investigate shape data on any shape. Pan and zoom is active and the user can toggle the visibility of layers.

Installing the Visio Viewer also provides a Visio Viewer control which can be embedded into a form or into a web browser and programmed against using the control’s automation interface. The automation interface allows access to some additional features of the drawing, e.g., the labels and values of all of the shape data can be extracted via automation.

However, the Visio Viewer cannot be used to edit the Visio drawing.

Deployment of a solution using the viewer control requires that the Visio Viewer be installed as a separate step before the solution using the viewer is installed.

The MSDN Office Developer Center contains a developer reference for Viewer.

Additional Resources

MSDN Office Developer Center - Visio 2010

All things related to developing with Visio. As new material becomes available, it should be posted here.

http://msdn.microsoft.com/en-us/library/ee839657(office.14).aspx



Overview of Add-ons and COM Add-ins in Visio 2007

Summary:   Learn the differences between Visio add-ons (.vsl and .exe files) and COM add-ins, and the benefits and limitations of extending Microsoft Office Visio 2007 with each.

http://msdn.microsoft.com/en-us/library/bb851468.aspx



Publishing Visio 2007 Solutions

Summary:   Learn about publishing content to Microsoft Office Visio 2007 by using a Microsoft Windows Installer (.msi) file and the Visio Solution Publishing Tool.

http://msdn.microsoft.com/en-us/library/bb677166.aspx



Using Universal Names and Syntax to Localize Visio 2007 Solutions

Summary:   Learn to use universal names and syntax in your code to localize custom Microsoft Office Visio 2007 solutions easily. Learn to access stencils, templates, and add-ons across differing locales.

http://msdn.microsoft.com/en-us/library/bb902804.aspx



Creating Visio Add-ins with VSTO 2005 SE

A nice summary of the issues from Chris Castillo’s weblog.

http://blogs.msdn.com/chcast/default.aspx



Deploying Visual Studio 2005 Tools for Office System SE Solutions Using Windows Installer (Part 1 of 2).

Summary: Learn how to deploy a Microsoft Visual Studio Tools for the Microsoft Office System solution using a Visual Studio Setup project to create a Windows Installer package.

http://msdn.microsoft.com/en-us/library/bb332051.aspx



Deploying Visual Studio 2005 Tools for the Office System SE Solutions Using Windows Installer: Walkthroughs (Part 2 of 2)

Summary: Read two walkthroughs about deploying Microsoft Visual Studio Tools for the Microsoft Office System solutions using a Visual Studio Setup project to create a Windows Installer package.

http://msdn.microsoft.com/en-us/library/bb332052.aspx



Visio 2007 Viewer Developer Reference

Provides important conceptual information for developing custom solutions for the Visio 2007 Viewer.

http://msdn.microsoft.com/en-us/library/dd392799.aspx



Deploying Solutions Review

Questions


  1. What tool is used for publishing localized versions of stencils and templates to multiple languages?

  2. How can you remove VBA project file information from a Visio document?

  3. True or False. A solution using the Visio Drawing control does not require the user to have a license for Visio.

  4. True or False. Failure within an add-on created as a VSL can cause the Visio application to also fail.

  5. What is the distinction between an object’s name and its universal name in the Visio automation model?

  6. True or False. The following line of code will work in all language versions of Visio.

  7. If objMaster.NameU = “Chair” Then HandleChairMater()

  8. True or False. The Visio Viewer control can be used to edit Visio drawings.

  9. True or False. The Visio Viewer control can be used to view shape data values.



Answers


  1. Visio Publishing tool available within the Visio SDK.

  2. Save the drawing as a .vdx file. Use a text editor to remove the XML tags and the project code.

  3. False

  4. True. To create an add-on that will not cause Visio to fail use either an EXE add-on solution, a shared add-in along with a COM shim to create a DLL, a shared add-in created using VSTO.

  5. The universal name of an object in the Visio object model does not change depending on the target language installation whereas the local name can change.

  6. True. The universal name for the master shape object has been used instead of the local name.

  7. False

  8. True



Some Important Developer Features


This section covers the topics from the Trust Center and XML that are important for the solutions developer.
Objectives

After completing this section you will be able to:

  • Develop solutions using Theme Colors and Theme Effects

  • Identify the elements of the Trust Center and how they affect the ability of solution code to execute

  • Using the macro recorder as a tool for learning about developing with Visio and some of its limitations

  • Understand the changes made to DataDiagramML for Visio 2007

  • Understand the changes made to DataDiagramML to allow for data to be round-tripped between Visio 2007 and Visio 2003.




Download 0.72 Mb.

Share with your friends:
1   ...   4   5   6   7   8   9   10   11   12



The database is protected by copyright ©ininet.org 2024
send message
    Main page
techniques used
correct number
implied warranties
above example
text displayed
many features
rule applies
rule that
same document
content provided
possible values