registration

Let's say I'm developing an application that installs COM component and installer registers them. This works great. Now the software is required to run from a memory stick. How can I register my libraries runtime and make sure, that the registry is cleaned up after running the application? Are you always running on XP or later? Don't bother. Use "registration free COM". Essentially what you do is create a manifest file for the COM component so the Windows loader know what its registration is without having to put that in the registry. A walkthrough of what to do is in this article on MSDN:

I have recently updated a Visual Basic 6 application that is an ActiveX exe, running on Windows XP. I have a couple of testers for this application who have received a copy of the exe and are attempting to run it. However, they are getting an error message "Unexpected error;quitting" when trying to do so. A key difference between their testing and my testing is that on the machines I tested on, I have admin rights and was able to register the application using the appname.exe /regserver command line. Reading the details at MS Support about file registration appears unclear: Visual Basic

A wiki I maintain has been hit pretty hard by spam bots... we don't have a lot of users, and I'd rather not saddle the legitimate users with captcha. Is there a simple way to make registration confirmation go to an admin? I've looked through the manual, and haven't been able to figure out how to do it. You could create a new user right, e.g. "approved", allow admins to assign that right and restrict things like editing to only approved users, like this: // Disallow editing and uploading from anons and registered users $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['user']['edit'

I am currently developing an ASP.NET MVC 4 app for the African market and was hoping to register a custom culture using the steps detailed in the following link http://msdn.microsoft.com/en-gb/library/system.globalization.cultureandregioninfobuilder.register(v=vs.110).aspx . Most of my target countries are not in the pre-installed cultures so it sounds like I need to register these cultures. Problem is, my console app for doing the registration will need admin previlidges to complete the culture registration. I am presuming windows azure does not allow developers admin control of the cloud

Situation I run a build system that executes many builds for many project. To avoid one build impacting another we lock down the build user to only its workspace. Builds run as a non privileged users who only have write ability to the workspace. Challenge During our new build we need to use a legacy 3rdparty DLL that exposes its interface through COM. The dev team wants to register the build(regsrv32.exe) but our build security regime blocks this activity. If we relax the regime then the 3rdparty DLL will impact other builds and if I have two build which need two different versions I may have

I'm creating a game currently and I want to limit one account per person. I have a lot of families that want to play and I can't think of a way to decipher families from cheaters. The way I'm planning on doing it currently is checking cookies and sessions to see if any are set on that computer if they are then I know someone has already played from that account. Than I will check their IP against the IP's I have stored in my database (I am storing the registration IP for each account as well as the last IP they logged in from). If they don't match any of those I than check the Email they have