|
Now you are spoiling the fun 
|
|
|
|
|
When MS get it right, they get it very, very right - and everyone else in the field should learn from them and improve. And Visual Studio has been very, very right for a couple of decades now.
Trouble is they tend to not know when "it's right" and try "gilding the lily": generally they make it worse, not better. Remember the Ribbon? So wonderful that "we'll put it everywhere!" - except even their own devs said "not on this one, pal." 
I just wish they would stop adding "features" and fix some of the older, more annoying bugs ...
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Well, you have to keep releasing new versions to make more money 
I think there is also a culture in software development that you always have to have new versions with more and better features, when sometimes that isn't necessary. Like you said, it happens that products get worse by 'overdoing' it.
|
|
|
|
|
Jacquers wrote: Well, you have to keep releasing new versions to make more money
They would make waaaay more money with "stability releases" or "really hearing devs releases" than with "new buzzword bingo releases"
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Jacquers wrote: I think there is also a culture in software development that you always have to have new versions with more and better features
I fight this all the time, especially with web (ASP.Net) development. If I had my druthers, I'd keep it all at .NET 4.0 using only native components. I still prefer VS 2010 over the newer versions mostly since it seems faster for builds/debugging.
Lately, I've been forced to upgrade due to a slew of widgets we bought a couple of years ago, mostly for the reporting tools...but they only work on .net 4.6 and better. It's not uncommon at all for me to have VS 6, VS 2010, 2017, and 2019 all running at the same time. 
"Go forth into the source" - Neal Morse
|
|
|
|
|
Me too! I have VS6, VS2015, and VS2017 going.
VS2017 loads and runs my solution just fine and it loads faster. But whatever happened to the "Bookmarks" feature?
Is it there and I just don't know how to activate it?
If you know, please reply/comment.
Member of the Evil Empire since 1976.
|
|
|
|
|
I too run many versions of IDE: VC6, VS 2013, and VS 2017. Would love to eliminate VC6. It is tricky to install under Windows 10 (See: https://www.codeproject.com/Articles/1191047/Install-Visual-Studio-on-Windows). The VC6 debugger is also an issue under Windows-10. Unfortunately, the project won't compile on newer versions. It includes a Microsoft module that is now obsolete and unsupported.
|
|
|
|
|
I just checked both VS 2017 and 2019 and the Bookmarks are there under the Edit menu. I've never used them, but after understanding what they are, probably will in the future. 
"Go forth into the source" - Neal Morse
|
|
|
|
|
|
Visual Studio bookmarks are very useful, I use em every day. Whenever I know I'm going to have to do some exploring to figure out what to do, I set a bookmark on the code I'm working on, and no matter how far I have to go I can get back by hitting F2 .
|
|
|
|
|
Windows - Visual Studio: I'll agree 100%
Linux - Visual Studio Code (C# / Glade -> Gtk3):
- The Glade is fine, and can be hooked into vscode with External Editor
- vscode - not so much. (Admit too spoiled by how easy Win-VS makes things)
It's called an "IDE", but too often have to go outside the IDE (command line!) to get things done. It's not an IDE, it's a PDE (partial)
simple task like adding a reference, if it's not in git (i.e. self downloaded library) have to manually update the csproj and .json(s) (manually key the whole path and dotted version etc).
It's also only one project per solution (directory) (- really not a full *solution* DE at all.)
the intelisense will tell you things like say the event handler xxArgs parameter is the wrong sort, but will not tell you what it's supposed to be, highlight problems but often won't un-highlight when fixed, other problems nothing or even bogus problem info, auto-popup method variants but just disappears them when you up/down arrow to scroll the choices...
... and so many other stupid/completely different things compared to the full VS inteli
-----
yes I'm way too spoiled by full vs,
after that using vscode feels like trying to fix a squeaky door with Jeremy Clarkson's tool and skill set's.
- but which is the newer "more up-to-date / latest and greatest" product again?
yes MS have SOME good tools, they also have their own share of crap ones too.
pestilence [ pes-tl-uh ns ] noun
1. a deadly or virulent epidemic disease. especially bubonic plague.
2. something that is considered harmful, destructive, or evil.
Synonyms: pest, plague, CCP
|
|
|
|
|
VS Code works well for things like Angular development. I haven't tried it as a full IDE for C#, but I don't think it will be quite as good as Visual Studio and I don't think it's meant to be.
|
|
|
|
|
I'm trying to learn Razor Pages for a work project. It needed .Net Core 3 which is not supported in VS2015 / VS2017 (latest versions on PC at work). So, at home, I tried it on my home PC from VS Code and .Net Core 3 downloads and works (once I had decided to ignore the large texts saying it was for VS2019 only).
|
|
|
|
|
I was introduced to VS early on in college, and using any IDE afterwards just felt, "meh." VS just has a nice feel to it. Thankfully, I get to use it professionally, and make a point to use it for hobby projects. Another IDE I like, though mostly for tinkering, is Spyder, though it's not as pretty or user-friendly imo.
|
|
|
|
|
Spyder looks decent from the screenshot.
SharpDevelop wasn't too bad, but became mostly obsolete when the free VS Community Edition became available. MonoDevelop doesn't look too bad either.
|
|
|
|
|
I used MonoDevelop a few years ago for some small Unity projects, and it did the job well, but I still know little about it. At some point, I made the transition to using VS for Unity.
Just looked up MD's screenshots, and I kinda miss that UI. Might have to give it another whirl.
|
|
|
|
|
It's incredible how experiences vary, I started with random IDEs and then tried Android Studio and I was amazed, now that I'm writing c# I can't not use Rider, VS feels slow, when I used it for the first few weeks by itself and it was constantly hanging.
Now I kinda use them both, because Rider has a lot less features, obviously ones that are used less frequently, so I write in Rider and edit configs, dependencies and such from VS.
I hope the JetBrains guys will try to achieve feature parity but... yeah, that's going to take a while, assuming they're aiming for it and they don't intend it to be use like I do
|
|
|
|
|
I used AS for one semester for an Android App, and my biggest complaint (that may or not be the fault of AS explicitly) was that the emulators just never functioned correctly. Debugging just became this giant rodeo and a nuisance. Once I found out that I could debug from my own personal android device, things went much, much smoother.
My disdain for it might also be partly because that semester was supposed to be a group project, and it largely became a, "my" project. 
|
|
|
|
|
I can absolutely relate to the "group" project part, sadly
I didn't use the Android emulator very much, since I was developing Flutter apps on a mac and the iOS emulator was so much better
|
|
|
|
|
I've been using Visual Studio for 23 years (it was called Visual C++ 4.0 back then), and it did have its issues, and it's still far from perfect. But it's the best software development experience I as a professional software engineer can imagine.
|
|
|
|
|
I've been using VS since it was called Visual Interdev when it was introduced to the UK in 1997 (I was at the launch event in London). I use it full time for web development. Then it was VB, then WebForms (big mistake) and now C# and Razor. The one thing that's REALLY hacked me off with it, despite bringing it up time and time again with MS is the fact you cannot totally switch off code formatting. It is definitely the case that I expend more key strokes correcting it's auto-formatting than I do writing code. It's such a pity. I think it's probably to do with the fact that Razor files contain multiple languages (HTML, C#, JS and poss CSS). Even simply cutting and pasting a piece of SASS, or JS or C# in file ends up with the whole file reformatted. Luckily Ctrl+z corrects it and then you can do what you wanted originally with it.
I think MS assume we all write code from scratch so their formatting is fine. But if you're constantly dipping in and out of loads of projects from all over the place, all with different formatting then you want to do it yourself. If any MS devs are reading this, PLEASE SORT THIS OUT. I have no respect for people that just rush onto the next eye-catcher that(let's be honest) hardly anyone uses, when you don't sort the basics out that effects everybody.
I feel better now
|
|
|
|
|
Here here!! While I generally agree VS is a top tier IDE. I want a moment on the soapbox..
How about bring back temporary projects. I got very spoiled with that feature and then they dropped it in vs2019. They claimed it was dropped because useage metrics deemed no one used it.. yet it immediately got feedback. I called out what usage metrics they could have possibly gotten to make this determination (unless VS phones home your every click??).
What probably happened is temp projects doesnt fit the way they implemented the new start screen, which I find actually a bit clunky to spin up new projects than the old way. It was handy to spin up a console app, tinker with a snippet of code, and discard. No neee to save to a Temp folder and remember to clear it out. For that I still open VS2017 instances.
I'll step off the soapbox now before I go on about their recent trend extensions.
|
|
|
|
|
I remember being in a launch presentation when temporary projects was touted as the big new thing that was going to be really useful, and yeah, it was. So why drop it?
I just recently threw out the set of manuals that came with Visual C++ 1.0 that I bought with my own money. Those were the days
|
|
|
|
|
Yes. The auto-formatting is annoying. Gets it wrong too often. Would be better to disable it completely.
|
|
|
|
|
Yes you're right. MS tooling with C# in particular is way more developed than most other options.
Sadly though it this becomes less true for cross-platform UI and C#.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
