davidfowl

Redmond, WA

davidfowl.com

Age: 28

Developer on the ASP.NET Team working on all sorts of awesome.

2h
answered How log to the Output window with ASP.Net vNext/5
2h
comment Is vNext completely "convention based programming"?
Check this out gist.github.com/davidfowl/700097cca459c1e78c86
2h
answered How to reference two versions of the same DLL on ASP NET 5 solution
17h
comment ASP.Net 5 (vnext) how to queue background task and access ApplicationServices
Nooo, pass the service provider in to your background task
17h
comment Observer for fire&forget Task
HostingEnvironment.QueueBackgroundWorkItem is not available in ASP.NET 5, don't even bother trying to use it. System.Web isn't around so it might do unexpected things or just outright explode.
17h
comment Dynamically load assemblies in ASP.NET 5
Beautiful :). That's great! It won't load again, it's cached.
17h
comment ASP.Net vNext App_Data folder
string path = AppDomain.CurrentDomain.GetData("DataDirectory").ToString(); will not work on CoreCLR
17h
answered ASP.Net self-hosted application
17h
comment ASP.Net self-hosted application
You can totally do this today
18h
comment Dynamically load assemblies in ASP.NET 5
Consider the MVC approach to find controllers. MVC looks at all libraries that reference MVC, and then loads only those and checks to see if there are any controllers defined in there.
18h
comment ASP.NET 5 (vNext) web project: library conflict upgrading from beta4 to beta6
Yes that example is correct. If you dnvm upgrade foo, it will set an alias foo to the upgraded version. If you set an alias, that you always update then you never have to touch global.json
18h
comment Updating to ASP NET 5 beta5 breaks everything
Nah that doesn't really matter so much. It would reduce noise but it's harmless for the most part.
18h
comment vNext Owin Middleware
blogs.msdn.com/b/webdev/archive/2014/11/14/…
18h
comment Updating to ASP NET 5 beta5 breaks everything
Yep! You got it! As an aside, the reason you want to remove the -* when the actual beta comes out is because we do some weirdness when we deploy to NuGet.org to make it easy to install official versions. When we publish to nuget.org, we remove build numbers. This means that 1.0.0-beta5-{somebuild} > 1.0.0-beta5, this isn't great but it makes it easier to find the right version of the package.
18h
answered Simplest Razor page in ASP.NET 5 vNext
18h
comment Dynamically load assemblies in ASP.NET 5
Most of the time you don't actually want to look at loaded types. What exactly are you trying to do?
20h
comment ASP.NET 5 (vNext) web project: library conflict upgrading from beta4 to beta6
Correct, that means it'll use the default alias. The other way to float is to be explicit about the alias in the sdk.version field. We don't support floating versions in global.json.
20h
revised Updating to ASP NET 5 beta5 breaks everything
deleted 21 characters in body
20h
comment Updating to ASP NET 5 beta5 breaks everything
1.0.0-beta5 came out. That's the last version of beta5. There's no need to specify build numbers or floating versions. It's meaningless.
20h
comment Dynamically load assemblies in ASP.NET 5
You should avoid loading all assemblies and try to use ILibraryManager in a way that doesn't do that if possible.
1 2 3 4 5