Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Microsoft Visio 2013 Business Process Diagramming and Validation

You're reading from   Microsoft Visio 2013 Business Process Diagramming and Validation Using Microsoft Visio to visualize business information is a huge aid to comprehension and clarity. Learn how with this practical guide to process diagramming and validation, written as a practical tutorial with sample code and demos.

Arrow left icon
Product type Paperback
Published in Nov 2013
Publisher Packt
ISBN-13 9781782178002
Length 416 pages
Edition 2nd Edition
Languages
Arrow right icon
Toc

Table of Contents (14) Chapters Close

Preface 1. Overview of Process Management in Microsoft Visio 2013 FREE CHAPTER 2. Understanding the Microsoft Visio Object Model 3. Understanding the ShapeSheet™ 4. Understanding the Validation API 5. Developing a Validation API Interface 6. Reviewing Validation Rules and Issues 7. Creating Validation Rules 8. Publishing Validation Rules and Diagrams 9. A Worked Example for Data Flow Model Diagrams – Part 1 10. A Worked Example for Data Flow Model Diagrams – Part 2 11. A Worked Example for Data Flow Model Diagrams – Part 3 12. Integrating Validated Diagrams with SharePoint 2013 and Office365 Index

Creating the ViewModel class

We created new classes to mirror the relevant parts of the Visio Type Library objects, and all of the Validation API objects and collections. We prefixed these wrapper classes with VE for ValidationExplorer, which is the project name. The next screenshot shows the files in the ViewModel folder in the Solution window:

Note

When you select a folder in the Solution Explorer, then select Project, Add Class and so on, Visual Studio will automatically insert the folder name to the namespace of the class.

As the Visio objects are COM objects, you cannot bind directly to them successfully because XAML really needs to bind to dependency objects that can notify the UI of any changes that take place.

Therefore, we created a BaseViewModel abstract class that implements the System.ComponentModel.INotifyPropertyChanged interface; this will notify the client when property values are changed.

All of my wrapper object classes implement this base class. The wrapper collections implement...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime