useless fucking client bastards. i sent an email to all clients 2 months ago about gdpr and the impending deadline. Explaining that they need to update privacy and check webforms and internal procedures etc are compliant. I said I would help them implement any changes to their respective sites. Heard nothing from these fuckers... except this morning an email “what does the new gdpr mean for our website?”
FUCK OFF AND READ MY EMAIL, FOLLOW THE LINKS DO THE RESEARCH AND FUCKING SORT YOUR CUNTING SELVES OUT, I AM NOT YOUR FUCKING LAWYER.

At work, my closest relation is with the DBA. Dude is a genius when it comes to proper database management as well as having a very high level of understanding concerning server administration, how he got that good at that I have no clue, he just says that he likes to fuck around with servers, Linux in particular although he also knows a lot about Windows servers.

Thing is, the dude used to work as a dev way back when VB pre VB.NET was all the rage and has been generating different small tools for his team of analysts(I used to be a part of his team) to use with only him maintaining them. He mentioned how he did not like how Microsoft just said fk u to VB6 developers, but that he was happy as long as he could use VB. He relearned how to do most of the GUI stuff he was used to do with VB6 into VB.NEt and all was good with the world. I have seen his code, proper OOP practices and architectural decisions, etc etc. Nothing to complain about his code, seems easy enough to extend, properly documented as well.

Then he got with me in order to figure out how to breach the gap between building GUI applications into web form, so that we could just host those apps in one of our servers and his users go from there, boy was he not prepared to see the amount of fuckery that we do in the web development world. Last time my dude touched web development there was still Classic ASP with JScript and VBScript(we actually had the same employer at one point in the past in which I had to deal with said technology, not bad, but definitely not something I recommend for the current state of web development) and decided that the closest thing to what he was used was either PHP(which he did not enjoy, no problem with that really, he just didn't click with the language) and WebForms using VB.NET, which he also did not like on account of them basically being on support mode since Microsoft is really pushing for people to adopt dotnet core.

After came ASP.NET with MVC, now, he did like it, but still had that lil bug in his head that told him that sticking to core was probably a better idea since he was just starting, why not start with the newest and greatest? Then in hit(both of us actually) that to this day Microsoft still not has command line templates for building web applications in .net core using VB.NET. I thought it was weird, so I decided to look into. Turns out, that without using Razor, you can actually build Web APIs with VB.NET just fine if you just convert a C# template into VB.NET, the process was...err....tricky, and not something we would want to do for other projects, with that in we decided to look into Microsoft's reasons to not have VB.NET. We discovered how Microsoft is not keeping the same language features between both languages, having crown C# as the language of choice for everything Microsoft, to this point, it seems that Microsoft was much more focused in developing features for the excellent F# way more than it ever had for VB.NET at this point and that it was not a major strategy for them to adapt most of the .net core functionality inside of VB, we found articles when the very same Microsoft team stated of how they will be slowly adding the required support for VB and that on version 5 we would definitely have proper support for VB.NET ALTHOUGH they will not be adding any new development into the language.

Past experience with Microsoft seems to point at them getting more and more ready to completely drop the language, it does not matter how many people use it, they would still kill it :P I personally would rather keep it, or open source the language's features so that people can keep adding support to it(if they can of course) because of its historical significance rather than them just completely dropping the language. I prefer using C#, and most of my .net core applications use C#, its very similar to Java on a lot of things(although very much different in others) and I am fine with it being the main language. I just think that it sucks to leave such a large developer pool in the shadows with their preferred tool of choice and force them to use something else just like that.

My boy is currently looking at how I developed a sample api with validation, user management, mediatR and a custom project structure as well as a client side application using React and typescript swappable with another one built using Angular(i wanted to test the differences to see which one I prefer, React with Typescript is beautiful, would not want to use it without it) and he is hating every minute of it on account of how complex frontend development has become :V

Just wanted to vent a little about a non bothersome situation.

I love using C# 3 language on a .NET 2.0 WebForms application... Fml

I FUCKING HATE ASP.NET WEBFORMS

Legacy dev writes grid system....to use with bootstrap...what even?

Old story, happened some way back. I worked part-time for a small web development company that did between other things something called SharePoint development, basically .net webforms with shit glitter on top of it.

The most weird part of it, was the fact that we were working on vms that hosted the app, it was our dev, test and staging environment, as well as were we showed the client the polished turd.

Did I say that it was on a vm? Well it was on a remote vm, that each of use had access to it, through our domain accounts, and they couldn't configure the windows server to accept more than two or three users at once to be connected.

That was our test enviroment and dev enviroment, sooo showing the app to the client meant for the rest of us to not write any code because it might crash or get stuck.

The app was accessible and discoverable by url and through google search from outside, I dont think that should have been allowed.

The most disastrous part was that we had NO source versioning whatsoever, just plain old copy and paste in different folders.
Deploying to client meant remoting to the clients host or whatever it was, and manually copying the source files

If someone wanted to debug the application you had to shout, and you also could hear it, in the office: "I'm debugging!" or "I'm deploying!". Because we were on the same machine, there was only one process with the server and it meant that if you debug or deployed it would block it for the others.

Should I talk about code quality? Maybe not.

Which is worse? A shitstorm written in php 5 or asp webforms

3.5 fucking hours wasted. Trying to get a fucking webform to post using smtp and swiftmailer. Fucking webforms, I fucking hate them. Done it now though.

I feel like saying "I know C#" (or Java or other similar languages) to mean that you know it as a language as opposed to more of a framework is ridiculous. We should say what programming language level we know (high, mid, low...) since the difference between say C# and Java is pretty much the same as the difference between say WinForms and WPF. Depending on which two languages and which two frameworks you choose it can be a much bigger difference between the frameworks than the languages.
In a CV I'd like to say "I know x-level languages with experience in [actual programming language + frameworks]" instead of saying I know C# and then recruiters and HR people and such assume I don't know Java at all, but know MVC, WebForms and whatever else even though I might specialise in something else and would take me pretty much the same to get proficient in Java as it would take me to get proficient in that framework or something that's technically C#.
It just makes so much more sense to me. As a dev you're supposed to know the principles, the syntax should be secondary. A pointer is a pointer regardless of it's marked with a * or IntPtr or just a value in a register with no special marking that it's a pointer...
Can we, as devs, come up with something like this?

No offense to anyone who uses it, but I can't stand ASP.net web forms. It just feels so wrong. Then to add the unexplainable behaviour that fixes it's self after creating a new file and pasting in the previous contents without changes.

Asdfdhfjjdsha

Sorry needed that off my chest :)

