Possibilities of using an app to "create" an app?

I am trying to understand app-ception (lol). What if I wanted to make an App, apply a bunch of settings such as label names or combo box names, then based on those settings, it essentially "creates" another app based on those settings? What is the best means to accomplish this?

For Example: If I wanted to create an app that contained 1 button that emails a report. The first thing I want to do, is let the user open, provide an email, then "Compile" an app that will only email the user email originally provided, and leave no trace of the original app.

What are the means of doing something like this? Such as A form destroys itself from an EXE (But I dont think thats possible?)

While it certainly is possible to do what you ask, the ends can be achieved using a much easier method. You could use a single program and dynamically instantiate the necessary controls and dynamically wire their events at runtime based on a config file.

Right, but what if I want just one exe and dont want to deal with config files

Now you've lost me. Clarify please.

It sounds like you are talking about a code generator. It's a massive undertaking. You might think that you have simplified it down to where it is reasonable, but if you start down this path you will quickly find that you have not. There will always be 'one more thing' to add. Code generators exist. There are any number of commercially available ones, but they all suffer from some serious limitations, and I personally feel that they always will. Every code generator has a few tasks that it does really well, but once you stray from that core competency, the quality of the product gets worse and worse. You, as the generator writer, will then perpetually chase after improvements for new scenarios until you drop dead from exhaustion.

Quote:

---

For Example: If I wanted to create an app that contained 1 button that emails a report. The first thing I want to do, is let the user open, provide an email, then "Compile" an app that will only email the user email originally provided, and leave no trace of the original app.

---

And the point of that would be what exactly? Anybody else smelling a well-known pressed meat product or is it just me?

no... not smelling any meats of any kind... this isn't the first time I've seen this kind of thread... with dang near the same wording too... not sure what to make of it. I don't think it's a malorderous issue in the state of Denmark however.

-tg

Quote:

---

Originally Posted by dunfiddlin

And the point of that would be what exactly? Anybody else smelling a well-known pressed meat product or is it just me?

---

I have been on this forum for a while, I am asking more about a proof of concept of writing apps to create apps. I am writing apps at my day job and believe me, If I wanted to write a "well-known pressed meat" product, I wouldnt need to ask anyone here to do it.

as a proof of concept, yes.,... it is possible... that's what VS is... it's an application that makes other applications... the CodeDom is probably what you're looking for...

-tg

Quote:

---

Originally Posted by techgnome

as a proof of concept, yes.,... it is possible... that's what VS is... it's an application that makes other applications... the CodeDom is probably what you're looking for...

-tg

---

Thanks. This is just something for me to brainstorm ideas with. I think config file ultimately will be the best bet. I want to try to make my applications independent of hard coded variables (such as pulling data from WBC). Just creating something thats hard for users to mess up, and all-in-one. I suppose this is where the strength of the config file/user settings comes into play.

And thanks shaggy, that seems about right. It would be not about maintaining or editing current functionality but adding more, which is to the point of, thats why you use visual studio

Quote:

---

Originally Posted by jayinthe813

Just creating something thats hard for users to mess up

---

Yeah. Good luck with that.