Thursday, October 22, 2015

Different encoding systems for "Hello" example:

48 65 6C 6C 6F

Unicode (little-endian) encoding with no BOM.
48 00 65 00 6C 00 6C 00 6F 00

Unicode (little-endian) encoding with BOM
FF FE 48 00 65 00 6C 00 6C 00 6F 00

Unicode (big-endian) encoding with no BOM
00 48 00 65 00 6C 00 6C 00 6F

Unicode (big-endian) encoding with BOM
FE FF 00 48 00 65 00 6C 00 6C 00 6F

UTF-8 encoding
EF BB BF 48 65 6C 6C 6F

UTF-7 encoding
2B 2F 76 38 2D 48 65 6C 6C 6F


Friday, October 16, 2015

How to fix issue "The target GatherAllFilesToPublish does not exist"?

#1 Option:
Add following tag into project file:
  <Target Name="GatherAllFilesToPublish">
But will output all of source files into web site.

#2 Option:
<Import Project="$(VSToolsPath)\WebApplications\Microsoft.WebApplication.targets" Condition="false"/>
<Import Project="$(VSToolsPath)\WebApplications\Microsoft.WebApplication.targets" Condition="'$(VSToolsPath)' != ''" />


Wednesday, October 7, 2015


Excerpt from DDD book:

"The beauty of objects is their ability to encapsulate all that so that client code is simple and can be interpreted in terms of higher-level concepts.
But if the interface doesn’t tell the client developer what he needs to know in order to use the object effectively, he will have to dig into the internals and understand the details. A reader of the client code will have to do that same. Then most of the value of the encapsulation is lost. We are always fighting cognitive overload. If the client developer’s mind is flooded with detail about how a component does its job, his mind isn’t clear to work out the intricacies of the client design. This is true even when the same person is playing both roles, developing and using his own code, because even if he doesn’t have to learn those details, there is a limit to how many factors he can consider at once."

It is so true if working on a larger dev team.