Forums

UI generator returns error when XAML files are moved to subfolders
Last Post 01 Jul 2016 10:16 AM by Filip Dušek. 4 Replies.
Printer Friendly
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
A TUser is Offline
New Member
New Member
Posts:34


--
20 Jun 2016 11:42 PM
    After I moved my .xaml files to subfolders, ekUIGen.exe started to exit with code -2, and I spent some time until I had figured out what's the reason (it wasn't the only change I made before trying to compile). It's not a big problem to simply run UI generator for each of the subfolders separately, but I want to ask: why does it return error when it finds .xaml files in any of the subfolders (there is no error if folders are empty or contain other kinds of files)? Does it try to generate UI from these files but fails because of some reasons? Is it a supposed behavior or a bug?
    Filip DušekUser is Offline
    Advanced Member
    Advanced Member
    Posts:695


    --
    21 Jun 2016 09:15 AM
    Depends on what is the actually error. Complete error message is in console output or in generated file if it's error during actual generation.

    So what was the error message?
    A TUser is Offline
    New Member
    New Member
    Posts:34


    --
    21 Jun 2016 11:15 PM
    I checked console output, UI generator threw System.IO.DirectoryNotFoundException because it wasn't able to find subdirectory in the output directory. After I manually added to it a subdirectory with the same name as in the input directory, it worked fine.

    Shouldn't UI generator automatically create subdirectories in the output folder? Or at least put generated files in the parent directory if it fails to find a required subdirectory?
    Filip DušekUser is Offline
    Advanced Member
    Advanced Member
    Posts:695


    --
    22 Jun 2016 09:08 PM
    It should, i will check that.
    Filip DušekUser is Offline
    Advanced Member
    Advanced Member
    Posts:695


    --
    01 Jul 2016 10:16 AM
    Fixed, fix in the next release
    You are not authorized to post a reply.