Any of you who go back with me are very accustomed to seeing "DBVT" code samples, like when I posted about CSTiers, an early version of what would become the Drive Template Library for Community Server.
DBVTUser user = DBVTContext.Current.DBVTUser;
if (user.IsInBillingGroup)
do something...
or
DBVTConfiguration dbvtConfig = DBVTConfiguration.GetConfig();
image.ImageUrl = Globals.ApplicationPath + "/images/" +
dbvtConfig.UploadImageFileName;
When I decided to package my CodeSmith CS templates as Drive I replaced all DBVT references in the template library with "DRIVE." Now that Drive has been released and I'm working with the actual framework every day, I feel it's time I moved away from using DBVT as well. It's time for DRIVE.
Using examples of Drive code here and on the Drive site blog instead of DBVT is basic Marketing 101. Coding with Drive references and in DRIVE-think will also most likely result in more frequent posts to the Drive blog with samples of the framework in action.
Below is a screenshot from a Community Server project that I transitioned to DRIVE-think. Needless to say, there were a lot of DBVT files and references requiring update, both in the renamed "DRIVE" class library and in the Web project. To update the client website files I used WinMerge's excellent diff ZIP function to zip-up the changed files only.
In DRIVE-think, the old DBVT code excerpt becomes
DRIVEUser user = DRIVEContext.Current.DRIVEUser;
if (user.IsInBillingGroup)
do something...
or
DRIVEConfiguration driveConfig = DRIVEConfiguration.GetConfig();
image.ImageUrl = Globals.ApplicationPath + "/images/" +
driveConfig.UploadImageFileName;
