I just got a new machine, and upon installing VS2013 (and I also tried VS2015 preview), one of our projects would not open.
The application which this project type is based on was not found.
Please try this link for further information:
http://go.microsoft.com/fwlink/?LinkId=441332&projecttype=CC5FD16D-436D-48AD-A40C-5A424C6E3E79
The output windows, gives this link, which is useless, and searching online for the GUID {CC5FD16D-436D-48AD-A40C-5A424C6E3E79} didn't bring anything up.
Any ideas what this could be? I have used Web Platform Installer to install the Latest Azure SDK.
It turns out that our project is based on Azure SDK 2.4, and I had incorrectly installed Azure SDK 2.5
Hopefully the GUID {CC5FD16D-436D-48AD-A40C-5A424C6E3E79} will show up in searches, if others have this same problem.
Related
my team is creating an Azure Service Fabric application using ASP.NET/Dotnet Core. Whenever I try to import the project into my Visual Studio 2017 for Mac I get the error
Error while trying to load the project '.../Project.sfproj: Unknown solution item type'
The solution contains several projects, some with a csproj (which I can open just fine), and some with a sfproj, that cause the problems. I can't even browse them in VS2017:
I can run msbuild from the shell (get some Compiler errors, but that's fine), but cannot manage to load the project into my IDE. I guess I'm missing the Service Fabric SDK, but that is not available for mac afaik. I managed to pull some jars from the vagrant image, as described here but that doesn't help me in a ASP.NET/Dotnet Core application.
Unfortunately, this feature is currently not available. If anyone wants it, vote for it on the visual studio user voice page.
I'm currently trying to work on Azure Service Fabric in Visual Studio 2015 but I have a general exception (hresult : 0x80131500) when i create a new service fabric project.
For example, I got this error when i create a stateless service project, or anything else coming from service fabric... Can't post screenshots of the process for now... Thing is that when I installed service fabric packages, there were errors (already installed package but not, couldn't access the package)...
Spent hours trying to resolve this problem, I tried to uninstall everything, to change from a version to another, I searched a lot for an answer but not found.
Maybe I didn't understand what is happening there, and maybe someone could help me !
Service Fabric Tools: 1.4
Visual Studio: 14.0.25431.01 Update 3
.NET framework: 4.6.1
UPDATE
Thank you everyone, Microsoft updated their packages, it seems that it was coming from them, i tried to reinstall packages again and it works now !
I don't know how this post can be marked as resolved, if someone could do it, it would be great !
I was able to repro this when the 3.5 .NET Framework was missing. Specifically project creation is looking for targets files under the C:\Windows\Microsoft.NET\Framework\v2.0.50727 folder triggering the exception. Need to investigate why the tooling has a dependency on the older .NEt framework.
For now to try to fix the issue, can you enable the .NET Framework 3.5 (includes .NET 2.0 and 3.0) feature in "Control-Panel->Programs and Features-> Turn Windows features on or off" and see if it also resolves the issue for you.
Microsoft updated their packages, it seems that it was coming from them, i tried to reinstall packages again and it works now !
Launch Web Platform Installer (type it in Windows run menu).
Select Microsoft Service Fabric package.
Install it, or update it.
Should work.
I recently installed Visual Studio 2015 Community for universal app development, but when ever I create a new project and select the universal app under windows the error pops up saying:
"One or more projects requires a framework SDK(.NETCore v=5.00) that
is either not installed or is included as part of a future update to
visual studio"
In that error box there is a hyperlink mentioned to download the update but it goes right to the Microsoft website's home page.
I read some where to install the .NETCore via nuget package manager console. I have done that it was successful, but again whenever I create a new project it says to install the Framework SDk(.NETCore v5).
I haven't found any solution on this particular error but their were some tutorials to install the .NETCore but they didn't helped me out.
Kindly tell me how to get rid of this, I have wasted almost my 5 days trying to fix this issue.
i actually fixed that issue by First Modifying the setup of vs and their unchecking the Window Universal App development option. it means uninstalling the universal Window App development from visual studio then again modifying the setup i re checked the universal window App development option and update it. that fixed my issue.
You have to install the "Tools and Windows SDK."
I've just installed the April 2015 release of the Azure SDK. It is version 2.6 and previously I was on 2.5. Now one of my projects will not load. It is the shared project in a Windows Universal application.
When I right-click the project and choose 'reload' I get the pop-up error
The method or operation is not implemented
The output window gives more detail:
Things.Shared.shproj : error : The composition produced a single
composition error. The root cause is provided below. Review the
CompositionException.Errors property for more detailed information.
1) No exports were found that match the constraint:
ContractName Microsoft.VisualStudio.ProjectSystem.References.IBuildDependencyProjectReferencesService
RequiredTypeIdentity Microsoft.VisualStudio.ProjectSystem.References.IBuildDependencyProjectReferencesService
Resulting in: Cannot set import
'Microsoft.VisualStudio.Azure.Deployment.ProjectReferenceMaintenanceService.ProjectReferencesService
(ContractName="Microsoft.VisualStudio.ProjectSystem.References.IBuildDependencyProjectReferencesService")'
on part
'Microsoft.VisualStudio.Azure.Deployment.ProjectReferenceMaintenanceService'.
Element:
Microsoft.VisualStudio.Azure.Deployment.ProjectReferenceMaintenanceService.ProjectReferencesService
(ContractName="Microsoft.VisualStudio.ProjectSystem.References.IBuildDependencyProjectReferencesService")
--> Microsoft.VisualStudio.Azure.Deployment.ProjectReferenceMaintenanceService
Resulting in: Cannot get export
'Microsoft.VisualStudio.Azure.Deployment.ProjectReferenceMaintenanceService.WireUp
(ContractName="Microsoft.VisualStudio.ProjectSystem.ConfiguredProject.AutoLoad")'
from part
'Microsoft.VisualStudio.Azure.Deployment.ProjectReferenceMaintenanceService'.
Element:
Microsoft.VisualStudio.Azure.Deployment.ProjectReferenceMaintenanceService.WireUp
(ContractName="Microsoft.VisualStudio.ProjectSystem.ConfiguredProject.AutoLoad")
--> Microsoft.VisualStudio.Azure.Deployment.ProjectReferenceMaintenanceService
The other parts to the Windows Universal app (the Windows 8.1 project and the Windows Phone 8.1 project) have two Azure NuGet packages installed: Windows Azure Mobile Services 1.3.2 and Windows Azure Storage 4.3.0. (N.B. Those two projects load without issue.)
This is not a show stopper for me since uninstalling the Azure SDK 2.6 removes the load failure. To uninstall I go via the Control Panel to 'uninstall or change a program' and then uninstall Microsoft Azure Tools for Microsoft Visual Studio 2013 - v2.6
I would like to know how to fix this without uninstalling the Azure SDK 4.6.
Over on the Azure Mobile Services forum Chuck Weininger has posted the following answer:
The [fixed] build of Azure SDK 2.6 is now available, but it may not have
propagated to all download servers yet.
You can run the Web Platform Installer and if you don’t have the new
build installed, it should allow you to install 2.6 again. But it
might not if you are accessing a download server that doesn’t have the
new bits yet. If WebPI doesn't allow you to install 2.6 again, then
wait a few hours and try again.
The build number for the version with the fixes is build
2.6.30508.1601. You can identify the build of the SDK from Control Panel -> Programs and Features -> Microsoft Azure Tools for Microsoft
Visual Studio 2013 – v 2.6. The Version column will display the build
number
I have followed Chuck's instructions and have the new build and the shared project now loads without issue.
We have been able to reproduce the issue, but don't have a workaround at this time. If you want to use the Universal App projects with VS 2013, you will have to uninstall Azure SDK for VS 2.6. The issue does not happen on VS 2015 RC if you would like to give that a try. We hope to have news soon about how we can get a fix for this issue on VS 2013.
Chuck Weininger, Dev Lead, Microsoft
https://social.msdn.microsoft.com/Forums/en-US/e8123821-dcb1-477f-a746-f6f016a724ea/cannot-load-shared-project-in-windows-universal-app-after-upgrading-to-azure-sdk-26?forum=azuremobile&prof=required#de621720-3afc-458c-ba85-f691be9e74c1
I have a newly installed laptop running Win7/x64 and installed Visual Studio 2010, then VS2010 SP1, and then the Windows Azure SDK 1.4.
When I attempt to debug a cloud service project in the local compute emulator environment, I get an error: "The was an error attaching the debugger to the IIS worker process for URL 'http://127.0.0.1:5102/' for role instance..."
Some searching turned up quite a few discussions on this issue with the Azure SDK 1.3 update and I've narrowed down the issue to my having multiple sites in the same Web Role in my Azure application. If I comment out the sites entries in the ServiceDefinition.csdef, there's no error and debugging works fine. I tried the other recommended solutions, reinstalling .NET, re-registering ASP, rebooting while facing Redmond, but same problem.
I'm surprised by this issue on a new VS/Azure 1.4 installation and I'm hoping someone else has resolved supporting multiple sites for local debug.
Thanks!
I ran into the same problem, and have two suggestions:
If you've pointed to the "Published" output of a website and not the source location in ServiceDefinition.csdef, you'll get this error. Point to the source location of the web site when you're debugging. You can always switch the location later if you'd rather deploy a published web site rather than the source.
Ensure that you have debug set to false in the each of the web application's web.config file. While obvious, this catches me from time to time.