Publish Web Application FAILS!

Posted by lugospod on 4/13/2013 at 2:19 AM

After installing SP2 for visual studio, publish for x86 is not publishing any files. ANY BUILD profile is still working...so basically, i was wrong to install the SP2 last night :(

Posted by WillSullivan on 4/10/2013 at 1:27 PM

Fixed? I just tried to do this (11.0.60315.01 Update 2) and can confirm that it is NOT fixed. Good job, guys!

Posted by Microsoft on 3/20/2013 at 7:55 AM

Hi Kaarel S,

The fix for this issue is not in the VS2012 Update 1, but it is available with the Azure SDK or in the Web Tools 2012.2 update. It will also be included in the final release of VS2012 Update 2.

Thanks,
- Jimmy Lewis
SDET, Visual Web Developer team

Posted by Kaarel S on 3/20/2013 at 5:40 AM

To accompany the last comment the version of Visual Studio is:
Microsoft Visual Studio Premium 2012, Version 11.0.51106.01 Update 1, Microsoft .NET Framework, Version 4.5.50709

Posted by Kaarel S on 3/20/2013 at 5:38 AM

A team mate created a publish profile. Set the configuration in the profile wizard to Debug. This matched his solution build configuration. The publish worked on his machine. He then checked the changes in to TFS. I pulled the changes to my machine. Publish did not publish any files even though the message in output windows said the publish was successful. Because the profile was set to delete existing files the end result was that the publish rather than publishing actually just deleted the whole web application.

I finally figured out that the configuration in the publish wizard is Release. When I changed that to Debug it worked again. It seems that the configuration in the publish wizard is not being saved. At least not in the pubxml where other publish profile settings are. That means every team member has to explicitly update their publish profile after getting the solution from source control.

Posted by Microsoft on 11/29/2012 at 11:03 AM

Hi Charlie, please install the latest Azure SDK from here: http://www.windowsazure.com/en-us/develop/net/. In it contains an update to Web Developer Tools 1.1 which fixes this issue.

Please email me directly johnwen [at] microsoft.com if you have any questions or problems.

Thanks,
John Wen
Visual Web Developer Team

Posted by Charlie Shen on 11/27/2012 at 2:32 PM

Please tell me that I'm doing something wrong and that this has been fixed in Visual Studio 2012 Update 1 because I have the patch installed and the problem still exists on my end.

If not, please provide a hotfix.

Thanks,
Charles

Posted by WOHIE on 10/25/2012 at 7:14 AM

Hi, I have the same issue but none of the workarounds worked. In the end it turned out that the problem lay with ReSharper. I suspended it from running and everything published fine.

Paul

Posted by Microsoft on 10/24/2012 at 11:04 AM

Hi Simon_Baer,

That is the 2nd issue I described below. We will have an update available for this soon with the fix for this issue, and its release should be announced at http://blogs.msdn.com/b/webdev/. In the meantime, the workaround is as you describe - change the value of the build configuration and then you should be able to change it back.

Thanks and sorry for the issue,
- Jimmy Lewis
SDET, Visual Web Developer team

Posted by Simon_Baer on 10/24/2012 at 12:27 AM

I can confirm and reproduce the following bug in the latest RTM version of VS2012 regarding publishing of web applications:

When I create a new publishing profile, a .pubxml and .pubxml.user file is created. But only the .pubxml file is checked in in TFS.
When my collegue retrievs the latest code from TFS, a .pubxml.user file is created locally on his computer, but this file is empty. He cannot publish using this profile. However when he creates a new publishing profile with the same settings than mine it works. A workarround is also to switch the configuration in the publish settings from release to debug and run the publish. This seems to recreate the .pubxml.user file with the correct content and afterwards publishing works.

Best regards,
Simon

Posted by Microsoft on 10/23/2012 at 3:27 PM

Hi Nicolai,

Are you sure you're seeing the same problems that the OP in this bug encountered? The issue specifically occurred if the web project had a different Configuration|Platform configured than the selected solution configuration. This issue was fixed in an update for VS2012 RC and in VS2012 RTM.

There is a separate, related bug in VS2012 RTM where the publish profile might get into a state where the build configuration information is not persisted correctly. Similarly in this case, the publish operation will fail to find the files needed to publish. The workaround for this is to change the build configuration for your profile, then change it back and save.

If you're encountering a separate issue than these, can you give more details?

Thanks,
- Jimmy Lewis
SDET, Visual Web Developer team

Posted by Nicolai Schlenzig on 10/23/2012 at 2:23 PM

This issue is NOT fixed in the latest version of VS2012.

I have to delete my publish profile and create it again to get things going.

The new publish profile is EXACTLY the same as the previous one, but it now works.

This happens 1 in 2 times or so. Really frustrating...

Posted by Microsoft on 10/19/2012 at 10:38 AM

Thanks for reporting the issue. The issue is now fixed in Visual Studio 2012 RTM.

Posted by Geir-Tore Lindsve on 10/10/2012 at 1:52 AM

I struggled with publishing too yesterday, and the workaround to switch from File System -> WebDav and back worked for me.

In case you guys are still struggling with replicating this bug, I will be coming to Redmond for \\Build\, so feel free to let me know if you want to see it on my computer.

Posted by westhedge on 10/2/2012 at 2:02 PM

So what's the score here? Is there NO update to this bug??? Are we going to see an update. My business is CRIPPLED by the decision to "upgrade" to VS 2012 as we can no longer roll out new releases to customers.

We should have stayed with 2010. At least that worked. Oh. and we also had setup and deployment projects that we now have to pay over $6K to InstallShield to get the same functionality. Thanks.

Posted by RubenP on 9/27/2012 at 10:12 AM

I'm having the same problems after installing the Azure Tools June 2012 SP1 update for VS2010. No errors, just nothing happens. (Except deleting existing files.)

Manually editing empty .pubxml.user files solved the problem for me a few times; deleting them sometimes also worked, sometimes didn't, same for changing build configurations.

I'm considering uninstalling the Web Publish component (1.0.30810.0), as it's obviously too broken to use.

Posted by H. J. van der Wijk on 9/5/2012 at 7:12 AM

This problem is new for me in Visual Studio 2012. In VS 2010 I never had this problem when publishing to an UNC

Posted by Microsoft on 9/4/2012 at 9:16 AM

@H. J. van der Wijk, I believe the behavior you describe is actually a property of all Windows processes, not just Visual Studio. If you change the drive mappings, you'll need to restart VS.

Posted by H. J. van der Wijk on 9/3/2012 at 8:11 AM

Visual Studio caches the directory and drive information and does not do a refresh. Even after mapping a drive letter, the new drive letter is not visible in Visual Studio (it is visible in Windows explorer) Visual studio does can't do a publish to the new mapped drive letter with the message 'The path 'V:\xxx' does not exist or you do not have access. The system cannot find the path specified.

Posted by guyven69 on 8/29/2012 at 8:12 PM

Hi, has anyone solve this problem / concrete solution? I'm having the same problem, I already tried all the recommendation from this topic but still not working.

THanks!

Posted by lns2 on 8/25/2012 at 9:20 AM

A Rebuild All on a website project fixed the problem for me.

Posted by Microsoft on 8/24/2012 at 10:24 AM

Harry and NipivRamuk, can you guys also email me using the address below? We haven't been able to pin down the cause for this, and email works better for trying to nail it down.

Thanks!

Posted by Harry Pfleger on 8/23/2012 at 1:24 AM

Addition: I have to do the following, EVERYTIME I deploy: Switch from "File System" to "Web Deploy" and back, then publish.

Posted by NipivRamuk on 8/22/2012 at 11:52 AM

I am having same issue. Tried Harry's work around. but it didn't worked for me.

I am using VS2012 Ultimate

Posted by Harry Pfleger on 8/22/2012 at 2:05 AM

I believe I found a work around:
In the “Publish Web” dialog, under „Connection“ switch from "File System" to "Web Deploy", enter the necessary information. Try to publish, if it fails, that’s OK.
Now switch back to “File System” and try to publish again. It should work now!
I could imagine that there are some configuration settings sitting around from pre-RTM versions…
Cheers Harry

Posted by Microsoft on 8/20/2012 at 10:04 AM

@Jimseiwert, can we work this out over email? My address is jimmy dot lewis @ microsoft. I think that will be easier/faster than trying to work it out over this Connect issue. Thanks!

Posted by Jimseiwert on 8/17/2012 at 10:30 AM

Is there any update on this now that VS 2012 was released?. Issue is still in the RTW version

Posted by Ethics Gradient on 8/9/2012 at 9:43 AM

Experiencing this exact issue - no files are copied. At version 1.0.30628.0. The publish profile was created on a different machine and was working there - having switched to a different machine it quit working. Editing the publish profile (changing deployment method, running it, and changing it back) resolved the issue.

Posted by Jimseiwert on 8/1/2012 at 12:29 PM

I still have the issue as well after installing the update. I am currently at version 1.0.30628.0

Posted by Microsoft on 7/27/2012 at 11:35 AM

Hi JHubSharp,

What version of the Web Developer Tools extension do you have installed? You can find this in Help -> About Visual Studio, or in Tools -> Extensions and Updates.

Thanks,
- Jimmy Lewis
SDET, Visual Web Developer team

Posted by JHubSharp on 7/27/2012 at 11:30 AM

I'm noticing this problem also, even after updating the tools. My solution publishes fine in 2010, but in 2012 it creates the folder on the file system and copies no files.

Posted by Microsoft on 7/13/2012 at 4:36 PM

Hi Andrew and Michael,

I have some good news! We've just released an update for VS2012 RC which contains the fix for this issue. You can find more information at http://blogs.msdn.com/b/webdevtools/archive/2012/07/12/visual-studio-2012-rc-web-tooling-extensions-update.aspx.

Thanks,
- Jimmy Lewis
SDET, Visual Web Developer team

Posted by Microsoft on 6/13/2012 at 12:00 PM

Hi Andrew,

This was a bug in how we handle the solution configuration vs. the project configuration. We incorrectly assumed that they would be the same (e.g. Solution's Release|x86 would have each project set to Release|x86 as well), which caused us to use the wrong build properties for publishing files.

The workaround is to make the solution configuration and build configuration match. This issue will be fixed in the next release of Visual Studio 2012.

Thanks,
- Jimmy Lewis
SDET, Visual Web Developer team

Posted by Andrew Ritz on 6/12/2012 at 1:15 PM

@Microsoft
Please take a look at Michael's comment for more information. His workaround 'resolves' the issue, but of course now VS crashes with each publish. At any rate, the "Build Configuration" option in the Settings tab should be fixed, or removed if it doesn't do anything.

Posted by Andrew Ritz on 6/12/2012 at 1:12 PM

@Michael
Thanks for the workaround, but the problem is still due to a bug in the publishing options, not a "misconfiguration" on my part. My project targets x86 after all...

Posted by Michael Beurskens on 6/9/2012 at 5:43 AM

I guess you misconfigured the Publish-options.
The new dialog is significantly more sophisticated and now requires you to enter the target platform. It (erroneously) defaults to "Release - x86" or "Debug - x86" which will not copy the necessary files. Instead you should set it to "Release - Any CPU" or "Debug - Any CPU" and things should work again...

Michael

Posted by Microsoft on 6/8/2012 at 5:20 PM

Hi Andrew,

We have been unable to reproduce this issue so far. Can you provide some more details?
- Is there anything special about your publish destination, such as a UNC path?
- There should be a folder under your project directory like obj\Release\Package\PackageTmp. Does this directory have the right files in it? (note: Release is the build configuration.)
- Does it publish any subfolders in your app? There should be some text in the Output Window that looks like this:
2>Publishing folder /...
2>Publishing folder bin...

Thanks for any info you can provide,
- Jimmy Lewis
SDET, Visual Web Developer team

Posted by Microsoft on 6/4/2012 at 11:15 PM

Thank you for submitting feedback on Visual Studio 11 and .NET Framework. Your issue has been routed to the appropriate VS development team for review. We will contact you if we require any additional information.

Posted by MS-Moderator01 on 6/4/2012 at 8:42 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)

Posted by Kaarel S on 3/20/2013 at 5:31 AM

Experiencing a similar issue. I got it working by explicitly ensuring that the configuration in the publish profile matches the solution build configuration (eg Debug, Release).

Posted by Miha Markic on 10/3/2012 at 3:38 AM

I've created another publishing profile (similar to suggestion in comments - this one is a copy though) with same settings and it worked. If/when this second profile stops working I'll try re-use the first I guess.

Posted by MattJordan on 9/5/2012 at 1:57 AM

I removed the recently updated web publish v1.0.30810.0

Posted by H. J. van der Wijk on 9/3/2012 at 8:18 AM

The solution is to open the unc in Windows Explorer. Then restart Visual Studio, so the cache for the drive information gets refreshed.

Publish Web Application FAILS! by Andrew Ritz