Click here to Skip to main content
15,906,569 members
Please Sign up or sign in to vote.
1.00/5 (1 vote)
hii guys..
i m trying to deploying an windows application developed in c# since last 30 days.
i build a setup project, add prerequistics (.NET framework, sqlserver etc), and as i begin to install this application on other computer following problems are faced:
1. first of all i've never seen any software which comes with these application (.NET framework, sqlserver etc), are they not developed in .NET???
2. as i start installing, first sql start installing itself and corrupted in the middle of the process. next, error is shown as " setup can not continue"
3.Next, What is simplest method to make an Exe of an windows form application?
Posted

1 solution

  1. You have never seen? Look harder. :-)
  2. Try to require SQL installation as prerequisite for your application. This is what's usually done.
  3. Incorrect question: EXE file is created by the build. There are no runnable projects without an executable file.
    Simplest method for installation? No installation. This method is also most encourages by Microsoft these days. Sometime this is referred as to "xcopy installation". The content of your output directory can be copied to any valid directory in a target computer and must work correctly immediately. As a user, I highly prefer this option of installation. It is provided by some best products, sometimes as an alternative to setup.exe if MSI.

—SA
 
Share this answer
 
v3
Comments
Richard MacCutchan 9-Nov-11 4:26am    
+5 for point 3; I thought I was the only one who thought it the best solution.
Sergey Alexandrovich Kryukov 9-Nov-11 10:10am    
Thank you, Richard.

Thank you for understanding. I have the same feeling. No, I knew people who understand the value of such approach, and this is really supported by Microsoft (since advent of .NET I think), but this idea acts like a "red cloth on a bull"; last time I explained this I got the vote of 1.

The problem is when the using of such application leaves a trace in the system which should be removed, so uninstallation is still needed, even though there is no installation. Last time I developed interesting system when each assembly implements some interface IUninstal and the universal uninstaller runs through all the assemblies, loads them and via Reflection tries to use the implementation of this interface. Another approach is self-uninstalling option in the application.

--SA

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900