EB,
Xml could work depending on the scenario.
If you add an Installer project, you can bundle the framework install with
it. The app installer itself is not .NET. It is an MSI with a
bootstrapper.
Hope this helps,
Steve
<(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi All,
> I have few questions about deploying windows apps developed in .Net
> framework. These days it is all about internet apps and services, and
> I need to develop small windows app and deployed it on a machine with
> no internet access, no database installed and no .Net framework
> either. This small Widows app includes presentation layer, business
> logic and data access layer.
> 1) Because client machines, where app will be running, doesn't have
> any database and I don't want to install new one (in order to save
> space), could XML files be a solution for storing and retrieving
> information needed and created by the app? Are there other options?
> 2) In order for app to run, I'll need to install .Net framework on
> client machines. Because there is no internet connection on client
> machine, can framework be distributed on same CD as the app and be
> installed seamlessly for the user (behind the scene with less
> interaction as possible)? How can app installer install framework, if
> in order to run installer, framework should be installed? How this
> circle can be broken?
> 3) In future more class libraries will be developed. How can I design
> app now, in order to simplify plug-in of the assemblies in future?
> I understand that each question is a discussion on its own and just
> need some point of reference at this moment to start my search for the
> best solution of all these issues.
> Thank you for any advice in advance,
> EB
>
|