I'm fiddling around with a property editor that needs to post a request to a web service that I've written, which then requests data from an external API (doing it this way as the external service requires oAuth2 and does not allow client-side authentication). It's an extra hop, but lacking an alternative will be fine for what I want to do.
So, given that I have a .asmx file which is a dependency of the property editor, where should I put it? Currently it's just sitting in the same folder as the rest of the property editor files. Everything works just fine, but want to make sure I'm doing things the best way possible. Does it even matter?
I don't know if there's an established best practice for this, but I like the idea of keeping it in the property editor folder. It makes things easier to keep track of, and when it's in there, it should be installed automatically when creating a package without having to specify it as an additional file.
Best practice for package structure
I'm fiddling around with a property editor that needs to post a request to a web service that I've written, which then requests data from an external API (doing it this way as the external service requires oAuth2 and does not allow client-side authentication). It's an extra hop, but lacking an alternative will be fine for what I want to do.
So, given that I have a .asmx file which is a dependency of the property editor, where should I put it? Currently it's just sitting in the same folder as the rest of the property editor files. Everything works just fine, but want to make sure I'm doing things the best way possible. Does it even matter?
I don't know if there's an established best practice for this, but I like the idea of keeping it in the property editor folder. It makes things easier to keep track of, and when it's in there, it should be installed automatically when creating a package without having to specify it as an additional file.
is working on a reply...