Executing C#.NET Managed Application

Yeah when you publish, normally it will goto somewhere remotely. This will enable features like if you update your program it can inform users that a new version is available and you can give them the option of downloading the newer version.

There is many more reasons for publishing but that is the first that came to mind. :)

sfx
 
The publish feature in .net 2005 is for "Click Once Deployment" which is, as said, for web deployment.

If you want to make a standard installation file you add a Deployment project to your solution and basically follow the wizard. You could also do that registry change at the end of the setup if you wanted.

How are you going to stop users doing ctrl-alt-delete > task manager > run > explorer.exe? Or even windows key + R? I'm sure it's possible, but thought i'd mention it incase you'd overlooked it.
 
Reezer said:
How are you going to stop users doing ctrl-alt-delete > task manager > run > explorer.exe? Or even windows key + R? I'm sure it's possible, but thought i'd mention it incase you'd overlooked it.
Click to expand...

We have already disabled Task Manager using Group Policy. I think Windows Key + R is an explorer shortcut thus if explorer.exe is not running then it won't run. I will add it to the testing document regardless just to be complete.

Initial testing seems positive, we are just working on a custom Group Policy to change the registry setting on workstation, once we have got that down to a tee I can package up the application as a MSI, deploy both .NET Framework 2.0 and the application to the workstations then apply the group policy as required.

Thanks again for everyones help.
 
You must log in or register to reply here.
Back
Top Bottom