NCrunch gets stuck at 'NCrunch is initialising' - ncrunch

On an occasion, I found NCrunch was getting stuck at this step when 'NCrunch engine is initialising':
Clean/rebuilds and restarting Visual Studio did not resolve this issue.

To resolve the issue, I closed Visual Studio and navigated to the Visual Studio project folder in the file directory and located the hidden .vs folder and the '_NCrunch _[projectName]' folder and deleted those.
Then I cleaned and rebuilt the solution and NCrunch started functioning again.

Related

libIEC61850 Microsoft.VisualStudio.ProjectSystem.References.UnresolvedBuildDependencyProjectReference" reference could not be resolved?

Hello i im running Visual studio 2022 professional. I have downloaded libiec61850-1.5.1 libIEC61850 I have compiled the code whit cmake. I have then opened it in visual studio code. The problem is that the References in the example projects could not be resolved.
I have tried the following things.
Remove the references then add them again save and rebuild project.
Remove the references the save rebuild project, closed and started visual studio again
the tried add the references.
Tried edit the path directly in vcxproj file.
I downloaded the libIEC61850 a second time to make sure there was no corrupt files. Made
a new compile whit cmake. still got the same problem,
Updated the visual studio to the newest update.
Anybody that have a idea what the problem can be. I have searched the a found nothing that could help. i have checked this post also
The problem was that Link to library dependencies was not set to "True".
After i changed this the reference error did go away.

EXEs does not copy on build in visual studio

I have a VB.NET solution containing multiple projects and the expected result is the EXEs in one project should be copied to bin folder of other projects on build. While rebuild solution does this, build solution does not copy the EXEs and even deletes the previously copied EXEs.
Any idea why this is happening?
Thanks
There provides two method which may help you solve your problem:
1.Renaming the executable file
2.Another method:
Closing Visual Studio
Deleting the bin and obj folders
Reopening Visual Studio.

When running Asp.NET Core App the app fails to launch with a 502.5 Process error on local IIS

Thank you for taking the time to answer my question. I'm having an issue when running my project. This project was running just fine previously. Something has happened to cause the following error to appear in the stdout log.
Error: An assembly specified in the application dependencies
manifest (.deps.json) was not found:
package: 'AutoMapper', version: '6.2.2'
path: 'lib/netstandard1.3/AutoMapper.dll'
Things I have tried:
Clear the nuget cache
Restore nuget cache
Restarted Visual Studio 2017
Restarted IIS
Gave Full Access to the 'Everyone' role to the
folder where the files are located
Any help is greatly appreciated.
UPDATE: This is the output from the Output Pane
I had the same issue, add the following to your .csproj file and publish again.
<PropertyGroup>
<PublishWithAspNetCoreTargetManifest>false</PublishWithAspNetCoreTargetManifest>
</PropertyGroup>
After spending sometime on this, none of the fixes suggested worked. After spending a lot of time looking up what the potential issue is, I decided to check for any available visual studio updates.
After I updated Visual Studio 2017 everything worked.
I hope this helps someone.

VS 2017 Could not find required file 'setup.bin' in csproj folder

When i try to build a project using MSBuil tools for VS2017 an error occurred Could not find required file 'setup.bin'
Sorry for the delay. I solved the problem re-installing VS2015 i think the has to do with the previous version of VS unnistaller. Seems to be removing folders that eventually are necessary to VS2017

apache cordova visual studio 2015: Unable to include some files and folders e.g bower_components files and folder

When I include files and folder it rolls back those files and excluded automatically
here's in screenshot. i tried many times but not succeeded.
In my case: Restart the visual studio (application) will solved this issue.