转换为.exe Windows应用程序后的.net

本文介绍了转换为.exe Windows应用程序后的的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

您好， 我已经使用C#(框架3.5)完成了 Windows应用程序.它的小型应用程序带有水晶报表，MS sql server2008.我需要将应用程序转换为.exe，然后需要在其他计算机上安装该应用程序.我没有安装框架，ms sql和crystal report.支持什么要添加的文件，以便在其他计算机上运行我的应用程序.

Hi frnds, I have completed my windows application using C#(framework 3.5). Its small application with crystal reports,MS sql server 2008.I need to convert my application to .exe and after i need to install that application in some other Computer.I didnt installed framework,ms sql and crystal report.What are support files to add for run my application in other computer.

推荐答案

转换为EXE很容易-所谓的构建就是全部，但是您需要选择菜单栏上目前显示"Debug"的"Release". 其他要求比较有问题. 您不一定要将exe文件从一台计算机复制到另一台计算机并期望它能工作-这很有可能不会.最好的办法是在解决方案中创建一个安装和部署项目，这将创建一个安装应用程序，该应用程序将安装必要的组件以运行您的exe. 如果您查看Google，它将帮助您做到这一点:设置和设置带有水晶报表的部署项目 [ ^ ] SQL Server完全是另一个问题！您不应在安装中包括SQL Server.有两个原因: 0)您只能出于版权原因分发SQL Server Express-不能分发SQL Server完整版. 1)他们可能已经在网络上安装了SQL Server.如果是这样，那么他们大概会想使用该版本. 2)如果他们确实安装了SQL Server，并且您开始激增SQL Server Express实例，那么您将烦恼数据库管理员... 3)与在用户控制下的多个分散版本相比，备份SQl Server的单个站点的可能性要大得多. 4)对于普通"用户来说，安装和管理Sql Server非常复杂-这不是一个好主意！ 5)它将破坏使用SqlServer而不是SqlCE或SQLite的主要优势-多用户访问.如果每个人都安装了自己的SQL Server副本，那么您将拥有数据库的多个副本，每个副本都由一个人使用.这会引起一些混乱，并且(取决于您编写原始数据库的方式)可能会花费一些精力才能在遇到问题时将其合并到单个实例中. Converting to EXE is easy - it''s called a build is all, but you need to select "Release" on the menu bar where it says "Debug" at present. The other requirements are more problematic. You can''t necessarily just copy you exe file from one machine to another and expect it to work - there is a good chance it won''t. The best thing to do is to create a Setup and Deployment project as part of your Solution, and that will create a setup application which will install the necessary components to run your exe. If you have a look at Google it will help you to do that: Setup and Deployment project with crystal reports[^] SQL server is another problem altogether! You should not include SQL Server in your installation. There are a couple of reasons: 0) You can only distribute SQL Server Express for copyright reasons - not SQL Server full version. 1) They may already have SQL Server installed on the network. If so, then they will presumably want to use that version. 2) If they do have SQL server installed and you start proliferating SQL server Express instances, you are going to annoy the heck out of the database administrator... 3) A single site installation of SQl Server is a lot more likely to be backed up than a number of scattered version under user control. 4) Sql server is quite complex for a "normal" user to install and administer - it is not a good idea! 5) It will destroy the primary advantage of using Sql Server over SqlCE or SQLite - multiuser access. If everyone installs their own copy of SQL server, then you will have multiple copies of your database, each used by a single person. This will cause some confusion, and (depending on how you wrote the original database) may take some considerable effort to combine into a single instance when the problem is realized.