Last post Sep 17, 2012 09:34 PM by WebD
Sep 17, 2012 09:34 PM|WebD|LINK
I am starting to take things to the next level with my web application programming experience and wanted some input from the community.
I have always been a Pro-Microsoft software kind of a guy. That is why I still use VB.NET, ASP.NET SQL.
But now the time has come when I am looking into other stuff such as Version Control and DB Schema Control.
For version control, I have heard of Subversion, Git, and Visual Studio 2012 Source Control - Team Foundation Server.
For DB Schema control, I have heard of Red Gate, and what Visual Studio 2012 can do out of the box from what I have researched so far.
My project is in it's infant steps into becoming a full blown team project. Right now my setup consists of two seperate projects. Project A: Clients can see. Project B: Administrative/reporting system.
In the future Project A will have multiple instances for each client I have. So there could be thousands of instances. Each instance will be slightly different from the next. But I might have one customer who might want custom logic which will cause their
instance to become different and so forth. I might have new versions and customers might want to upgrade. But at the end of the day, everyone is in their own sandbox enviornment with their own instance. What I want to be able to do, is figure out how I
will manage this as this business grows? What is my best route?
Project B: will be a uniformed interface that will be backwards and compatible with all of Project A.
What are your thoughts and experience?