Web Deploy Failing After Upgrade to VS 2012 - webdeploy

I have a project, for which the publish (web deploy) to localhost was working under VS 2010. I made no changes to the project, other than opening it in VS 2012 RC.
The publish from VS 2012 RC failed when I attempted it, with message saying that the service does not exist, even though the site exists in IIS and can be posted to.
Now when I open the project in VS 2010 and attempt to publish, the publish fails with the same issue. Other projects where I have not attempted a publish in VS 2012 RC still have working publish profiles.
Has anyone else run into this issue, and if so, what have you done to correct it? I have looked into all the usual issues as to why a publish might fail, but publishes of other projects to IIS as local host on the same machine are working, so I think that rules out any failing services.

Your question is quite old. I propose installing not RC, but final VS and to the newest update - ms guys fixed a bunch of problems.

Related

Web Setup Project on Visual Studio 2022 - Unable to open project error

Good evening,
I have created a Web Form using Visual Studio 2022, and I have created a Web Setup project to help our customers to install the site on their server. I used the official extension that allows to create Setup projects in VS2022 (Microsoft Visual Studio Installer Projects); everything worked fine until some days ago, when VS2022 started to show the following error when trying to load the installer project:
"Unable to open project .../Setup.vdproj".
This is the error I am getting when I try to open/create a Web Setup project
I tried to open it also with VS2019, which I still had installed on my computer, but I got the same error.
At the beginning I thought it was an issue related to the project (maybe for some reasons some files had been corrrupted), so I tried to create a new Web Setup project, both on VS2022 and VS2019. Again, the same error appeared, on both versions of VS. At this point I tried to load the already existing project on another computer, and on the other computer everything worked perfectly, the project was loaded immediatly and no issues have been detected.
I tried to unistall and re-install the Microsoft Visual Studio Installer Projects extension, it didn't solve the problem; I tried to repair VS2022, it didn't solve the problem; I tried to completely uninstall VS2022 and VS2019 and re-install only VS2022, and guess what? It didn't solve the problem.
Does anyone know how to fix this problem, and what is the reason why I am unable to neither load nor create Web Setup projects?
Thank you,
Giacomo

VS2015: The components for communicating with FTP servers are not installed

