[Sherlock]

OK yes, that works, if I scroll down the template list I see VSGDB stuff near the end, just wasn’t expecting it to appear like that.

I created a trivial blinker and it runs fine, all good.

Thanks for your patience!

[Sherlock]

One last post,  this is what’s at the bottom  of that .json file:

[Sherlock]

Apparently the latest version of SSMS (quite different to old familiar SSMS) is called v21 but it creates entries here:

Inside the JSON we see entries for SSMS v22, I’m not sure what this all means but it seems it leverages aspects of Visual Studio’s extension features.

This make me suspicious that something that isn’t Visual Studio, is present in a Visual Studio system folder and refers to 21 and 22…

 

• This reply was modified 1 month ago by Sherlock.
• This reply was modified 1 month ago by Sherlock.

[Sherlock]

Could somebody please confirm that the presence of Visual Studio Professional 2026 Insiders edition as well as standard Visual Studio 2026 Enterprise, does not lead to installation problems with VisualGDB 6.1.103.5547 ?

Also I have SQL Server Mgmt Studio vs 21 installed – could that in any way impact the installation of this VisualGDB extension?

Thanks

• This reply was modified 1 month ago by Sherlock.

[Sherlock]

Wow, OK I will attempt that when I get a suitable point, thanks.

[Sherlock]

This is what I see in VS2026:

But the extension is installed:

So I can’t see any Wizard, but I can in VS2022.

 

[Sherlock]

By the way the About VGDB appears in both VS2022 and VS2026

[Sherlock]

OK I can try that, I did have trouble installing it too.

I originally had an older version of VGDB ( bought it some years ago) and used that fine in VS2022.

A few weeks ago I was in VS2022 and saw an option to update or something and clicked it without much thought.

It said my license was not compatible with the update (fair enough, it was an old license) and I somehow aborted.

Today I decided to uninstall the old VGDB and install the latest 6.1r3 (trial) when I did that I get a series of two dialogs saying that reported “unknown major VS version: 21” and another for 22 I think.

I did a repair of VS2022 just to see if that was a factor.

I closed all VS instances and retried, I got the same two dialogs but the install did appear to work this time.

So now the only issue is the absence of the new project option in VS2026.

Should I just uninstall and reinstall as you suggest or is there anything you’d like to know/see before I do that?

 

Thanks

PS: I did some digging around the registry but saw nothing obvious and did not change anything in there.

• This reply was modified 1 month ago by Sherlock.

[Sherlock]

Thanks, but in the old versions page the most recent “old” version is 6.1R3 and in the history page it just shows 6.1, so should I assume the newest version is 6.1R4 ?

 

Many thanks

[Sherlock]

Hi, so if one is in VS with that solution open, how does one choose which of the two ways to publish the code to the board?

[Sherlock]

This was user error, After entering a friendly name, I was using the bright green down arrow and never noticed the smaller green check mark.

• This reply was modified 1 year, 3 months ago by Sherlock.

[Sherlock]

Thank you, I fully understand your position re: support costs.

I rarely find myself seeking support here so it would be money wasted I think. Although I’m a professional software developer (and initially studied electronics) I play around with these MCU systems for leisure purposes, hobby so to speak.

If I used this for anything more I would certainly renew my support.

[Sherlock]

Thank you Mr Flannery!

I’ve only ever used MSBuild based projects, so perhaps I need to move away from that.

Is that kind of project created using the “Advanced CMake” option when I create a new project?

• This reply was modified 1 year, 3 months ago by Sherlock.

[Sherlock]

The file stm32.props is referenced by the VS build settings and so that can easily be made part of a build configuration, but the file stm32.xml is not something I can find referenced anywhere…

OK it is referenced, the various .vgdbsettings files refer to stm32.xml and so I think this can be done with a bit of experimentation.

Perhaps there’s a case here for Sysprogs to expose this a build time option?

• This reply was modified 1 year, 3 months ago by Sherlock.

[Sherlock]

OK I got it, when we create two new identical projects but choose SRAM for one and FLASH for the other when creating the projects, only two files contain differences:

and

There might now be a way to define two configurations…

 

• This reply was modified 1 year, 3 months ago by Sherlock.
• This reply was modified 1 year, 3 months ago by Sherlock.
• This reply was modified 1 year, 3 months ago by Sherlock.

[Author]

Posts