# ASP.NET ASP.NET is an open source web framework for building modern web apps and services with .NET. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## CodeSOD: Extremely One Line DevFeed: [CodeSOD: Extremely One Line]() Original publisher: [Read original article]() Author: Remy Porter Published: 2026-09-16T06:30:00Z Content type: opinion Language: en Sources: [The Daily WTF]() Topics: [ASP.NET](), [Code](), [Visual Studio](), [Command-line interface](), [browser](), [HTTP]() Tags: [asp-net](), [browser](), [cli](), [code](), [codesod](), [http](), [studio]() ### AI overview This CodeSOD commentary examines an ancient ASP .Net application containing a function written on one line, Safari user-agent detection, and a mysterious "uplevel" value. It criticizes the confusing style and notes that the same pattern appears on multiple pages. ### Source excerpt Autoformatting your code is a standard thing to do these days. And in those days past, if we're being honest. There's no excuse to not use some kind of autoformatter. Whether you configure your editor to do it or are a weirdo like me who runs a formatter from the CLI as a build step, you've got an easy way to format your code so it looks neat and readable. And some IDEs, like Visual Studio, are pretty insistent about doing this for you. Which makes today's code sample a bit more perplexing. This comes from an ancient ASP .Net application that Austin has the misfortune to work with: protected void Page_PreInit(object sender, EventArgs e){if (Request.ServerVariables["http_user_agent"].IndexOf("Safari", StringComparison.CurrentCultureIgnoreCase) != -1)Page.ClientTarget = "uplevel";} protected void Page_Load(object sender, EventArgs e) { Logic(); } Which function is Logic() called from? The fact that I'm asking probably is enough to get you to scroll over. The entire Page_PreInit function is on a single line, followed by the declaration of the Page_Load function. A confusing and annoying choice. The real bonus is that if the browser has "Safari" in its user agent, we set a field to a mysterious "uplevel" value. A mix of user agent sniffing, strings as enums/flags, and wonderfully unclear names. And yes, this particular pattern appears in more than one page in Austin's application. Someone thought this was not just a good idea, but good enough to do over and over again. [Advertisement] Picking up NuGet is easy. Getting good at it takes time. Download our guide to learn the best practice of NuGet for the Enterprise. ## How to Orchestrate Multi-Call Conversations with an LLM and Twilio Conversation Memory DevFeed: [How to Orchestrate Multi-Call Conversations with an LLM and Twilio Conversation Memory]() Original publisher: [Read original article]() Author: Amanda Lange Published: 2026-09-15T00:00:00Z Content type: tutorial Language: en Sources: [Twilio Blog]() Topics: [Large Language Model](), [.NET](), [ASP.NET](), [C#](), [Artificial Intelligence](), [Command-line interface](), [OpenAI](), [Environment Variables]() Tags: [account](), [agent](), [ai](), [api](), [c-sharp](), [cli](), [code](), [conversation-memory](), [developer-insights](), [environment-variables](), [how-to](), [llm](), [net](), [net-9](), [openai]() ### AI overview This tutorial shows how to build a C# .NET 9 ASP.NET Core service that preserves caller context, preferences, and action history across separate inbound calls using Twilio Conversation Memory and an LLM. ### Source excerpt How to Orchestrate Multi-Call Conversations with an LLM and Twilio Conversation Memory ## Logging, Metrics, and Distributed Tracing in .NET with OpenTelemetry and ClickStack DevFeed: [Logging, Metrics, and Distributed Tracing in .NET with OpenTelemetry and ClickStack]() Original publisher: [Read original article]() Author: Alex Soffronow Pagonidis Published: 2026-06-03T09:21:38Z Content type: tutorial Language: en Sources: [ClickHouse Blog]() Topics: [ASP.NET](), [OpenTelemetry](), [tracing](), [Grafana](), [telemetry](), [Instrumentation](), [SQLite](), [API](), [gRPC](), [SQL]() Tags: [api](), [instrumentation](), [logging](), [metrics](), [observability](), [opentelemetry](), [sql](), [sqlite](), [traces](), [tracing]() ### AI overview A practical walkthrough of instrumenting two ASP.NET services with OpenTelemetry and sending traces, logs, and metrics to ClickStack. The example uses an Order API and a Payment Service, with SQLite persistence and cross-service trace correlation. ### Source excerpt A walkthrough of adding OpenTelemetry instrumentation to two ASP.NET services -- an Order API and a Payment Service -- and shipping traces, logs, and metrics to ClickStack, with auto-correlated signals and cross-service trace waterfalls out of the box. ## Building a .NET API Gateway with ClickHouse and Aspire DevFeed: [Building a .NET API Gateway with ClickHouse and Aspire]() Original publisher: [Read original article]() Author: Alex Soffronow Pagonidis Published: 2026-06-02T00:00:00Z Content type: tutorial Language: en Sources: [ClickHouse Blog]() Topics: [Aspire](), [clickhouse](), [.NET](), [API](), [ASP.NET](), [OpenTelemetry](), [Blazor](), [dashboards](), [C#](), [Docker]() Tags: [analytics](), [api](), [apis](), [asp-net-core](), [backend](), [blazor](), [c-sharp](), [clickhouse](), [containers](), [docker](), [metrics](), [opentelemetry](), [telemetry](), [web]() ### AI overview A walkthrough of building a .NET API gateway with YARP and Aspire. The gateway routes traffic to backend APIs, records proxied requests in ClickHouse for aggregate analytics, and emits OpenTelemetry metrics. A Blazor dashboard presents the results while Aspire provides live service telemetry, logs, traces, and metrics. ### Source excerpt A walkthrough of building a .NET API gateway with YARP and Aspire that logs every proxied request to ClickHouse for aggregate analytics, with a materialized view keeping dashboard queries fast as traffic grows. ## Structured Logging in .NET with Serilog and ClickHouse DevFeed: [Structured Logging in .NET with Serilog and ClickHouse]() Original publisher: [Read original article]() Author: Alex Soffronow Pagonidis Published: 2026-03-23T00:00:00Z Content type: article Language: en Sources: [ClickHouse Blog]() Topics: [clickhouse](), [log management](), [.NET](), [ASP.NET](), [SQL](), [data](), [observability](), [dashboards](), [Docker Compose](), [GitHub]() Tags: [clickhouse](), [dashboards](), [data](), [docker](), [github](), [how-to](), [learn](), [logging](), [logs](), [net](), [observability](), [sql]() ### AI overview Learn how to send structured .NET logs directly to ClickHouse with Serilog. The article covers configuring the ClickHouse sink, designing a schema in C#, enriching logs with request context, and querying them with SQL for diagnostics. ### Source excerpt Learn how to send structured .NET logs directly to ClickHouse using Serilog -- with full schema control, full-text search, and SQL queries over your log data. ## Native .NET Buildpack Support is Now Available on App Platform DevFeed: [Native .NET Buildpack Support is Now Available on App Platform]() Original publisher: [Read original article]() Author: Bikram Gupta Published: 2026-03-05T21:21:25Z Content type: release Language: en Sources: [DigitalOcean]() Topics: [Digital Ocean](), [.NET](), [Deployment](), [SDK](), [Dockerfile](), [Git](), [ASP.NET](), [NuGet]() Tags: [asp-net-core](), [c-sharp](), [deployment](), [digitalocean](), [dockerfiles](), [dotnet](), [f-sharp](), [git](), [net](), [product-updates](), [release](), [sdk]() ### AI overview DigitalOcean App Platform now supports native .NET buildpacks, allowing developers to deploy .NET applications from Git repositories without maintaining Dockerfiles. The platform detects the project, selects the SDK version, restores dependencies, and builds the application for production. ### Source excerpt The .NET ecosystem continues to power a significant share of enterprise and cloud-native applications, from web APIs and microservices to full-stack applications built with ASP.NET Core. Developers building with C#, F#, and Visual Basic need a deployment experience that matches the productivity of the framework itself: push code, and let the platform handle the rest. Today, we're excited to announce native .NET buildpack support on DigitalOcean App Platform. You can now deploy your .NET applications directly from a Git repository without writing or maintaining Dockerfiles. App Platform automatically detects your .NET project, installs the correct SDK version, and builds your application for production. Benefits Zero Configuration: Push your .NET code to a Git repository, and App Platform handles runtime detection, SDK installation, and build configuration automatically--no Dockerfile required. Multi-Language Support: Build applications in C#, Visual Basic, or F# using the .NET and ASP.NET Core frameworks, all with the same streamlined deployment experience. Automatic SDK Management: App Platform selects the appropriate .NET SDK version based on your project's TargetFramework or global.json configuration, supporting .NET 8.0, 9.0, and 10.0. Production-Ready Defaults: The buildpack compiles with the Release configuration by default and automatically detects ASP.NET Core web applications to configure the correct process type. How Detection Works Once you connect your Git repository, App Platform identifies your application as a .NET project by looking for specific files in your repository root. App Platform confirms a .NET application if it detects any of the following: Solution files: *.sln, *.slnx Project files: *.csproj, *.vbproj, *.fsproj File-based apps: *.cs Once detected, the buildpack takes over: SDK Detection: Determines the required .NET SDK version from your TargetFramework property or global.json file Dependency Restore: Runs dotnet restore to fetch NuGet pa ## Heroku Support for .NET 10 LTS: What Developers Need to Know DevFeed: [Heroku Support for .NET 10 LTS: What Developers Need to Know]() Original publisher: [Read original article]() Author: Rune Soerensen Published: 2025-11-11T08:00:23Z Content type: release Language: en Sources: [Heroku]() Topics: [Heroku](), [.NET](), [ASP.NET](), [Deployment](), [migration](), [releases]() Tags: [2025](), [asp-net](), [asp-net-core](), [buildpacks](), [c-sharp](), [deployment](), [developers](), [engineering](), [heroku](), [languages](), [lts](), [migration](), [net](), [nextgen](), [product-features](), [release]() ### AI overview Heroku now supports building and running .NET 10 applications, including ASP.NET Core 10, with buildpack support for features such as file-based apps and solution files. .NET 10 is the new three-year Long Term Support release, while .NET 8 and .NET 9 are scheduled to reach end of support on November 10, 2026. ### Source excerpt It's that time of year for .NET when we get a new major version and a bunch of exciting features. .NET Conf 2025 kicked off earlier today, bringing with it the release of .NET 10, as well as ASP.NET Core 10, C# 14, and F# 10. Congrats (and a big thank you) to the .NET [...] The post Heroku Support for .NET 10 LTS: What Developers Need to Know appeared first on Heroku. ## HTML Minifier: A 12-Year Journey Building and Maintaining an Open Source Tool DevFeed: [HTML Minifier: A 12-Year Journey Building and Maintaining an Open Source Tool]() Original publisher: [Read original article]() Author: Dean Hume Published: 2025-10-30T14:49:50Z Content type: opinion Language: en Sources: [Dean Hume]() Topics: [HTML](), [Web](), [Open Source](), [ASP.NET](), [Angular](), [build tools]() Tags: [angular](), [asp-net](), [build-tools](), [html](), [journey](), [open-source](), [performance](), [web-performance]() ### AI overview The author reflects on developing and maintaining an open-source HTML Minifier over 12 years. The tool reduces HTML size by removing unnecessary whitespace, line breaks, and comments, and evolved with framework compatibility, recursive scanning, multi-file support, line-length controls, and performance metrics. ### Source excerpt Discover the 12-year journey behind HTML Minifier an open source tool that helped developers optimize web performance and reduce page load times. ## Cookie Chaos: How to bypass \_\_Host and \_\_Secure cookie prefixes DevFeed: [Cookie Chaos: How to bypass \_\_Host and \_\_Secure cookie prefixes]() Original publisher: [Read original article]() Author: Zakhar Fedotkin Published: 2025-09-03T14:46:23Z Content type: article Language: en Sources: [PortSwigger Research]() Topics: [browsers](), [Security](), [browser](), [ASP.NET](), [Django]() Tags: [attacks](), [browser](), [browsers](), [django](), [frameworks](), [security]() ### AI overview This article explains how discrepancies between browser and server-side cookie parsing can bypass the security restrictions of the __Host and __Secure cookie prefixes. It describes UTF-8 and Unicode whitespace techniques, including behavior in Django and ASP.NET, and notes differences in Safari's handling of cookie names. ### Source excerpt Browsers added cookie prefixes to protect your sessions and stop attackers from setting harmful cookies. In this post, you'll see how to bypass cookie defenses using discrepancies in browser and serve ## Updating to .NET 8, updating to IHostBuilder, and running Playwright Tests within NUnit headless or headed on any OS DevFeed: [Updating to .NET 8, updating to IHostBuilder, and running Playwright Tests within NUnit headless or headed on any OS]() Original publisher: [Read original article]() Author: Scott Hanselman Published: 2024-03-07T01:12:13Z Content type: tutorial Language: en Sources: [Scott Hanselman]() Topics: [Playwright](), [.NET](), [Testing](), [Browser Automation](), [Integration testing](), [ASP.NET](), [Selenium](), [GitHub Actions]() Tags: [asp-net](), [automation-testing](), [browser](), [ci-cd](), [debug](), [devops](), [dotnetcore](), [integration](), [linux](), [net](), [playwright](), [selenium](), [testing](), [tests](), [unit-testing](), [visual-studio](), [vs-code](), [web](), [windows]() ### AI overview A tutorial on updating a .NET application to .NET 8 and running Playwright browser tests through NUnit. It explains the transition from IWebHostBuilder to IHostBuilder and describes cross-platform, headless or headed testing across local systems, containers, and CI environments. ### Source excerpt I've been doing not just Unit Testing for my sites but full on Integration Testing and Browser Automation Testing as early as 2007 with Selenium. Lately, however, I've been using the faster and generally more compatible Playwright. It has one API and can test on Windows, Linux, Mac, locally, in a container (headless), in my CI/CD pipeline, on Azure DevOps, or in GitHub Actions. For me, it's that last moment of truth to make sure that the site runs completely from end to end. I can write those Playwright tests in something like TypeScript, and I could launch them with node, but I like running end unit tests and using that test runner and test harness as my jumping off point for my .NET applications. I'm used to right clicking and "run unit tests" or even better, right click and "debug unit tests" in Visual Studio or VS Code. This gets me the benefit of all of the assertions of a full unit testing framework, and all the benefits of using something like Playwright to automate my browser. In 2018 I was using WebApplicationFactory and some tricky hacks to basically spin up ASP.NET within .NET (at the time) Core 2.1 within the unit tests and then launching Selenium. This was kind of janky and would require to manually start a separate process and manage its life cycle. However, I kept on with this hack for a number of years basically trying to get the Kestrel Web Server to spin up inside of my unit tests. I've recently upgraded my main site and podcast site to .NET 8. Keep in mind that I've been moving my websites forward from early early versions of .NET to the most recent versions. The blog is happily running on Linux in a container on .NET 8, but its original code started in 2002 on .NET 1.1. Now that I'm on .NET 8, I scandalously discovered (as my unit tests stopped working) that the rest of the world had moved from IWebHostBuilder to IHostBuilder five version of .NET ago. Gulp. Say what you will, but the backward compatibility is impressive. As such my code for Progr ## Announcing official Apollo Federation support for .NET with Hot Chocolate and Federation 2! DevFeed: [Announcing official Apollo Federation support for .NET with Hot Chocolate and Federation 2!]() Original publisher: [Read original article]() Author: Phil Prasek Published: 2023-10-24T15:46:07Z Content type: release Language: en Sources: [Apollo Blog]() Topics: [GraphQL](), [.NET](), [ASP.NET](), [C#]() Tags: [announcement](), [apollo-federation](), [github-actions](), [graphql](), [net](), [open-source]() ### AI overview Apollo announces an official open-source Apollo Federation support library for Hot Chocolate, a .NET GraphQL framework. The v1.0 library includes full Federation 2 support, including field migrations, entity interfaces, and more flexible type ownership. ### Source excerpt Apollo Federation is an open specification for exposing API services as a single GraphQL access layer, known as a supergraph. In a supergraph, you connect and curate your services through smaller, modular graphs called subgraphs. There's a vibrant ecosystem of community-led frameworks that let you write subgraphs in every common language, bolstered by official Apollo Federation support libraries for JavaScript and Java. ## The next CEO of Stack Overflow DevFeed: [The next CEO of Stack Overflow]() Original publisher: [Read original article]() Author: Joel Spolsky Published: 2019-03-28T14:00:53Z Content type: news Language: en Sources: [Joel Spolsky]() Topics: [Stack Overflow](), [Microsoft](), [Software as a service](), [ASP.NET](), [mvc](), [.NET]() Tags: [advertising](), [asp-net](), [browser](), [ceo](), [co-founder](), [employees](), [microsoft](), [mvc](), [net](), [news](), [revenue](), [saas](), [software](), [stack-overflow]() ### AI overview Joel Spolsky announces that Stack Overflow is looking for a new CEO. He is stepping away from day-to-day operations to become chairman of the board, while describing the company's growth, profitability, products, employees, and audience. ### Source excerpt We're looking for a new CEO for Stack Overflow. I'm stepping out of the day-to-day and up to the role of Chairman of the Board. Read more "The next CEO of Stack Overflow" ## Памятка начинающего программиста DevFeed: [Памятка начинающего программиста]() Original publisher: [Read original article]() Published: 2016-11-09T09:12:28Z Content type: opinion Language: ru Sources: [Blog by Michael Dubakov]() Topics: [ASP.NET](), [Domain-driven design (DDD)](), [Artificial Intelligence]() Tags: [ai-ml](), [asp-net](), [ddd]() ### AI overview A Russian-language advice article for programmers with a few years of experience. It recommends seeking responsibility early, following industry trends, learning English, blogging, studying broader software concepts, building personal projects, and avoiding prolonged outsourcing work. ### Source excerpt Я часто получаю резюме от программистов. Возьму на себя смелость дать несколько конкретных советов тем, кто в профессии пару лет. Конечно, советы только для тех, кто хочет стать отличным программистом. 1. Первую работу найти непросто. Раньше было очень непросто, сейчас, конечно, все гораздо легче. Но если у вас получится, постарайтесь не попасть сразу в огромную корпорацию. В таких местах слишком много формализма, устаревших процессов и мест, где можно не напрягаться. И нет ничего хуже для новичка быть в расслабленной атмосфере на задворках аутсорса. Лучше выбрать стартап с маленькой зарплатой и большой неопределенностью, пока вы можете себе это позволить. Там у вас будет больше ответственности и развитие будет идти гораздо быстрее. Год за два :) 2. Всеми правдами и неправдами избегайте старых технологий. ASP.NET, O/R mappers, ExtJS, MSSQL, Oracle, Windows -- оставьте вот это все ветеранам. Вам может быть пока сложно понять, куда все двигается, но постарайтесь интересоваться трендами отрасли. Не все новое одинаково полезно, но со временем вы научитесь выбирать и лучше поймете, чего вы хотите и что вам интересно. 3. Учите английский. Вы как минимум должны научиться свободно читать техническую литературу. Без этого крайне сложно стать хорошим программистом. 4. Заведите блог. Вам кажется, что вам не о чем писать. Конечно же, это не так. Любое новое знание, усвоенное вами и выраженное письменно с учетом ваших личных переживаний и мыслей, может быть полезно другим. Напишите 100 постов. Потом можно решить, продолжать или нет. 5. Не зацикливайтесь на книгах о технологиях. Конечно, у вас есть явная потребность углубиться в ASP.NET на работе, но разбавляйте такие книги более абстрактной литературой. Почитайте про ООП и ФП, почитайте про дизайн систем, почитайте о разных концепциях (микросервисы, конкурентность, DDD, AI/ML). 6. Программируйте дома. Начните свой проект. Неважно какой. Простое мобильное приложение. Движок для сайта. Трекер расходов. Выбор следующего фильма для п ## Stack Overflow: The Architecture - 2016 Edition DevFeed: [Stack Overflow: The Architecture - 2016 Edition]() Original publisher: [Read original article]() Published: 2016-02-17T00:00:00Z Content type: article Language: en Sources: [Nick Craver]() Topics: [Stack Overflow](), [ASP.NET](), [Redis](), [SQL](), [Hardware](), [servers](), [elasticsearch](), [Server]() Tags: [architecture](), [asp-net](), [blog](), [cloudflare](), [elasticsearch](), [hardware](), [http](), [load-balancer](), [performance](), [redis](), [servers](), [sql]() ### AI overview This article describes Stack Overflow's 2016 architecture using daily traffic and performance statistics from February 9, 2016, compared with November 2013. It covers HTTP requests, page loads, SQL queries, Redis hits, Elasticsearch searches, Tag Engine requests, and processing times. The author attributes reduced ASP.NET processing time to a 2015 hardware upgrade and application performance tuning, then lists the main server and load-balancer hardware. ### Source excerpt This is #1 in a very long series of posts on Stack Overflow's architecture. Welcome. Previous post (#0): Stack Overflow: A Technical Deconstruction Next post (#2): Stack Overflow: The Hardware - 2016 Edition To get an idea of what all of this stuff "does," let me start off with an update on the average day at Stack Overflow. So you can compare to the previous numbers from November 2013, here's a day of statistics from February 9th, 2016 with differences since November 12th, 2013: 209,420,973 (+61,336,090) HTTP requests to our load balancer 66,294,789 (+30,199,477) of those were page loads 1,240,266,346,053 (+406,273,363,426) bytes (1.24 TB) of HTTP traffic sent 569,449,470,023 (+282,874,825,991) bytes (569 GB) total received 3,084,303,599,266 (+1,958,311,041,954) bytes (3.08 TB) total sent 504,816,843 (+170,244,740) SQL Queries (from HTTP requests alone) 5,831,683,114 (+5,418,818,063) Redis hits 17,158,874 (not tracked in 2013) Elastic searches 3,661,134 (+57,716) Tag Engine requests 607,073,066 (+48,848,481) ms (168 hours) spent running SQL queries 10,396,073 (-88,950,843) ms (2.8 hours) spent on Redis hits 147,018,571 (+14,634,512) ms (40.8 hours) spent on Tag Engine requests 1,609,944,301 (-1,118,232,744) ms (447 hours) spent processing in ASP.Net 22.71 (-5.29) ms average (19.12 ms in ASP.Net) for 49,180,275 question page renders 11.80 (-53.2) ms average (8.81 ms in ASP.Net) for 6,370,076 home page renders You may be wondering about the drastic ASP.Net reduction in processing time compared to 2013 (which was 757 hours) despite 61 million more requests a day. That's due to both a hardware upgrade in early 2015 as well as a lot of performance tuning inside the applications themselves. Please don't forget: performance is still a feature. If you're curious about more hardware specifics than I'm about to provide--fear not. The next post will be an appendix with detailed hardware specs for all of the servers that run the sites (I'll update this with a link when it's liv ## Publishing a ASP.NET 5 Web-Application to IIS Locally DevFeed: [Publishing a ASP.NET 5 Web-Application to IIS Locally]() Original publisher: [Read original article]() Author: Abhinaba Basu \[MSFT\] Published: 2015-12-22T18:10:48Z Content type: tutorial Language: en Sources: [Abhinaba Basu]() Topics: [ASP.NET](), [web applications](), [Visual Studio](), [Windows](), [Firewall](), [Web Development]() Tags: [asp-net](), [firewall](), [visual-studio](), [web](), [windows]() ### AI overview A practical guide to publishing an ASP.NET 5 web application to IIS locally using Visual Studio and file system publishing, then configuring IIS to serve the application. It also explains enabling Windows Firewall access and finding the local IP address so other devices on the same network can connect. ### Source excerpt I ran into few issues and discovered some kinks in publishing the new ASP.NET 5 Web-Application to... ## How we build Targetprocess DevFeed: [How we build Targetprocess]() Original publisher: [Read original article]() Author: Andrew Khmylov Published: 2015-06-18T00:00:00Z Content type: tutorial Language: en Sources: [Despite the odds]() Topics: [Web Development](), [JavaScript](), [Single-page application (SPA)](), [ASP.NET](), [C#](), [Authentication](), [Authorization](), [Routing (disambiguation)](), [Back end]() Tags: [asp-net](), [authorization](), [c-sharp](), [client](), [frontend](), [javascript](), [routing]() ### AI overview A developer explains how Targetprocess is built as a large single-page web application, focusing on its JavaScript frontend, C# server APIs, and ASP.NET application startup. The article introduces authentication, authorization, routing, and ASPX-generated configuration. ### Source excerpt Preface For the last 2 years my professional career have been diverging further and further away from the path it was set on early. I've started as a desktop application developer a long time ago, occasionally building web APIs on the server-side and doing some mobile app development, and then slowly getting into the frontend web development. Nowadays, working at Targetprocess, I think I'm spending roughly 70% of the time on the frontend (mostly general presentation logic and client-side business rules, not the crazy HTML markup/positioning/styling stuff) and 30% on server-side APIs. This is not a marketing post, but I'd like to give you some context on the things I'll be talking about. Targetprocess is an agile and visual project management tool [1], so you may expect it to be a fairly sophisticated on the visual interface side. Indeed, it's a massive single page web application written mostly in JavaScript on the client-side and C# on the server. At the same time, I see that some fellow developers still don't believe that it's possible to build anything beyond a simple product promotion website or a landing page with a toy language with JavaScript, which is only good for document animation. That's a common misconception I hear quite often from the friends doing mostly server-side and mobile things, and I'd like them (and any other reader) to see how the things look from my point of view. I also think that the details on how we build a large product may be interesting for anyone in the web development business. [2] With no further delay, let's dive right into the technical details! Application startup The entry point to the client app is a usual ASP.NET web application, which handles authentication, authorization and a top-level routing. Those things should be of no surprise for anyone familiar with building web applications with ASP.NET or any similar technology, so I won't go into details here. The authorized user is redirected to the main ASPX file. If you're no ## 'object' does not contain a definition for 'errors' DevFeed: ['object' does not contain a definition for 'errors']() Original publisher: [Read original article]() Published: 2013-08-29T00:00:00Z Content type: tutorial Language: en Sources: [Juri Strumpflohner]() Topics: [Exception](), [Testing](), [ASP.NET](), [Visual Studio]() Tags: [api](), [asp-net](), [errors](), [exception](), [exceptions](), [testing](), [unit-test](), [visual-studio]() ### AI overview A unit test for an ASP.NET Web API exception filter fails when it tries to inspect the anonymous object returned for validation errors. The article explains that the anonymous type is not visible outside the tested Api assembly and shows that adding InternalsVisibleTo to Api.csproj makes the test pass. ### Source excerpt Lorem ipsum dolor sit amet ## ASP.net MVC Action Methods: Testing Against Anonymous Return Types DevFeed: [ASP.net MVC Action Methods: Testing Against Anonymous Return Types]() Original publisher: [Read original article]() Published: 2013-01-17T00:00:00Z Content type: tutorial Language: en Sources: [Juri Strumpflohner]() Topics: [mvc](), [Testing](), [ASP.NET]() Tags: [assembly](), [controllers](), [mvc](), [testing](), [types]() ### AI overview A tutorial on testing ASP.NET MVC action methods, including how to inspect values returned through ActionResult and how to test anonymous return types with dynamic access. It also explains granting the test assembly access to internal anonymous types. ### Source excerpt Lorem ipsum dolor sit amet ## Retrospective 2012 DevFeed: [Retrospective 2012]() Original publisher: [Read original article]() Published: 2012-12-30T00:00:00Z Content type: opinion Language: en Sources: [Juri Strumpflohner]() Topics: [Jekyll](), [JavaScript](), [GitHub](), [hosting](), [CSS](), [Bootstrap](), [ASP.NET](), [mvc](), [JSON](), [Single-page application (SPA)]() Tags: [asp-net](), [css](), [github](), [hosting](), [javascript](), [jekyll](), [json](), [mvc](), [rest](), [retrospective]() ### AI overview A personal retrospective of 2012 covering a move from Blogger to a Jekyll static site hosted on GitHub, a site redesign using Bootstrap, and increased JavaScript work. The author also describes replacing ASP.NET WebForms front ends with JavaScriptMVC applications and ASP.NET MVC JSON REST endpoints. ### Source excerpt Lorem ipsum dolor sit amet ## Programming ASP.net MVC4 by J. Chadwick, T. Snyder and H. Panda DevFeed: [Programming ASP.net MVC4 by J. Chadwick, T. Snyder and H. Panda]() Original publisher: [Read original article]() Published: 2012-12-13T00:00:00Z Content type: opinion Language: en Sources: [Juri Strumpflohner]() Topics: [ASP.NET](), [mvc](), [web applications](), [Web Development](), [JavaScript](), [jQuery](), [Routing (disambiguation)](), [Authentication]() Tags: [asp-net](), [authentication](), [best-practices](), [caching](), [javascript](), [mvc](), [routing](), [techniques](), [web-development]() ### AI overview A review of the book Programming ASP.net MVC4 describes its coverage of ASP.NET MVC development, from MVC fundamentals, routing, authentication, and application architecture to deployment, client-side JavaScript, mobile web development, and production practices. The review presents the book as suitable for both beginners and experienced developers. ### Source excerpt Lorem ipsum dolor sit amet ## Output Caching in ASP.net MVC DevFeed: [Output Caching in ASP.net MVC]() Original publisher: [Read original article]() Published: 2012-10-28T00:00:00Z Content type: tutorial Language: en Sources: [Juri Strumpflohner]() Topics: [ASP.NET](), [Caching](), [mvc](), [jQuery]() Tags: [asp-net](), [browser](), [caching](), [javascript](), [mvc]() ### AI overview This tutorial explains output caching in ASP.NET MVC, including default response behavior, cache-control headers, ways to disable server and client caching, and the use of the OutputCache mechanism. It also discusses caching effects on AJAX requests. ### Source excerpt Lorem ipsum dolor sit amet ## Lessons Learned: Don't Expose EF Entities to the Client Directly DevFeed: [Lessons Learned: Don't Expose EF Entities to the Client Directly]() Original publisher: [Read original article]() Published: 2012-10-23T00:00:00Z Content type: opinion Language: en Sources: [Juri Strumpflohner]() Topics: [ASP.NET](), [mvc](), [API](), [Back end](), [JavaScript](), [web applications]() Tags: [api](), [architecture](), [asp-net](), [backend](), [javascript](), [json](), [mvc](), [rest]() ### AI overview The article examines the risks of directly exposing Entity Framework entities through an ASP.NET MVC REST backend to a rich-client JavaScript application. It highlights oversized JSON responses caused by entity relationships and warns that exposing entities couples the client to backend implementation details. ### Source excerpt Lorem ipsum dolor sit amet ## Strange Error When Downloading File in IE8 from SSL Site DevFeed: [Strange Error When Downloading File in IE8 from SSL Site]() Original publisher: [Read original article]() Published: 2012-07-15T00:00:00Z Content type: tutorial Language: en Sources: [Juri Strumpflohner]() Topics: [ASP.NET](), [Caching](), [Internet Explorer](), [SSL](), [mvc](), [browser]() Tags: [article](), [asp-net](), [browser](), [caching](), [firefox](), [internet-explorer](), [mvc](), [ssl]() ### AI overview A troubleshooting article explains that IE8 fails to download files generated by an ASP.NET MVC backend from an SSL-protected site when cache-control headers prevent caching. It proposes overriding the default output-cache behavior for file downloads in IE versions below 9. ### Source excerpt Lorem ipsum dolor sit amet ## Why I hate generated code DevFeed: [Why I hate generated code]() Original publisher: [Read original article]() Published: 2011-12-26T00:00:00Z Content type: opinion Language: en Sources: [Tim Kellogg]() Topics: [Code generation](), [maintenance](), [Rails](), [ASP.NET](), [mvc](), [SQL]() Tags: [asp-net](), [code-generation](), [maintenance](), [mvc](), [rails](), [software]() ### AI overview The author argues that generated source code can create maintenance problems when it produces large amounts of unused or dead code. The article distinguishes this from compiler output and just-in-time code generation, which the author considers useful because it is generated only when needed. ### Source excerpt If you've worked with me for any amount of time you'll soon figure out that I often profess that "I hate generated code". This position comes from years of experience with badly generated code. Let me explain.The baby comes with a lot of bathwaterIn the past year I had an experience with a generated data layer where CodeSmith was used to generate a table, 5 stored procedures, an entity class, a data source class, and a factory class for each entity that was generated. My task was to convert this code into NHibernate mappings.The interesting thing about this work is how little of the generated code was actually being used. I'm sure, in the beginning, the developer's thoughts were along the lines "oh look at all this code I don't have to write manually :D". However, after some time, subsequent developer's thoughts were along the lines of "with all this dead code, it's hard to find real problems". It's funny how some exciting breakthroughs turn into headaches down the road. The table is always used, but some entities are created & read but never modified, others are only created during migrations and only read from during run time.Code generators often produce code you don't need. Since all code requires maintenance, dead code is just a liability because it doesn't provide any benefit. I always delete dead code and commented out code (it'll live on in version control, no need to release it into production).There are several professional developer communities that generate code as a way of life. Ruby on Rails comes prepackaged with scripts to generate models, views, and controllers in a single command. ASP.NET MVC will generate controllers and views with a couple clicks. And if you've ever used either of these frameworks, you'll probably find yourself deleting a lot of generated code.The problem of transient code generationThe issue that I keep running into with my policy of hating code generation is that it's nearly impossible to be a professional software engineer and [Next page]()