{"id":58,"date":"2016-08-28T20:16:23","date_gmt":"2016-08-29T00:16:23","guid":{"rendered":"http:\/\/langstonsoftware.com\/?p=58"},"modified":"2016-09-21T10:50:01","modified_gmt":"2016-09-21T14:50:01","slug":"3-things-to-evaluate-for-your-next-net-project","status":"publish","type":"post","link":"https:\/\/langstonsoftware.com\/2016\/08\/28\/3-things-to-evaluate-for-your-next-net-project\/","title":{"rendered":"3 frameworks to evaluate for your next .NET project"},"content":{"rendered":"

In software development today there is always a stream of new technologies, languages, frameworks, paradigms, and stacks to evaluate. Even if you narrow your scope to C# web stacks, there are plenty of new developments in development tech. I’ve seen and read about a lot of them, but I’ve found a few that really seem to apply to developers across the C# web stack spectrum.<\/p>\n

Here are 3 frameworks I will be looking at for my next .NET project, each of which might take my development toolkit to the next level.<\/p>\n

3. Serilog
\nhttps:\/\/serilog.net\/<\/a><\/p>\n

I’ve had a lot of good success with Log4Net over the years, but Serilog seems to be showing up in discussions and package references more often lately. In part, I’d put this to the simplicity of Serilog. But also, it makes a focus on structured data, letting you serialize log data in useful ways. One of the most useful parts of this is outputting objects in nice serializable and JSON representation in your logs. In general this small change makes creating readable logs much more intuitive than Log4Net, meaning you spend less time trying to craft or understand individual logging statements, and more time creating more useful logging statements or actually producing business logic.<\/p>\n

Especially when working with asynchronous programming, as much of my cutting edge projects do, logging like this can be invaluable, as traditional debugging becomes almost useless. The tried and true Log4Net can get you there, but Serilog seems to get you there faster, with more detail and less fuss.<\/p>\n

2. Angular 2<\/p>\n

https:\/\/angular.io\/docs\/ts\/latest\/<\/a><\/p>\n

AngualarJS 1.x has done a lot of work around my code bases. While I’m still not a fan of their community’s default to non-HTML 5 valid attributes, I can’t deny the effectiveness of their data binding workflow. Angular 2 promises to take that power a step further, with TypeScript as a first class option. Angular 2 has received a lot of Microsoft community love via its TypeScript examples and Visual Studio guides. Some of the syntax has been cleaned up, while elsewhere it has been broken up to make it more composable and explicit. Overall it feels like a good balanced set of changes to an already powerful framework. If you’d like to stay on top of the latest changes in this framework, making the move to Angular 2 in your next project seems like a wise move.<\/p>\n

Especially as you are first starting a new project, taking a strong and hard dependency on a specific JS framework can save you a lot of time down the line. I’ve been in many codebases with a cacophony of frameworks. By giving other developers, including your future self, an opinionated stance from the beginning it can save you a lot of time down the road from bike shedding between different ways to solve the JS data binding question. <\/p>\n

1. .NET Core<\/p>\n

https:\/\/www.microsoft.com\/net\/core#windows<\/a><\/p>\n

If you haven’t heard about .NET Core yet, you should really listen up. .NET core is a re-engineered subset of the .NET framework, with heavy emphasis on true cross platform and containerized development. It is slimmed down, so existing projects may not have all the pieces they need from the standard .NET framework, but for a new project evaluating Core is a must. With the continued move for multi-provider cloud hosting to prevent a single provider outage from taking down your application, those truly interested in resilient applications should take notice.<\/p>\n

In particular it appears Docker will be part of these multi-provider cloud environment solutions. .NET Core seems perfect for setting you up for success for such stacks, being both small and increasingly fast, containing only what is strictly necessary for your project and not the cruft that the standard .NET framework has accumulated over the years. I expect especially the fans of the small microservice API patterns will find .NET Core tempting, perhaps even pulling a few back from NodeJS that may have strayed from a .NET solution.<\/p>\n

Conclusion<\/p>\n

There you go, 3 frameworks to evaluate in your next .NET project. I hope that gives you enough data to prioritize which new techs to add to your toolkit. Let me know in the comments what you’ll be evaluating in your next project or if there is a hot framework you think I’ve missed.<\/p>\n","protected":false},"excerpt":{"rendered":"

In software development today there is always a stream of new technologies, languages, frameworks, paradigms, and stacks to evaluate. Even if you narrow your scope to C# web stacks, there are plenty of new developments in development tech. I’ve seen and read about a lot of them, but I’ve found a few that really seem …<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"nf_dc_page":"","jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":true,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","enabled":false},"version":2}},"categories":[11],"tags":[],"class_list":["post-58","post","type-post","status-publish","format-standard","hentry","category-frameworks-libraries"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p6Os38-W","_links":{"self":[{"href":"https:\/\/langstonsoftware.com\/wp-json\/wp\/v2\/posts\/58"}],"collection":[{"href":"https:\/\/langstonsoftware.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/langstonsoftware.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/langstonsoftware.com\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/langstonsoftware.com\/wp-json\/wp\/v2\/comments?post=58"}],"version-history":[{"count":4,"href":"https:\/\/langstonsoftware.com\/wp-json\/wp\/v2\/posts\/58\/revisions"}],"predecessor-version":[{"id":74,"href":"https:\/\/langstonsoftware.com\/wp-json\/wp\/v2\/posts\/58\/revisions\/74"}],"wp:attachment":[{"href":"https:\/\/langstonsoftware.com\/wp-json\/wp\/v2\/media?parent=58"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/langstonsoftware.com\/wp-json\/wp\/v2\/categories?post=58"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/langstonsoftware.com\/wp-json\/wp\/v2\/tags?post=58"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}