Errors in build with MSBuild

[Jack Mod]

Hi all,
I work in the VS2005 and IS11.5.
In my solution I have the project with name that contain the dot, for example:
'CompanyName.ModuleName'.
The IS project reference to the project output of the 'CompanyName.ModuleName'.
When I build this solution in the VS2005 IDE all works fine, but when I try to build this solution with MSBuild in command line the build fail with error:
"...\Macrovision.InstallShield.targets: error: No outputs for project "ComapanyName" were provided, but the installation project references "CompanyName.ModuleName.Primary output".

[MichaelU]

Hi Jack Mod,
Are you using the default .isproj file, with the installed Macrovision.InstallShield.targets file? If not, please give them a try. If so, it's possible that the period in the project name is being misinterpreted somewhere along the line. If it's in our task, I should be able to whip up a test version that might fix the issue. So if you're willing, let's try to isolate this problem.

In the Macrovision.InstallShield.targets files ([ProgramFilesFolder]MSBuild\Macrovision\IS11.5) near the bottom there is a commented out Message task that reads like:

<Message Text="Project Output Files:@(TaggedOutputs->' %(ProjectName).%(OutputGroup):%(FileName)%(Extension)')"/>

I'd like you to back up the original, then uncomment this, and change the dot to a colon so we can tell for sure whether the task has the right split between project name and output group.

<Message Text="Project Output Files:@(TaggedOutputs->' %(ProjectName):%(OutputGroup):%(FileName)%(Extension)')"/>

Then run MSBuild and scan your output for

CompanyName.ModuleName:Primary output:<filename>

If it exists, then I think the task is fine and the problem is on the other end where we query the task. If not, it's either in the task or in MSBuild (probably the task) unless your project actually has no primary output. Could you let me know what this test shows?

[Jack Mod]

Hi MichaelU,

I found the problem.
The MSBuild itself in the Microsoft.Common.targets uses instead the project name with period the converted name like "CompanyName_ModuleName".
The fix is to convert the name of the reference project in the .isproj file, and in the .ism file correspondly change
the <FileName> of the component in the "File" table.
This work well, but after each editing in IDE I must manualy refix those lines .

Some additional points:

Originally Posted by MichaelU

Hi Jack Mod,
Are you using the default .isproj file, with the installed Macrovision.InstallShield.targets file?

Yes, I'm using the default .isproj file.
But when I try to build the solution a build is fail with MSBuild error: the "OutputPath" not defined.
The problem is missed "Platform" property, which not defined for project of type .isproj.

Originally Posted by MichaelU

In the Macrovision.InstallShield.targets files ([ProgramFilesFolder]MSBuild\Macrovision\IS11.5) near the bottom there is a commented out Message task that reads like:

<Message Text="Project Output Files:@(TaggedOutputs->' %(ProjectName).%(OutputGroup):%(FileName)%(Extension)')"/>

I'd like you to back up the original, then uncomment this, and change the dot to a colon so we can tell for sure whether the task has the right split between project name and output group.

<Message Text="Project Output Files:@(TaggedOutputs->' %(ProjectName):%(OutputGroup):%(FileName)%(Extension)')"/>

Then run MSBuild and scan your output for

CompanyName.ModuleName:Primary output:<filename>

If it exists, then I think the task is fine and the problem is on the other end where we query the task. If not, it's either in the task or in MSBuild (probably the task) unless your project actually has no primary output. Could you let me know what this test shows?

I found this line and used it.
But output (even for "normal" projects) little beet strange - the metadata %(ProjectName) is always empty.
In fact the output is:

 ...: .Primary Output: A.dll ....

Thank you.

[MichaelU]

Hmm, yeah looks like the commented out debug code rotted a bit when some other changes cleaned things up. Instead of %(ProjectName) it now needs to be %(Name) now.

As for the dot vs underscore in the project name, I'll try to get this fixed for the next release. We'll track this under IOC-000045403. At least for the moment it sounds like you've got an effective workaround with replacing it manually. Let me know if you run into any problems with the workaround.

Erk, I misread. I thought this was a one time change, but on rereading it sounds like you have to reapply after any project edit. I'll see if I can push this up a bit (our schedule is a bit tight though).

[ggreig]

This is also a serious problem for us - all of our projects include dots in the name.