The overall idea of solution (workaround) is to do not use NAME with EMAILS. So both TO and FROM fields must be in form “TO: john@localhost.org” or “FROM: john@localhost.org” but not “TO: “John Doe” <john@localhost.org>”

I recently encountered this problem with osCommerce.

Solution to overcome this:

1. I added define to both includes\configure.php and admin\includes\configure.phpdefine(‘WIN32′, true);

2. Then in includes\classes\emails.php and admin\includes\classes\email.php in “send” function find this lines:$to = (($to_name != ”) ? ‘”‘ . $to_name . ‘” <’ . $to_addr . ‘>’ : $to_addr);
   $from = (($from_name != ”) ? ‘”‘ . $from_name . ‘” <’ . $from_addr . ‘>’ : $from_addr);

   and place following code BELOW them:

   //WIN32 FIX
   if (WIN32) {
   $from = $from_addr;
   $to = $to_addr;
   }

That’s all, and now I can test email sending on my local win maching. Good luck!

So the solution is: replace common spaces with non-breakable ones.

string s = ”ABCD EFGHI”;

string result = s.Replace(” “, (char) 0x00A0);

WebDev.WebServer check this internally in WebDev.WebHost.dll

List of protected dirs: “/bin”, “/app_browsers”, “/app_code”, “/app_data”, “/app_localresources”, “/app_globalresources”, “/app_webreferences”.

There is an easy fix for this with “yumagic”

Open terminal and run:

yum install php-gd

<table><tr><td style=”white-space: nowrap”>qwe-asd</td></tr></table>

And of course it works fine both in Opera and FireFox but not in IE7 (have not tested under IE6). The picture changes of course but some cells are still wrapping.

Workaround is to use template field with span:

<table><tr><td><span style=”white-space: nowrap”>qwe-asd</span></td></tr></table>

After performing such steps when you run Coverage from TestDriven.Net context menu, you can notice that there is coverage only for the test assembly.

Solution: Many chances you didn’t copy .pdb file for the .exe, but NCover can only profile assemblies which have .pdb files for them

MSDN says:

The string result from the HtmlAttributeEncode method should be used only for double-quoted attributes. Security issues might arise when using the HtmlAttributeEncode method with single-quoted attributes.

So you should use double quotes

From what I can read it from the docs it is really nice for small projects and allows you to live without creating large xml files for configuration and it also uses .NET 2.0+ DynamicMethods to improve object creation speed.

I am going to give it a shot!

The ?? operator returns the left-hand operand if it is not null, or else it returns the right operand.

Example:

string s = null;
int? i = null;
Console.WriteLine(s ?? "(null)");
Console.WriteLine(i ?? -1);

Will produce:

(null)
-1

http://spietrek.blogspot.com/