You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@mrdavidlaing - thanks for getting the ball rolling on all of this.
I think there really are only two types of .NET apps that will be hosted in Cloud Foundry - Console and ASP.NET apps. I don't think differentiating by application framework is necessary since these apps should be totally self-contained when deployed ("bin deployable").
Concerning types - I'm starting to think that containers is perhaps a better name; it will probably boil down to installing the dependancies and generating the "start" script to actually launch your application.
Console -> no dependancies, with start script being "mono MyConsoleApp.exe" for Mono runtime and "MyConsoleApp.exe" for .NET CLR runtime
IIS -> iishost.exe dependancy + startup script to launch iishost on the correct port
xsp -> nginx + mono xsp + startup config to link nginx to xsp's fastcgi interface
Concerning frameworks - I've been poking into the java-buildpack notion of frameworks, and these seem to be mainly concerned with autoconfiguration - i.e, injecting DB connection params.
Maybe this is the right way to think of frameworks; ie, configuration frameworks, of which a specific app could have several:
Like the cloudfoundry/java-buildpack, the .NET buildpack is composed of a number of components
The text was updated successfully, but these errors were encountered: