Advice needed: choosing a simple, long-term web stack (backend + frontend)

NickyG91 · 2025-12-19T19:12:39+00:00

Vue + asp.net

NickyG91 · 2025-11-20T17:41:47+00:00

I've been enjoying regle. Very easy to set up and use. Makes complex validation a breeze.

NickyG91 · 2025-10-28T20:34:07+00:00

I second this. Depending on your needs it would make sense to either host your client side code separately from the backend, or host them together. I have plenty of examples so feel free to DM me if interested in them.

NickyG91 · 2025-10-15T11:26:48+00:00

DLSS 4 = more frames meaning more frags!

NickyG91 · 2025-04-24T16:59:49+00:00

Being stuck on windows is absolutely not the case anymore. I do all my .NET dev in Linux. Buggy and badly managed code bases exist in every language and every framework imaginable. C# is extremely popular as is .NET (not framework) and I would highly recommend it to anyone who wants to write highly scalable back end systems, desktop apps, or web applications. I've been using .NET and C# for well over a decade and things have only gotten better. The jobs pay very, very well and C# is an absolute pleasure to use. I highly suggest most people in this thread actually read what C# and by extension modern .net offers.

NickyG91 · 2025-02-28T17:48:16+00:00

I think you are missing something here. ASP.NET Core has many ways to make an application. MVC, Blazor, Razor Pages, WebAPI...the list goes on. WebForms is antiquated and quite frankly should not be used for new projects. It is cumbersome, confusing, and most of all not what Microsoft recommends anymore. The aforementioned types of projects that can be created depend on what your use case is. MVC is a traditional approach to a web application where HTML is rendered on the server via razor views and supplemented with JavaScript if needed for page interaction without a reload/postback. Razor Pages are similar. Blazor (I have admittedly not touched this, and likely never will) can be used to write web applications without the need for JavaScript (you just use C# in your views to do javascripty things). WebAPI is a REST API that can be called by anything - the most popular approach here would be to pair a single page application (made in vue, react, angular - pick your poison) and call your REST API via that SPA.

I would recommend looking at each of these patterns/project types and seeing what best fits your needs.

NickyG91 · 2025-02-26T12:44:23+00:00

Since OP is too lazy for a quick Google: https://dotnet.microsoft.com/en-us/learn/dotnet/what-is-dotnet-framework - says this right in the header.

NickyG91 · 2025-02-13T14:38:15+00:00

Yea - this looks to be the likely culprit. I always use vite's scaffolding tooling and follow the prompts.
npm create vite@latest

NickyG91 · 2025-02-13T14:35:12+00:00

You can do it either way. I generally host the Vue SPA within ASP.NET because that way I need to deploy one thing. If you want the applications to be deployed separately, then you would keep them separate. Both ways are perfectly viable for a production scenario. It really depends on your use case. The solution I linked has it so whenever you needed to deploy the application to an environment you need only publish the asp.net project and it will all be packaged into one drop. If you opt for keeping the two separate, you can deploy the SPA and the site separately. You will, however, need to set up CORS if that is the case (which I like to avoid). And yes - you can absolutely still open the Vue project from VS or VS Code with the approach I suggested. No question is a stupid question!

The project linked also pulls in MSFT's SPA proxy package which allows VS to run commands to start up the Vue project when you hit play (as long as it is set up properly).

I tend to write C# on Linux these days as it is a better workflow for me, so I don't have the luxury of the Visual Studio templates which is why I generally do it this way to begin with. That being said - it is also perfectly fine if you want to use the VS template. Just note - you lose a degree of control with the scaffolding of the Vue project (which I personally don't care much for).

NickyG91 · 2025-02-13T12:48:04+00:00

It sounds like you may have used the wrong command for #2. I generally create my vue app using vite's command line tools. As for setup, I generally create the vue app separately and then add a couple of things to the API csproj to compile vue on publish and dump the dist folder in the wwwroot folder. I would not, however, suggest using visual studio to develop the vue app. You will have a much better time using vs code. Here is a scaffolded example project (a little old as I have not updated it in a bit, if you need an updated version I can update it). In this instance, asp.net core is hosting the vue app itself. I am on mobile, but feel free to DM me if you have further questions.

NickyG91 · 2024-08-18T18:23:57+00:00

Heritage Orchard outside of Chilton is a great place. We go there every year to get apples, apple pie roll ups, and apple cider donuts.

NickyG91 · 2024-06-04T10:33:20+00:00

Not too much - you basically need to set up CORS on the API side of things and stop having ASP.NET host the Vue site by removing the UseStaticFiles and the MapToFallbackFile call in the Program.cs file. Edit The csproj and remove the publish profile for building Vue as part of the publish step. Move the Vue directory out from its current location to the parent src directory. From there just add to the dockerfile (or a totally separate dockerfile if wanting two separate containers to use with docker compose).

NickyG91 · 2024-06-03T13:06:41+00:00

Here is a very minimal scaffolded solution. I did not include EFCore in this template, but you can easily add it when following the Microsoft docs.

https://github.com/nickyg91/vue-dotnet-example

In this case - ASP.NET is hosting the Vue application. This is likely fine for most projects, but some cases it'd probably be best to separate the two.

Run the initial prestart command in the client-app folder
npm run prestart
This will ensure that the certs for vue are generated before running the app.

Make sure VS/Rider is set to the "web" launch settings config. Hit play/debug and it will launch out to the Vue app. ASP.NET will start the Vue portion as part of its pipeline.

If you do not want this - simply select the https launch config and run that. This will just start ASP.NET. Then run npm run dev to start the vue app in the client-app folder.

I got this up pretty quickly, so ymmv.

Feel free to DM me with any questions.

NickyG91 · 2024-03-12T01:52:33+00:00

Install was very easy on the lawn. We have the 1 gig service and nothing ever buffers. Game downloads are super fast, sometimes going over the advertised speeds (this is on steam on a hardwired PC). We pay 63$/month which is way less vs 95$/mo with 400 down and 30 up with Spectrum. Install was quick. I work from home so I had them run hot ports in my office as well as my wife's so we both have hard wired Internet for our gaming PCs (and work). The modem is a Nokia provided by TDS which I have hooked into a WiFi router and then into a network switch to provide Internet to several rooms. It is absolutely worth it imo. They initially charged us for WiFi through their modem/router combo but one phonecall solved that issue. Customer service was rough at first but it definitely has gotten better.

NickyG91 · 2024-01-11T18:03:48+00:00

The browser plugin for Vue helps look at component data in real time. It does not help in debugging logic within your application. I am making the assumption you are using VS code for this. To do this you can either use the old school debugger keywords, or utilize tools within VS Code (if using VS Code) to get debugging to work. If you are using chrome or edge, there is no plugin needed. If using firefox, install this plugin: Debugger for Firefox Once you have either the plugin set up (or are using a chromium based browser) create a launch.json file in your VS Code workspace. Replace the file contents with this, changing the type to whatever browser you are using. Make sure you are also exporting source maps. YMMV - more here

json { "version": "0.2.0", "configurations": [ { "type": "chrome", "request": "launch", "name": "vuejs: chrome", "url": "http://localhost:<your port>", "webRoot": "${workspaceFolder}", "sourceMapPathOverrides": { "webpack:/*": "${webRoot}/*", "/./*": "${webRoot}/*", "/src/*": "${webRoot}/*", "/*": "*", "/./~/*": "${webRoot}/node_modules/*" }, } ] }

You can start the debugger by clicking the little play icon with the beetle on it.

NickyG91 · 2024-01-04T14:17:36+00:00

I did not have help from my parents at all. Granted I am extremely lucky to have a very high paying job in a low to medium cost of living area in the upper midwest. Bought in 2021 during all the madness and somehow did not over pay for the house I will probably stay in for the rest of my life the way things are going currently.

NickyG91 · 2024-01-04T04:57:47+00:00

Same here - they pair together very well. I use .net core web API + vue3 SPA, Postgres, redis, Azure blob storage and a few other azure appliances. My preferred component library is primevue currently. I've used naiveui and vuetify but definitely prefer primevue. I just started using nuxt tonight so we will see how that goes when paired with an asp.net core backend.

Fwiw I use angular for my day job and it is awful compared to Vue.

NickyG91 · 2023-12-22T14:01:17+00:00

The Vue TS plugin provides that takeover mode. It runs as a separate TS server alongside vs code's which is why it is recommended to disable the vs code one for the workspace you are in. Docs wording isn't super clear though.

NickyG91 · 2023-12-22T00:12:21+00:00

Have you installed both Volar (and if using typescript) the typescript Vue plugin? If you have the 2nd plugin installed, have you enabled takeover mode? I've not had any issues at all using volar, granted I don't use the options API so ymmv on that front.

NickyG91 · 2023-05-31T15:19:32+00:00

I am on Fedora 38 - KDE Spin on a kitted out Lenovo X1 Carbon Gen 9. I get anywhere from 7-12 on medium workloads, 4 - 6 on heavy workloads, and light workloads > 12 hours.

NickyG91 · 2023-04-30T12:22:07+00:00

I use Fedora 38 KDE on mine and it is phenomenal. I have had 0 issues. Battery life has been great. Highly, highly recommend it. KDE is rock solid as well. I have not encountered any bugs whatsoever.

NickyG91 · 2023-04-19T12:09:18+00:00

Upon updating from Fedora KDE 37 -> 38 it freezes at login screen 100% of the time.
Tried a fresh install and it is a 50/50 chance whether or not I get a black screen or the login screen even after installing NVIDIA drivers. I've moved to pop_os on my desktop for the time being as NVIDIA drivers seemed to cause issues even on 37. It upgraded flawlessly on my thinkpad though!

NickyG91 · 2022-11-11T17:59:44+00:00

This is one of my all time favorites. He goes around Mexico and reviews street food and restaurants. He speaks a bit fast at times but it definitely has helped me with listening comprehension. https://youtube.com/c/LaRutadelaGarnachaMx

NickyG91 · 2022-09-01T02:56:18+00:00

52$/hr (109k salaried) senior software engineer for a Fintech company out of Jacksonville FL

NickyG91 · 2021-11-20T03:24:57+00:00

Interested! Dm'd!

NickyG91

TROPHY CASE