11–20 of 26 posts
But I really dislike reading this kind of code. It is just really hard to understand. And if it's hard to understand, it's hard to maintain.
After having spent a lot of time working in Javascript (and node.js specifically), I'm diving back into C# in my spare time, but learning to forget all the nonsense- no factories, no web.config, no ASP.NET framework... it's great. One highlight is Nancy.fx[1], a very lightweight web framework. Setting up routes is as simple as:
Get["/list"] = parameters => {
return "The list of products";
};
It's stuff like this that gives C# a bad name. If you strip away the enterprise-y, ASP.NET stuff it's usually wrapped in, it's a fantastic language. After having spent a lot of time working in Javascript (and node.js specifically), I'm diving back into C# in my spare time, but learning to forget all the nonsense- no factories, no web.config, no ASP.NET framework... it's great. One highlight is Nancy.fx[1], a very lig…
It's stuff like this that gives C# a bad name. If you strip away the enterprise-y, ASP.NET stuff it's usually wrapped in, it's a fantastic language. After having spent a lot of time working in Javascript (and node.js specifically), I'm diving back into C# in my spare time, but learning to forget all the nonsense- no factories, no web.config, no ASP.NET framework... it's great. One highlight is Nancy.fx[1], a very lig…
Asp.net webapi is quite good, I have to say!
The sad thing is that even ASP.NET MVC- which is 100x better than WebForms- is used 0.001 as much. The same fate may apply to the Web API. It just doesn't seem like there is much interest.
It's stuff like this that gives C# a bad name. If you strip away the enterprise-y, ASP.NET stuff it's usually wrapped in, it's a fantastic language. After having spent a lot of time working in Javascript (and node.js specifically), I'm diving back into C# in my spare time, but learning to forget all the nonsense- no factories, no web.config, no ASP.NET framework... it's great. One highlight is Nancy.fx[1], a very lig…
Earlier quoted context omitted.
Asp.net webapi is quite good, I have to say!
I haven't had a chance to look at it, but have heard good things. The sad thing is that even ASP.NET MVC- which is 100x better than WebForms- is used 0.001 as much. The same fate may apply to the Web API. It just doesn't seem like there is much interest.
i would have thought ASP.NET MVC is quite mainstream and that webforms is slowly dying personally...
now with webapi and a pure html client, i see no point in MVC whatsoever!
> When an Application Service receives control, it loads an Aggregate and retrieves any supporting Domain Services needed by the Aggregate’s business operation. When the Application Service delegates to the Aggregate business operation, the Aggregate’s method produces Events as the outcome. I'm genuinely curious: does anyone here understand anything about that? What do those words even mean ? I mean, even if you assu…
This has nothing to do with C# and .NET. I think it's some kind of ASP.NET framework. As far as I know, C# and .NET do not have this reputation (at least, no more than other technologies in the same space, like Java).
Ummm, what exactly is a "C# Application Service"? This post has no introduction and dives right into the details.
This seems to be some kind of ASP.NET thing. It has nothing to do with the C# language, as far as I can tell.