Comparison of Empty Versus Web API ASP.NET Web Application Templates (VS 2013)

Update 10/2016 - This posting is better viewed in my new blog.


A quick comparison of the complexity of Web API versus Empty templates in ASP.NET Web Application creation. Values were recorded through inspection of the projects and the project folders after a successful debug compile.

Empty template, Web API core references

  • NuGet Packages: 5
  • References: 22
  • Files: 61
  • Folders: 33
  • Size: 12.3 MB


Web API template, MVC and Web API core references

  • NuGetPackages: 34
  • References: 48
  • Files: 374
  • Folders: 157
  • Size: 62.3 MB


Comments

Post a Comment

Popular posts from this blog

ClickOnce, Squirrel and Nuts

Image
Update 10/2016 - This posting is better viewed in my new blog . Background In a  post two years ago I expressed my admiration of ClickOnce. At the time we'd experienced years of tremendous success using it as our client application's primary deployment mechanism and since that time it has not faltered. I now regret to say that over the last year I've seen evidence that makes me question continued reliance on ClickOnce. I think its life-cycle may be coming to end. Though that saddens me I understand that in the tech world all technology is transient and the best ideas don't always last as long as they should (see Silverlight). Data, however, must continue flowing. About eight months ago I started searching for alternative deployment mechanism which might provide some of the benefits we'd leveraged with ClickOnce. That search came up mostly wanting. However, one candidate identified was the open source project Squirrel.Windows . The moniker on the GitHub proj...
Read more

How HTML5 destroyed my CSLA dream

Update 10/2016 - This posting is better viewed in my new blog . Let me start by stating, emphatically: I LOVE CSLA .NET ! I first became aware of this excellent framework in 2008 when my boss dropped Rocky's book Expert C# 2008 Business Objects on my desk. In very short order I recognized the enormous benefits CSLA could provide to developers like myself who where trying to to produce great enterprise applications. The idea that I could create completely self-contained classes which would flow naturally between the various application layers and physical tiers made me fairly giddy with excitement. This excitement was reinforced by my efforts as I implemented user presentation layers for WinForms, WPF and Silverlight all based on the same business core with little impedance between the architectural layers or the physical tiers. Concerns such as validation and n-level undo were mostly handled by the CSLA framework with very little additional effort from the developer (me). ...
Read more

A Walk Through Azure Functions

Image
Update 10/2016 - This posting is better viewed in my new blog . Rocky Start I saw the initial announcement for Azure Functions in one of the Azure newsletters. I watched two channel9 videos and read what documentation I could find. I even emailed a friend about it. I was pretty excited. My first experience with Azure Functions was a couple months back. It did not go well. I selected a C# HTTP Trigger template as my first function type and the pain began. Nothing worked as expected and I was met with frustration at literally every level. By the end of the night I'd decided the Azure Portal's Blade for Azure Functions had some significant usability and stability issues. I ended the night extremely frustrated. Two weeks later I took another look at Azure Functions. Whatever issues the Azure Functions Blade was having during my previous attempt appeared to have been resolved. Where previously the simplest change to function code would fail to be executed, changes were sudd...
Read more