![Principle app not importing layers](https://kumkoniak.com/44.jpg)
I suspect because there are no app layers created with the new OS layer yet. When we create a new image template based on the new OS layer, there no app layers to choose from. Just looking for what the best practice is for something like this. We tried re-publishing the image with a new OS layer, but the new OS layer is not listed in the available OS layers. Then again Microsoft likes to put all kinds of new stuff\shuffle things around whenever they come out with a new OS build and so maybe just updating the App Layer to the new OS build might cause unintended consequences. Part of me thinks I should be fine just updating the App Layers to the new OS build. What is the best practice to "upgrade" the app layers over to the newer OS layer?ĭo I just create a new version of the app layer and associate it with the newer OS layer? Do I clone the app layer and then start building from there? Do I do a fresh app layer based off the new 1803 OS build? Are there any "gotcha's" to simply updating the App Layer to the new OS build? Would something like office 2016\365 behave well just updating it to the 1803 OS build? If app.go starts to grow, you can split it into multiple files. Next, we start the server and wait for signals in select for graceful completion. This makes the business logic independent from other layers. All our app layers are based off the 1703 build layer. This technique allows us to layer the application using the Dependency Injection principle. We've got a Windows 10 Build 1703 OS layer. I'm fairly new to the app layering process and I have a general question.
![Principle app not importing layers](https://kumkoniak.com/44.jpg)