Learn to use Visual Studio, Visual Studio Online, Application Insights and Team Foundation Server to decrease rework, increase transparency into your application and increase the rate at which you can ship high quality software throughout the application lifecycle
More videos »
The specific issue is that "The breakpoint will not currently be hit. No executable code of the debugger's target code type is associated with this line. Possible causes include: conditional compiliation, compilier optimizations, or the target architecture of this line is not supported by the current debugger code type."
Thanks in advance.
The day I wake up and can do the same I do in Monodevelop in linux and git, with Visual Studio 2013. That day, I will be a happy guy :P
I think Microsoft has made a good decision supporting git from the IDE but IMO this is a very basic stuff. It is a shame such a powerful developing tool used by million of developers lacks more git integration.
Done some work around with SeeTest in visual studio using some sample application. Working well doesn't faced any issues till now..
Can you contact us at firstname.lastname@example.org? This may be easier to troubleshoot over email. It would be most helpful if you could provide detailed repro steps about what you are trying to do and the results you are seeing (what type of project, does it happen for all the projects you tried or a particular one, what do you do - set a BP, F5, etc.) and a simple repro project.
thanks, Sasha. at present we don't have a supported way to create theses GCdumps manually. You are correct that it uses PerfView code under the covers to create them but they get wrapped in a non-trivial way. Thanks for the feedback that this would be useful. We're examining a few different options for how to get this into folks' hands at present.
Also, Sasha... for a more on-road version of this scenario, you should check out the Application Insights product which has a version of this workflow and can also collect diagsessions for applications under monitoring that have leaks.
I've just upgraded TFS 2012.2 to TFS 2013 and it told me I needed to apply these changes.
For the record, some feedback:
The detailed instructions are great. However, IMO this page would be much easier to use if it also provided the old and new versions of the XML files. This would allow people to diff/merge using tools instead of fiddling through by hand. It would also mean that where the templates have not been customised we could just upload the latest version and be done in a few seconds. (This seems like something the installer should do automatically where the templates are not customised).
Confusingly, although I have been directed here by the upgrade process, it seems that my templates are already up to date. This implies that the upgrade process (2012 RTM -> .1 -> .2 -> 2013) does upgrade the files if they have not been customised. If this is the case it would have been more reassuring for this page to mention that, or even better for the upgrade system to have realised everything was up to date and therefore not told me that I needed to make these changes at all!
Apart from that, the upgrade was easy and seamless - great job! (I upgraded 2005->2008->2010 so I really appreciate how much better this process has become)
Thanks for the nice comments. It is a great suggestion to include the xml files in a future blog post. I will play with the idea when I create the next upgrade blog post.
I would like to comment on your already upgraded templates. When you do an upgrade of your TFS server, we will install the new process templates. These process templates can be used when you create a new team project. This blog post however is how to update your existing team projects. If we introduce a new feature (like portfolio management in TFS 2013) that needs updated settings, we will do our best to make it friction free with the "Configure Features" wizard. There are however a couple changes that are not critical, and we will not apply them automatically. And that is what this post describes.
We will not apply the changes automatically because we don't know what your customizations have made in the past.
@Sasha, can you describe a bit more the scenarios where you would like to use this functionality. That will help inform us as to the best way to deliver that. Please feel free to reach out to me at email@example.com
Do you know if VS 2010 can connect to TFS 2013?
Thanks. Helpful =)
I have now successfully integrated Release Management into my deployment process. I have some bugs I would like to submit and also some feedback I would like to post to improve the system. Where would I be able to do this.
Where is the global .gitconfig located? For me it's not using the same one as Git4Windows (%userprofile%/.gitconfig) by default.
Fwiw when/if this code runs out of activations please leave a comment so I can get updated ASAP
@Terry: please submit a bug so we can try to repro and fix the issue: connect.microsoft.com/visualstudio
@Mauricio: we know we've got more work to do; if you want to propose or vote for specific improvements, I invite you to do so here: visualstudio.uservoice.com