Visual Studio 2015 hanging after adding Azure SDK - c#

So I set up the latest Azure SDK that integrates with Visual Studio 2015. It all seemed to work well and I was happily playing around with it for an hour or more in my small .net 4.6 MVC app with 3 projects in the solution. I went in to the Azure web portal and set up a new resource group there, and when I went back to VS I refreshed the Server Explorer my resource group was visible under App Service and data from the ApplicationInsightsExtension.log file appeared when I opened the file in a tab. All fine and dandy.
However, the next time I opened the solution VS hung and wouldn't respond. The active tab is the ApplicationInsightsExtension.log file and it seems to be trying to connect to Azure but is getting stuck. I've tried everything including rebooting etc but nothing works. I'm also opening VS in Admin mode
Is there a setting somewhere in the config / project files that specifies what tabs are opend when you open a solution? I'm thiinking if I stop the ApplicationInsightsExtension.log file from opening that might fix the issue. However I've looked in the .csproj and csproj.user files and can't see any setting that might correspond to this.
Visual Studio load error

You could reset your settings to prevent VS to restore your opened tabs.
Ensure your Visual Studio is Closed.
Navigate to your solution directory in windows explorer.
Ensure your are displaying hidden files on Solution Explorer. View Tab -> Show/hide ribbon group/ check Hidden items checkbox.
A folder named .vs must be shown now in Windows Explorer.
Navigate to .vs\<SolutionName>\v14
Delete .suo file in the directory.
Open your solution.
Now VS will not load any tabs by default, so maybe you can see what is happening.
Hope this helps!

Related

Project in VS2010 unavailable and can't reload

I've been trying to load a project from a SourceGear Vault Client that has a plug-in for Visual Studio 2010. After selecting the solution file, the solution explorer populates with the associated projects but appends (unavailable) to the end of each project name.
The usual remedy is to reload each unavailable project but in doing so briefly reveals all files within each project but then VS quickly hides them and makes the project unavailable again.
So far, I have tried opening the code in VS2015, removing all related source control information from the .csproj and .sln files, and deleting the associated .suo file. Nothing has worked yet and I have exhausted all the known fixes.
Thanks for your help.
For clarity, I'm copying #PeterRitchie solution that worked for me, below.
You could try running Visual Studio in safe mode to see if a 3rd party plugin is to blame: devenv.exe /SafeMode – Peter Ritchie

WinForms App Doesn't Run Outside Visual Studio

I'm using Visual Studio 2013, C#, Windows Forms application on a new laptop with Windows 7 Ultimate.
From within VS, if I Build and run my app, it opens fine (no errors or warnings). If go into the debug folder and double click the exe file, the app doesn't open. It appears in task manager, but I can't kill it. I get no error messages. Because it's running, I can no longer Build or run the project from VS as the file is in use.
I tried Building to Release and got the same problem.
The only way to get rid from the task manager is to restart the laptop.
This wasn't a problem on my old PC - which also had Win7 Ultimate and VS2013.
Do you know why my exe isn't running and why I can't kill it in Task Manager? Any help would be appreciated.
I had exactly the same problem. I have VS Express 2015 for Windows Desktop. Recently build app worked only from Visual Studio, old builds work fine. After some research I found that the promblem was my Avast Antivirus 2015, which prevented the new apps from running.
So I suggest, if you have Antivirus running, pause it for a while and see what happens. If indeed that is was the cause for your problems, the configure Antivirus so that it will not check your app when loading.
In Avast: Settings->Active protection->File system protection
(Not sure if that is excatly so, because I have Avast in other language than english)
Hope that works!
I have the same issue with Avast 2015 (licensed) that locks File Explorer up if I double click my c# apps in the bin\debug or release folders.
As others have suggested, rather than disabling Avast "Scan programs while executing" you can add your app path into the scan exclusion list via:
Left click the Avast Icon
Click Settings
Click Active Protection
Click Customize link for "File System Shield"
Click Exclusions and add your build folder. e.g. \bin
Also,
If Windows Explorer has locked up because of this issue, rather than rebooting you can open Task Manager, end-task "Windows Explorer" (your start bar will vanish) then click File->Run new task and type in Explorer, then hit enter to get everything back.
Cheers

Xamarin Studio source code windows not syncing up with Solution Explorer

