Need no setup...
-
How can write a program that dose not need any install or setup and all of dll or libreries be with program(for example only copy program in destination and progarm work)
-
How can write a program that dose not need any install or setup and all of dll or libreries be with program(for example only copy program in destination and progarm work)
You're gonna have to redistribute the .Net framework, largely because MS hasn't really pushed it to end-users yet. :mad: There is an app I downloaded a day or two ago that allowed you to take only the portions of the .Net framework that your app uses and bundle it inside your executable (along with any other dlls needed by your app). Can't remember the name of it offhand...maybe someone else knows it. The graveyards are filled with indispensible men.
-
How can write a program that dose not need any install or setup and all of dll or libreries be with program(for example only copy program in destination and progarm work)
Besides the .NET Framework (which MUST be installed), you can use touchless deployment by writing your application correctly, i.e. rely on .config files only (no registry). The application I architected runs both from local or LAN machines, or from across the Internet or an intranet with no change. The assembly binding uses the current codebase of the application plus any private paths your config files specifies (see the
<runtime>
section documentation in the .NET Framework SDK). You also need to worry about code access permissions, though. In .NET 1.0, the default Internet Zone allows no code to run. In .NET 1.1 some basic permissions are granted to code running from the Internet. You can change or add these code policies, though. There is plenty of documentation about code access security in the .NET SDK Documentation. Just look for "code access security". I'm also working on an extensive article or chain of articles but it'll be some time. It's important to read, though, because you really must understand them before using them. You don't want to open someone's machine to attach by accident, and you want to make your application work with different permissions granted, i.e. some are required and some are optional. Take a look at theSystem.Security.Permissions
namespace classes for more information about this stuff, as well as the documentation for code access security. If you don't need to run from a remote source, you don't necessarily have to worry about it (although it's still a good idea to check permissions in your app before executing an action that requires them, otherwise a SecurityException is thrown). Just use COPY/XCOPY to copy your apps and dlls to the local machine and make sure they are in the right place. You can leave all the exes and dlls together with no problem. You can use the application configuration file to specify additional paths, similar to what ASP.NET Web Matrix does.-----BEGIN GEEK CODE BLOCK----- Version: 3.21 GCS/G/MU d- s: a- C++++ UL@ P++(+++) L+(--) E--- W+++ N++ o+ K? w++++ O- M(+) V? PS-- PE Y++ PGP++ t++@ 5 X+++ R+@ tv+ b(-)>b++ DI++++ D+ G e++>+++ h---* r+++ y+++ -----END GEEK CODE BLOCK-----