I fixed a bug this week in the managed CA remote-invocation channel that is
probably the cause of the exception you're seeing. Can you check if you can
still reproduce the problem on today's build 3.0.4206? (It's not published yet,
but should be there soon...)
-Original Message-
From: [
What is the value of MYPROPERTY ( msi log ) at the moment that you attempt to
get it? I'd like to see if I can mock this up and debug it. Perhaps
there is some kind of escaping problem.
Christopher Painter, Author of Deployment Engineering Blog
Have a hot tip, know a secret or read a really
2 matches
Mail list logo