I have been using Visual Studio 2010 Pro for my vb.net desktop application development. I publish the apps via clickonce to a web server with ftp. My settings look like this:
Publishing folder location: ftp://www.webaddress.com/folder/
Installation folder : http://webaddress.com/folder/
This works perfect in VS2010.
I am now trying to upgrade to Visual Studio 2015 community edition. When I try to publish my app, I get the error "The components for communicating with FTP servers are not installed". I am getting this error on both computers I have installed VS2015 on.
Strangely enough, there isn't much info on this error. The only solution I've seen is to repair the installation. I did this but still a no go.. Another cause I read about is having Xamarin installed, but I have never had that installed.
Has anybody run into this and know what the fix is??
EDIT:
It appears to not actually have anything to do with installed components. After I posted this question, I realized the publish via FTP had worked earlier on a little sample Hello World project i made (brain fart). It was only once I loaded my existing project that this error started showing up.
I closed the solution, created another simple project, and still got the error. I closed visual studio, reopened the sample project, and ftp worked! I then opened my existing project and ftp worked there too?! So I don't know what the trigger is, and I haven't had it fail again yet, but maybe this info will help figure out what is causing the failure.
EDIT (3/30/2017)
Just an update - I am still having this issue. This issue happens on visual studio 2013, 2015, and 2017. I have tried reinstalling the c++ redistributable, still nothing. It seems others are having this issue with a web project but mine is a desktop app publishing with clickonce via FTP. It must be something to do with solution I am working on that was originally created in 2010, as the issue is not present in any other project.
I had the same issue with Visual Studio 2017. What fixed it for me was to start the Visual Studio Installer and install the ".NET Core cross-platform development" workload.
I had the same issue in Visual Studio 2015 / Update 3. It was resolved after installing the 32-bit version of Visual C++ Redistributable Packages for Visual Studio 2013 (https://www.microsoft.com/en-us/download/details.aspx?id=40784)
See also https://github.com/aspnet/Tooling/issues/748
I had the same problem with Visual Studio 2015. And Publish used to work fine so I went going crazy looking for and trying different solutions. Then I read on another thread of doing a Setup-> Repair (submitted by Erikest). I did a Setup->Repair and the publish process now works! I think it's also possible that the Repair not only did the trick on the FTP components but also replaced the C++ redistributable (often mentioned as a solution to this problem),
This is a total work around, but I've noticed I get this error every time I open my app (that originated in VS2010) and try to publish without first opening a sample app. I created a new project and published it to my FTP server. When I receive this error, I close Visual studio, reopen and the open the sample project, publish that app, then open my real app. The publish then works.
This works every time, and seems to be a bug in Visual studio, and probably has something to do with the fact that my app was originally built in 2010.
Maybe this will help somebody else with the same issue. It's a big pain so hopefully MS gets a fix in for this.
I have been banging my head against this problem for many months, re-installed VS over and over and just did a clean install of Windows 10 in the hope it would work but to no avail. By chance I cleaned some old .accdb files from the App_Data folder that I no longer need since I converted to SQL Server database and FTP publishing now works.
So it seems VS does not like the .accdb files but was happy with .mdb files when publishing with FTP.
As soon as I put the file back in App_Data the problem returns. Hope this is some help.
I had the same issue here, I was using the Publish right click option on the project, which had been working fine. What fixed it for me was going back through the publish options and re-testing the connection. Publish seemed to work after that. Maybe it forgot a password or settings?
I also installed the x86 C++ Redistribution Package.
Hope this helps someone who is in the same boat.
After many successful website publishes with Visual Studio 2015 Community Edition, we experienced the "components for communicating with ftp servers are not installed" issue. :(
First attempt at resolution was uninstalling VS Community 2015, then installing VS Community 2017. Received the same error: "components for communicating with ftp servers are not installed" when attempting to publish our business website.
With some work, we found that by uninstalling Microsoft Web Deploy and re-installing, this seemed to fix the problem. We can now use Visual Studio > Publish function to our ftp without problems.
See this link for download of Microsoft Web Deploy components.
https://www.microsoft.com/en-us/download/details.aspx?id=43717
Dont know what broke this VS IDE functionality, but hope this fix helps some.
I encountered the same error with Visual Studio 2019
I fixed it by using the Visual Studio Installer to install the Web Deploy (inc .netcore 2.1) under individual components
I just did a simple "repair installation" in the installer. Worked for me.
I am using Microsoft Visual Studio Community 2019 and had this problem for a while.
The problem went away after I updated about 10 NuGet updates that were over due.
I had the same problem, I closed all the open windows I closed Visual Studio and then I opened again and published and then it worked!

msbuild this application couldn't be started

i've got computer with Windows 8 and fresh installation of Visual Studio 13 Express.
I'm working on project which runs on .NET 4.0 Client profile.
Problem is when i try to complile, this error message is shown:
Solutions:
social.msdn : This one says:
try to restart your VS and rebuild - not working
check MSbuild from promt - not working (Message is shown twice)
I also checked project configuration vsproj and tried to make sample project
Reinstall framework:
i tried ot reinstall almost everything, framework, sdk.
when i've installed .NET Framerork v4.5.2 my VS was unnable to start and anoter .NET apps complied before had missing library
I haven't tried to reinstall VS, yet. (But i dont think if it helps)
Edit: Temporary solution shoud be Visual Studio Express 2012, but it not solves problem.
Reinstalaion of VS didn't help.

Getting Auto Deploy to work with MSBuild on a build server

Please pardon a newbie's question about MS TFS and Visual Studio 2012, I hope I'm using the correct vocabulary.
Our shop has recently moved to MS TFS and Visual Studio 2012 to build internal web services for integration. Currently we have a TFS 2010 Server running on Server2008R2 and a Build server on a Windows 7 box, our dev application server is also running Server2008R2. I have been given the job of getting a nightly build and deployment running. I have the build definition working but the deployment portion is not functioning. I have installed Web Deploy on both the dev application server and the build server as per these articles:
http://www.kevingao.net/version-control/how-to-auto-deploy-web-application-with-tfs-build-server.html
and
http://www.iis.net/learn/install/installing-publishing-technologies/installing-and-configuring-web-deploy
We have configured an user, web_deploy_dev in active director and that user is a local admin on the dev app server.
The parameters added to the build definition are:
/p:DeployOnBuild=True
/p:DeployTarget=MsDeployPublish
/p:MSDeployServiceURL="https://PA-APPSRV1-DEV:8172/msdeploy.axd" /* double quotes not in original code */
/p:DeployIISAppPath="DW/DWServices" /* E:\Webroot\DW\DWServices */
/p:CreatePackageOnPublish=True
/p:MsDeployPublishMethod=WMSVC
/p:AllowUntrustedCertificate=True
/p:UserName=migp\web_deploy_dev
/p:Password=******
I suspect that MSBUILD is not even calling msdeploy.exe as I see no errors in the windows event and application logs, but I do not know all the places to look. I can use a web browser and connect to the service on the dev app server as the web_deploy_dev user from the build server, I receive a web page not found error after inputting user name and PW, but I assume that is to be expected.
I am at a loss as to where to look next, I've tried searching the web but nothing I try seems to work.
Thank you in advance for your help and input.
Roy
It sounds like you are experiencing a problem where your build completes and claims success, but you aren't getting any error and nothing is actually deployed. When I've experienced this with my TeamCity build server, the problem was that MSBuild was not set up on the machine that would do the building and deploying. These are my steps to resolve the problem I think you might be having:
Make sure that at least Visual Studio Express is installed. you can tell if a full enough version of Visual Studio is installed by navigating to the
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\ directory. If you see folders like 10.0, 11.0, or '12.0', look inside them and verify that there is a Microsoft.WebApplications.targets file. Note the versions that pass that check.
In your Build Configuration, add a /p:VisualStudioVersion=12.0 or whatever version of Visual Studio is appropriate.
Let me know if this gets you anywhere or not. I'm really curious to hear if you are finding any errors or logs anywhere. Basically, in my experience using Web Deploy and MSBuild with TeamCity, if the machine that is building and deploying doesn't have the MSBuild installed with the Microsoft.WebApplication.targets file, it silently fails.

Sharepoint 2010 workflows via VS2010 - really need server installed locally?

I went to create a SP2010 Workflow project in VS2010, and it complained that I did not have SP Server installed on my machine.
Well, I do not want to install SP2010 on my dev machine. I have a perfectly good dev instance installed onto a VM.
Is it possible at all to design SP 2010 workflow projects in VS2010 without having a local instance of Sharepoint?
Cheers,
Daniel
Well, it looks like the answer is "No, you must have SP2010 installed locally"
Will VS let you continue after receiving that message?
Microsoft recommendation is to install Visual Studio on the your DEV VM (running Windows Server 2008 R2) that has SharePoint running. You'll also get additional debug features by doing this, like F5 debugging/breakpoints, and auto deploy/retract of your solutions.