Home Dashboard Directory Help
Search

web publish doesnt copyfiles by chuck02323


Status: 

Closed
 as Fixed Help for as Fixed


1
0
Sign in
to vote
Type: Bug
ID: 764776
Opened: 9/26/2012 9:39:33 AM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

http://stackoverflow.com/questions/12201146/visual-studio-2012-web-publish-doesnt-copy-files/12393154#12393154
Details
Sign in to post a comment.
Posted by Microsoft on 10/3/2012 at 3:23 PM
Thanks Chuck,

We're hoping to be able to release an update to our publish feature, including this fix, sometime soon, but I don't have a specific date available. It will be announced on http://blogs.msdn.com/b/webdev/ when it does come out.

In the meantime, I'm going to resolve this bug as fixed since it is the issue we've already identified.

Thanks!
Posted by chuck02323 on 10/3/2012 at 3:18 PM
Jimmy,
The problem does seem to resemble that of the posting you referenced.
The workaround of changing publish settings from release to debug. Re-publish and then change back to Release does appear to work.

We hope that the fix to the issue is released soon.

We are using and have only used vs12 RTM
Posted by Microsoft on 10/3/2012 at 10:42 AM
Hi Chuck,

Can you confirm if the issue I described was the same bug you were encountering?

Thanks,
- Jimmy Lewis
SDET, Visual Web Developer team
Posted by Microsoft on 9/27/2012 at 1:27 PM
Hi Chuck,

We had a bug in VS2012 RTM which would cause this to happen if the profile's .pubxml.user file was generated incorrectly. This can be worked around by changing the build configuration for the profile. Can you confirm whether this resolves the issue for you?

We have a fix for this issue internally, and we're currently working on the schedule to ship the next update for our publish feature.

Thanks,
- Jimmy Lewis
SDET, Visual Web Developer team
Posted by Microsoft on 9/26/2012 at 9:51 AM
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.