Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login

    Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

    If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

    .NET : Unable to build 'X86' and 'Any CPU' projects together

    Scheduled Pinned Locked Moved Support
    buildmasternetbuilds
    2 Posts 1 Posters 61 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • ? This user is from outside of this forum
      Guest
      last edited by

      Hi,

      I am evaluating BM for my team and having no way to get through this.

      I build a exe. project (using Build .NET Project action or MSBuild action) and this is set up as an X86 project (Target Platforms - X86)since it contains some references to unmanaged code and does some Pinvoke stuff. This project refers to other projects which are built with 'Any Cpu' settings. (Target Platform- Any Cpu).

      When I build this X86 executable project, I get an eror as 'Output path is not defined for all configruations in the the 'Any Cpu' project. No output path for Release and X86' in the referenced project. '

      It works fine when I build the solution in VS. But with BM, again, I cannot build solution because I just cannot set bin\debug of all projects as the target dirs of respective projects and hence all the projects' output to a fixed single target dir folder. Hence, I had to go with building projects that need to be deployed but in this case stuck up with this output path issue !

      How do I get around this. I am really stuck up having tried several options to build this project !

      Any help is appreciated.

      1 Reply Last reply Reply Quote 0
      • ? This user is from outside of this forum
        Guest
        last edited by

        I think the problem may have to do with your project/solution configuration (i.e. .sln and .vbproj/.csproj files).

        In the action's execution log, you can see the exact command run by the Action. I would suggest to run that command at your desktop, and then try to see what specific project is missing the output path... and then tweak the project files.

        1 Reply Last reply Reply Quote 0

        Hello! It looks like you're interested in this conversation, but you don't have an account yet.

        Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

        With your input, this post could be even better 💗

        Register Login
        • 1 / 1
        • First post
          Last post
        Inedo Website Home • Support Home • Code of Conduct • Forums Guide • Documentation