Entered for tracking since I do not want to divert from the job at hand right now.
1) when loading XMLTooling.sln an error is reported "Cannot load some projects". It doesn't specify which projects and it doesn't specify the error. I think the project is one of the pseudo-ones which contain the schema and so forth since manualling loading the real projects works. This is new since I moved the project to Build\VC10
2) Both in XMLTooling and OpenSAML a batch build of all platforms/targets will fail with a link error about the wrong type of input file. Building one by one works. Individual builds work. AFAICS this is day 1.
Environment
None
Activity
Rod Widdowson
January 4, 2017 at 3:14 PM
Closing - not customer visible
Rod Widdowson
January 4, 2017 at 3:14 PM
Looks like this is done
Rod Widdowson
May 3, 2016 at 4:04 PM
We should add the path to Wix to one of the properties files. Its biting us.
Rod Widdowson
May 1, 2016 at 1:13 PM
The warning has been supressed. Doing a batch build is less interesting because of the issues with the installers build - which is why we have the cpp-msbuild.
Entered for tracking since I do not want to divert from the job at hand right now.
1) when loading XMLTooling.sln an error is reported "Cannot load some projects". It doesn't specify which projects and it doesn't specify the error. I think the project is one of the pseudo-ones which contain the schema and so forth since manualling loading the real projects works. This is new since I moved the project to Build\VC10
2) Both in XMLTooling and OpenSAML a batch build of all platforms/targets will fail with a link error about the wrong type of input file. Building one by one works. Individual builds work. AFAICS this is day 1.