Search

No extensibility from UI for File System Publish in Web Applications by JAGlick

Closed
as Deferred Help for as Deferred

1
0
Sign in
to vote
Type: Bug
ID: 780051
Opened: 2/26/2013 12:00:57 PM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
The extensibility available from the commandline is not available in the UI when using File System Publish, so extensions are not able to extend the functionality.
Details (expand)

Visual Studio/Team Foundation Server/.NET Framework Tooling Version

Visual Studio 2012

Steps to reproduce

Install an extension such as SlowCheetah, which transforms config files during publish. Add transforms for Debug, Release, etc. When you do a File System publish via the GUI, SlowCheetah is unable to extend the functionality and transform the config files after the build but before the publish.

Product Language

English

Operating System

Windows 8

Operating System Language

English

Actual results

Actions taken by an extension (such as SlowCheetah config file transformations) take place after the file has been copied to the bin directory.

Expected results

Actions taken by an extension (such as SlowCheetah config file transformations) should be able to take place before the file has been copied to the bin directory.
File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 3/13/2013 at 9:09 PM
Hi JAGlick, thanks for posting this. I was hoping that this would be something simple that we could take care of as a bug fix. Unfortunately it looks like it will be a significant amount of work, and will need to be prioritized with our other features. In order to help with this I've created a new item at http://aspnet.uservoice.com/forums/41199-general-asp-net/suggestions/3743796-file-system-publish-extensibility. Let's see how much interest there is for this.

I will resolve this item at this time, but feel free to re-open it if I have misunderstood anything.

Thanks,
Sayed Ibrahim Hashimi | http://msbuildbook.com/
Posted by Microsoft on 2/27/2013 at 12:42 AM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.

Posted by Microsoft on 2/26/2013 at 12:50 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.