All geek questions in one place

How to avoid the chaotic deployment of ASP.NET web applications?

So here it is.

I am developing an existing one (it began to be an ASP classic application, so you can imagine: P) a web application under ASP.NET 4.0 and SQLServer 2005. We are 4 developers using local instances of SQL Server 2005 Express, with source code and a project Visual Studio Databases

This webapp has several "universes" (as we call it). Each universe has its own database (currently on the same server), but they all have the same scheme (tables, sprocs, etc.) and the same source / site code.

Therefore, manual deployment is really annoying because I need to deploy the source code and then run the SQL scripts manually in each database. I know that manual deployment can cause problems, so I'm looking for a way to automate it.

We recently created a Visual Studio database project to manage the schema and create diff-schema scripts for different purposes.

I have no idea how to collect fragments

I would like to:

  • You have a way to make the “synchronization” take place on the target server (fortunately, I have full access to the RDC servers so that I can set things up if necessary). When deploying sync, I mean that I don’t want to fully deploy the entire application because it has a lot of files, and I just want to deploy these new ones or change them.
  • diff-sql script. -.
  • sql script .

MSBuild, MS WebDeploy, NAnt .. , , .

, , , .

, , , , , , . .

,

,

+3
1

Multi-Tenancy? , , , "", ...

:

http://en.wikipedia.org/wiki/Multitenancy

http://msdn.microsoft.com/en-us/library/aa479086.aspx

UPDATE:

( ), , , /db, SaaS? .. / , ..?

, (PaaS):

. http://en.wikipedia.org/wiki/Platform_as_a_service

( ):

1:

, . URL-, / byt, .. ( ).

2:

, . "TenantID" , TenantID, . / URL-, TenantID , . ( )

+1

Source: https://habr.com/ru/post/1743071/

More articles:


All Articles