Cryptography: strange msdn sample code, help please....

Question

Apparently that line of code does nothing, to continue the discussion
I would like to know your guys opinion of MS and the level of security they provide, I assumed everything was top-notch, but looking through their usage of their own libraries it appears they are incompetent.
Can I get some opinions on this, I have updated the question to a discussion
ORIGINAL QUESTION - EVERYTHING BELOW (irrelevant):
I have been able to create a complete class for network server and client TCP/IP unlimited secure data transmission using RSA/AES (.NET framework cryptography only), and am implementing an EC/DH version  (.NET framework cryptography only). Everything
is working ok, I was just curious: on the VB example on this page:
https://msdn.microsoft.com/en-us/library/system.security.cryptography.ecdiffiehellmancng.aspx
What is the purpose of this line:
Dim k As CngKey = CngKey.Import(bob.bobPublicKey, CngKeyBlobFormat.EccPublicBlob)
On this page in the VB example??
EDIT reason: forum bug correction
EDIT2: I have noticed that the people writing the msdn samples do not understand the underlying cryptography, mostly based on their naming of variables. For the most part their usage follows the federal standards. Should I be worried that MS might not be
properly implementing the .NET cryptography algorithms?

Answer 1

You have completed the class and everything seems fine, you sent several GB of data through the class and it appears to be as secure as the RSA version. However, you found a line in a sample that isn't needed so you are concerned that they may be incompetent
and the .NET crypto libraries may not be secure. Is that an accurate description ?
I listed a single example, I have found dozens of them - including many examples which break the security rules and no information is given that it is doing such.
Did you have any opinion or you just want to stir up arguments???
I think the code is fine. I programmed a windows phone application myself and the samples are okay but most of the Microsoft samples are starter points and in some they clearly state that and not to use the code in production machines (if you have not noticed
that in the MSDN programmer documentation you probably are new to Microsoft programming or have only been programming a few years on their platforms). This excludes the GUI controls included with some of the samples for windows application which
are expected to work. They are one of the few and only rare exceptions to this rule. vb.NET 0.0 is right Microsoft is slow sometimes to stay modern but the libraries are effective.
Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth. - "Sherlock holmes" "speak softly and carry a big stick" - theodore roosevelt. Fear leads to anger, anger leads to hate, hate leads to suffering
- Yoda. Blog - http://www.computerprofessions.co.nr
BTW, COM is still a pain and the device drivers/kernel components are becoming better in Microsoft software but its a good progression right now.
Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth. - "Sherlock holmes" "speak softly and carry a big stick" - theodore roosevelt. Fear leads to anger, anger leads to hate, hate leads to
suffering - Yoda. Blog - http://www.computerprofessions.co.nr