Skip to main content

C# error at compile time challenge

Problem:
I have a challenge for you. You will find at the end of thispost a link to a zip that contains a .NET 4.0 projects. The challenge is tomake this project to compile and give me the cause of the problem. I will letyou until Friday morning.
Good luck.
https://skydrive.live.com/redir?resid=BB7D9F52E4FDB024!259&authkey=!APfTPi6HWX0VJQg


Solution:
In the ‘class’ word from the Foo class we had an odd character for Unicode world. The character named is ‘Zero with space’. Is like a space between words but without a visible space (width). Because Visual Studio can process also Unicode files, we have no limitation to add Unicode characters that are not visible using a normal editor. If we open the file with Total Commander viewer for example we will be able to see the character (in hex view for example).
Nice job :-)

Comments

  1. Hehe, simple one.

    When in doubt, retype the text. The problem is with the keyword "class". For example, if you put the cursor at the end of "class", and press CTRL+Left (that is, jump over one word), it will jump INSIDE the class, after the 'l' char.

    Looking at the source with a HEX Viewer we see:
    cl​ass . That is the ANSI representation. There is some UTF-8 garbage in there :)

    ReplyDelete
    Replies
    1. You are almost there. You need to tell me what is that character? What represents?

      Delete
    2. U+200B

      Unicode line break:
      http://www.fileformat.info/info/unicode/char/200b/index.htm

      Probably from some weird editor/another operating system

      Delete
    3. Nice - the file is UTF-16 encoded (big endian), that is ok.. Word has the habit to insert zero-width-spaces sometimes.. :)

      Delete
  2. I think that the file is encoded in ANSI and the "a" character in "class" is "â" which isn't a latin character. The ANSI encoded file permits to use characters from other alphabets not only latins character.

    ReplyDelete
  3. I added the solution to the post. Enjoy.

    ReplyDelete

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(...

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see...

Navigating Cloud Strategy after Azure Central US Region Outage

 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provi...