Installation packages for server applications.
-
Hi. This is a general discussion post, that i've posted in the System Administration forum as well. I've come to a point where i have a finished ASP.NET web application that i want to distribute. It use ASP.NET web as a front-end, .NET Windows as a front-end for the SQL Server backend db. I want to create some sort of installation package for my application. I should do the following things: 1) Create FTP login 2) Create Virtual Directory in IIS 3) Copy ASP.NET files to virtual directory 4) Duplicate SQL database 5) Update web.config file in ASP.NET app. At the moment i have some issues on point 4. What is the best approatch on duplicating SQL server databases programaticly. Are there any pre-made serverinstaller packages? Got any good articles/guitlines on the subject? In general, i need some info on what is the best approatch to take when distributing a server app. -Jonas
-
Hi. This is a general discussion post, that i've posted in the System Administration forum as well. I've come to a point where i have a finished ASP.NET web application that i want to distribute. It use ASP.NET web as a front-end, .NET Windows as a front-end for the SQL Server backend db. I want to create some sort of installation package for my application. I should do the following things: 1) Create FTP login 2) Create Virtual Directory in IIS 3) Copy ASP.NET files to virtual directory 4) Duplicate SQL database 5) Update web.config file in ASP.NET app. At the moment i have some issues on point 4. What is the best approatch on duplicating SQL server databases programaticly. Are there any pre-made serverinstaller packages? Got any good articles/guitlines on the subject? In general, i need some info on what is the best approatch to take when distributing a server app. -Jonas
Jonas Follesø wrote: At the moment i have some issues on point 4. What is the best approatch on duplicating SQL server databases programaticly. Are there any pre-made serverinstaller packages? Got any good articles/guitlines on the subject? You can create a custom action for your MSI installer, simply by creating an "Installer Class" (select it from the File/Add New Item). IIRC, there is a sample for creating a database in a custom action on MSDN, but sorry, I can't remember where now. My latest article: GBVB - Converting VB.NET code to C#