When I try open my VS Solutions I get the following error:
When I click ok:
I see this error in the log file:
C:\Users\Dylan\Dropbox\Work\Code\FSK Logging Server\FSK Logging Server\FSK_LoggingClient\FSK_LoggingClient.csproj : error : Package 'Microsoft.VisualStudio.TeamFoundation.VersionControl.HatPackage, Microsoft.VisualStudio.TeamFoundation.VersionControl, Version=12.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' failed to load.
Does any one have any Ideas? I haven't been able to work all day. I have followed other advice on other forums etc. And I have not come right.
This happened after installing VS update 3 ?
Is there a way I can Unbind my projects from TFS so that I can at least work on them?
Hope this helps someone in the future:
This worked for me:
to solve this issue delete all the files under C:\Users\Developer\AppData\Local\Microsoft\Team Foundation\3.0\Cache and restart my VS2010 and everything gone as i need!
https://social.msdn.microsoft.com/Forums/vstudio/en-US/36f1d2e5-af78-4c8c-879e-a85dc2d6ef92/package-load-failure-microsoftvisualstudioteamfoundationversioncontrolhatpackage?forum=tfsgeneral
Run the Visual Studio installer, and choose repair. If that doesn't work, uninstall/reinstall Visual Studio.
I could resolve this issue after I re-installed the Team Explorer for VS 2013. http://www.microsoft.com/en-us/download/details.aspx?id=40776
Related
Getting this error when I select a "publish target" in VS 2015 update 3. Had a look for a while online but didn't see anything, so any help would be appreciated if you could point me in the right direction.
An error has occurred while processing the request: Method 'StopRemoteProfiler' in type 'Microsoft.VisualStudio.Web.WindowsAzure.AzureWebSite' from assembly 'Microsoft.VisualStudio.Web.WindowsAzure.Impl, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' does not have implementation
I updated to the to Azure sdk 2.9.6 last night because of a different issue but related where there was no error, but no existing apps were listed.
I can confirm that this works on my work computer and I have existing apps on Azure, but not working on my home computer.
I am a bit loath to uninstall and reinstall VS, so any help would be appreciated. Of course, if the only solution is to reset, then so be it.
Thanks,
Jarrod
I faced the same problem. This is what worked for me.
I updated the "Microsoft .NET Core 1.0.1 - VS 2015 Tooling Preview 2" by going to Menu -> Tools -> Extensions and Updates -> Updates -> Visual Studio Gallery. It shows all the available updates for your version of studio. Select the component to update. It should download a file named "DotNetCore.1.0.1-VS2015Tools.Preview2.0.3.exe" or something similar. When you run this file, if you have the software already installed then select the repair option. It will ask you to close any running instances of Visual Studio, also make sure you have internet connection.
Also if you are using Web Deploy to publish your app make sure you have Microsoft Web Deploy v3 or higher installed or you will get error. You can do it using Microsoft Web Platform Installer.
Hope it helps.
When I am trying to run an ASP.Net Core project in Visual Studio 2015, a Microsoft Visual Studio dialog appears "The project doesn't know how to run the profile IIS Express".
Does anyone know anything about this message, or how to fix it? I've searched Google and the MSDN. There's nothing in the build logs, or the Windows event log.
This dialog showed up for me when I had migrated a project from dotnet RC1 to RC2.
Before the fix I could still run it using dotnet run and from Visual Studio choosing the profile other than "IIS Express".
I had misread this guide and forgot the .Web
\DNX\Microsoft.DNX.targets –> \DotNet.Web\Microsoft.DotNet.Web.targets
After fixing this and restarting Visual Studio(not sure if needed) I could run the project using the IIS Express profile.
Should also be noted that as per the comments, adding .Web in the top level node is required in the xproj. <Project Sdk="Microsoft.NET.Sdk"> should be <Project Sdk="Microsoft.NET.Sdk.Web">.
In my case the issue was solved after added the ASP.NET and web development tool extension to my VS instalation.
To clarify the answer from hultqvist, it is a problem with the xproj. To fix it, edit the xproj directly and change this
<Import Project="$(VSToolsPath)\DotNet\Microsoft.DotNet.targets"
Condition="'$(VSToolsPath)' != ''" />
to this
<Import Project="$(VSToolsPath)\DotNet.Web\Microsoft.DotNet.Web.targets"
Condition="'$(VSToolsPath)' != ''" />
That is, insert Web twice.
There is an associated issue in the aspnet tooling repo.
I had the same issue and found a very simple solution for Visual Studio 2017. In Visual Studio 2017 go to Solution Explorer then right click on your project file. In the menu you will see "Set as StartUp Project". If you can select it then select it. Now run your project again.
I had a similar issue but with "MyProjectName" instead of IIS Express.
In my case, I was trying to start as a standalone application, so I cleaned the launchSettings.json
I inadvertently changed the "commandName" parameter from "Project" to "MyProjectName" and that caused the popup to show up.
Resetting it back to "Project" solved my issue, silly me 😁
I had a similar issue, In my case ASP.NET and web development is enabled but Development time IIS support is not checked in the optional sections.
Once I enable the Development time IIS support solved my issue.
You can get this error with RTM if <BaseIntermediateOutputPath gets corrupted or is incorrect in your .xproj file.
I had this same issue and after digging around for a while I discovered that I had dotnet preview v1.0.0-preview2 installed under Programs Files (x86) and a non-preview version in x64. I think VS is launching the x86 (preview) version but expecting to see the full version. To fix this, I did the following.
from programs and feature uninstall every visible dotnet core. (note: this did not remove the x86 preview)
go to https://www.microsoft.com/net/download/core#/sdk and install BOTH x86 and x64 SDK packages
open command line and from the root directory check run: dotnet --version (at the time of writting it was 1.0.4
fire up .net core project in VS 2017 and run.
When I did all of the above, I was able to start up the site in IIS Express from VS.
This happened to me after a failed update of visual studio 2017 15.9.4
Setup completed with warnings and when I checked the problems saw that .NET core SDK 2.1 installation is failed.
I will try to install it manually.
Otherwise currently the only solution I found is to uninstall visual studio and re-install it.
In visual Studio 2017, i fixed this error by doing the following two steps.
I went to add or remove a program in windows, and deleted everything ending with ".net". I then reinstalled them in the visual studio installer. Then loading the project again produced a new error, which condiosluzverde provided the solution to here:
How Can I Fix the Microsoft Visual Studio Error: "Package Did Not Load Correctly"?
Same thing happened to me, my project was working fine. I didn't do any RC1 to RC2 update & this popup appeared from nowhere.
I fixed the problem by updating visual studio. You can also consider repairing VS.
I'm trying to run an SSIS package in Visual Studio 2012. When I click the "Start" button I get this very odd error in a popup from Visual Studio:
Method not found: 'Boolean
Microsoft.SqlServer.Dts.Design.VisualStudio2012Utils.IsVisualStudio2012ProInstalled()'.
(Microsoft.DataTransformationServices.VsIntegration)
Clicking on the show technical information, I get this stack trace:
===================================
Failed to start project (Microsoft Visual Studio)
===================================
Method not found: 'Boolean Microsoft.SqlServer.Dts.Design.VisualStudio2012Utils.IsVisualStudio2012ProInstalled()'. (Microsoft.DataTransformationServices.VsIntegration)
------------------------------
Program Location:
at Microsoft.DataTransformationServices.Project.DataTransformationsPackageDebugger.LaunchVsDebugger(IVsDebugger iVsDebugger, DataTransformationsProjectConfigurationOptions options)
at Microsoft.DataTransformationServices.Project.DataTransformationsPackageDebugger.ValidateAndRunDebugger(Int32 flags, IOutputWindow outputWindow, DataTransformationsProjectConfigurationOptions options)
at Microsoft.DataTransformationServices.Project.DataTransformationsProjectDebugger.LaunchDtsPackage(Int32 launchOptions, ProjectItem startupProjItem, DataTransformationsProjectConfigurationOptions options)
at Microsoft.DataTransformationServices.Project.DataTransformationsProjectDebugger.LaunchActivePackage(Int32 launchOptions)
at Microsoft.DataTransformationServices.Project.DataTransformationsProjectDebugger.LaunchDtsPackage(Int32 launchOptions, DataTransformationsProjectConfigurationOptions options)
at Microsoft.DataTransformationServices.Project.DataTransformationsProjectDebugger.Launch(Int32 launchOptions, DataTransformationsProjectConfigurationOptions options)
Has anyone ever seen this error before or know what the issue might be? A bit of googling turned up absolutely nothing for me.
I was able to happily develop and run SSIS packages from Visual Studio 2012 without any issues just a couple days ago (I did reboot my PC over the weekend and some windows updates were installed)
ETA:
I was able to find a couple very recent technet posts about this here and here so I suspect this was something that broke in an update over the weekend. One post says he solved the issue by reinstalling, but of course I'd rather not go that route if I don't have to.
Open the Developer Command Prompt for VS212 as Administrator
execute the command cd "C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\PrivateAssemblies"
execute the command gacutil /if Microsoft.SqlServer.Dts.Design.dll
restart Visual Studio
Source msdn Fail to start project
For visual Studio 2013 execute the command cd "C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\PrivateAssemblies" in point 2 and then execute point 3 and 4.
The following is the command we have to use to resolve the issue:
"C:\Program Files\Microsoft SDKs\Windows\v8.0A\bin\NETFX 4.0 Tools\gacutil.exe" /if "C:\Program Files\Microsoft Visual Studio 11.0\Common7\IDE\PrivateAssemblies\Microsoft.SqlServer.Dts.Design.dll"
Make sure that your dll file and Gacutil.exe file locations are correct. It may be different in other systems.
Note: You should open your “Command Prompt” as an administrator to run the above command.
I experienced the same problem.
Downloaded and installed SQL Server 2012 SP2 and that seemed to have fixed the problem.
Hope this helps!!
This is probably happening because you have Visual Studio 2013 and the BI tools for it installed also. If you use Visual Studio 2013 for the same package it will probably work. The other answer suggesting the run of gacutil to register the old version may have negative impacts later when you want to use the Visual Studio 2013 tools for SSIS.
I had the exact same thing just happen and miraculously now my machine has been "fixed".
(I actually had it happen on both a Win 8.1 machine and a new Win 7 machine.)
My colleague and I noticed that the SSIS toolbox was missing from my IDE. After opening an SSIS package, going to the SSIS menu, and adding back in my "SSIS Toolbox", for some strange reason, my packages now run fine.
I'm guessing a recent update reset the behavior of the IDE.?.?
If this black magic worked for me, I'm hoping it will work for others.
EDIT:
I had the behavior revert itself.
I uninstalled SQL Server 2012 SP2 HF 5522, then rebooted
I then uninstalled SQL Server 2012 SP2, then rebooted
After that, my IDE still gave the error.
I then tried to apply SQL Server SP1 CU 9, but my environment said it wasn't needed.
I then rebooted one last time.
My SSIS Packages run again.
Voodoo...
If you're running across this issue somewhat after the fact (as I did), it appears that it has been fixed in a later release of the SSDT-BI tools installer. Either that, or the process of re-installing fixed it for me.
The file name of the installer on the download page has not changed, but there was a new version released in March of 2015. The new version number is 11.0.5583.0, and the previous version that was causing this error was 11.0.3436.0.
So a simple update might be sufficient. It worked for me with no changes to the GAC.
I have this problem with both VS2012 and 2013. When I load an existing or create a new solution I get a ProviderPackage error - An exception was thrown during package instantiation and was caught in the package manager. After I close the error dialog, the solution explorer window is empty, although there are solution files open in the editor.
The ActivityLog.xml file shows different modules loading when the error occurs, depending on the project type. Is there a way that I can determine the common thread between 2012 and 2013 that is causing this error.
There is probably a corrupted dll which I have to replace. I am dead in the water until I figure this out.
Help.
Clearing the Visual Studio Component Model Cache worked for me (details: Error message "No exports were found that match the constraint contract name")
None of the previous suggestions worked for me, but this one did:
http://www.hjerpbakk.com/blog/2014/7/25/no-content-in-solution-explorer-using-visual-studio-2013
This issue is because of a MEF cache corruption. Installing [or uninstalling any extension] will invalidate the cache causing VS to rebuild it.
I ran into the empty solution explorer with Visual Studio 2013, and fixed it with a repair install.
Solution: This worked for me.
I had the same problem in Visual Studio 2015 with the Solution Explorer always showing empty, even after deleting the ComponentModelCache folder. Looking at the Microsoft.VisualStudio.Default.err file, one of the errors was:
"----- Catalog construction errors -----
Error #1
Microsoft.VisualStudio.Composition.PartDiscoveryException: Failure while scanning type ......"
Doing a Google search on Microsoft.VisualStudio.Composition.PartDiscoveryException lead me to a Nuget package for Visual Studio MEF. Since I read so many posts of people have this same problem, I figured the problem was with Visual Studio and not necessarily any particular extension. So I installed this Visual Studio MEF Nuget package, restarted Visual Studio, and now the Solution Explorer is populated every time.
Nuget: https://www.nuget.org/packages/Microsoft.VisualStudio.Composition/
Deleting the .suo file worked for me.
Close VS, delete suo file of your project (is hidden), open your project again.
I had this problem with two projects, this fixed it in both cases.
Also, creating a new project (in my case a Console Application) also worked! That was probably the easiest fix i've found thus far and you don't have to delete anything! Nice...
Go To Window menu in visual studio and click reset window layout...it will work
I'm not sure if this is a add-on/extension issue but I'm having a heck of a time with Visual Studio 2012 on two computers. I believe it is DevExpress CodeRush causing the problems as it seems to work fine when I uninstall it but I'm not 100% sure.
I startup VS 2012, answer YES to the Get Latest from TFS 2012 and the solution right-click the solution node in the Solution Explorer and choose Project Dependencies... - it shows nothing checked. Of course the build will fail. I close and restart VS 2012 and then it shows. I typically do this through the course of the DevExpress option to clear the solution cache which causes the solution to reload.
Does anyone have any suggestions as to what may cause the project dependencies to get lost yet after a restart they are fine again? Is there something I need to delete and rebuild to try and resolve this?
The fix (so it seems) is to not check the option in VS source control settings to do a Get Latest when opening the solution. It seems to prevent the solution from initializing properly. I will consider reporting this to Microsoft Connect.
As I know CodeRush does not change anything in the Project Dependencies dialog. However you can write to DevExpress Support Center (http://www.devexpress.com/Support/Center) for a more detailed answer and research.
I also recommend you include a project and a video that illustrates the problem (if possible).
I was facing same issue. However got fixed after deleting .suo file from solution folder