Notepad++ ( download here) can help a lot in re-format or tidy up an messy XML
From Notepad++ menu: TextFX -> HTML Tidy -> Tidy: Reindent XML
This feature however wraps XMLs and that makes it look 'unclean'. To have no wrap,
C:\Program Files\Notepad++\plugins\Config\tidy\TIDYCFG.INI, [Tidy: Reindent XML] and add wrap:0 so that it looks like this:[Tidy: Reindent XML]
input-xml: yes
indent:yes
wrap:0
Enjoy XML everyone !
If you are here because you might want to ask TFS 2010 to auto-update some fields (such as remaining work vs. completed work), then you’re lucky because of there is a TFS Aggregator plugin:
http://tfsaggregator.codeplex.com/
Download link : here
This server-side plugin let TFS does such things. Some of its nice features:
OK that’s it. Please visit the site for more info.
Happily working on Sunday.
I know this is not a technical blog – but I found it is encouraging to keep a collection of my favorite quotes and update it whenever I found a good one.
Today’s quote come from my build team:
“A true hero need not speak. The world will speak for him when he is gone”
Ping back from : http://blogs.telerik.com/kevinbabcock/posts/08-12-23/visual_studio_ldquo_error_creating_control_rdquo.aspx
I’ve run into this error before and last night it reared its ugly head again. You’ll find it from time to time when switching to Design View in Visual Studio to work with custom server controls. The bug is in Service Pack 1 of VS and can be quite annoying.
It has been submitted to Microsoft and they claim to be working on a solution which will “fix it in subsequent releases” of Visual Studio. Unfortunately, developers (like me) don’t want their productivity to suffer while we all wait for a fix from Microsoft. So here are a couple of steps you can take to try to resolve this issue yourself:
Solution 1. Close and restart Visual Studio. Some developers claim this solved the problem for them. I cannot confirm that this works because it did not solve the problem for me, but it’s certainly worth a try since it’s quick and does not require you to modify your system in any way.
Solution 2. Delete all project assemblies from your ProjectAssemblies directory.
The second solution did the trick for me. Hopefully one of the above solutions worked for you. If you have run into this bug and found an alternate solution, please let me know and I’ll make sure it gets added to the list.
At a client we were testing our newest line of development machines. After installing Visual Studio 2010 we noticed that the performance was VERY slow when connecting to Team Foundation Server (2010). Performing a get latest of a large solution took several hours(!).
Some investigation showed that it does not appear to be a TFS issue per se but rather something lower in the .NET Framework stack, having to do with automatic proxy discovery through the WPAD protocol.
You can work around the issue by turning off proxy autodiscovery on a per-application basis by using a .exe.config setting.
The .exe.config for Visual Studio is %VSINSTALLDIR%\Common7\IDE\devenv.exe.config and it already contains a section in the .exe.config for System.Net. After adding the defaultProxy element, that section would look like this:
1: <system.net>
2: <defaultProxy enabled="false" />
3: <settings>
4: <ipv6 enabled="true"/>
5: </settings>
6: </system.net>
