[$OutputDirectory]\[$TargetAssembly].licenses can't be found

[jwyother]

I have added a deployment project to my VS 2005 solution.  My main project uses Measurement Studio Controls.  I added the Primary output to the deployment project which correctly pulls in all dependencies needed.  Part of the Primary output of my project is the [$OutputDirectory]\[$TargetAssembly].licenses file that I assume is from Measurement Studio.  When trying to build the deployment project I keep getting the error that this file can't be found.  It seems as though VS should be expanding these variables.  Have searched for the reason why I am getting this error with no success.  I think it is related to Measurement Studio.  Any help would be greatly appreciated.

Thx

[Josh_W]

jwyother,

I made some distribution projects here, and wasn't able to find the file you're referring to.  I wasn't able to find any .licenses files as part of the primary output of my program, but maybe I'm looking in the wrong place.  Could you send a screenshot with the error that you're seeing, and one of the file as part of your primary output?

Josh W. | National Instruments | Applications Engineer

[jwyother]

The .licenses file is part of the Primary output of my main program not the deployment program.  I have attached a zip file that includes the screenshots you requested as well as a sample project that demonstrates the error.

You can find the .license file in the license_test\license_test\Debug directory.

If you need more information please let me know.

Thx for your help!

[Josh_W]

jwyother,

I spoke with R&D regarding this error.  When the setup project imports the primary project output, it should assign values to the fields [$OutputDirectory] and [$TargetAssembly].  For some reason, it is not, and what we are seeing is the raw macro code.  I have passed this information along to R&D so that they can let Microsoft know of this issue.

As a possible work around, instead of adding the project output, you can add the actual .exe file that is being created.  In that case, you will probably have to add all the assemblies and references manually.  You can find information regarding distributing C++ applications in the Measurement Studio help under "Deploying Measurement Studio Windows Applications"

Josh W. | National Instruments | Applications Engineer

[Matt in Ohio]

I'm having the same problem. I created a new posting, but thought it may be useful to reply to this older posting.

What was the resolutioin to this problem?

Matt

[JonathanN]

Hi Matt,

See my response here.

Best Regards,