.net - Distributing ASP.NET applications -
we released asp.net (.net 2.0) application. application files pre-compiled , installer generated in visual studio. it's pre-compiled it's written in delphi prism, not c#.
everything worked while testing, once in wild, started see several issues e.g.
- the installer refuses install saying application installed, though "remove previous versions" option set in install builder.
- the installer seems sensitive setup of iis. e.g. if ii6 compatibility not installed ii7, installer exits no error message.
- when trying connect app, users "failed access iis metabase" (still not figured out is).
- there doesn't seem way create app pool in installer. therefore, .net 2.0 application can end app pool using .net 3.5/4.0.
these of issues we've encountered.
is there better method of distributing asp.net applications doesn't require advance knowledge of end user's system? doing stupid? if these common problems, there fool proof installs install nicely and, if problems occur, provide users informative error messages.
as there have been no answers in year , half guess there's no better answer 1 came with.
we used innosetup run asp.net installer. however, first checks if asp.net installed and, if is, uninstalls it. @ least gets around first issue mentioned in question.
Comments
Post a Comment