.Net Std library for diagram component

[Abhishek Singhal]

Hello

Have a multi platform app which uses diagram in winforms/asp.net mvc / asp .net core.

Would like to make a .net standard library for model manipulation which can be consumed by projects of all above platforms.

Kindly advise

Thanks

[Gowtham Gunashekar]

Hi Abhishek, 

From the above query, we though that the requirement is a common library which needs to be used in all the frame works (Winforms/ asp.net mvc / asp .net core). We can able to provide a common .net standard library for MVC and core. But it could not support winforms. Since Diagram uses more Dom access to render the component in MVC and Core. But the Winfroms component rendering was completely different from others. So we could not able to create a .net standard library to use in all the frame works. If we misunderstood the requirement, Could you please provide more details? 

Regards, 

Gowtham G. 

[Abhishek Singhal]

Hi Abhishek, 

From the above query, we though that the requirement is a common library which needs to be used in all the frame works (Winforms/ asp.net mvc / asp .net core). We can able to provide a common .net standard library for MVC and core. But it could not support winforms. Since Diagram uses more Dom access to render the component in MVC and Core. But the Winfroms component rendering was completely different from others. So we could not able to create a .net standard library to use in all the frame works. If we misunderstood the requirement, Could you please provide more details? 

Regards, 

Gowtham G. 

Basically need classes like Group, Model, Line, Rectangle to be platform independent.

We should be able to interact with their object model (like adding nodes etc) in a business logic layer, common for all platforms. This would be ideally a .Net Std project.

During rendering, we should be able to use a platform specific library, which could be separate for windows forms and mvc or core.

Kindly advise.

[Gowtham Gunashekar]

Hi Abhishek, 

 

We can understand you requirement, but as we said earlier, we don’t have support for the .Net common library support and we don’t have any feature plane to implement that. 

 

Regards, 

Gowtham.