New and updated VisualGDB Project and solution files

[gojimmypi]

Description

This is a no-code-change update that only adds VisualGDB project and solution files to the test and benchmark Espressif examples.

Fixes zd# n/a

Testing

How did you test? n/a

Checklist

• added tests
• updated/added doxygen
• updated appropriate READMEs
• Updated manual and documentation

[gojimmypi]

The failing PRB is not likely related to this PR.

[dgarske]

"+1,492 −28" -> My preference is for these to be in wolfssl-examples. The VisualGDB creates a lot of cruft for something very few people use. You are welcome to dispute my remark.

[gojimmypi]

"+1,492 −28" -> My preference is for these to be in wolfssl-examples. The VisualGDB creates a lot of cruft for something very few people use. You are welcome to dispute my remark.

Well, since you left the door open to discussion... :)

I certainly agree that there are more project files than desired. I reached out to the Sysprogs folks regarding the difficulties changing targets. As of now it is a known problem with no easy resolution.

My objective here is to make things as easy for the new user as possible. Having the project files for the different chipssets that are just ready to go is extremely convenient. Very little instruction is needed. This is much more likely to give a positive first impression.

I fully understand that development in Visual Studio with VisualGDB for embedded targets does not have as big of an audience as it could have. I'm trying to grow that audience. I want to show all those Windows developers that they can easily get into the embedded world using familiar tools. I happen to be working on Espressif chipsets, but VisualGDB supports over 1000 devices in a single IDE.

I plan to feature VisualGDB in my upcoming webinar. It is an incredibly productive tool.

To put the wolfssl Espressif example project and solution files in the separate wolfssl-examples would be awkward and cumbersome. I suppose we could duplicate the TLS client/server, test, and benchmark apps there... but having duplicate code and keeping them in sync is not very desirable.

I suppose we could cut the file count in half by omitting the solution .sln files, and perhaps even only include the most recent ESP-IDF versions. However it is nice to have the pre-defined Solution Items file shortcuts available for quick reference:

I could update the respective README.md files to inform the end users of the key files that may be of interest to add to the solution, such as the wolfssl user_settings.h if you'd be willing to have all the project files, but no solution files.

It's certainly possible to have just one project file per example (total)... but the instructions would need to be considerably longer.

Keep in mind I plan to also [propose to] add project files to the TLS client & server Espressif examples as well.

Given this information, please let me know what you prefer.

[gojimmypi]

Closing this lingering PR as the project files are typically updated with each example.