Update My services documentation to clarify support in .NET 5+

[shethaadit]

Summary

This update clarifies which My services are supported in .NET 5 and later. A new section, "Supported My Services in .NET 5+", has been added to explicitly list the supported and unsupported My objects. References to relevant APIs and documentation have been included for better discoverability.

Changes:

• Added a new section detailing My services support in .NET 5+
• Listed supported and unsupported My objects
• Maintained existing structure while improving clarity
• Ensured proper <xref:...> references and documentation links

This update improves transparency for developers migrating to .NET 5+.

Fixes #40061

---

Internal previews

📄 File	🔗 Preview link
docs/visual-basic/developing-apps/development-with-my/index.md	Development with My (Visual Basic)

[BillWagner]

Hi @shethaadit

There will be a delay on review for this PR. I want to check with @KlausLoeffelmann (one of our VB experts) to discuss the wording. He's currently out of the office.

[KlausLoeffelmann]

The facts stated here are not correct.
Let's address those and go from there?

Thanks!

[shethaadit]

The facts stated here are not correct. Let's address those and go from there?

Thanks!

Hi @KlausLoeffelmann, thank you for your comments. I have updated the wordings according to comments. Could you please review again?

[KlausLoeffelmann]

I'd like to ping @paul1956 on this, if he wants to take a look?
I know there were other changes in contrast to Framework, like, I do not know, if all the device, sound, network support via My is implemented.

@paul1956 - do you happen to know by heart, what we have and what not?

@merriemcgaw: (OT) This could be another example to "crawl" an exact result, btw.

[paul1956]

I'd like to ping @paul1956 on this, if he wants to take a look? I know there were other changes in contrast to Framework, like, I do not know, if all the device, sound, network support via My is implemented.

@paul1956 - do you happen to know by heart, what we have and what not?

@merriemcgaw: (OT) This could be another example to "crawl" an exact result, btw.

@KlausLoeffelmann Everything that I have encountered in existing VB Application that use My is working in .Net 8. Nothing is missing NOW, to my knowledge there are some behavior differences see below. I have removed all my workarounds from .Net 5. I wrote a lot of tests last year to test much of the My code, not to beat a dead horse but the only area without any tests is UploadFile and DownloadFile. All my tests were run on Framework at some point to verify identical behavior.

UploadFile and DownloadFile with ProgressDialog works differently from Framework, In Framework cancelling a transfer using ProgressDialog will immediately terminate the file transfer. In .Net through .Net 9 the transfer will complete and then be cancelled, for download the file will be deleted at the end, for upload it will depend on the server.

If I misunderstood the question, please let me know.

[KlausLoeffelmann]

I'd like to ping @paul1956 on this, if he wants to take a look? I know there were other changes in contrast to Framework, like, I do not know, if all the device, sound, network support via My is implemented.
@paul1956 - do you happen to know by heart, what we have and what not?
If I misunderstood the question, please let me know.

No, perfect answer - thanks so much!
OK, so, given that we at one point HOPEFULLY will have the time to modernize the Up- and Downloading (and I acknowledge Paul's hard work here), I think we're good to go with this.

I'll ping @BillWagner. :-)

Thanks everyone!

[KlausLoeffelmann]

This is good to go now!
Thanks every one!

[BillWagner]

This LGTM as well. I'll