Search icon CANCEL
Subscription
0
Cart icon
Close icon
You have no products in your basket yet
Save more on your purchases!
Savings automatically calculated. No voucher code required
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Microsoft Visio 2010 Business Process Diagramming and Validation

You're reading from  Microsoft Visio 2010 Business Process Diagramming and Validation

Product type Book
Published in Jul 2010
Publisher Packt
ISBN-13 9781849680141
Pages 344 pages
Edition 1st Edition
Languages
Author (1):
David Parker David Parker
Profile icon David Parker

Table of Contents (15) Chapters

Microsoft Visio 2010 Business Process Diagramming and Validation
Credits
Foreword
About the Author
About the Reviewers
1. Preface
1. Overview of Process Management in Microsoft Visio 2010 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

Creating the ViewModel


I created new classes to mirror the relevant parts of the Visio Type Library objects, and all of the Validation API objects and collections. I prefixed these wrapper classes with VE for ValidationExplorer, which is the project name.

Note

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

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

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

All of my wrapper object classes implement this base class. The wrapper collections implement the System.Collections.ObjectModel.ObservableCollection<T> class because this will provide...

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 ₹800/month. Cancel anytime}