Character encoding issues
June 26, 2007 | 4:20 pmCharacter encodings and the surrounding terminology can be quite tricky sometimes. I found this article, which is quite good:ä
A tutorial on character coding issues.
Character encodings and the surrounding terminology can be quite tricky sometimes. I found this article, which is quite good:ä
A tutorial on character coding issues.
I use the excellent plugin ReSharper in my Visual Studio 2005 when developing software. It adds a whole lot of refactorings, gives coding assistance, enables asp.net editing and much more. I also use Subversion for my version control with Tortoise as the version-control client. You can tell Subversion to ignore the files and cataloges that ReSharper produces by setting the global ignore pattern to:
*/_ReSharper* *resharper* _ReSharper*
If you use Tortoise as a version-control client you can enter the ignore pattern in the General Settings window.
I was trying to create a project in Visual Studio today and was warned that the path was too long. The path was 118 characters long and project/solution name was 24 characters long. I was a bit surprised, since OS (Windows XP) allows for 260 characters. I did some research and found out that Visual Studio counts like this: Path length + 1 (separator) + Solution name length + 1 (separator) + Project name length + 1 (separator) + Project name length + 80 (Reserved space). Project name length is added twice and Visual Studio wants a reserve of 80 characters at the end. In my case I ended up with: 118 + 1 + 24 + 1 + 24 + 1 + 24 + 80 = 273, which is well beyond the limit.
I am in the process of moving my mail and blog from my own server to a web hotel. In many ways it is nice to have your own server. You have full control and you can experiment. But sometimes it is a real pain. For example, when hardware breaks down and software fail and you want to spend your time with something else.
Recent Comments