Hi Jacci.

As to the installation, it's pretty much a copy operation, depending only on whether you need to put the assemblies into the GAC or the application folder, but I've only deployed one app, so I'm in no way an expert.

As to the SQL Server issue:

1) Scripting is the only way I know of to do it
2) You can use Xcase to do a diff on two SQL Server databases and generate a synchronization script
3) You can use SQL Compare to do the same thing, but IMO Xcase does a better job (but is more expensive)
4) I'm working on a tool to address this issue - you'll still need the scripts, but it's more of a script administration tool, designed specifically for deployment/maintenance issues, and designed to be incorporated into an application (similar to SDT). Don't know how long it'll be in development (it's a "spare time" project) but I'll let you know when it's ready for beta testing <g>



>Hi All,
>
>I understand .NET web application installations are supposed to be easy, but we are running into several issues. One of which is dealing with SQL Server database changes. Is there a SQL Server tool out there like SDT?
>
>Also, what are the procedures of creating installation CDs for .NET web applications with a SQL server backend? Can one use WISE or INNO do do these things? What about setting up IIS?
>
>I'm just trying to find out what the "masses" are using or the procedures to creating .NET web app installs.
>
>Thanks,
>Jacci