Hi,

Could someone tell me ANY way that they use version control to manage their DNN skins?  I understand that not everything is a one-size fits all but I'm not able to gain any insight into approaches that people are taking for skinning.

It general it seems like it is may be a bad practice to version the portal itself rather than the custom development work for the portal.  In the case of module development, it seems that there are good examples on keeping isolated projects.  Can this be done with skins?

I would like to use Visual Studio 2010 and TFS 2010 for my development.

Thanks,
Scott

Scott,

I use VS2010 & TFS for source control on skins and modules.  Start by adding a TFS project (for example called DNNDEV).  Say your local TFS path is something like:

c:\tfs\DNNDEV

Now copy your local dnn installation to that directory. (don't add it to source control!) We use the install version, not the source version.  Next, in the TFS source code explorer, add the skin folder(s) you want to keep in source control.   (say c:\tfs\dnndev\portals\_default\skins\myskin)  that should do it.