Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ask HN: Who is using the .NET stack for their startup (2022)?

news.ycombinator.com

Post reply on HN
Print view View original

21–26 of 26 posts

Re: Ask HN: Who is using the .NET stack for their startup (2022)?

#21

Post by WorldMaker »

HeyLaughingBoy wrote: post #18
mdaniel wrote: post #16

Earlier quoted context omitted.

That's good to know, thank you. To help with the first part of my comment, upon which local system did you develop that product (and, I guess implied in that question is: was it just you, or were there other developers with their own workstation setups)?

Visual Studio on Windows 10. I don't know why you'd use anything else for a .NET project: it's by far the path of least resistance. I was one of 3 developers but the others were writing iOS and Android apps that interfaced with my Web product. That said, they had identical setups. Since the code was hosted locally on the Pi and we were all remote, they needed to be able to build and deploy my code also.

Anecdotally, I've been using Visual Studio mostly regularly since the original ".NET Version" of Visual Studio (~2002), and I'm increasingly closing it and just using VS Code and the dotnet command line tools. Visual Studio is definitely starting to feel its age/weight and between all the C# 10 language features (finally) removing boilerplate (things like namespace statements and global usings), I'm often feeling more productive in VS Code than in full Visual Studio. For hobby projects I've moved entirely to VS Code even for .NET.

I'm inclined to imagine that with extensions like SSH remoting in VS Code you'd probably have a better Raspberry Pi deployment and debugging experience in VS Code than in Visual Studio, if you gave it a chance.

Re: Ask HN: Who is using the .NET stack for their startup (2022)?

#22

Post by hoofhearted »

thehappypm wrote: post #17
hoofhearted wrote: post #13

We use .net core with a React Typescript frontend. Our production exe runs on bare metal Ubuntu instances behind NGINX.

How’s the performance? This seems like a terrific stack

The performance is insane, and the development tooling around it is pretty impressive as well. I can live debug the react frontend app in Visual Studio without any setup or config. The project builds and runs the same on every box from dev up to production, so no need for virtualization, or Vagrant or VirtualBox anymore.

Re: Ask HN: Who is using the .NET stack for their startup (2022)?

#23

Post by DarrenDev »

I am. The core app is a desktop Electron app with a .Net 6 backend. There's some communication with a web api, also written in .Net 6 and hosted on Azure, but the desktop app is the heart of the product.

Even though it's a cross platform Electron app I haven't built the Mac version yet - so I can't answer yet for any issues that might pop up there. (Only reason being I haven't got around to buying a Mac to test it on.)

Two reasons for using .Net. The first was it's what I've used most in the day job. Second is that a core sdk I need to use inside the app is .Net. Rolling my own in a sexier language would have added months or years to the development time.

Re: Ask HN: Who is using the .NET stack for their startup (2022)?

#25

Post by thehappypm »

hoofhearted wrote: post #22
thehappypm wrote: post #17

Earlier quoted context omitted.

How’s the performance? This seems like a terrific stack

The performance is insane, and the development tooling around it is pretty impressive as well. I can live debug the react frontend app in Visual Studio without any setup or config. The project builds and runs the same on every box from dev up to production, so no need for virtualization, or Vagrant or VirtualBox anymore.

If you have any resources or maybe a sample on GitHub this sounds great for my next project

Re: Ask HN: Who is using the .NET stack for their startup (2022)?

#26

Post by seektable »

In 2022 we use NET6, last .NET Core was 3.1 which reaches end-of-life soon.

Our SeekTable started as .NET Core 1.1 app 6 years ago, it was upgraded to 2.1, then 3.1 and now it is a NET6 app. Upgrades up to 3.1 were pain in the ass, API/SDK evolution was quick and not backward compatible, however last upgrade to NET6 was easy - this is more a change of the run-time version, as APIs are not changed anymore and become stable.

Post reply on HN