I have a web application that I am installing. We want to be able to send out "patches", specific to each client. Basically, what the "patch" does is it updates some stored procedures in the database specific to that particular client. The thing is is that we don't want it to increase the version number. Is there some other way, besides a patch project, or some tips that you can give us to accomplish this?
In other words, say, client A purchases and installs our application at version 1.0.0. After conferring with the client, looking at their current systems, we create a number of stored procedures that imports data to our application that are custom to client A's existing systems. We bundle these stored procedures into an installable "patch". The client runs the installer, and the stored procedures are added/updated to the database, but the application's version number stays at 1.0.0. A year later, we update our application and add bunch of functionality to it and client A is sent the new application and installs it. The new files are installed, the system is updated, but the previously "patched" stored procedures are left alone. The application is now set at version 2.0.0.
FOLLOW US
Get the latest news in Application Packaging