Our web project root...

Haha oh boy

😑this causes pain.
Can we just pick 1 naming convention today?

Wait... there's a Space in one of those folders 😱

@C0D4 jqwidgetsupdatednew
Jqwidgetsnewupdatedv7.6451.2
Jq widgets brand new DO NOT DELETE

@Owenvii I'm more of a
Jquery-widgets-v7.8/
type of guy.

@C0D4 ah thats neat, cool

Actually im more of a non existant file kinda guy

Ok, now I see how mine is "Only half bad" !

You're using visual studio (not code) for web development? a rare animal

@JoshBent Well, vs code is cool, but it’s like comparing notepad (the basic, not++) and sublimetext.
There are just too many nice features and integrations to pass on.
The project is a mix of MVC, webforms, SQL, TypeScript, SAAS.
I never need to leave VS. Wanna backup a database ? 2 clicks.
Wanna run SQL queries ? here
Wanna run a random C# code ? Here : Interactive C#
Need powershell ? Here
Need to see what controllers have exceptions in production based on AppInsights analytics ? Yep : here
I never need to leave IDE. Except write something. There is no good autocorrect for VS2019 ☹

@NoToJavaScript I've tried before the "universal hammer" solution, but it always lacks what separate tools do better (mainly because they have one focus only and not 50), especially with the amount of plugins atom/vscode have, that nuget can't replace or the amount of things dbeaver can do.

vsCode became a thing to begin with, because finally people could modify it to heck to do what studio never could, because of its locked interface, locked language servers, ..

but it does sound nice that you're able to use it as the one-stop, thanks for adding that :)

@JoshBent Yes I agree. The specialized tool will in most cases do it better for that one task.
But, If when you hire a new developer you need to spend 2 days to configure toolchain, it’s a no go.
And the moment you need something else (I needed powershell scripting), well you start by looking for addons. I just do file=>new=>powershell.
I guess it all depends on your project.
This project was built with visual studio in mind.
Debug out of box for everything is great !

@JoshBent (needed to slice answer in 2)
C# ? Sure. TypeScript ? No problems. Debug SQL directly on a server ? YEP.
Browser link so when you edit a SCSS file its auto applied without reload ? Yep
Publish your code to production ? 2 clicks
Unit tests ? 3 clicks. (Or 1 key bind)
Migrate production database ? 4 clicks (you get a list of changes after 2)
Basically, right now, using Visual Studio (for me at least) removes all need of devops.
I just looked on dbeaver. And I can do everything it does from visual studio without any plugins.
Again it all depends on what you want to build and how. My primary goal with this project was : Never need to leave VS. So of cause everything is working.

@NoToJavaScript that's what ansible is for or making a preconfigured image/backup of windows/linux/.. and then just restoring that image.

@NoToJavaScript "Publish your code to production ? 2 clicks" that should never be 2 "clicks" - CI/CD or make it a process that can't be accidental.

@JoshBent Lol they should really add info and examples on their landing page.
I read it, I still have no idea what their offering is. And then I saw “Red hat” logo. So it’s hard pass. They never produced anything usable without calling (and paying) their support every time.

@JoshBent Depends.
Why is it a problem?
Only master branch can be published in production.
No one (including admins) can commit to master
PR go through code review and tests (half automated, need more people !!!!!).
So when everything is green I find it good to be a manual click to deploy.

@NoToJavaScript

"need more people!!!" sounds like you're not using CI enough, though if you could elaborate further, maybe that'll clear it up.

Also in my opinion it's quite a discrediting opinion to call on red hat like that and to ignore ansible just out of spite, which is (only) one of the most powerful deploying / mass provisioning tools out there.

You also ignored the idea of just setting up all devtools necessary, backup/image that and then setup any new workstation with it.

@JoshBent RedHat: My personal opinion only.

This opinion is based on 6-month work with one of their products. (I don’t have a name. It was about 6 years ago. It was a Java pipeline to manage servers and surveil their state. It was a nightmare. It was a Russian Red Hat team what “supported” that project). I’ll come back if the name of the product enters my head. Well, also it was way beyond my Java/Maeven understanding.
Need more people refers to : We need more automated test coverage. Right now we have “some” unit tests (Coverage about 1% of code base or less) and an automated integration test (Which has about 1500 steps and covers about 25% of application).
I WANT to focus on it, but reality doesn’t permit it. Clients want functionality. Putting everything on pause to add missing tests = company dies. So we invest about 5% of time on that.
And I yes I know In a long run it’s bad. But it’s a choice between closing company or not

@NoToJavaScript Closing company today or tomorrow changes nearly nothing, it's like you're telling me "it's fine, we use always maxi pads, instead of helmets and cups filled with water in case the building burns down" lol.

Have you tried e.g. reinvesting a significant enough part of the money you get into people dedicated to implementing exactly that? you're wasting work hours and people on keeping the strings from pulling under your feet, which would be solved by proper implementation of CI+CD chains.

Regarding red hat, just because some ass hat (scnr) subdivision did some funny java stuff, doesn't discredit the entire company or all that comes out of it in the future.

Visual studio is for C# development, otherwise it’s not really that appealin

What. The fuck.

F