Why doesn't ClickOnce in Visual Studio deploy content files from dependent assemblies?

File and asset naming: Where can I look for a rational approach that is applicable to a digital design workflow?

• As a motion graphic designer, part of a studio that interacts with freelancers, we see all kinds of file and asset naming habits. Problem is, they are all half improvisation and half mysterious dogmas. We have to name project files, asset files, and output files based on the project they originate from. We have to name layers and groups inside the files based on their content. We have to build a folder structure to accommodate a workflow that allows from the output of one project to serve as assets for another project. I think that to stick, the naming methodology should be logical. From tricks to come up with consistent descriptive names for the content all the way down to the spacing character usage. I seriously researched the subject many times but never found anything usable as a starting point.

• Answer:

  Thanks for the ask: This question requires a lot more information before answering. I'm going to assume we're not talking about client folders, account service folders, billings, correspondence, or any folders/assets not related to creative, production, or development. So, if this is true, I find this method to work the best. Top level folders are named after the program. These are assets that have been created within one program. PSD, IA, INDD, DOC, PDF, etc. When a project begins or is officially opened, these folders then become asset folders within the main project folder, which is labeled by date. As for file naming: 021813_QuoraHomePage_0001.psd Date, descriptive short name, numerical versioning starting in the thousand range. This also allows people to reference locations/files verbally, as well. "It's in the IA folder," "Check PSDs, today's date, version 3 or 4" Example: Within folder 021813_QuoraHomePage: CDA DOC HTML IA INDD MPG PSD   021813_QuoraHomePage_0001.psd   021813_QuoraHomePage_0002.psd (if it's a version from the same day)      Archive        010412 (previous archive date/batch)            010412_QuoraHomePage_0001.psd            010412_QuoraHomePage_0002.psd            010412_QuoraHomePage_0003.psd       Output (jpegs or pdfs, file types for other to review) QT It's typical in large working environments for people to be responsible for taking your asset folders and moving them over to another department's asset folders. Eventually, 021813_QuoraHomePage_0001.psd may go to DEV. And then within DEV, they'd have their respective framework. Departments are highest level possible. For methodology within the program specific folders, I'll offer that most people just say: be organized. A web page design in Photoshop could have Header, Footer, Content, Interstitials, Main Nav, Sub Nav as it's top tier folder structure, but once you drill down, it's relative to the native creator. Maybe their vector art is Illustrator Art saved as a smart object, or it's a vector object within Photoshop... No way to control that entirely. Depending on who I'm working with and their respective skill sets, I'll put CSS notes on the layer names sometimes. Other times I'll create SmartObjects instead of Folders, with a functional spec layer turned off until someone needs it. Essentially, people need to respect each other and work together to create a common framework. Those that think it's silly or don't have time for it should probably work by themselves. It depends on the size of your team and how well skills overlap. Great project managers and producers usually create Asset Matrices or Development Matrices for tracking files and who's worked on what. But this is another form of naming, versioning, and tracking. As I said initially though, this is relative and subjective to your team, company, or even industry.