ASP.NET

jkirkerx wrote:

Maybe I spoke too soon, one of my Docker MongoDB container crashed.

Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.

jkirkerx wrote:

Didn't like the way they tried to make it like WinForms,

jkirkerx wrote:

you never really master HTML or HTML5

jkirkerx wrote:

Perhaps a WebForms app written for in-house use might be OK, but not for world wide production use

jkirkerx wrote:

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.

jkirkerx wrote:

Google just didn't play nice with WebForms

jkirkerx wrote:

And then the single use of the Form element

jkirkerx wrote:

I dumped WebForms and went MVC...Then I dumped MVC and went .Net Core MVC...Last, I took the Angular jump

F-ES Sitecore wrote:

there wasn't as much of a learning curve.

Advantages of server-side View State

The main advantage is that if a browser does not support a large encrypted file that is generated by the client-side View State then by the client-side View State we can handle it. As we know sometimes when we open an ASP web site in ASP.NET there will be some time corruption problem so it also minimizes the corruption problem. It also converts large client-side pages into a small client-side page because the View State data is stored at the server.

Disadvantages of Server-side View State

The main draw back is that the developer does not know how much space is taken by a View State on the server. If it takes a very large space there will be a problem. Another disadvantage is that server-side View State uses the server memory for the session object.

Quote:

As a negative effect, you never really master HTML or HTML5.

Quote:

I also got burned by the Ajax Control Toolkit.

using System.Web.UI;

namespace WebApplication1
{
    public partial class SiteMaster : MasterPage
    {
        public string SayHello()
        {
            return "Hello";
        }
    }
}

<%@ Page Title="Home Page" Language="C#" MasterPageFile="~/Site.Master" EnableEventValidation="false" AutoEventWireup="true" CodeBehind="Default.aspx.cs" Inherits="WebApplication1._Default" %>
<%@ MasterType TypeName="WebApplication1.SiteMaster" %>

protected void Page_Load(object sender, EventArgs e)
{
    string text = Master.SayHello();
}

var master = (SiteMaster) Master;
string text = master.SayHello();

public interface ISiteMaster
{
    void DoSomething();
    string ReturnSomething();
}

public class SomeClass
{
    public string Foo(ISiteMaster master)
    {
        master.DoSomething();
        return master.ReturnSomething();
    }
}

public partial class SiteMaster : MasterPage, ISiteMaster
{
    public void DoSomething() { ... }
    public string ReturnSomething() { ... }
}

public partial class HomePage : Page
{
    protected void Page_Load(object sender, EventArgs e)
    {
        var helper = new SomeClass();
        
        // If you've used the MasterType attribute:
        string value = helper.Foo(Master); 
        // Otherwise:
        string value = helper.Foo((ISiteMaster)Master);
    }
}