The future of component object models

Question

Has anyone heard that Microsoft does not support COM in future versions of Windows?

I assume that Microsoft engineers were stuck in it (even if they only preferred to develop and support the .NET platform), simply because of excessive backlash, it would come from their huge client base. There should be literally billions of lines of COM ballad in the wild. I know that I do not look forward to being pushed into mass migration simply because some smart pants that are superior to the architecture of the astronaut must prove that he is the Greatest ... (sheesh, why would they just go in for boxing?).

I suspect I'm just paranoid, but can anyone provide any official links (Google doesn't find much)? Ideally, Microsoft’s White Paper saying "COM remains in Vienna, or more!" soothe my nerves.

Answer 1

Well, the reason they are called .NET is because COM3 was taken as the serial port name .. NET is the new COM. Of . Runtime Uneashed Net Common Language :

Changing the name from COM3 to COR to COM + 2.0 ... to NGWS and finally to .NET.

The reason the primary assembly is called mscorlib is because it corresponds to the Microsoft Common Object runtime library.

Answer 2

COM is still a technology for inter-process communication. See how you can manage Word, Excel, etc. From another application. There is no way .Net can replace this.

Answer 3

COM and .Net serve different needs. As long as there is native code, a binary component standard is required, i.e. Com. Even if the OS was rewritten from scratch (which it will not, and should not), it will primarily be native code for reasons such as performance and version control. You would quickly need to come up with something like COM, so why not save the one that has been tested and works?

Answer 4

I know that it is easy to understand that the Microsoft world is .NET only from now on, thanks to the excellent work done by their marketing department, but Microsoft always supports its old things, they have no choice.

Look at MFC, they have released new packages, and RibbonBar works only on MFC (since it has an office). Of course, they will start writing more and more .NET code over time and less and less COM materials, but they will still support it.

Visual Studio's COM development capabilities will remain in place when they go, which when you know they no longer want us to use it.

I read a blog entry from the Visual Studio project manager where he said he received a lot of complaints from developers regarding the focus on C # recently. He agreed and said that the next version of Visual Studio would focus primarily on unmanaged development in C ++.

Answer 5

I can’t see COM disappearing anytime soon, since there is a huge amount of outdated COM code. For the same reason, I expect to see Win32 hanging around for the foreseeable future. Nobody cares about Windows as a platform; they care about their application software.

COBOL on S / 360, S / 370, S / 390, zSeries and C / unix remain very widely used platforms for the same reason.

Answer 6

There are no official statements that COM support is supported in future versions of Windows. It is widely used through internal OS components. Preventing a complete reinstallation of the OS from scratch (which I cannot imagine in the near future), we can safely assume that COM will be there for some time.

Answer 7

So, we summarize:

COM will remain because: 1. It works fundamentally 2. It handles interprocess communication, as opposed to inter-machine communication. 3..NET inherited a lot from COM, but not all. 4. Even Microsoft itself still relies on this.

And I confirm that in production systems there are still basilia of the FORTRAN and COBOL lines ... because they basically work.

Thank you all for your answers ... Fashion, do not hesitate to clear this spoken answer, but (IMHO) this site will be good for posters to publicly thank those who were not in a hurry to answer.

Greetings to all. Whale.