I am opening up a project in Xamarin Studio but the source files that I open in it are not kept synchronised to the Solution Explorer window.
How do I get the solution explorer window synchronised with the file that I am currently editing?
After a bit of investigation, it does sync, and keep the active document highlighted in Solution Explorer....
HOWEVER...
This does NOT work for files opened from a Shared Project.
Does anyone know how to get this to work with a Shared Project?

Visual Studio 2013 Publish Profiles saving inconsistently

When I modify an existing publish profile, Visual Studio 2013 Update 1 does not always save the corresponding pubxml file in the /Properties folder. I'm playing a constant game of modifying files until my changes are registered correctly in the file system.
For example, one publish profile that I edited and "saved" using the prompt has its pubxml file marked as delete. I suspect the profiles are cached and Visual Studio 2013 is not reflecting what's in the file system in real time.
The save prompt only shows up when I go to another profile or hit the publish button. It would be nice to have a save button that would force the pubxml files to show the latest.
Does anyone have a clear workaround this? I had a similar experience with web.config transformation in the same project and ended up editing the project file.
I'm certain this is not bound to the specific project I am currently dealing with as I see the same behavior in other projects. I never had this issue in Visual Studio 2010.
You'll not see this issue if you have just created new profiles. I am only seeing this behavior when I modify the existing profiles.
Not sure if this helps, I was able to delete the Profile in the VS GUI.
this is in VS 2013 Professional.
I clicked the Build menu / Publish "yourSite"
Then on the Publish button was able to click it or right click it and then I could see the Manage button show up under the publish section. I clicked that, then was able to delete my original profile. then I created a new one.
I guess once you create a profile the manager button disappears.

Visual Studio 2013, changes not showing in debug

Have recently upgraded to Visual Studio 2013 Pro and am having some teething problems.
Primarily if I change any HTML or CSS in either a .aspx page for Web Forms or .cshtml for MVC, the changes aren't always reflected on the page I'm working on when I debug it and don't appear not matter how times I refresh or clear my cache.
Am using web essentials, which should put the changes straight on the page with have to refresh the page but this doesn't seem to be working either.
Also occasionally, but not always, if I stop debugging, change the code behind then run the project again it says it's running from a different version of the code than the one being debugged and I have to stop it, rebuild and then debug.
Have never had these problems on previous version of Visual Studio.
Any suggestions?
Go to Tools-Options
Under Projects and solution -> Build and Run select "Always build" under "On Run, when projects are out of date"
I had the same issue today. I already had that setting on (Always Build). Cleaning & rebuilding the solution didn't do the trick. I looked under C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\ and I found a folder named root with a lot of temporary hexa-numeric named folders. Only one folder had today's date. I closed all VS 2013 windows and removed that folder. After I restarted VS 2013 I simply run the project and my changes are now back.
I just spent the past hour trying every answer and none of them worked. I simply cleared the cache on the browser I was using to debug (google chrome) and it updated my changes. This question had the correct answer:
visual studio not updating html / javascript to server / browser
I was experiencing old code in the debugger with a console application calling a DLL. I believe it was occurring because the previous version of the DLL was installed in the Global Assembly Cache (GAC), and the Visual Studio debugger was calling the DLL in the GAC (Which had the old code) instead of the current version. I uninstalled the DLL from the GAC and the problem was resolved.
Uninstall an assembly from the GAC (MSDN)
I had this issue and tried all the Build config changes etc without success. I'm running VS2015 in a Parallels VM and saving the project on a drive on the Mac. It appears that there is some odd/tiny difference between the Mac time stamps and the Win10 clock.
Setting the Win10 clock back 5 seconds resolved the issue. Bizarre but saved my sanity...
for my case, I tried all the before mentioned answers but nothing worked. and then I went to the system logs and found a hint about failure in loading IIsexpress for the running application. I changed the port that the application used and voila! everything is back to normal. thought this might help someone
I had a similar issue and found the solution by checking the path of the virtualDirectory for your sites that are found within your applicationhost.config file.
Typically located here:
C:\Users{your user name}\Documents\IISExpress\config
You want to make sure the physical path for both locations are the same since sometimes they get wonky when working on various branches/projects etc.
it's not a bug at all, and has nothing to do with the above answers.
Go to solution explorer and click on --> sync with active document. as shown bellow:

Categories