|
Switched from OneNote and Evernote to [Obsidian](https://obsidian.md/).
|
|
|
|
|
I use it for documentation. I have a suite of network automation tools and I use OneNote as a repository for each project from start to current. You can divide each project page into sections for troubleshooting, program purpose, change history, etc. I link in specific network folders for project files and documents. It is easy to navigate and search.
|
|
|
|
|
I love OneNote for dumping notes in. if you have the full office I would suggest adding on NoteHighlight it allows you to insert formatted and colored code in quite a few programming languages.
also using it to checkoff tasks or reminders, cheat sheets, locations of things on the servers....
my only issue is going back one in a while and cleaning up my notes.
If I ever leave this place, they are going to keep the OneNote backups safe.
|
|
|
|
|
I've used it before at work and it has a lot of features. However isn't it tied to the Microsoft eco system? Does it exist outside of Windows? I'm a big Notepad++ user, but I also save a lot of notes in a TiddlyWiki for various projects. Anyone else explore TiddlyWiki? https://tiddlywiki.com/
|
|
|
|
|
I used to - but after losing data through broken cloud synch a few times, I've given up. I'm using text files and markup(with images) - with a python script that indexes the lot. At least I can validate it's being saved and grep across the detail if I need to do a word search.
|
|
|
|
|
I use a 20yr old delphi tool called ActionOutline.
A Spell Checker and slightly improved export feature set would be welcomed... LOL
But for similar things. I take meeting notes, track things. It's multi-tabbed (multiple open projects).
And then it's an outline. Very easy to navigate.
In any outline, F3 lets me search downward from where I am.
I do store snippets of commands, SQL, etc. In some files, TODO items, Recipes. Etc.
Many many years ago there was a fancy tool.
the BIGGEST downside is that it is SO GOOD of an outliner, that I prefer it over everything. LOL
And then you go to use MSFT Project, and you LITERALLY WANT TO CHOKE SOMEONE!
|
|
|
|
|
My organization has dozens of small C# projects, compiled in every version of VS that has been published, and some have not been recompiled in a decade (not broken, don't fix it!). Unfortunately, as time marches on, the older code is less and less likely to compile successfully in newer versions of C#/VS. I'm looking at upgrading some of the programs to either VS 2019 or 2022.
Moving to VS 2022 provides a longer lifespan before it's sunsetted (01/13/2032), at which point I should be retired and it will no longer be my problem.
Is VS 2022 ready for usage, or does MS need to fix more things first?
|
|
|
|
|
Some of our devs are using 2022 now and they don't see any major issues. I think we will moving to it here soon.
for what it is worth, Microsoft is still fixing bugs with VS 2019. The VS IDE versions are never "really" ready for prime time.
|
|
|
|
|
Slacker007 wrote: Microsoft is still fixing bugs with VS 2019. The VS IDE versions are never "really" ready for prime time.
Very true!
|
|
|
|
|
VS 2017 seems to finally be stable.
|
|
|
|
|
...only because MS Devs are not really messing with it anymore.
|
|
|
|
|
We have been using it since the production release without any issues. You may have more issues moving to the new .net version than with VS itself. We are staying on .Net 4.8 with VS2022 for our desktop app, but we moved to .NET 6 for the Blazor app. No issues for us in either case.
|
|
|
|
|
GadgetNC wrote: We are staying on .Net 4.8 with VS2022 for our desktop app
The old applications are mostly desktop -- written in every version of .Net possible.
On the plus side, there is currently no listed end-date for .NET Framework 4.6.2, 4.7.x or 4.8. Current projects are all on 4.8, and I suspect all our older desktop applications will remain on 4.8 until they are rewritten, or until the end of time, whichever comes first (although "end of time" is more likely).
I assume others are facing the problem I am. How are you handling it?
|
|
|
|
|
I recently moved from VS2019 to VS2022 without any glitch.
Only one (very small) annoyance: if you keep both VS2019 and VS2022 installed, the solution file (.sln) is not automatically saved as a VS2022 solution and keeps opening in VS2019. You have to manually save it (Ctrl+S) to make it upgrade. Really small stuff.
Mircea
|
|
|
|
|
Right-click ⇒ Open With
Change the default from "Visual Studio Version Selector" to "Visual Studio 2022".
Tick the "Always open with this application" box.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
I know, but I still have a few solutions that are VS2019 and I'd like each one to open with the proper IDE. The thing with Ctrl+S worked fine.
Mircea
|
|
|
|
|
Visual Studio has been out since 1997. C# did not appear in it until 2003 2002.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
modified 11-Feb-22 16:04pm.
|
|
|
|
|
Rick York wrote: C# did not appear in it until 2003.
Technically, C# appeared in 1988, although that version was never released: 
My History of Visual Studio (Part 1) | Microsoft Docs[^]
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
It was designed in 2000 and first released in 2003 : C Sharp (programming language) - Wikipedia[^]
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
So where am I? Ah yes, 1988. The project I’d been hired to work on was cancelled after a few months (I expect I’m in good company on that score), that project by the way was a cute variant on the C language designed for incremental compilation – it was called, cough, C#. Strangely, through the lens of 2009, it looks remarkably like what you would get if you tried to make C.Net.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
 That was an excellent read!  Thank You!
(kept me from actually working for > 15 minutes at least!)
"Go forth into the source" - Neal Morse
"Hope is contagious"
|
|
|
|
|
Rick York wrote: C# did not appear in it until 2003.
My archives folder shows
VS6
VS97
VS2002 (.NET 1.0)
VS2003 (.NET 1.1)
VS2005 (.NET 2.0)
.
.
.
When mounting the ISO for VS 2002, I can see most of files have a timestamp of January 2002. This is where .NET was introduced. C# was very much part of it.
|
|
|
|
|
Yes, 2002 is the correct year. I had all of those versions of VS except for 2002. I never used that one. I remember joining the MSDN and getting NT when it was in beta and installing VS97 on it. The next several years were very enjoyable.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
 VS 2022 (page does not exist)
:squishing noise:
|
|
|
|
|
We migrated to it a week after release (always wait for at least the X.0.1 release!).
We've not had any issues at all with it - it's been remarkably smooth. It'll take up more memory because they (finally) converted it to 64 bit, but there's a number of gains that were realized because of that conversion.
We have a variety of applications as well, and solutions with over a hundred projects of varying types, though we've done pretty good at getting everything to be "standardized" on targeting either .Net 4.8 or .Net 6 (we did quick upgrades after release for all our .Net core based applications).
I personally like it quite a bit. They cleaned up the dark mode as well so there's no longer random bright glaring controls or panels running around.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
