Differentiate extract/publish Office document about vbasync HOT 4 CLOSED

I've thought about this before, since I use VBA Sync myself to help with developing an Excel .xla add-in. But I don't want to complicate the UI with extra fields that many people won't use! Perhaps you could use VBA Sync's command-line interface instead:

VBASync -r -x -f WorkingCopy.xls -d Repo
copy /y BaseAddIn.xla PublishedAddIn.xla
VBASync -r -p -f PublishedAddIn.xla -d Repo

from vbasync.

I have to test that kind of process. I didn't think about it as I was still in automation mode in my reflection. And when you use automation, even if the vba files didn't changed, the generated document would be changed. And this we cannot afford.

If VBASync generates exactly the same document every time then we might have a winner ;-) .

So I going to evaluate this option...

from vbasync.

Ok it seems to work properly.

Maybe you could had a non-regression test to verify that the generated office document is exactly the same when you generate twice without modifiying neither the "template" document nor the vbas.

I think I might not be the only one to have this concern.

Thx.

from vbasync.

Okay, I've added that integration test for a very basic scenario. Let me know if you ever notice a scenario where publishing is non-repeatable, and I'll add another integration test to cover that case.

from vbasync.