Topic: Bleeding Edge ....

[kdub_nz]

 . . . Well not really
It's been pretty well tested.

https://devblogs.microsoft.com/visualstudio/visual-studio-17-8-now-available/

. . .  this version is fully compatible with .NET 8, which is also generally available as of today.

https://devblogs.microsoft.com/dotnet/announcing-dotnet-8/?WT.mc_id=dotnet-35129-website

Enjoy

[It's Alive!]

installed it this morning

Works pretty good.

The sort #includes seems to just sort by alphabetical order. I don’t think it actually optimizes any dependency order. Probably okay for most things..  could be dangerous in some cases

Broke my toggle between headers and source ALT+O,
CTRL+K,CTRL+O works and I have my hot keys

I do like the linter for uninitialized variables, that’s been in for a while, the const linter seems new.
I also like the Code Analysis for C/C++, except it reports stuff I can’t change, like the ARX headers.

C++ 20 is the bomb, can't wait to try C++23 stuff!

 

[kdub_nz]

I've been using the Preview for the next version  . . currently VS 2022 Preview 17.9.0, prev 1.0

I've really enjoyed it , but my C# playstuff isn't as mission critical as your C++

It seems the C++ is really getting better and better each release

Next year will be interesting when AutoCAD starts using .NET 8.0 in place of Framework 4.8 for the plugins

Providing peer support will be a real bitch I think.

google searches may not be enough . . . really happy I decided to hate VB.

[kdub_nz]

Visual Studio 17.9 Preview 2 has arrived
They are getting there !

https://learn.microsoft.com/en-us/visualstudio/releases/2022/release-notes-preview#17.9.0-pre.2.0

Finally have  'Auto Surround with Quotes or Brackets' by default.

Intellisense is pretty good, and getting better each release.

.NET MAUI is starting to look interesting.

There has been a bit more work on
.NET migration documentation
Learn about migrating apps from .NET Framework to .NET.
https://learn.microsoft.com/en-us/dotnet/navigate/migration-guide/

added:
That probably sounds like something from '1984'

[MickD]

Not exactly related to the 'bleeding edge' but Visual Studio 2022 now (since 17.4) has the capability to run multiple repos in one solution....finally!

This is the main reason I just updated, haven't used them just yet (gotta git stuff done ) but this is very handy when you have a growing/changing in house library you use in multiple projects.

https://learn.microsoft.com/en-us/visualstudio/version-control/git-multi-repository-support?view=vs-2022

[57gmc]

If you are interested in finding out more about migrating acad projects, there will be a webinar on this from Autodesk APS. Note that you have to fill out an NDA.

[It's Alive!]

Version 17.8.3

The latest version screwed up my fonts and dialogs (the find dialog is way too small to see).
I love the gadgets, mostly, I need to find a convent way to toggle them when they start getting in the way.

The GIT tools are interesting, I haven’t tried them yet. Currently, while writing python wrappers, I have visual studio and vs code running side by side, both are notifying me of file changes, I end up using tortoise git to commit lol

I only have one .NET module published, .NET and I broke up after the announcement framework was being depreciated.
Still on the fence on whether to move it to .NET 8 or port to C++. Guess I should watch the webinar, see how side by side installs work.

[kdub_nz]

Next Year is going to be interesting.

Perhaps we'll need/should-have a new forum for .Net 8+,
Searching for solutions to version/pre-version issues may be a nightmare otherwise.

Answers from 15-20 years ago may not be valid any longer.

[It's Alive!]

Might be a good idea, “.NET Core”, it’s going to take a year or two for the clones to catch up.
From a CAD API perspective, nothing has changed right? It’s mainly everything else?

[kdub_nz]

I believe most code could be valid still.

It's just that there is loads of "new" code stuff in .NET5, 6, 7, 8 that may be smart to isolate from the Framework 4.7, 4.8

We're seeing people trying to use things like expression-bodied members in Framework 4.8 now (unsucessfully), so having code designated as requiring .Net8 C#12+ will save a lot of pain for cut&pasters and those that provide peer-peer support.