Hi
I've developed a Add-in for Microstation v8i with vb.net and I'm trying to figure out how to register key-ins so I can create a toolbar Icon to run my code from.
I've found some code in the programming wiki but can't seem to get it to work. Does anyone have any sample code for this.
Thanks
Dave
Hi Dave,
check this discussion, I posted there example C# and VB.NET addin projects. They provide information how to wrote "minimalistic addin with own key-ins".
With regards,
Jan
Bentley Accredited Developer: iTwin Platform - AssociateLabyrinth Technology | dev.notes() | cad.point
Jan,
So much for plans...I'm just getting back to this after three years. Is there a good example somewhere of how to write similar plug-ins for the Connect version of Microstation?
Daverode said:Is there a good example somewhere of how to write similar plug-ins for the Connect version of Microstation?
Things have changed. With MicroStation V8i, you were mostly calling into the VBA API from your VB.NET AddIn. MicroStation CONNECT has new .NET APIs DgnPlatformNet and MstnPlatformNet. However, those are not delivered with MicroStation, instead you must download the MicroStation CONNECT SDK.
The SDK delivers C# examples using those new APIs. I don't see any VB.NET examples.
Regards, Jon Summers LA Solutions
Daverode said:Is there a good example somewhere
as Jon wrote ... no :-(
It's important to realize that the main language for NET development is C# and VB.NET is (from more reason, some them are real and serious, some not) a seconday langauge, so often, not specifically when talking about MicroStation, examples are delivered in C# only.
But it depends on development skill: It's possible to check C# code, even if one is not able to write own C# code, and to follow the same structure and concept in VB.NET.
Alternatively it's also possible to compile C# examples (or to use some dll delivered with MicroStation) and to use decompiling tools like JustDecompile or .NET Reflector and to decompile back to VB.NET. It does not provide all information, especially how the original project was configured, but these details can be discussed as separate questions here.
Thanks for the reply. I could most likely figure out what to do based on C# code. I just need an idea of where to start. It's been a few years since I wrote the other programs we use, I'm just trying to get my head back into it. I was looking for the SDK in the download section and can't find it. Any idea how to go about getting that?
Thanks again,
Jon,
Thanks for the reply. Do you know where to download the SDK from? I can't seem to find it in the software download section.
Daverode said:Any idea how to go about getting the SDK?
I think that you, or your organisation, must be a member of the Bentley Developer Network (BDN). If you are a SELECT subscriber then I think that they will let you in. It's all a bit mysterious, what with having to know the secret handshake.
Try contacting bdn at bentley.com.
bdn
bentley.com
Thanks,
Glad it's just a handshake and not a tattoo or piercing.
Daverode said:Glad it's just a handshake and not a tattoo or piercing.
Well ... in my opinion it is not big difference ;-)
In world where a majority of companies actively hunt developers to motive them to use their platforms and tools, usually providing some amount of APIs and documentation for free (sometimes even as opensource), so anybody from students, hobby developers and employees developing in-house tools can quickly try and do something, Bentley policy is oppposite: To don't share anything publicly, provide no information and require to sign and agreement to receive an access.
In result, there are no students or hobby developers producing macros and tools for Bentley products and there are no candidates for professional top developers with deep knowledge of product(s) and API(s). Compare a number of tools available for MicroStation with any other product (not only AutoCAD, but Archicad, Rhine, QGIS...). When more products provide enough functionality for your project, what you will choose? What I see around me is "anything else than MicroStation", because for other products it's easy to download plenty of extensions or easily to hire somebody who will create such tool.
From this perspective, a small tattoo is much smaller problem...