I started a fresh new ASP.NET Core project targeting .NET Core in Visual Studio 2017 -- final version.
I installed a bunch of NuGet packages for authentication. What does the yellow warning mean? Looks like I only have it for Microsoft.AspNetCore.Authentication and Microsoft.AspNetCore.Authentication.OAuth. The Facebook and Google packages seem OK. Any idea what the issue is?
UPDATE: Closing VS 2017 and reopening it seems to have fixed the issue. I'm seeing quite a few issues like that with VS 2017 where closing and reopening it seems to make problems go away. Am I the only one having this issue? Any suggestions on how to get VS 2017 to behave correctly?
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!
with VS 2015 Enterprise i get always following message on a solution while debugging: XAML Visual Diagnostic is either disabled or is not supported by the current application
Tools - Options - Debugging - General:
Enable UI Debugging Tools for XAML is enabled
Preview selected elements in Live Visual Tree is enabled
I have tried:
VS Restart
Clean Solution / Rebuild
Fresh Checkout
Curious: If i start the solution without debugging and i attach the debugger to the process, it works ...
Update:
If i select "Enable native code debugging" in project settings - debug, it works !
I needed an additional debugging option to be disabled in order for the tools to work with my projects:
Tools - Options - Debugging - General:
Use Managed Compatibility Mode --> disabled
I also faced this problem for some WPF projects that came to my pc from various sources. In my case the problem was in the project target framework - it was set to .NET Framework 3.5. The Live Visual Tree and the Live Property Explorer in VS 2015 do not work with .NET 3.5:
Inspect XAML properties while debugging
https://msdn.microsoft.com/en-us/library/mt270227.aspx
So I just changed the target framework to .NET Framework 4.0 in the project properties dialog (the Application tab) to make these 'live' tools work.
I faced the save issue on VS 2019. It happened all of a sudden on a project which it used to work on. Restarting VS did not help. But it got resolved after PC restart.
If you're having that problem in VS 2017 while debugging on a remote machine, installing the Visual C++ 2017 Redistributable (x64 in my case) made UI debugging work.
I always had this VM where UI debugging worked but my colleagues couldn't get it to work on their machines until I was experimenting with something where I had to uninstall all redistributables. After finishing my experiments I realized I couldn't debug the UI anymore. I reinstalled the 2017 redistributable and the functionality got enabled again.
I have installed visual studio ultimate 2012 for windows 8 store apps but it doesnt show JavaScript in the new project.
The setup is good, i have installed it before using the same setup but i dont know what is the problem now..
I have also tried Visual studio Express, but got the same issue.. And one more thing BLEND is also not working in both the cases.
Are you looking in the right place? They can be 'hidden' in "Other Languages"
Search in the upper right hand corner of "New Project" for javascript to be sure.
Make sure you are up to date as well on the following updates as good measure
http://support.microsoft.com/kb/2797912
http://www.microsoft.com/en-us/download/details.aspx?id=38188
After uninstalling the current VS and then deleting all registries and finally installing Vs 2012 ultimate, fixed the issue.
We are using MVVM Light Toolkit (from Galasoft - Laurent Bugnion).
Until now we were using Visual Studio 2010.
Everything was working well (thanks to Laurent).
Two days ago we moved to Visual Studio 2012.
And now Intellisense is no longer working in Xaml files (but still working in code-behind).
After looking on forums and made some tests, it appears that we have an issue with "GalaSoft.MvvmLight.Extras.SL5.dll".
As soon as GalaSoft.MvvmLight.Extras.SL5.dll is removed from project references, intellisense is working again.
Someone already had same problem and/or know a solution ?
Thanks.
Alain.
We had a similar problem when we migrated from Silverlight 4 to 5. We were using a local copy of GalaSoft.MvvmLight.Extras.SL5.dll copied from another computer.
Once we installed the MvvmLight .msi package and changed the reference in our Silverlight project to C:\Program Files (x86)\[...]\GalaSoft.MvvmLight.Extras.SL5.dll, IntelliSense started working again.
Hope this helps