SlowCheetah: converted files from a class library project are not copied to the specified projects

Scenario:

I have a class library project with custom .config files. To build these configuration files, they are set to Content and Always Copy. This library project then refers to at least 4-5 console applications within the same solution. When the solution is built, the class library assembly and custom configuration files are copied to the bin folder of the referenced projects.

What I'm trying to do:

Using SlowCheetah to Convert Custom Configuration Files

Problem:

Although SlowCheetah converts configuration files to a class library project, it does not copy the converted file to referenced projects. that is, it always copies the source / source file.

Found a couple of other threads, but none of them was a solution based on SlowCheetah, any suggestions would be helpful. Please note that I am using Install Shield Limited Edition, so the solution should work for .msi / setup files. In addition, I do not want to link files and apply the conversion in related files, since then I would have to do the same conversion in all the projects referenced.

thanks

+8
app-config slowcheetah
source share
2 answers

Given the ClassLibararyA of the ClassLibraryB reference:

  • Make sure the configurations from both class libraries are called App.config
  • Customize conversions for App.configs using SlowCheetah (even if you only care about one)
  • Build

In the output folder for ClassLibraryA you will find ClassLibraryB.dll.config (converted by App.config ClassLibraryB).

0
source share

I know this is not a solution, but this is what I found on this issue, as I have the same problem. Adding this here, as it is too much to add a comment, and hopefully in the end it will be the answer when they close the error.

I know that a slow cheetah is in maintenance mode, but they are still fixing bugs, and it looks like Microsoft will be building the project, so I hope they fix it.

This case is found here, where they admit that this is a mistake, but then it seems that they are fixing another problem.

https://github.com/sayedihashimi/slow-cheetah/issues/34

so I opened a new bug report here

https://github.com/sayedihashimi/slow-cheetah/issues/174

0
source share

All Articles