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.
Related
I have installed the Visual Studio 2019 community version 16.4.4 on a brand new laptop
OS:- Windows 10 Home Single Language
The following are the .NET Core SDKS installed in my laptop
The command dotnet --info gave me the following details
I created a Azure function with V3 template
The project settings are given below
When I try to debug , i get the following error
A fatal error has occurred and debugging needs to be terminated. The debugger was configured to use the Desktop CLR (.NETFramework) Managed debugger, but the target process loaded the CoreCLR (.Net Core) runtime. To debug this project, configure it to use the 'Managed (CoreCLR)' debugger."
Tried several options like the one mentioned in the link below
https://social.msdn.microsoft.com/Forums/en-US/59f880f7-ed60-4842-bc55-a9400971c58b/problem-debugging-net-core?forum=vsdebug
EDIT: This has been fixed in the latest release of Visual Studio v16.4.5
The problem seems to be a mismatch in the version of the Azure Functions CLI. As a workaround, you can do this:
Install the latest Azure Functions CLI, from the command line run:
npm i -g azure-functions-core-tools#3 --unsafe-perm true
or if you are using Chocolatey:
choco install azure-functions-core-tools
Restart Visual Studio.
I still have this issue after reinstalling my VS2019, downloading the latest sdk and downloading the core tools multiple times. Seems like the only way for now is to run without using the debugger (Ctrl + F5). Sometimes I downgrade the function to v2.1 for this only happens on v3 functions.
Edit: I got this fixed when I updated my VS to 16.5.1
It looks like one similar issue which has been reported to DC forum. However it works well in my side with same 16.4.4 version. Since I didn't reproduce same issue, I can't provide a direct answer.
Here're some possible workarounds which may help:
Repair VS and go Tools=>Import and Export Settings=>Reset all settings=>No,just reset, overwrite... (Since my same version works well)
Hint from this one, you may backup the launchsettings.json in project and then delete it, rebuild and debug(F5) it again.
And if the issue persists, you can try installing .net core 3.0 sdk and recreate a new project to check if it helps.(I have both .net core 3.0 and 3.1 installed, but by default it picks .net core 3.0 when I create the project, not sure if it makes any difference.)
Hope it helps :)
Update:
Sorry for not noticing that the solution will not work for you. Since the solution doesn't work, you can choose another way. As the error says, you need to
configure it to use the 'Managed (CoreCLR)' debugger."
So, try to configure on hand, Select 'Debug' above the VS 2019 tab, then
Original Answer:
I faced exactly the same error before and solved it with below solution, it works well.
Solution:
Just enable the native code debuging.
Right click your project > properties > Debug. Tick 'enable the native code debugging' like this:
I have the same issue, I have upgraded visual studio 2019 to 16.4.4 and it resolved my issue. that was the bug by visual studio 2019 in 16.3 versions. please upgrade visual studio. it will definitely resolve your issue.
Issue was resolved with the next upgrade of Visual Studio 2019
Trying Install the v3.x Core Tools package from the command line run npm install -g azure-functions-core-tools#3.
Reference: Use npm to install Core Tools on Windows
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 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.
In my web application I have added WCF service which is hosted on IIS. It was all working fine until the time windows has installed the update on the my development machine, and now Visual Studio 2010 does not recognize the service reference which I have added previously.
It is giving the error as 'Type Service_Createuser is not defined'
Intellisence does not show the service reference either.
Below are the updates had installed on the machine :
KB2504637 Microsoft .Net Framework 4 Multi-Targeting Pack
Security Update for Microsoft.Net Framework 4.5.1 (KB2901126)
Security Update for Microsoft.Net Framework 4.5.1 (KB2898869)
I have removed the service reference and added again but still the same problem.
Webservice was created using .Net 3.5 and my web application is also set to .Net 3.5.
I have googled in but no luck!
Could someone please tell me what this updates has done. And how to resolve this problem.
Please let me know if you need more information. Any help will be appreciated.
Many Thanks
John
I have a problem when trying to load an SSIS package in VS 2008. In the about it says it has "SQL Server Integration Services" installed but on loading a package I get a message that says:
Microsoft Vistual Studio is unable to load this document:
To design
Integration Services packages in Business Intelligence Development
Studio, Integration Services has to be installed by one of these
editions of SQL Server 2008: Standard, Enterprise, Developer or
Evaluation. To install Integration Services, run SQL Server Setup and
select Integration Services.
I thought maybe it was a version problem so I thought I'd look at a new Intergation Services project to play spot the difference. However when I told visual studio to create a new IS project (which was in the list quite happily) it created it and then gave me the above error message again.
To give some idea about my environment I have several version of Visual Studio (2k5, 2k8, 2k10) and several version of SQL server (2k5, 2k8) so I don't know if there is some confusion between versions...
The other thing that I am wondering is if there is a problem with what order things got installed in (ie my VS2008 wasn't installed when SSIS stuff was installed).
I am hoping there is a simple approach to this that won't mean reinstalling things. I can go to our IT to ask them to try to get it working but that would take some time. If it does come to that though I'd like to have some idea of what I should ask them to install since it does seem to be all installed currently...
So if anybody can either a) help me work out precisely what components are installed and what is missing that would be great. Bonus points for helping fix it without needing the install media...
Edit: A thought occurs to me. Coudl it be that I only have 2005 Integration Services installed? If so how can I determine that? And I still am not sure why VS is behaving as it is and letting me create a project but no SSIS in it, even if they were older versions...
Edit: Also it seems that if I load up VS 2005 I can create IS projects but of course can't load up the newer SSIS packages, I assume because they are from a newer version maybe...
Edit: Version information for SSIS in VS 2008:
Microsoft SQL Server Integration Services Designer
Version 10.0.1600.22 ((SQL_PreRelease).080709-1414 )
The following line can tell you the version of the package:
<DTS:Property DTS:Name="PackageFormatVersion">3</DTS:Property>
3 is for 2008, 2 is 2005 and 6 is 2012.
By the way, how patched is your system? The 10.0.1600.22 does sound like the original installation of 2008. Try to install SP3 and the latest cumulative update - this will bring your installation to 10.00.5788 and the issue might go away.
If you previously had the components from a Express 2008 installation, and then you install an Standard, Enterprise, Developer or Evaluation, instead of actually installing a new instance/components (probably you see Integration Services grayed out) use the Upgrade option of the SQL Server 2008 setup, and then VS will load perfectly the DTSX file.