Visual C++.NET 2003 and Broken Managed Assemblies
This is some really annoying bug in Visual Studio .NET 2003 (SP 1), took me two hours of my life: If the intermediate directory is set to something like ".obj/$(ConfigurationName)", the Assembly created will be broken, since it "does not contain a CLI header" - so the error message. It seems something is going completly wrong during compilation, since the dll is only 3 to 4 kB in size. If you omit the leading dot and set the intermediate directory to "obj/$(ConfigurationName)", it works.
Related Articles
- Using scriptaculous slider with two handles: ... similar to Macromedia Captivate or Producer for PowerPoint 2003. Check my blog entry for what I'm trying to do. Do you think this is ...
- Is C++ still needed?: ... and C#, the same as I did back when I was programming in Visual Basic 6. You may note however, that I'm doing this because I can. C++.NET managed code can be used by C# without any problems (Dude, I really love it). ...
- Comment Spam: I'm sick of it - Drupal Version: ... comment spam was dramatically reduced: Only one spam bot managed to bypass the catcha, posting around 1 comment spam a day. I wrote ...
- Yet another browser! Safari On Windows: ... Unfortunately, the current build seems terribly broken, as the following screenshot shows (Click to enlarge): ...
- Building A Better C++ String Class?: ... isn't highly efficient. Let's take a look at the Visual C++ implementation, for example. Doesn't it fullfill, what Preston ...