Infralution Support

[extropy]

Just installed the evaluation.

Immediately after running Globalizer.NET a following error message appears:

Bootstrap error
An unhanded exception (Unauthorized Process Error (1)) occurred while bootstrapping the application.

Using Windows XP, 32bit, SP3.
Note that I have my system drive labeled as H: (not C.

[Infralution]

What version of Globalizer.NET have you installed?

You can check in the Control Panel Add/Remove Programs (the version is shown there). The current release is 2.3.1.

The only known reason for this error is if you try to debug Globalizer.NET (which of course you shouldn't be doing). There was an issue in versions earlier than 2.2.2 which could cause this error to occur when certain virus checkers were in use.
_________________
Infralution Support

[dbrillon]

I upgraded from 2.1 to 2.3.1 and now I'm not able to run the application. I reinstalled 2.1 and it work. We don't try to run the application in debug we just use it normally.

[Infralution]

Thanks for the info. I will email you a small diagnostic program to see if we can find out why 2.3.1 isn't working on your system.

Are you receiving exactly the same error?
What operating system are you using?
_________________
Infralution Support

[Infralution]

I think I have tracked down the source of the problem. It appears that you must have .NET profiling enabled globally. Check your System and User Environment variables (right click on MyComputer, select "Properties", select "Advanced" Tab, click "Environment Variables") . If you remove the COR_ENABLE_PROFILING variable then you should be able run Globalizer 2.3.1 without issues.

Alternatively if for some reason you actually do want to profile all .NET applications started on your machine then you can create a small batch file to run Globalizer.NET that removes this variable from the environment before running Globalizer. To do this create a file called "Globalizer.bat" with the contents:

[Infralution]

We have just released Version 2.3.2 of Globalizer.NET. It changes this behaviour somewhat. While you still cannot run Globalizer.NET with profiling enabled, it will now run if the COR_ENABLE_PROFILE environment variable is defined but set to any value other than "1". Setting this environment variable to one "1" enables global profiling and consequently means Globalizer.NET will not run. This change allows you (or the profiler) to set the variable to 0 when your are not profiling without affecting Globalizer.NET. The error message you receive if profiling is enabled has also been changed to be less cryptic.
_________________
Infralution Support