Hi Roy
Please download the latest version of the MSBuild Sidekick - that should take care of the non-MSBuild parts not being saved problem.
We've released a patch for it less than a day after the release.
Regarding the absence of Team Build elements from the UI, please note my post about schema-support. This is a known issue and we are working hard to solve it as soon as possible.
Thank you for being alert about this. I'll be coming to the Agile Israel meeting next Thursday, to hear you and Justin speak, and I'd be glad to use this opportunity to hear any other comments you might have about the sidekick. With any luck, I might even have some news of my own related specifically to Team Build Types :-)
Is this a C# only tool? I can't seem to get it to open a .vbproj file.
Sean,
The MSBuild Sidekick should work just fine with .vbproj files.
Though we are not using VB.NET very often in our office, we did perform several tests with basic .vbproj files and didn't notice any special problems.
If you have a specific file that's causing the problem, you can email it to tfs@3vium.com and I'll check it to see why you can't open it in the MSBuild Sidekick.
Thanks,
Matan
Matan,
I ASSumed that VB wasn't supported when the Open dialog listed the file types (*.msbuild;*.csproj;*.proj) and didn't see *.vbproj. I guess I'm just used to VB not being supported that I didn't even try the *.* option to open a *.vbproj file.
It DOES open *.vbproje files. Guess I need to go try it out now.