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!

    TFS 2013 New Application Wizard from Solution File

    Scheduled Pinned Locked Moved Support
    buildmaster
    4 Posts 1 Posters 1 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

      Trying to utilize the New .Net Application Wizard for a .sln file in source control that we have in place. The solution file has two projects, one of which is a dependency of the other. Our build order and dependencies are setup correctly in the solution, but when we go to the wizard to add the applications, after detecting the two applications giving us the checkboxes, selecting the class library that is the first in the build order references a relative path in source control (based on the location in the team projects) and gives us a Server 500 error. I've seen this very relative path mentioned in the Event Viewer on the server for the ASP.Net error when Buildmaster failed.

      My question is thus:

      Is the issue with our solution file, with the TFS extension (or Windows-SDK extension) or should we just avoid using this wizard altogether?

      Any help is much appreciated.

      Product: BuildMaster
      Version: 4.1.4

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

        It's likely an issue with the WindowsSDK extension. It might be easiest to just create a Standard Application and add the following actions (the same as the recipe would):

        Get Source

        • Apply Label (%APPNAME%-%RELNO%.%BLDNO%)
        • Get Labeled (%APPNAME%-%RELNO%.%BLDNO%)
        • Optional: Write Assembly Version
        • Optional: Install NuGet Packages (if any)

        Build

        • Build MSBuild Project
        • Create Build Artifact

        Deploy

        • Deploy Build Artifact

        You may want to build each project independently and capture each into separate artifacts as opposed to the Solution, that's up to you.

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

          Okay, we're still figuring out how to setup the dependencies though as required deployables, as we're having trouble with building.

          I assume this might be a good bug to post to github for that particular recipe, correct?

          We're relatively new to this environment, so thanks for the patience.

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

            Sure, feel free to post that to GitHub. What types of projects are these? Typically you don't need to worry about dependencies if you get the source for the whole solution and just build the .csproj as MSBuild will handle that for you in the same way as if you built it in Visual Studio.

            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