Good point. However, the down side of recommending the OARX SDK assemblies is that I am assuming the developers downloaded and installed the right version of SDK. In fact, in my experience, I have found customers face unresolved assembly errors more with the sdk rather than acad install. This is because, it is more likely that users install acad at default location then the arx sdk. Another reason I did not emphasise the SDK was that it is not necessary for customers to install the SDK to do pure Acad .NET programming (though installing the SDK helps a great deal with samples and documentation). Finally, I wanted to keep the tutorial document as simple and clutter free as possible so that inexperienced programmers can get up and running as quickly as possible.
I guess there is no way to win here. As the next step to the the tutorial doc, I am planning to create a project template the developers can install on VB and C# express and use that to create skeletal AutoCAD .NET projects. The problem here too is the assumption of the location of the references.
However, I am interested in a typical scenario where you see the White Screen of Death. Can you think of a common scenario with the the acad assemblies? Or are you talking about unresolved assemblies too because of install into non-default path?
