Automatically Close Braces in Visual Studio

If you're an Eclipse or Netbeans user, you'll be very familiar with this topic.  These IDEs automatically close braces, parenthesis, quotes, and brackets -- ( {},[],(),"",'' ) -- for you as you type in the code editors.  It may sound like laziness, but it can actually save you debug/troubleshooting time as it ensures (well, helps to ensure) that for every open you have a corresponding close.

One complaint I've always had, along with many other people based on my Google searches, is that Microsoft Visual Studio does not have this functionality.  If you're like me and spend a lot if time in both the Java IDE's and Visual Studio, you probably find it very annoying that the editors don't behave quite the same.  It can really mess with your muscle memory and make you less productive.

While there are a few very good commercial packages out there that provide this functionality (along with a host of other cool toys), I haven't been able to find any free/open ones, so I wrote one.  Milestone Visual Studio .Net Toys in born.

Milestone Visual Studio .Net Toys is an open source project currently available on Milestone's web site (http://www.milestonetg.com/products/52-close-braces-vs).

Though the only feature currently available is the auto closing, the long term goal is to continue to provide useful productivity tools we've all become accustomed to in Eclipse that aren't available in Visual Studio--ie. Rename a namespace on move of a class to another folder or project :)

I hope you find the add-in useful and the source code inspiring.  If you have any requests on what you would like to see the toy box, let me know.

Comments

  1. AnonymousJanuary 2, 2012 at 10:36 PM

    Hi thanks so much for this extension but I've a very noob question (I'm newbie with VS because always I've worked with intellij idea and emacs) How can Install it..I tried install it directly but doesn't work and I've copy this to my VS extensions folder but doesn't work neither..I'm using visual studio shell edition 2010 with f#...thanks so much

    ReplyDelete
  2. Jason M PennimanJanuary 3, 2012 at 6:46 AM

    The plugin/extension is currently only supported by Visual Studio Professional, Premium, or Ultimate. Shells and Express editions are not supported.

    ReplyDelete
  3. VickyMarch 18, 2012 at 4:36 AM

    Thanks
    Works Fine :)

    ReplyDelete

Post a Comment

Popular posts from this blog

Adding New Microsoft Extensions to Legacy WCF and ASMX Web Services

I was asked by several people recently: Can I use dependency injection with my legacy WCF and ASMX web services? Microsoft has some new stuff they released with core–specifically, a new configuration system, caching, and logging providers. Can I use them in my legacy WCF and ASMX web services? The answer to both is yes you can! In fact, I recommend it! To illustrate this, we’ll take a look at taking a sample application that has a WCF service and a ASMX service and we’ll: Add dependency injection using Ninject. Add the new Configuration provider from the new  Microsoft.Extensions.Configuration  packages. Add caching functionality using Microsoft’s new  Microsoft.Extensions.Caching  packages. Use the new logging providers from  Microsoft.Extensions.Logging  packages. Dependency Injection We use Ninject, but you can just as easily use AutoFac or SimpleInjector as they also have packaged integrations for WCF. You can use other containers, but may need to hand-roll your
Read more

Using NHibernate in Asp.Net Core

Starting with version 5.1, NHibernate now supports .Net Core and .Netstandard as well as the full framework. Let’s take a quick look at how to set it up in an ASP.Net Core 2.x/3.x application. Configuration As of this writing, NHibernate doesn’t support the configuration system within Asp.Net Core based on Microsoft.Extensions.Configuration. The good news is, you don’t have to use a  hibernate.cfg.xml  file or the   section in app.config. You can add the properies manually, and pull the values from Asp.Net Core’s configuration, taking advantage of all the goodies that come with it. This opens up a world of configuration deployment possibilities. var config = new Configuration (); IDictionary < string , string > properties = new Dictionary < string , string > { { "connection.connection_string" , Configuration . GetConnectionString ( "Default" ) }, { "dialect" , "NHibernate.Dialect.SQLiteDialect" },
Read more

Code Coverage for Multiple Projects in a Single Build using Dotnet Test and Coverlet

Most of the time, your solution will have more than one project and a test unit project for each of those. Azure DevOps only, as of this writing, only allows you to update a single code coverage summary. If you upload more than one, each overwrites the next and only the last one remains. To accomplish this, we can use the merge functionality in Coverlet . I use the MSBuild extension, because it is better suited for CI pipelines. In your test project XML, add the package... <PackageReference Include="coverlet.msbuild" Version="2.7.0">     <PrivateAssets>all</PrivateAssets>     <IncludeAssets>runtime; build; native; contentfiles; analyzers</IncludeAssets> </PackageReference> Then, in your dotnet test command or msbuild command, tell it to use Coverlet and to merge results. If you're using Azure DevOps, your test task looks this... (line wrapped for read ability in the article) - task: DotNetCoreCLI@2 displayName: Test i
Read more