Having spent a month building an installer for an enterprise ASP.NET application, and watching it fail 50% of the time due to ACL restrictions, I can say that WPI and it's deployment packages are an ambitious task, and they've done pretty well. These applications are installed with default settings, or really the settings they had when a developer used MS's web deployment wizard, or web package builder to create them - dig too deep into this technology, and you'll get woozy quick.
WPI can be configured to read third-party RSS feeds. It actually works most of the time, and does a good job registering ASP.NET into IIS.Īdditionally, the WPI will read a default RSS feed from MS, which publishes popular Open Source IIS applications, like CMS, Blog and ECommerce systems. NET 2,3.5&4, ASP.NET, ASP.NET MVC, SQL Server Express, then installs and configures those applications if they are not there.
Recently, MS released the Web Platform Installer WPI, which is a master installer that checks for the existence of IIS. Off the top of my head, they include: Visual Studio Web Developer Express, SQL Server Express, IIS Express (which is IIS stand-alone, but bundled with WebMatrix, so don't hold your breath for a stand-alone distributable of IIS, which would be real awesome). WebMatrix is a compilation of technologies that MS has put out over the past few years.
I use ASP.NET MCV, the latest version, every day, at the day job, and it's pretty easy to get stuff done, provided you are committed to an MS stack.
0 kommentar(er)
