Click here to Skip to main content
14,387,205 members
   

ASP.NET

 
AnswerRe: During redirection localhost is not attached and page failed to load Pin
Richard Deeming28-Nov-19 2:18
mveRichard Deeming28-Nov-19 2:18 
QuestionASP.net In Visual Studio 2019 Pin
Ebrahimaw20-Nov-19 14:09
MemberEbrahimaw20-Nov-19 14:09 
AnswerRe: ASP.net In Visual Studio 2019 Pin
Eddy Vluggen20-Nov-19 15:03
mveEddy Vluggen20-Nov-19 15:03 
QuestionSQL Parameter Collection - Not able to assign to SQLCommand Pin
Member 1115418819-Nov-19 7:11
MemberMember 1115418819-Nov-19 7:11 
AnswerRe: SQL Parameter Collection - Not able to assign to SQLCommand Pin
Richard MacCutchan19-Nov-19 7:19
mveRichard MacCutchan19-Nov-19 7:19 
General[Solved] Re: SQL Parameter Collection - Not able to assign to SQLCommand Pin
Member 1115418819-Nov-19 20:10
MemberMember 1115418819-Nov-19 20:10 
QuestionWhat's so bad about webforms? Pin
DerekT-P18-Nov-19 5:29
professionalDerekT-P18-Nov-19 5:29 
AnswerRe: What's so bad about webforms? Pin
jkirkerx18-Nov-19 14:47
professionaljkirkerx18-Nov-19 14:47 
Guess I must be the biggest opponent of WebForms here, even as far as calling it stupid.

What I didn't like?
Didn't like the way they tried to make it like WinForms, in which objects create HTML. So you create all these labels which are just span tags. Then when you go to port your HTML to another framework, you have to change all the objects back to actual HTML. As a negative effect, you never really master HTML or HTML5. If you stick with WebForms and not move forward, you stay stuck in that world of objects for years, never really moving forward to support phones, tablets and desktops.

I also got burned by the Ajax Control Toolkit. It worked great locally, but failed on long distance connections. The Partial Update control worked the same way. They added so much junk that was never really stable. Perhaps a WebForms app written for in-house use might be OK, but not for world wide production use. And then all of this stuff has to play nice with the Web Server such as IIS. It seems like WebForms with it's ViewState worked tightly with IIS server in order to post data back, and IIS server would have to keep track of every session out there.

Google just didn't play nice with WebForms. WebForms had a way of placing a script on the page, and using a weird URL for it's location that Google didn't like. I think it was a query-string added to the script name. Then Google complained about other elements I had no control over. And then the single use of the Form element, and having to work within that parameter or rule.

I could name probably 10 more things I didn't like about it.

Moving Forward
I dumped WebForms and went MVC, and loved it. After the steep learning curve, I was able to reduce the time for new projects in half. Learned how to write very effective models and are close to my database designs. With views and razor, I was able to create new UI that where more user friendly, and much more fluid. Learned Gulp to package my CSS and compress files.

Then I dumped MVC and went .Net Core MVC loving it even more. Delivering blazing fast speeds but I still didn't care for Razor much. But my SEO tests were off the charts and Google loved it.

Last, I took the Angular jump, Angular wrapped in a .Net Core project. Figured out how to pack all my stuff like SASS, and compile it into a single project that runs in a Docker container. With this technology, I can now focus on providing a great user experience, with super efficient models and database designs, with blazing fast speeds. I spend very time writing code, in which most are just a few lines. I don't have to worry about slow connections any more.

Now I can develop in 1/16 the amount of time it took me in WinForms. My website below is version 298 at the moment. I have no regrets at all about leaving WebForms, even MVC as well. The WebPack train is running and lots of people are hopping on the train.
If it ain't broke don't fix it
Discover my world at jkirkerx.com

PraiseRe: What's so bad about webforms? Pin
Eddy Vluggen18-Nov-19 15:19
mveEddy Vluggen18-Nov-19 15:19 
GeneralRe: What's so bad about webforms? Pin
jkirkerx18-Nov-19 17:07
professionaljkirkerx18-Nov-19 17:07 
GeneralRe: What's so bad about webforms? Pin
Eddy Vluggen19-Nov-19 3:47
mveEddy Vluggen19-Nov-19 3:47 
GeneralRe: What's so bad about webforms? Pin
F-ES Sitecore19-Nov-19 0:18
mveF-ES Sitecore19-Nov-19 0:18 
GeneralRe: What's so bad about webforms? Pin
Richard Deeming19-Nov-19 2:21
mveRichard Deeming19-Nov-19 2:21 
GeneralRe: What's so bad about webforms? Pin
F-ES Sitecore19-Nov-19 2:35
mveF-ES Sitecore19-Nov-19 2:35 
GeneralRe: What's so bad about webforms? Pin
jkirkerx19-Nov-19 13:59
professionaljkirkerx19-Nov-19 13:59 
GeneralRe: What's so bad about webforms? Pin
F-ES Sitecore20-Nov-19 0:04
mveF-ES Sitecore20-Nov-19 0:04 
GeneralRe: What's so bad about webforms? Pin
jkirkerx20-Nov-19 11:43
professionaljkirkerx20-Nov-19 11:43 
GeneralRe: What's so bad about webforms? Pin
DerekT-P20-Nov-19 2:22
professionalDerekT-P20-Nov-19 2:22 
GeneralRe: What's so bad about webforms? Pin
DerekT-P19-Nov-19 1:23
professionalDerekT-P19-Nov-19 1:23 
AnswerRe: What's so bad about webforms? Pin
F-ES Sitecore19-Nov-19 0:30
mveF-ES Sitecore19-Nov-19 0:30 
AnswerRe: What's so bad about webforms? Pin
A_Griffin20-Nov-19 6:57
MemberA_Griffin20-Nov-19 6:57 
GeneralRe: What's so bad about webforms? Pin
DerekT-P20-Nov-19 10:05
professionalDerekT-P20-Nov-19 10:05 
AnswerRe: What's so bad about webforms? Pin
Steve Naidamast24-Nov-19 7:53
professionalSteve Naidamast24-Nov-19 7:53 
GeneralRe: What's so bad about webforms? Pin
DerekT-P24-Nov-19 10:18
professionalDerekT-P24-Nov-19 10:18 
GeneralRe: What's so bad about webforms? Pin
Steve Naidamast25-Nov-19 5:30
professionalSteve Naidamast25-Nov-19 5:30 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.