Preview transform only works for Project configurations about slow-cheetah HOT 7 OPEN

This is the only reason I even "need" to use slowcheetah -- to preview, because nothing else will do this. I am using octopus deploy / nuget to do the actual build transform step. I just need something that lets me preview the darn files. The old version works for this and I will continue to use that until something else comes along: https://github.com/sayedihashimi/slow-cheetah/releases/tag/v2.5.48

from slow-cheetah.

Related to https://slowcheetah.uservoice.com/forums/185106-general/suggestions/4227888-allow-transforms-based-on-solution-configuration-s and https://slowcheetah.uservoice.com/forums/185106-general/suggestions/9294063-allow-config-transforms-that-are-not-tied-to-build

from slow-cheetah.

SlowCheetah needs to determine if these files are actually transform files or if they are just part of the project. As I stated in #46, generating transforms for configurations that are not part of the project would not work since on build, the configuration would just default to an existing one for that project. As for specifically previewing transforms that you generated for other processes, it seems like a good idea.
One possible way to do this is to look ate the parent of the file and see if the name of the files match. Unfortunately, I can't think of a way to know if file A is a transformation file corresponding to file B unless A is nested under B or if A has a name corresponding to a configuration of the project.

from slow-cheetah.

unless A is nested under B

Exactly, our projects are setup just like that.

Do you think using SlowCheetah as a 'preview' tool is a good fit? Or should I look into creating an extension limited to preview only. This has the added benefit of not needing a nuget package import.

from slow-cheetah.

I think SlowCheetah is a complete tool, especially since it now includes JSON transformations. If you want to write your own preview tool, that could be fine although it might have limited functionality.

from slow-cheetah.

I think this could be a feature to have metadata that allows for custom transform names that map back to a configuration.

Example:

<None Include="Web.Acceptance.config">
  <DependentUpon>web.config</DependentUpon>
  <IsTransformFile>True</IsTransformFile>
  <TransformConfiguration>Debug</TransformConfiguration>
</None>

from slow-cheetah.

As far as "generating transforms for configurations that are not part of the project would not work since on build, the configuration would just default to an existing one for that project": anything that happens "on build" doesn't affect previewing transforms. I don't want the build to transform configs, but I do want to be able to preview the transforms. I've started on a fork that restores that functionality.

from slow-cheetah.