Update 2/14/2017 – I am happy to announce that we have updated the SlowCheetah extension to work with Visual Studio 2017 and 2015. You can install the extension from the VS marketplace: https://marketplace.visualstudio.com/items?itemName=WillBuikMSFT.SlowCheetah-XMLTransforms
We are also in the process of adding support for additional project and file types. For the latest development news for the extension, check out the GitHub repo: https://github.com/sayedihashimi/slow-cheetah
Please let us know if you run into any issues by reporting them at the issue tracker on SlowCheetah’s GitHub page.
Note: if you installed the preview extension for Visual Studio 2015, please be sure to remove it before installing the new one to avoid conflicts.
I hope everyone realizes that almost every part of Visual Studio is an extension of some kind.
Now, the fact that it doesn't get released with VS, that's an issue.
@random: I have never had a problem maintaining transform files. If it were painful, then nobody would want them.
@anonymous, why do want Microsoft to waste resources on a problem which already has a solution? Only with the withdrawal of support did it become necessary for Microsoft to spend resources.
Thank you for using Visual Studio and for your commitment to improving it. We are actively evaluating whether we will be able to bring this suggestion into the product for .NET developers for the System.NullReferenceException in a future release.
We have recently made an improvement, similar to this suggestion, for debugging C++ Access Violations in Visual Studio 2015 Update 1.
Read about it here: http://blogs.msdn.com/b/visualstudioalm/archive/2015/10/29/improvement-to-debugging-c-access-violations-in-visual-studio-2015-update-1.aspx
We encourage you to continue to comment on and vote for this UserVoice item to share any additional feedback that you have for this suggestion.
Visual Studio Diagnostics
Maybe since you've already done it for C++, but I'm still not voting for this one.
FYI, ReSharper does an excellent job of pointing out possible NullReferenceExceptions, and of helping you mitigate them by adding null checks.
James, the exception has nothing to do with an IDE. Surely, a tool like ReSharper could help you to rewrite the expression to make it easier to see the NullReferenceException, but at runtime, there is no information that would know what pieces of source code caused the problem.
@Zev: yes, but I meant to make a separate suggestion so that it can get votes.
@Zev: That's an interesting suggestion. Feel free to directly suggest it to Microsoft. In fact, it suggests a broader feature. The Exception Assistant could come with links to guidance on typical reasons for the exceptions, and it would be interesting if those links could be customized. The Process Guidance in TFS could be a model of how to do this.
This is an unworthy request, in my opinion. It's better to learn what causes such exceptions rather than have the CLR try to hold your hand. Also, exactly what would the CLR tell you, since it doesn't know, at the time it tries to access "e", that the instance came from a call to "d".
Just break up the call chain if you need to debug:
va bv = a.b();
var cv = bv.c();
var dv = cv.d();
var ev = dv.e();
var fv = ev.f();
var gv = fv.g();
That makes it pretty easy to see where the null is coming from.
@James, just to be certain we understand you, do you expect to have problems if you use Visual Studio 2012 to develop ASP.NET 4.0 applications which will run on Windows Server 2003? Can you say what problems you expect?
The lack of a service pack more strongly affects those who can't test and debug their application in the target environment. Are you unable to test on Windows Server 2003?
@Reinhard Ostermeier: I believe I understand your concern, but I don't understand why you can't use VS2012 to build .NET 4.0 applications, then deploy the application to the Windows XP machine which has the special hardware installed on it.
Perhaps I wasn't clear. You can develop in VS2012 and support XP. The only thing you can't do is be assured that finding no problems when you debug on your VS2012 machine implies there will be no problems when running on XP. You will need to do QA on a machine running only .NET 4.0.
That is the only restriction I have seen. Have you seen something else, or is this the restriction which will prevent you from upgrading to VS2012?
We are continuing work on the new Analytics Service for TFS Hosted and will have an announcement on when public preview will be available for the hosted version in the next few months. If you are interested in testing a private preview of the service now, please contact me at email@example.com.
I also want to reassure everyone that the On-Premises version is in development and we are fully committed to delivering on it.
The Analytics Service is the backend for a suite of new features we are very excited about including new Dashboard Widgets, Power BI connectors, Power BI templates but most importantly we want you to be able to get your data where you need it. I would like to hear what your goals are for reporting and what we can do to help. Please email me or just post to this thread directly.
If you want more votes, you should substantiate your assertions. For instance, would power pivot and rally handle all of the existing TFS reports? For what scenarios are there "better, easier, and more powerful ways to do reporting"?
Enabling the ability to move projects between collections is a feature that we’re committed to delivering. However, due to the impact that this has across all of our development teams we are choosing to delay investments in this area in order to let those teams accelerate investments in DevOps workflows. We will re-evaluate picking this up mid-way through 2017 and will provide an update on our plan at that time.
TFS & VSTS Program Manager