Is this admission that codeplex is dead?
At long last I can avoid codeplex for browsing the aspnet source!
Source code of ASP.NET
61–70 of 104 posts
Re: Source code of ASP.NET
#62Not all of ASP.NET though...notably absent: Web Forms.
Trust me; that's a good thing. Nasty, deeply misguided platform - whoever came up with the idea of PostBack and trying to make the web look like VB6 is definitely not on my Christmas card list. Ties you in knots trying to make the web something it fundamentally isn't. I'll be quiet now, and get back to working on my MVC code. The day when I can finally stop having to work on WebForms code too will be a happy one :-)
Not a rhetorical question: What's so wrong
with Web Forms?
Postback? That's really part of HTTP. What the browsers send back to the server is as specified by HTTP, not Microsoft or Web Forms.
Viewstate? Okay, it's a bit of a tricky thing, but really can mostly ignore it. Else it provides a somewhat useful service.
Controls? Yes, for each HTML 'control', there is an ASP.NET class so to send the HTML for the control to the user, get an instance of the class corresponding to the control, assign values to the properties, attach the instance to a big tree that gets walked by the code in one of the ASP.NET 'events', maybe PAGE_PRERENDER, and move along. Why is this so bad?
Web Forms is my first and so far only way I've written Web pages. Explain what is wrong with Web Forms and what is much better and why?
Re: Source code of ASP.NET
#63Earlier quoted context omitted.
The old one was open sourced a couple months (years?) back and is on CodePlex. http://aspnetwebstack.codeplex.com/
Not quite: that's "ASP.NET MVC", the razor view engine, "web pages", and some other libraries like Entity Framework and SignalR. Technically these are just libraries built on the closed-source ASP.NET stack, colloquially known as System.Web, which is essentially IIS.
It's at least available to view the source:
http://referencesource.microsoft.com/System.Web/xsp/system/W...
Re: Source code of ASP.NET
#64Earlier quoted context omitted.
I think Hudo's point is that experience with technologies is subjective. I loathe Windows after having been comfortable in terminal, and I loathe Eclipse after having been comfortable in VS.
I've gotten apps working on .net and ubuntu -- configuration was a drag in both, but it works, and isn't the entire basis for loving or hating a platform. So what I'm saying is I agree with your comment. The catch here (and point) is why should you have to switch from VS at all? If it's a real source code editor shouldn't it handle Java, Clojure, Haskell, Python, Ruby, JavaScript, etc all just fine? Some of the oldes…
Other editors certainly 'do it', but they're so embarassingly bad that a huge amount of non-VS devs resort to using text editors instead of dealing with the clunky IDEs.
Re: Source code of ASP.NET
#65Earlier quoted context omitted.
Trust me; that's a good thing. Nasty, deeply misguided platform - whoever came up with the idea of PostBack and trying to make the web look like VB6 is definitely not on my Christmas card list. Ties you in knots trying to make the web something it fundamentally isn't. I'll be quiet now, and get back to working on my MVC code. The day when I can finally stop having to work on WebForms code too will be a happy one :-)
Not a rhetorical question: What's so wrong with Web Forms? Postback? That's really part of HTTP. What the browsers send back to the server is as specified by HTTP, not Microsoft or Web Forms. Viewstate? Okay, it's a bit of a tricky thing, but really can mostly ignore it. Else it provides a somewhat useful service. Controls? Yes, for each HTML 'control', there is an ASP.NET class so to send the HTML for the control to…
The real issue is the amount of "Black Box" in WebForms. A lot of the guidance is "Do it this way". Why? "Because". You really can't know what is going on behind the scenes. ViewState and the PostBack model are both parts of that. I used them for years...never knew how they worked or what was going on to make them work.
This in turn forced people to go to the MVP pattern to manage those systems, but I still find plenty of clients with code behind that is THOUSANDS of lines long. Everything in one file.
Also, many of the controls were very hard to style, with some very strange html in there.
Re: Source code of ASP.NET
#66Earlier quoted context omitted.
The old one was open sourced a couple months (years?) back and is on CodePlex. http://aspnetwebstack.codeplex.com/
Not quite: that's "ASP.NET MVC", the razor view engine, "web pages", and some other libraries like Entity Framework and SignalR. Technically these are just libraries built on the closed-source ASP.NET stack, colloquially known as System.Web, which is essentially IIS.
In ASP.NET vNext, there is no System.Web any more. They have broken the core into separate components, and their source is in the OP link.
Re: Source code of ASP.NET
#67Earlier quoted context omitted.
Too slow for what? Are you suggesting that .NET technology is traveling on a steady path towards becoming irrelevant?
Yes. Most users of .NET is in the enterprise (as opposed to tech and startups) and Java has positioned itself as the go-to platform for big data analytics and processing. I think this comes down to clinging to an antiquated product model. A lot of the technologies that are seeing rapid adoption are open source and driven by transparent communities. In some cases companies back them (e.g. cloudera, datastax, 10gen, ty…
And where exactly do you think most devs work? As far as startups go, and we may be usual, but we are a healthcare analytics company using Sql Server for medium? data and processing, with a pretty light .Net middleware/front-end.
Re: Source code of ASP.NET
#68Is this snippet of code bad? I was just randomly browsing
https://github.com/aspnet/KRuntime/blob/dev/src/Microsoft.Fr...
private bool IsDifferent(ConfigurationsMessage local, ConfigurationsMessage remote)
{
return true;
}
private bool IsDifferent(ReferencesMessage local, ReferencesMessage remote)
{
return true;
}
private bool IsDifferent(DiagnosticsMessage local, DiagnosticsMessage remote)
{
return true;
}
private bool IsDifferent(SourcesMessage local, SourcesMessage remote)
{
return true;
}Re: Source code of ASP.NET
#69Earlier quoted context omitted.
Trust me; that's a good thing. Nasty, deeply misguided platform - whoever came up with the idea of PostBack and trying to make the web look like VB6 is definitely not on my Christmas card list. Ties you in knots trying to make the web something it fundamentally isn't. I'll be quiet now, and get back to working on my MVC code. The day when I can finally stop having to work on WebForms code too will be a happy one :-)
Not a rhetorical question: What's so wrong with Web Forms? Postback? That's really part of HTTP. What the browsers send back to the server is as specified by HTTP, not Microsoft or Web Forms. Viewstate? Okay, it's a bit of a tricky thing, but really can mostly ignore it. Else it provides a somewhat useful service. Controls? Yes, for each HTML 'control', there is an ASP.NET class so to send the HTML for the control to…
IMO, there was nothing horribly wrong with WebForms itself when it was introduced -- So long as you were writing your HTML by hand and using HtmlControls rather than the drag-n-drop stuff.
ViewState was far better than other frameworks that shoved the client state into a server session object and broke the Back button. Plus the clients were saving state instead of wasting server memory. If it got too ugly, you didn't even have to use it, the http variables were still there.
Remember this was all designed back when Netscape 4 was a popular browser and any Javascript was considered exotic. Of course we have much better way to do things now, the WebForm approach broke down hard as soon as it encountered AJAX. But originally it was fine.
Re: Source code of ASP.NET
#70Is this snippet of code bad? I was just randomly browsing https://github.com/aspnet/KRuntime/blob/dev/src/Microsoft.Fr... private bool IsDifferent(ConfigurationsMessage local, ConfigurationsMessage remote) { return true; } private bool IsDifferent(ReferencesMessage local, ReferencesMessage remote) { return true; } private bool IsDifferent(DiagnosticsMessage local, DiagnosticsMessage remote) { return true; } private b…
lolwat