Recent Posts

Pages: [1] 2 3 ... 10
1
Network Diagramming / Re: find the shortest path between two shapes
« Last post by cliff50 on Today at 04:51:29 AM »
Wapperdude ...  I realized the yellow coloration is crucial  to a consistent outcome.  I am unsure if the distancing calculation is incorporated into the outcome in any way ... it appears not .. but I will follow the "yellow brick road"
2
ok, did a a bit of research and found a method that is used to calculate the shortest distance between 2 points, won't work for me here but has given me an idea about how this can be done .  My programming skills may not be up to it but I'll give it a go, thank you
3
Programming & Code / Re: Creating Visio extension with .NET framework CORE
« Last post by Nikolay on September 29, 2020, 06:39:37 PM »
That's why I'm asking - has anyone tried to build an extension in .NET CORE (in the title of the topic).
One clickable button could be good enough I guess. The main mess is COM registration I guess (i.e. actually making a .net core library a visio add-in)

Are .net core components registered the same way?
They are asking to run regsvr32 - this already looks suspicious, like something fishy is hapenning here, usually it's regasm for .net components. What is this .comhsot dll exactly?
Also, type libraries (.tlb) files are not supported. Will Visio load an extension that does not provide type library? And does not implement IDsipach, because it's also not supported in .net core (there is no DLR runtime)?
4
Programming & Code / Re: Creating Visio extension with .NET framework CORE
« Last post by Visisthebest on September 29, 2020, 05:19:51 PM »
“ Please port VSTO to .NET 5 (.NET Core). JS is no replacement for a real programming language and proper API, even if it is COM-based. I don't care that it is Windows-only, as that is already the case with VSTO, but having access to the many new features and performance enhancements in .NET Core would be huge. With the enchancements to COM Interop in .NET Core 3 along with Winforms, not much should be needed to port over VSTO.”

https://developercommunity.visualstudio.com/idea/757925/please-port-visual-studio-tools-for-office-vsto-to.html
5
Programming & Code / Re: Creating Visio extension with .NET framework CORE
« Last post by Visisthebest on September 29, 2020, 05:01:20 PM »
Nikolay do you have a link with more info about COM support in .NET Core / 5.x? Thank you!
6
Programming & Code / Re: Creating Visio extension with .NET framework CORE
« Last post by Paul Herber on September 29, 2020, 02:30:06 PM »
According to my experience, it's always not much work until you start actually doing it...   ;D

Everything is just a 5-minute job until you actually get down to it.
Once upon a time I got three 5-minute jobs done in one day!
7
Programming & Code / Re: Creating Visio extension with .NET framework CORE
« Last post by Visisthebest on September 29, 2020, 01:07:10 PM »
I hope not. Office add-ins are a key benefit of Office desktop, which has long term support. It would be a bad decision to drop a key feature.

A COM add-in in .NET 5.x plus making Ribbons manually still an ok compromise, if other COM add-ins cause issues this can be diagnosed and treated (other COM add-in removed).
8
Programming & Code / Re: Creating Visio extension with .NET framework CORE
« Last post by Nikolay on September 29, 2020, 12:21:49 PM »
According to my experience, it's always not much work until you start actually doing it...   ;D
My bet (one good whiskey bottle): Microsoft will deprecate (move to maintenance) VSTO in about 2 years.
Anyone?  ;D
9
Hi,
I guess my query isn’t specific to visio vba though the outcome of it would be used by my visio vba code (to link objects together) so hopefully this post is ok in this section.
My code needs to link various objects together which I think I know how to do.  However, if you think of the objects as milestones where the milestone is the start or finish of an activity (in a schedule) the objects that need to be linked to it are the successors, if that successor is part of a list of task IDs I have defined (and so would be an object on the chart), which belong to a schedule that may contain many more activities, typically thousands.
The tricky part here is that in a normal schedule each activity might have several, sometimes many,  successors.  If I want to know if one of my activities is linked to any of the others via any task in a schedule then I would need to follow the chain through every successor’s successor until I find it or until the chain ends (no successors).  This means there would be multiple branches and any number of task IDs in the chain.
This would be a very clever bit of code which I don’t mind saying is beyond my capabilities.  Has anyone here had the same problem / is there anyone out there that knows how to do this?  If so I’d love to hear from you.  My code is for my own benefit at work but I’m not expecting something for nothing.
For info,  my visio vba code opens an excel file that contains an extract from the Planning Tool i.e. all the activities, their IDs and their successors.  Another worksheet identifies the activities I use for milestones.  I don’t know whether it would be easier/better to have an excel macro that did this (using excel functions) and then populated the relevant worksheet which the visio vba could read or have the visio vba do it all.
Please get in touch if you can help me.
Kind regards
Matthew
10
Programming & Code / Re: UndoScopes and transactional integrity
« Last post by Visisthebest on September 29, 2020, 10:47:23 AM »
Yes you’re right that should not be proper behavior, but we thought of it as a test to understand the ‘transactional’ behavior of the undoscopes.

For instance, for our current solution it is essential that some data like the UniqueID is set in a shape, if a shape would be created but not properly initialized with data we want to set bcommit to False when running the endundoscope method:
https://docs.microsoft.com/en-us/office/vba/api/visio.application.endundoscope

to avoid creating a ‘corrupt’ diagram.

Pages: [1] 2 3 ... 10