Re: .Net packaging/wrapper application?
This means that your potential customer that is still on dial-up, the
I don't know the details of Thinstall and/or Xenocode, I've only been
reading through this thread, but for this particular point to actually
support your position, you'd have to have your one-EXE program include:
- your app's own code
- the Thinstall/Xenocode code
- the .NET framework
....and all of these components together somehow would have to result in a
single file that's smaller than the 25MB .NET framework on its own...is that
correct?
And then as soon as you have another application that also uses
Thinstall/Xenocode, it would also have to include the same components
internally. IOW, a copy of .NET is wrapped up in every single application.
Please tell me this is not how it works.
This means that your potential customer that is still on dial-up, the
25+MB .Net framework may never get downloaded so your apps are worthless
to them.
to them.
reading through this thread, but for this particular point to actually
support your position, you'd have to have your one-EXE program include:
- your app's own code
- the Thinstall/Xenocode code
- the .NET framework
....and all of these components together somehow would have to result in a
single file that's smaller than the 25MB .NET framework on its own...is that
correct?
And then as soon as you have another application that also uses
Thinstall/Xenocode, it would also have to include the same components
internally. IOW, a copy of .NET is wrapped up in every single application.
Please tell me this is not how it works.
Comment