It seems that this behavior is turned off by default. 
It can be enabled under 
**Tools &gt; Options &gt; Text Editors &gt; C# &gt; Advanced &gt; Outlining &gt; &quot;Collapse #regions when collapsing to definitions&quot;**

I have a script I run to deploy 2 web services and a front-end application. The script calls a method that checks to see if the 2 back-end services are up and running. If so, deem the deploy successful, otherwise revert.

The 2 services sometimes take longer than the front-end to start up. Currently I put in a sleep call to delay the web service check. This allows them time to start up.

I want to remove this sleep and add in a retry mechanism so that if a service is down, just retry the check repeatedly until I get a response.

Tp check if the device is up, I use curl. I&#39;ve read that curl has a retry mechanism but I&#39;ve never used it.

Have any of you solved this problem before? I want to understand the things I must consider when solving it, e.g. do I retry until i get a HTTP 200 from my service?

Anyone any suggestions how I&#39;d test this? I&#39;d need to find a service that was down.

EDIT: I see that -retry only reacts to transient errors &#39;Transient error means either: a timeout, an FTP 4xx response code or an HTTP 5xx response code&#39;. My service can return a 404 therefore curl&#39;s retry is not my solution.

Curl retry mechanism

Is there any advantage in using `tf.nn.*` over `tf.layers.*`?

Most of the examples in the doc use `tf.nn.conv2d`, for instance, but it is not clear why they do so.

tf.nn.conv2d vs tf.layers.conv2d

I&#39;ve noticed that in Visual Studio 2017, when I hit CTRL+M, CTRL+O, regions do not collapse to definitions. Has there been a change on this? How do I collapse everything -- including regions?

BTW, I get the same results whether I use the keyboard shortcut or go through the context menu by right-clicking. Regions just do not collapse at all.

Visual Studio 2017 Collapsing Regions

<p>I've noticed that in Visual Studio 2017, when I hit CTRL+M, CTRL+O, regions do not collapse to definitions. Has there been a change on this? How do I collapse everything -- including regions?</p>
<p>BTW, I get the same results whether I use the keyboard shortcut or go through the context menu by right-clicking. Regions just do not collapse at all.</p>


I have just installed *Visual Studio 2017* on a PC having the following specifications:

*Intel Xeon E5-1600 v3 @ 3.50 GHz processor,
16 GB RAM and Windows 10 Pro 64-bit operating system*.

Although the PC performance is almost perfect, I usually encounter slowness problem in *Visual Studio 2017* especially during build and debug processes. In addition to this sometimes I need to restart it after *&quot;Not responding&quot;* message.

Is there a stable solution regarding to this problem for *Visual Studio 2017*?.. 

Visual Studio 2017 is too slow during building and debugging

I&#39;ve just installed Visual Studio 2017. I have a project using NUnit for the test cases. &lt;kbd&gt;Ctrl&lt;/kbd&gt; + &lt;kbd&gt;R&lt;/kbd&gt; - &lt;kbd&gt;T&lt;/kbd&gt; no longer runs the tests, and the Test Explorer no longer finds any test cases marked with the TestCase attribute.

Is there a way to get NUnit running yet, or an update I could find?

I reinstalled NUnit from the NuGet Package Manager to the latest version with no improvement.


How can I run NUnit tests in Visual Studio 2017?

I have spent the better part of a few hours trying to find a way to auto-increment versions in a .NETCoreApp 1.1 (Visual Studio 2017).

I know the the AssemblyInfo.cs is being created dynamically in the folder: ```obj/Debug/netcoreapp1.1/```

It does not accept the old method of: 
```[assembly: System.Reflection.AssemblyFileVersionAttribute(&quot;1.0.0.*&quot;)]```

If I set the project to package I can set versions there but this seems to be used to build the AssemblyInfo.cs file.

My question is, has anyone figured out how to control version in .NET Core (or .NETStandard for that matter) projects.

Auto Versioning in Visual Studio 2017 (.NET Core)

I want to create a NuGet package which adds multiple .dll files as references to my project.

I have a folder with 10 .dlls files in it. 

When I install this via nuget, I want these files to be added to the project&#39;s references.

Create nuget package from dlls

VS 2017&#39;s new &quot;Go to All&quot; (Ctrl + T or Ctrl + ,) does not lists items for me.

Searched for a setting for it, no luck. Also no error messages regarding this at all. Any ideas?

Thanks.

Visual Studio 2017 &quot;Go to All&quot; does not list items

I have been struggling with VS 2017 since I installed it. Now it seems Unit Tests will only run from the command line &quot;dotnet test.&quot;

My project is .NET Core 1.1.1. I have the SDK and the framework update for 1.1.1 installed. 

I have tried the sample at MSDN (https://msdn.microsoft.com/en-us/library/ms182532.aspx) which also fails exactly the same way. 

All NuGet packages for the tests and the main project are current. And both the test project and the main project build without errors. An the tests run successfully from the command line.

Has anyone gotten Unit Tests to run in VS 2017, if so how?

Thanks,
John

---

## Update - Extend

Here is an example of a simple test project that is not working on [GitHub][1]. This is an example with xUnit but I have tried NUnit and visual studio built in MS tests. No matter what testing or what changes I make I cannot get the VS test runner to find any tests. 

### What I&#39;ve Tried

* Deleting VS test cache files `DEL %TEMP%\VisualStudioTestExplorerExtensions`
* Restarting VS
* Closing/Opening test explorer
* for xUnit installed `Microsoft.DotNet.InternalAbstractions` ([see SO post][2])
* for NUnit ensure adapter installed and same version (3) as NUnit package
* `test -&gt; test settings -&gt; default processor architecture` is set to x86

**The Question**  
Can anyone please provide a working example of a .Net Core 1.1.0 solution in VS2017 (.csproj project files) where the VS test explorer successfully finds the unit tests **OR** show me the issue in the example given.

  [1]: https://github.com/raykrow/xunit-vs2017/tree/master
  [2]: https://stackoverflow.com/questions/35103781/why-is-the-visual-studio-2015-2017-test-runner-not-discovering-my-xunit-v2-tests

Unit Tests not discovered in Visual Studio 2017

I edit the project.csproj. and re-open the solution the errors occurred:
The operation failed as details for project xxx could not be loaded

I try delete  obj &amp; bin folder, clear the nuget cache by tool&gt;options. 
but the error still exist.

Remark: the error do not occur each time, i just restart the project  three times. the first and second is correct. but the third the error occur

vs2017:
Microsoft Visual Studio Community 2017
Version 15.0.26228.9 D15RTWSVC
Microsoft .NET Framework
Version 4.6.01586

Package Manager Console Host Version 4.0.0.2323



Content Type	Original Author	Original Content on Stackoverflow
Question	Sam	View Question on Stackoverflow
Solution 1 - Visual Studio	Gelásio	View Answer on Stackoverflow

Visual Studio 2017 Collapsing Regions

Visual Studio Problem Overview

Visual Studio Solutions

Solution 1 - Visual Studio

tf.nn.conv2d vs tf.layers.conv2d

Curl retry mechanism

Attributions