You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure if this is necessarily a SlowCheetah issue or not...I have the Log4net.xml config file defined in a central location and have added the file (and transforms) to each project via add existing item as linked-file.
When publishing my console and web-based apps, the log4net.xml file is transformed but our TFS build (configured with /p:DeployOnBuild=True /p:DeployTarget=Package /p:DestinationManifestRootPath=) acts differently:
It will tranform both app.config and web.config files.
It will also transform the log4net.xml files associated with web-base applications but will not do that for our console applications.
We've modified the project files of the console apps so that we can use web deploy to package them. I'm not sure if this is interfering with the transformation process.
I'm at a loss.
Thank you,
Marshall
The text was updated successfully, but these errors were encountered:
Hello,
Not sure if this is necessarily a SlowCheetah issue or not...I have the Log4net.xml config file defined in a central location and have added the file (and transforms) to each project via add existing item as linked-file.
When publishing my console and web-based apps, the log4net.xml file is transformed but our TFS build (configured with /p:DeployOnBuild=True /p:DeployTarget=Package /p:DestinationManifestRootPath=) acts differently:
We've modified the project files of the console apps so that we can use web deploy to package them. I'm not sure if this is interfering with the transformation process.
I'm at a loss.
Thank you,
Marshall
The text was updated successfully, but these errors were encountered: