When a developer says they are debugging their code, that really means they are doing some superficial looking in the debugger. Today’s debuggers are so much more powerful than most developers realize. With a little bit of training they can easily cut the time they spend debugging by 20 percent. That means more time spent on features that customers want, which means more revenue for the company. Even more important is learning how to deal with problems that occur in production. Very few developers know anything about the real tools used to quickly solve those production problems.
If you would like to learn more about debugging using Visual Studio and its amazing breakpoint capabilities, make sure to attend this free one-hour webinar, ‘Taking a Break in the Debugger,’ led by John Robbins, the head of Wintellect’s Debugging Service and a prolific author/speaker on all things related to debugging. Click on the video above to view, and let us know your feedback in the comments.… Read more
Microsoft is holding it’s 2015 Connect() virtual conference today which was kicked off by a lengthy keynote from Scott Guthrie. In the keynote there were several new announcements including a sneak peek into Visual Studio 2015 Update 1, new features in Visual Studio Code, and a new model for getting Microsoft developer tools. Here’s an overview of some of the key announcements.
The next update for Visual Studio 2015 is due out later this month and will include several new features including support for viewing AppInsights data about your application directly in the IDE, support for Bower package imports, improved support of Node.js and Python, and newly added support for the R machine learning language. Also to be released on November 30 will be an update for the Windows 10 SDK and development tools that support the features of the November Windows 10 update.
Microsoft is releasing the open source .NET Core and ASP.NET 5 release candidates effective today. You can get the latest ASP.NET 5 bits at http://get.asp.net. .NET Core will be released on all platforms including Linux and OSX with GoLive licenses for production applications. For more information on the key features of ASP.NET 5 RC and .NET Core, check out the .NET Blog announcement. … Read more
Getting and installing modules is easier than ever with the PowerShell Gallery and PowerShellGet. Instead of downloading and extracting files into your PowerShell modules directory, a simple call to Install-Module takes care of everything for you. Today I’ve published my WintellectPowerShell module. Now you can install and get started setting up Visual Studio to access symbol server, source servers, and many other cmdlets for debugging support. All you need to do with PowerShell 5.0 (or by adding the Package Management Preview to PowerShell versions 3 or 4) is issue the following command:
If you haven’t heard of WintellectPowerShell, here are all the commands it offers.
Now you can join the ranks of Boba Fett and Dog the Bounty Hunter! Microsoft is taking the stability of their open source CoreCLR and ASP.NET 5 stacks to the people by offering up cash rewards for developers who can find, and prove, defects in the CoreCLR or ASP.NET 5. Not every bug is created equal of course and the pay scale is based on the severity of the defect and the ability of the developer to show the exploit working. It also doesn’t include the entire beta stack but there’s ample opportunity to find defects.
The bounty includes all supported platforms .NET Core and ASP.NET runs on; Windows, Linux and OS X. However with the first eligible release, beta 8, we are excluding the networking stack on Linux and OS X. In later beta and RC releases, once our cross platform networking stack matches the stability and security it has on Windows, we’ll include it within the program. — .NET Web Development and Tools Blog
The payouts are outlined in a table on the official Program Terms page with the highest rewards of $15,000 going for functional exploits that allow remote code execution and the lowest for seemingly poorly documented CSRF and XSS defects which will fetch a mere $500.… Read more
Last week amid all the hardware releases, Microsoft also released a CTP of the next update for Visual Studio 2015. This release includes support for Edit and Continue in C++ Windows Store projects, the C# Interactive debugging window, and a pull request hub in the Team Explorer window.
Team Explorer now features a new Pull Requests hub where you can see the list of pull requests that you’ve created, as well as the pull requests that others have assigned to them. We’ve also improved the Create Pull Request experience so you can publish branches and create pull requests in a single action. — Visual Studio Blog
How many clicks has this dialog eaten out of your life?
The idea for the warning is good because, you know, SECURITY. However, if you’re developing web apps or anything running in IIS, this gets old by the thousandth time you click the Attach button. It’s easy to turn off with an undocumented registry key. Make sure to shut down all instances of VS before changing this key as it will get overwritten on shutdown.
For Visual Studio 2015: HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\14.0\Debugger
For Visual Studio 2013: HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\12.0\Debugger
In the Debugger key, add a REG_DWORD value of DisableAttachSecurityWarning and set it to 1, and you now have one less click when you attach to a process.… Read more
When debugging a nasty problem in your code, one of the most helpful things you can get is a minidump. With that picture of what your app was doing at the time of the crash, hang, or when the memory started spiking, you’ve got a big hint to jumpstart your exploring. While there’s a bunch of tools out there, such as the wonderful ProcDump, and the debuggers themselves to create minidumps, the real moment of truth is when you have to look at those minidump. That’s easy to do with one or two, but what happens if you have 200? In my line of work, where I debug other’s software problems (and will be glad to help you with yours), I’m routinely faced with hundreds of dumps from a client. As much as I would like to carefully open each minidump and lovingly type the same commands over and over for the greatest consulting billing statement ever, I just can’t get my clients to pay for that.
What I really need is a way to say, “Here’s a bunch of .DMP files; go run these WinDBG commands across all of them.” It turns out that accomplishing that basic task is not hard at all when you combine a little WinDBG knowledge with a little PowerShell magic.… Read more
Now that Visual Studio 2015 RC is fresh off the build machines and available for everyone, I’ve updated my Wintellect.Analyzers project (http://johnr.us/1bEO4h8) with full RC support. Go forth and add them to your project so you can get the benefit of advanced compiler analysis and code fixes. To add the analyzers, hit up your Package Manager Console with the following command:
I guess you could go through the fancy new NuGet window in Visual Studio, but you want to be hard core and use PowerShell in VS!
If you’re interested in writing your own analyzers, as I have discussed previously, you’re immediately going to run into errors and warnings with projects based off the default Roslyn template when you try to install your analyzer masterpiece. Here’s what you’ll see:
Attempting to gather dependencies information for package ‘Analyzer126.96.36.199’ with respect to project targeting ‘.NETPortable, Version=v4.5, Profile=Profile7’
Attempting to resolve dependencies for package ‘Analyzer188.8.131.52’ with DependencyBehavior ‘Lowest’
Resolving actions to install package ‘Analyzer184.108.40.206’
Resolved actions to install package ‘Analyzer220.127.116.11’
Adding package ‘Analyzer1 18.104.22.168’ to folder ‘c:\junk\code\Analyzer1\packages’
Added package ‘Analyzer1 22.214.171.124’ to folder ‘c:\junk\code\Analyzer1\packages’
Added package ‘Analyzer1 126.96.36.199’ to ‘packages.config’
Executing script file ‘c:\junk\code\Analyzer1\packages\Analyzer188.8.131.52.0\tools\install.ps1’
Get-ChildItem : Cannot find path ‘C:\junk\code\Analyzer1\packages\Analyzer184.108.40.206.0\tools\analyzers\C#’ because it does not exist.… Read more
My deep abiding love of Roslyn continues! I just published a new video Writing Roslyn Analyzers and Code Fixes up at WintellectNOW: https://www.wintellectnow.com/Videos/Watch?videoId=writing-roslyn-analyzers-and-code-fixes. My goal was to take you from zero knowledge of Roslyn to writing a real world analyzer and code fix in 1.5 hours. This video covers everything from using the Syntax Visualizer to developing and testing analyzers and code fixes. Along the way I show how I solved some of the hard real world issues you’ll encounter.
Given that there’s not a lot of documentation on Roslyn I thought this video would help get folks up to speed as we approach the release date for Visual Studio 2015. I would love to hear any and all constructive criticisms you have on the video. What did I do right, what did I do wrong, and what else do you want to see. Sign up for a free WintellectNOW account and post to the discussion area under the video.
Please note that we reserve the right to move the video to subscription required in the future. Given how new Roslyn and VS 2015 are at the time of recording we thought it was good to get the info out now.… Read more