Whats the deal VCL.NET?

[InOut NET]

Can someone shed some light on why this exists?

[Nish Nishant]

Isn't that a Delphi thing?

Regards, Nish

---

Nish’s thoughts on MFC, C++/CLI and .NET (my blog)
My latest book : C++/CLI in Action / Amazon.com link

[InOut NET]

I think its the delphi version of .NET. They use the Microsoft (R) in the name. I dont get why they want to extend the VCL to be .NET compatible.

[Nish Nishant]

It's probably a library that's similar to the non-.NET delphi libs. Kinda like how VBers use a Visual Basic assembly that has a lot of class wrappers that make it all seem familiar to VB6 devs.

Regards, Nish

---

Nish’s thoughts on MFC, C++/CLI and .NET (my blog)
My latest book : C++/CLI in Action / Amazon.com link

[Lost User]

There you go ... Why VCL for .NET?[^]

[Robert Rohde]

Its purpose is to ease the usage of existing VCL components in .NET. See here[^]. Borland is pushing Delphi for .NET forward and this one is an important step. Robert

[InOut NET]

Do you recon Delphi developers care for .NET and have an urge/need to be .NET compatible? Universities bumped Delphi from their syllabus a while ago - new developers are mostly trained in C++ and C#. The focus group are clearly the older programmers. The 'important step' you mean converting old Delphi Developers, or recruiting new?

[blackjack2150]

With VCL.NET the migration of Delphi Win32 applications to .NET will be much-much easier than before. I find that a sufficient reason for VCL.NET to exist.