When you introduce support for MVC projects into a webforms application you've been working with for 4 years and it takes about 3 hours.

#whydidinotdothis4yearsago

worst interview is when the panel is insisting that asp.net webforms is better that asp.net mvc.

it ended with a debate instead of an interview

In 2014 I made a promise to myself that I will never work again in webforms again. Next day I put a resignation notice to my boss and said : "I have dignity". That was my last day when I looked at aspx file. Fast forward to 2024. I break my promise everyday for the last half a year. I can't quite because I don't see any job offers paying that handsomely as 3-4 years ago and I fear that now it may be difficult to find any work at all... I am imprisoned again in VIEWSTATE :(

WebForms wannabe SPA on internet explorer 11, and finished it quiet well <_<

Don't know if proud or horrified

I've been typed cast as a VB.NET WebForms developer. Don't let it happen to you!!!
Off to an Angular code meetup where I'll pretend I use it in my career.

Everytime I have to work on some old Asp.Net shit. WebForms/WinForms etc.

Everything with that bullshitass designer. You wanna open a file you've just created? Sorry, error. Restart IDE and maybe...

Restarted website? Sorry. Old instance still hangs somewhere in IIS, so the port is taken...

Seeing code light up red when cleaning the project. Compiler being like "What the fuck is 'void'?"

Or - I know you didnt make any changes, but Im gonna build AppCode folder anyway... Its only gonna take a minute or two, no worries.

Or - You have XML template file to this class (codebehind)? You wanna open the XML? Would be shame if it was opened in the designer view and your entire IDE crashed 'cuz of some unsuported third party UI element.

Or - just unexpected debug session crashes.

And dont make me start on Xamarin...

Just discovered Katalon and Selenium. If I knew about it earlier I could have saved days back in 2017 if not weeks. <3 this is a good start to 2018!

.Net Dev here with a degree in graphic design. Almost 9 months into my first dev job, 85% of it has been dealing with god damn webforms. Unfortunately, sometimes it doesn't play too nice with a bootstrap / jQuery especially with code behind and when you have post backs. I never thought I would say this but fuck the front end lol at least when it come to this dumpster fire. At least I'm learning a lot but damn I can't wait to get back into an MVC project or service work.

One word... Postback.

Joining a job to build rich single page applications deployed in the cloud, then watching it slowly turn into porting shitty legacy code to slightly less shitty .NET Core code and hooking it to an existing WebForms application...

Time to start the hunt again!

asp webforms is like communism. It solves problems created by it.

Running your .Net WebForms app without any tests? It'll be fine

So at work we use ASP.NET web forms. Since the .NET Core exists now, and that uses ASP.NET MVC, is it worth looking into that and learning about it? My boss is hesitant to move over for our next project because web forms will go faster because we don't have to learn something new.

I hate webforms.

So, we've finally finished our ASP.NET Webforms application, and we're looking onto MVC. We've decided against core just because it isn't as stable yet, and there are fewer libraries, which I'm cool with. However, we still have some baggage from webforms left in our way of approaching the problems. Since the college at large has a custom bootstrap release, we already have bootstrap and jQuery included in the project. What is the best way of going about implementing an equivalent of ComboBoxes, gridviews with paging, and anything else included in the default asp elements and AJAX toolkit ones? My boss is very much against taking in anything but large, well supported libraries like Angular & Angular-UI, so no jQuery plugins unless super stable and supported. I'm trying to save us from having to buy DevExpress for like 3000 across our team. Sorry for the long bullshit, and thanks if you even read it!

Listening to Wendy Renes "After laughter (comes tears)". Trying to do some clientside scripting against a componentart tabstrip. Never felt so hopeless in my whole life.

I had to make a web chatroom for a school project ... in asp.net webforms.

Hello all, recently I have been doing alot of front end work in web forms and lead generation. I would love to learn more about marketing and how it can be applied as a dev.

Does anyone recommend any good books atall?

Thanks!

I need to create a very simple, 2 page website with a simple form on the first page which is processed and a results page shown. It will run on a shared hosting platform.

I've created a few of these over the years for the same client and will have more to do. They started as .NET WebForms (yes, that long ago!) and morphed into more client-side driven but not particularly flexible.

So, is there a front-end framework which will simplify my life and continue to generate accessible, cross-platform output, or would such a choice be overkill and I should keep spitting out reasonable HTML?