ASP.NET MVC - Developers - Facepunch Forum

I have been using it for quite a while now. Compared to my work in PHP I find working with ASP.NET much easier and cleaner to work with. Was curious how many other people use it, if it be in production environments or personal use.

I would assume most revisions of the new forums have been using ASP.NET, unsure how far back it goes since labpunch is a relatively old project. But you can take a look at the response headers for the forums and you'll notice that the server runs on ASP.NET MVC 5.2 (On Asure) If I was to ask anything, why would such an old version be favourable, or is it because it's the last version before Core?

Last I looked at the source code I saw he was using SignalR too, though this was a while ago when labpunch only had support for the rust forums. Would love to see the back end to this. I know how I would do it, but you can learn so much by seeing how others do their work.

I love everything about using .NET over PHP. It feels cleaner. Nuget has everything and makes life easier. Razor is nice to edit. Entity Framework is a revelation after manually typing mysql for 10 years.

asp.net gives me nightmares. I used to have to use it at a company I worked at. Never. Again.

ok...why? I find asp.net really easy to use and it has a lot of libraries like @garry said to be really useful and reduces revinvenintg the wheel.

It might be good mechanically but I just don't like using it. Probably a stupid reason but you know.

I have a love hate relationship with ASP.NET, but what they've been doing over the last couple years with Core is great. The problem with a lot of jobs in my area (Portland) is that companies are using ancient versions of ASP.NET that are really difficult to work with. If you start a new project give ASP.NET another try. It's come a long way.

Oh the joy of webforms. I remember working with it on my first project at my current job. It was such a mess of code.

You still at Microsoft?

PHP is good and bad for beginners. It's good because you can really easily set something up with minimal configuration. It's bad because it gives you so much freedom that it's very easy to start writing code that's all in one HTML file that's merged with PHP. Once you understand MVC then you will realize how much that organises your code, and how easier it is to manage.

I am kind of curious how you know this. I know I mentioned it a long time ago but surprised anyone would even remember, especially considering I changed my username from the old forums. However; nevertheless, I do still work at Microsoft.

Same avatar

Huh, not a huge poster, surprised you remembered.

I use ASP.Net MVC at work for everything. It's super comfy and publishing to Azure is e-z-p-z

It looks so much shinier than PHP, had the pleasure of working with a 5 year old PHP web app written by someone with questionable skill last year and I wanted to kill myself very quickly. (That whole job is a story that could fill a book) Unfortunately im stuck doing auto testing work, the asp.net is there but I'm only allowed to look....

It's pretty good to get going with. I was dropped into it head-first with no experience and had no problem getting up and moving with it. It's much nicer to work with than some of my previous projects.

Honestly don't know why you'd use ASP.NET unless you're a hardcore Microsoft developer. I guess there's .NET core now which makes it a lot more flexible. It just limits you to closed source technologies like Windows Server and IIS.

People should understand there's a huge difference between ASP.NET and ASP.NET Core. They're completely different frameworks, just like before with ASP Classic (the one that uses vbscript) and ASP.NET Personally, I think ASP.NET is awful but I love ASP.NET Core. They got rid of a lot of the crap: no more webforms, built in dependency injection, MVC/WebApi/WebPages are all merged into one now, etc. ASP.NET Core is separate from IIS and runs on basically any OS. And if you can help it ask them if you can use MVC instead of webforms

> And if you can help it ask them if you can use MVC instead of webforms I wish. To be honest, I haven't been paying any attention to any of the lectures. It's pretty basic stuff. Just gonna do the basic tasks they've given and call it a day.

I like Asp.Net. But my only other backend experience is php, and haven't used it for years. What's your preference?

How good is asp.net with linux?

Better be running Core or you're in for multiple types of fucc

My personal preference is Ruby on Rails. I love the Ruby programming language and Rails the framework is solid. Easy to throw pretty much anything together with it. Laravel is very nice for PHP though. WordPress a last resort if I need to provide an administration panel. Haven't found one better than WordPress'es to be honest. I hate working with it though as it's a pain to work with version control and git repos get pretty big pretty fast.

Little late but ill agree with that, ruby on rails is fantastic for getting something done really quickly. Me and a friend were selected to do a web app for a company through our university and decided that since we had such a small amount of time (like 3 months) to get what was effectively an employee/accounting/invoicing system done it would be a good idea. Between yeoman and rails we had so much scaffolding and pregen stuff done it worked out rather well, only thing is I had never used rails before so I felt like I flat out didn't understand how alot of it worked. I suppose thats the trap with anything that does things for you, not knowing what the things it does for you do can lead to really having a skewed impression of something.

Rails does a lot of 'magic'. It's very good at it, but it does it nonetheless.

True. I definitely did my fair share of 'put everything into massive un-maintainable PHP files' when starting out (until I learned about CodeIgniter, then it became massive views and massive controllers. What is a model?). It does help you build a solid foundation though and you'll begin to realise why proper MVC patterns make sense and how things work. I used to write PDO/SQL by hand, authentication systems and validations by hand (nothing in proper production, don't worry). Now I'm happy to let frameworks and libraries do the heavy lifting for me.

I think a lot of people struggle with asp.net for the same reason they struggle with a lot of microsoft stuff. There's a lot of confusion about it, their documentation sites are trainwrecks, there's not a ton of enthusiast adoption so tutorials are either out of date or don't exist. The biggest thing for me was that there's a whole ecosystem of technology that I'd never seen before. What's Razor, what's Entity Framework, is ASP a programming language? Am I using the right version? Is Razor what I should use or has it been superseded? How does clientside stuff interact, what's all the clientside javascript bullshit in Razor? That's a whole lot of shit to overcome when all you want to do is write a tiny hello world. With PHP you just install it and make a .php file and you're done.

Yeah sure, it's all preference, but preference isn't a random number generator in everyone's head, it's created by experiences.

Microsoft have never been good at naming or versioning anything, ever. .NET Core does add a bit more complexity seeing as it's pretty much a brand new CLR with its own compatibility rules. ASP.net Core is different from what MVC was and is practically MVC, Web API and Razor Pages rolled into one. It's nice having a portable application that you can run on Windows, Mac and Linux without having to fuck around with Mono. I'm pretty excited for the future of the .NET ecosystem though and there are a lot of cool things in the works such as Bladezor which is .NET running on the client using WebAssembly so you don't have to use any of that React or Vue.js shit.