TomSmith
Topic Author
Posts: 15
Joined: 31 Mar 2014, 22:23

project setup options

18 Apr 2014, 23:55

Hi,

Im still rather new to noesis, but I am trying to figure out the best way to integrate it into my projects workflow. I prefer to keep all xaml files in source control, so for now I have a project with the ui files and associated resources in it. What I would like to do is run Resource.BuildTool.exe as part of my build process, to rebuild the resources for my targeted platforms. Is there any way to specify the Data paths for packages, and for compiled output on the command line?

I am using ogrebindings in my project, so I can set the path to look for the compiled output easily enough.

Eventually I would like to achieve packaging the code-behind classes and xaml in separate dll file projects, so I can decouple my main project from ui code changes. Is there any guidance on what needs to be done to support this? does reflection work correctly in this scenario?
 
User avatar
jsantos
Site Admin
Posts: 2900
Joined: 20 Jan 2012, 17:18
Contact:

Re: project setup options

19 Apr 2014, 17:07

Is there any way to specify the Data paths for packages, and for compiled output on the command line?
No, sorry to say, but is not possible in noesisGUI 1.1 changing those paths. Data must be in \NoesisSDK\Data\Packages and the compiled output goes to \Bin\Data.

We are changing this in 1.2 to improve the flexibility. We expect to have a beta version very soon.
Eventually I would like to achieve packaging the code-behind classes and xaml in separate dll file projects, so I can decouple my main project from ui code changes. Is there any guidance on what needs to be done to support this? does reflection work correctly in this scenario?
Do you mean having several dlls? Yes, everything should work perfectly that way. You can even have the xaml cache inside the dll if you implement a custom file system

Who is online

Users browsing this forum: No registered users and 1 guest