Announcement

Collapse
No announcement yet.

[CLOSED] [#531] [1.10] Support .csproj wildcard configurations

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

    [CLOSED] [#531] [1.10] Support .csproj wildcard configurations

    Hi guys, bit of a cracker here potentially, I'm using the following piece of code in a standard c# library's csproj file to include external files in the build where I have multiple projects requiring the same codebase:
    MSBuild
        <Compile Include="../core/**/*.*">
          <Link>core/%(RecursiveDir)%(FileName)</Link>
        </Compile>
    However the build fails when I try to use this same setting in my Bridge Project. I strongly expect it is because the Bridge Translator does not expect (or has trouble handling) wildcard characters in the configuration file as my only successful work-around so far involves explicitly specifying each file with the compile tag.

    I'd love to not have to rely on maintaining the csproj file every time I add/move/rename a file so would really appreciate a solution :)

    Good Luck!

    #2
    Thanks for the report. Fun problem. We will try our best to get this working and keep this thread updated with our progress.

    Comment


      #3
      Created a new Feature Request.

      https://github.com/bridgedotnet/Bridge/issues/531

      Comment


        #4
        We have impleneted this feature. It will be included into 1.10 release.

        Comment


          #5
          Thank you !
          Also takes a lot of it!

          ;)

          Comment

          Working...
          X