This has been a long known issue with Firefox, and so far it doesn't seem like there is an answer, the error messages are:
"This application has failed to start because js3250.dll was not found. Re-installing the application may fix the problem."
"The Procedure entry point in JS_HasInstance could not be located in the dynamic link library js3250.dll"
some suggest uninstalling/reinstalling Firefox, creating a new profile, removing FF completely before reinstalling, downloading a new js3250.dll file, deleting a trojan file ipv6monl.dll, etc; some solutions work for some people, some work for others, here's what worked for me
In my case the problem only happened under a restricted (non-admin) user, I looked in the C:\Program Files\Mozilla Firefox folder and the js3250.dll file was there, so I ran the firefox.exe directly from there and it ran ok, then I replaced the shortcut I had to point to that location and it's working so far
hopefully this will help some other soul
Sunday, October 21, 2007
Wednesday, October 17, 2007
My predictions (about Leopard) for next week
- Apple will have their biggest software/hardware (MacPro, MacBookPro & Leopard) sale in history.
- There will be people camping out, waiting to be the first ones to get Leopard.
- They will run out of stock in a few stores.
- Adoption of Macs grows at least 25%.
- Very soon we'll start seeing problems (and updates) in a few applications.
- We'll also see quite a few (a lot?) security problems in the OS and applications for the rest of the year and there after actually
...and I hope to contribute to the cause! =0), and I know quite a few others in the blogosphere will too
- There will be people camping out, waiting to be the first ones to get Leopard.
- They will run out of stock in a few stores.
- Adoption of Macs grows at least 25%.
- Very soon we'll start seeing problems (and updates) in a few applications.
- We'll also see quite a few (a lot?) security problems in the OS and applications for the rest of the year and there after actually
...and I hope to contribute to the cause! =0), and I know quite a few others in the blogosphere will too
Labels:
Mac
Monday, October 15, 2007
small refactoring for working with nullable types
the article applies to: C# 2.0
C# 2.0 brought a new feature: nullable types, you already know they are cool and have been using them for a while, however, how many times have you seen (or written) something like:
//SomeClass.SomeObject.BoolProperty is of type bool?
if (SomeClass.SomeObject.BoolProperty.HasValue && SomeClass.SomeObject.BoolProperty.Value)...
//something
because you can't write:
if (SomeClass.SomeObject.BoolProperty)...
That will not compile
The problem I have with that code is that it is repetitive, and is long, so what can we do?
you can write this instead:
if (SomeClass.SomeObject.BoolProperty??false)
much better, isn't? if BoolProperty has a value and the value is true, it will return true, otherwise it will return false; now, of course you can use the same technique with other types:
string firstName;
public string FirstName { get{ return firstName??""; }}
this code would ensure that FirstName will never be null (I'm pretty sure you've seen lots of "object reference not set blablabla" because of this)
Other examples:
int? result;
...
return result??-1; //if result was not set, return -1
---------------------------------------------------
bool? result;
...
return result??false;
---------------------------------------------------
That's it, hope you find it useful
Remember that the best code, is no code at all
C# 2.0 brought a new feature: nullable types, you already know they are cool and have been using them for a while, however, how many times have you seen (or written) something like:
//SomeClass.SomeObject.BoolProperty is of type bool?
if (SomeClass.SomeObject.BoolProperty.HasValue && SomeClass.SomeObject.BoolProperty.Value)...
//something
because you can't write:
if (SomeClass.SomeObject.BoolProperty)...
That will not compile
The problem I have with that code is that it is repetitive, and is long, so what can we do?
you can write this instead:
if (SomeClass.SomeObject.BoolProperty??false)
much better, isn't? if BoolProperty has a value and the value is true, it will return true, otherwise it will return false; now, of course you can use the same technique with other types:
string firstName;
public string FirstName { get{ return firstName??""; }}
this code would ensure that FirstName will never be null (I'm pretty sure you've seen lots of "object reference not set blablabla" because of this)
Other examples:
int? result;
...
return result??-1; //if result was not set, return -1
---------------------------------------------------
bool? result;
...
return result??false;
---------------------------------------------------
That's it, hope you find it useful
Remember that the best code, is no code at all
Labels:
C#,
nullable-types
Subscribe to:
Posts (Atom)