Wednesday, June 7, 2017

Sitecore: TDS Global Config issue with VSO Build Definitions

This is an issue I encountered with Sitecore, TDS and VSO. Everything would compile just fine locally, but when I setup a Build Definition in VSO I would get the following error for all of my projects...

"d:\a\1\s\src\Feature\Category\tds\TLG.Feature.Category.Master\TLG.Feature.Category.Master.scproj" (default target) (25) ->
  d:\a\1\s\TdsGlobal.config(2,1): error MSB4025: The project file could not be loaded. '.', hexadecimal value 0x00, is an invalid character. Line 2, position 1. [d:\a\1\s\src\Feature\Category\tds\TLG.Feature.Category.Master\TLG.Feature.Category.Master.scproj]
"d:\a\1\s\TLG.sln" (default target) (1) ->
"d:\a\1\s\src\Feature\Ceros\tds\TLG.Feature.Ceros.Master\TLG.Feature.Ceros.Master.scproj" (default target) (26) ->
  d:\a\1\s\TdsGlobal.config(2,1): error MSB4025: The project file could not be loaded. '.', hexadecimal value 0x00, is an invalid character. Line 2, position 1. [d:\a\1\s\src\Feature\Ceros\tds\TLG.Feature.Ceros.Master\TLG.Feature.Ceros.Master.scproj]
"d:\a\1\s\TLG.sln" (default target) (1) ->
What I ended up doing was removing the following from the top of the generated TDSGlobal.config...

<?xml version="1.0" encoding="utf-8"?>
After that, VSO compiles everything just fine. As far as I can tell the TDSGlobal.config is still working. I'm not sure of any possible negative repercussions from removing this line, but so far I haven't seen any and it got around the error.

Monday, June 5, 2017

Sitecore: TDS bundling error

Another random TDS error I've encountered a few times now. It seems to stem from renaming and/or moving around TDS projects too much. I'm not 100% on the exact cause, but the error that gets generated...

Which isn't very useful. Looking at a more Detailed output...


"Bundling files from project 'xxx.TDS.Master.scproj' into pacakge...
Exception Value cannot be null."

If you attempt to build only the TDS project listed, then it compiles without any errors. If you attempt to build a different TDS project that uses the Multi-project Properties tab to do Package Bundling, then you get the shown error.

The fix (for me at least) was to change the value of the "Recursive Deploy Action" dropdown, then save and rebuild. You can immediately change it back to the original value, but you need to force it to re-save its value to the .scproj file.


Repeat for any affected TDS projects, and your bundling functionality should work again.