Open Design File using .NET 7

Hi,

please follow the best practices and specify what product and version you use. To explain context (used API, whether you create addin or external application etc.) and what do you want to achieve is also recommended.

Ramakrishnan Sivasubramanian said:

I am not able to opendesign file using .NET 7 C# program.

It is not clear what product and version you use. You tagged your post with V8i C#, so I guess your question is about MicroStation V8i (SELECTseries <something>)?

MicroStation V8i used NET Framework 3.5, so when you wrote MicroStation addin, you must target the same version.

If you want to access MicroStation from another process, you should be able to use any technology and language that support Interop (or COM at least).

With regards,

  Jan

HI Jan,

I am using .NET 7 to develop an API to replace the text in design file . 

.NET 7

C#

V8

Is it possible to develop api using .NET 7 with V8 ? if not  , is it ok to proceed with .NET Framework 4.8 with V8

Note : I am adding microstation reference in my project

Thanks!

Ramakrishnan Sivasubramanian said:

Answer :  Bentley MicroStation 10.x Object Library 10.1

Are you sure you use MicroStation V8i?

Because of the version, it sounds more like a reference to some product based on PowerPlatform CONNECT Edition (like MicroStation CONNECT Edition).

Regards,

  Jan

To me, Jan is pretty clear, but if .NET 7 allows you program via 32bit COM (Because V8 is 32bit application) then yes you can write an external application to interact with MicroStation. Note: you may want to check your licensing for MicroStation, unless things have changed I'm pretty sure you are not allowed to write server based applications with a standard MicroStation license. Technically it could be done, legally, I'm not sure.

Since you show your reference as Bentley MicroStation 10.x Oject Library, that is not V8 but a CONNECT version of MicroStation which is 64bit. V8 would use a reference of Bentley MicroStation DGN 8.9 Object Library.

sorry its not server based application. just checking the possibility with .NET 7 instead of VBA. 

Ramakrishnan Sivasubramanian said:

just checking the possibility with .NET 7 instead of VBA

We can't answer your questions unless, as Jan requests, you supply consistent and accurate information.  Your answers so far have told us that you use either MicroStation V8 (32-bit) or MicroStation v10.x (64-bit).  Which is it?

What is the exact version no. (e.g. v10.x.y.z) of MicroStation that you are using? Use key-in VERSION to see the version no. in the MicroStation Message Center, or Help→About MicroStation in the backstage.

See this blog that shows you how to obtain MicroStation's version number.

If you're using an additional product (e.g. ProjectWise, OpenXxx) let us know about that too!

Ramakrishnan Sivasubramanian said:

just checking the possibility with .NET 7 instead of VBA. 

The problem is that when you use MicroStation V8i (which was not confirmed, as you reference 10.x object library), you use old unsupported  version.

MicroStation V8i offers C (with some C++ options in V8i SS3 and later) as the main programming environment, plus VBA/COM object model for VBA and NET, that is quite limited.

MicroStation CE offers new (main) C++ API and also new NET API, that offers less than C++, but the difference is not big.

So, when you are serious about MicroStation programming, to use C/C++ should be a primary option, but in CE, NET (specifically NET Framework 4.6) is sufficient for the most of projects. Anything else (VBA or current .NET) are limited or not supported.

With regards,

  Jan

got it.

.NET Framework and .NET Core are two different things. The highest version of .NET Framework is 4.8. So your mentioned .NET 7 must be .NET Core 7.0.

MicroStation V8i use .NET Framework 3.5 and MicroStation CE use .NET Framework 4.6. They don't support .NET Core.

Yongan.Fu said:

.NET Framework and .NET Core are two different things.

And to make the things more complicated, it should be noted .NET Core does not exist today :-)

.NET Core is old name, used until .NET Core 3.1 release, when it was primarily web platform technology, not offering desktop development feature.

When version 5, which includes also desktop technologies like WPF, was released, Microsoft changed the name to simple "NET" ;-)

Regards,

  Jan

And for convenience, announced and easy to sort out .NET and older .NET Framework version naming changes directly from the .NET 5 Readme. 

Thank you Jan & Bob. I need to update my knowledge.

But we know .NET 4.8 and .NET 5.0 are very different. This is why a lot of desktop applications still stop below .NET4.8.

Thank you Jan & Bob. I need to update my knowledge.

But we know .NET 4.8 and .NET 5.0 are very different. This is why a lot of desktop applications still stop below .NET4.8.